Pfsense kernel: GEOM: da0s2: geometry does not match label (16h,63s != 255h,63s)



  • So, I'm trying to mount a nanoBSD CF card on a pfSense system running the full version, to edit the configuration.

    Upon inserting the CF card into an USB card reader attached to the system running pfSense, I get these messages:

    Apr  4 07:19:05 pfsense kernel: ugen3.2: <vendor 0x05e3="">at usbus3
    Apr  4 07:19:05 pfsense kernel: umass0: <vendor 0="" 2="" 0x05e3="" usb="" storage,="" class="" 0,="" rev="" 2.00="" 91.44,="" addr="">on usbus3
    Apr  4 07:19:05 pfsense kernel: umass0:  SCSI over Bulk-Only; quirks = 0x0000
    Apr  4 07:19:06 pfsense kernel: umass0:0:0:-1: Attached to scbus0
    Apr  4 07:19:07 pfsense kernel: da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
    Apr  4 07:19:07 pfsense kernel: da0: <generic 9144="" storage="" device="">Removable Direct Access SCSI-0 device 
    Apr  4 07:19:07 pfsense kernel: da0: 40.000MB/s transfers
    Apr  4 07:19:07 pfsense kernel: da0: 3908MB (8005536 512 byte sectors: 255H 63S/T 498C)
    Apr  4 07:19:07 pfsense kernel: (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0 
    Apr  4 07:19:07 pfsense kernel: (probe0:umass-sim0:0:0:1): CAM status: SCSI Status Error
    Apr  4 07:19:07 pfsense kernel: (probe0:umass-sim0:0:0:1): SCSI status: Check Condition
    Apr  4 07:19:07 pfsense kernel: (probe0:umass-sim0:0:0:1): SCSI sense: NOT READY asc:3a,0 (Medium not present)
    Apr  4 07:19:07 pfsense kernel: da1 at umass-sim0 bus 0 scbus0 target 0 lun 1
    Apr  4 07:19:07 pfsense kernel: da1: <generic 9144="" storage="" device="">Removable Direct Access SCSI-0 device 
    Apr  4 07:19:07 pfsense kernel: da1: 40.000MB/s transfers
    Apr  4 07:19:07 pfsense kernel: da1: Attempt to query device size failed: NOT READY, Medium not present
    Apr  4 07:19:08 pfsense kernel: (probe0:umass-sim0:0:0:2): TEST UNIT READY. CDB: 0 40 0 0 0 0 
    Apr  4 07:19:08 pfsense kernel: (probe0:umass-sim0:0:0:2): CAM status: SCSI Status Error
    Apr  4 07:19:08 pfsense kernel: (probe0:umass-sim0:0:0:2): SCSI status: Check Condition
    Apr  4 07:19:08 pfsense kernel: (probe0:umass-sim0:0:0:2): SCSI sense: NOT READY asc:3a,0 (Medium not present)
    Apr  4 07:19:08 pfsense kernel: da2 at umass-sim0 bus 0 scbus0 target 0 lun 2
    Apr  4 07:19:08 pfsense kernel: da2: <generic 9144="" storage="" device="">Removable Direct Access SCSI-0 device 
    Apr  4 07:19:08 pfsense kernel: da2: 40.000MB/s transfers
    Apr  4 07:19:08 pfsense kernel: da2: Attempt to query device size failed: NOT READY, Medium not present
    Apr  4 07:19:08 pfsense kernel: (probe0:umass-sim0:0:0:3): TEST UNIT READY. CDB: 0 60 0 0 0 0 
    Apr  4 07:19:08 pfsense kernel: (probe0:umass-sim0:0:0:3): CAM status: SCSI Status Error
    Apr  4 07:19:08 pfsense kernel: (probe0:umass-sim0:0:0:3): SCSI status: Check Condition
    Apr  4 07:19:08 pfsense kernel: (probe0:umass-sim0:0:0:3): SCSI sense: NOT READY asc:3a,0 (Medium not present)
    Apr  4 07:19:08 pfsense kernel: da3 at umass-sim0 bus 0 scbus0 target 0 lun 3
    Apr  4 07:19:08 pfsense kernel: da3: <generic 9144="" storage="" device="">Removable Direct Access SCSI-0 device 
    Apr  4 07:19:08 pfsense kernel: da3: 40.000MB/s transfers
    Apr  4 07:19:08 pfsense kernel: da3: Attempt to query device size failed: NOT READY, Medium not present
    Apr  4 07:19:08 pfsense kernel: GEOM: da0s1: geometry does not match label (16h,63s != 255h,63s).
    Apr  4 07:19:08 pfsense kernel: GEOM: da0s2: geometry does not match label (16h,63s != 255h,63s).</generic></generic></generic></generic></vendor></vendor> 
    

    The messages about da1 to da3 can be ignored, they are simply slots for different types of flash memory. da0 is the CF slot. There it complains about messed up disk geometry.
    This is a 4GB CF card, which was just prior to written on Mac OS X with this command:

    
    root# dd bs=16384 if=~/Downloads/pfSense/amd64/pfSense-2.0-RC1-4g-amd64-20110402-0204-nanobsd.img of=/dev/rdisk11
    244615+1 records in
    244615+1 records out
    4007775744 bytes transferred in 335.319037 secs (11952127 bytes/sec)
    
    

    Am I doing something wrong writing the disk image (problem between chair and screen) or is there an issue with the disk image, or is there something else I'm forgetting?



  • The img file is gzipped, so you need to decompress it before writing it with dd



  • rcfa: Not sure if it helps you any but on my one board I had to manually set it to LBA because it would not boot with Auto.
    (I realize there are no BIOS settings for a USB flash reader.. Just pointing out that there could be something funny going on between translations either in the image itself, device/computer it was written with and/or device/computer reading it.)
    Btw I wrote my 4GB card with 1GB image in Win7 using USB card reader & had placed the CF card in CF->IDE adapter.
    Bill



  • @clarknova:

    The img file is gzipped, so you need to decompress it before writing it with dd

    Uhm, I did that ;)
    Check the number of bytes written by dd, they would be lower had I not decompressed first.



  • @Bill48105:

    rcfa: Not sure if it helps you any but on my one board I had to manually set it to LBA because it would not boot with Auto.
    (I realize there are no BIOS settings for a USB flash reader.. Just pointing out that there could be something funny going on between translations either in the image itself, device/computer it was written with and/or device/computer reading it.)
    Btw I wrote my 4GB card with 1GB image in Win7 using USB card reader & had placed the CF card in CF->IDE adapter.

    Hm, in both cases the card is hooked up to the computer by means of a card reader.
    The computer writing is running Mac OS X 10.6.7, the one reading, of course, is pfSense 2.0-RC1

    Unfortunately, Mac OS X doesn't support the BSD disk layout and file systems, so I'm not sure if the OS tries to "repair" the disk somehow as it's written/unmounted.
    Maybe there are also somewhere old partition tables past the end of the written disk image that pfSense picks up on. I'll have to try to force-null the entire CF card somehow to see if that helps.



  • I'm starting to feel stupid.
    So I got another CF card, because the CF card in question was one of these old ones one could switch between 2 different 2GB devices and a 4GB device (for older cameras that can't handle 4GB). So I now have a "modern" 8GB CF card, too.
    I also put the image file on a 8GB USB stick. And I used two different USB CF card interfaces.
    And I wrote the image now no longer with OS X, but directly from a working pfSense box, reading the image from the USB stick and dd-ing it to the daN device.

    Result: still the same!

    Is there anything that prevents an image properly being read/written from/to a USB CF card interface?
    Or are there any assumptions I'm not aware of, like the CF card has to be formatted first in some way, and the image is not dumped onto the device, but into some partition?

    I mean, this should be simple, dumping a disk image with dd onto a CF card, but I can't get it to work. :(



  • Indeed, this is an issue with USB readers!

    I finally hooked up the same CF card with a CF-SATA converter and connected it to the SATA port => no problem mounting the disk!

    Interestingly enough, though, these are USB readers that allowed me to boot Mac OS X from. So is there an issue with FreeBSD and USB devices? (Note: I didn't even try to boot, just to mount the file systems!)

    Clearly it would be helpful if one could access a flash memory card from a USB reader, but for some reason that doesn't seem to work…
    ...so while I now can access the CF card in a roundabout way, it's still puzzling that two different readers resulted in the exact same result.



  • Another datapoint…

    I too am getting this "geometry does not match label" error. But in my situation, I'm using an Intel (D945GSEJT) motherboard, with specifically supported USB SSD (2GB Intel Z-U130 Value SSD). I'm attempting to use pfSense-memstick-2.0-RC3-i386-20110621-1650.img.gz

    Specifically, whenever this SSD module is connected, wether booting from it or another disk (always booting from a disk containing the above IMG), this error is reported for the SSD disk. So, I'll add that this issue seems to be merely related to flash-based USB devices?

    When attempting to install onto the SSD, the Installer gets to the point where it tries to run…

    ,-<<< Executing ‘/sbin/fdisk -v -f /tmp/new.fdisk da1’
    | ******* Working on device /dev/da1 *******
    | parameters extracted from in-core disklabel are:
    | cylinders=250 heads=255 sectors/track=63 (16065 blks/cyl)
    |
    | parameters to be used for BIOS calculations are:
    | cylinders=250 heads=255 sectors/track=63 (16065 blks/cyl)
    |
    | Information from DOS bootblock is:
    | 1: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
    | start 63, size 4016187 (1961 Meg), flag 80 (active)
    | beg: cyl 0/ head 1/ sector 1;
    | end: cyl 249/ head 254/ sector 63
    | 2: <unused>| 3: <unused>| 4: <unused>| fdisk: Class not found
    ‘->>> Exit status: 0

    … the next command /sbin/fdisk da1 runs fine, it's just gathering "the now current" state of the target disk. But what follows does fail:

    ,-<<< Executing ‘/sbin/bsdlabel -B -r -w da1s1 auto’
    | bsdlabel: unable to get correct path for da1s1: No such file or directory
    ‘->>> Exit status: 1

    At this point, the Installer stops & offers reading the installer log.

    For perspective, I'm not terribly familiar with getting around in BSD, but have been happily using pfSense for years. I'm now in the process of building a new router platform (as described above) and would love to not need to use a literal USB flash/other drive, nor some sort of ata hard drive. This motherboard, with the Z-U130 SSD module is beautifully low power.</unused></unused></unused>



  • Sorry to hear about your problems, however, glad that I'm not the only one having it.
    Maybe that way some data can be gathered, and this issue can be eliminated.

    Ronald



  • same message here on a 4gb usb stick.

    i cannot do an upgrade either, something about drive size mismatch.

    are these 2 problems related?



  • Hi,
    get the same problem by installation from a USB Stick on a HDD. Tried out with SATA and ATA, result the same.
    What can be cause this problem?
    The installation from CD works also not, I get not the GEOM error but the installation fails, becuase the installer cennot find anymore the HDD.
    Other OS installation works without any problems.
    I found out that in the bootblock menu I see ad0 (my Harddrive) and da0 (the USB Stick), both have the flag to install bootblock.

    PD


Locked