ALIX.2 v0.99h 4GB CF GEOM: ad0s1: media size does not macht label.



  • Try to upgrade a ALIX.2 from pfSense 2.1.4 to 2.2 (nanobsd i386 4g) with no success.
    Autoupdate and manual firmware upload print "GEOM: ad0s1: media size does not macht label." on the serial console,
    after restart it's pfSense 2.1.4 again.

    Any idea?

    Can I reflash with 2.2 and restore the backup from 2.1.4?


  • Netgate Administrator

    @slu:

    Can I reflash with 2.2 and restore the backup from 2.1.4?

    Yes, though I recommend you use a different CF card so you have the original as a fall-back option.

    Steve



  • Flash and restore backup work.  ;)

    My both ALIX has the same issue, when I connect the CF card to my Debian Linux workstation dmesg show:

    [13418.743359] sd 7:0:0:0: [sdb] 7806960 512-byte logical blocks: (3.99 GB/3.72 GiB)
    [13418.746726] sd 7:0:0:0: [sdb] Write Protect is off
    [13418.746730] sd 7:0:0:0: [sdb] Mode Sense: 03 00 00 00
    [13418.749844] sd 7:0:0:0: [sdb] No Caching mode page found
    [13418.749853] sd 7:0:0:0: [sdb] Assuming drive cache: write through
    [13418.757978] sd 7:0:0:3: [sde] Attached SCSI removable disk
    [13418.759227] sd 7:0:0:1: [sdc] Attached SCSI removable disk
    [13418.776967]  sdb: sdb1 sdb2 sdb3
     sdb1: <bsd:>
     sdb2: <bsd:>
    [13418.777129] sdb: p3 size 102816 extends beyond EOD, enabling native capacity
    [13418.798462]  sdb: sdb1 sdb2 sdb3
     sdb1: <bsd:>
     sdb2: <bsd:>
    [13418.798612] sdb: p3 size 102816 extends beyond EOD, truncated
    [13418.805474] sd 7:0:0:0: [sdb] Attached SCSI removable disk
    [13419.141739] ufs was compiled with read-only support, can't be mounted as read-write
    [13419.142099] You didn't specify the type of your ufs filesystem
    
    mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
    
    >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
    [13419.149305] UFS-fs error (device sdb3): ufs_check_page: bad entry in directory #2: rec_len is too small for name_len - offset=0, rec_len=12, name_len=260
    [13419.149322] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149384] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149429] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149471] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149513] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149555] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149595] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149636] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149683] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149722] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149766] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149800] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149833] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149864] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149894] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149923] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149953] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.149986] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.150021] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.150067] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.150119] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.150164] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.155659] UFS-fs error (device sdb3): ufs_readdir: bad page in #2
    [13419.174185] UFS-fs error (device sdb3): ufs_readdir: bad page in #2</bsd:></bsd:></bsd:></bsd:>
    

  • Netgate Administrator

    Hmm, I believe the correct type is ufs2. However the fact that it seems to be reporting a filesystem that's bigger than the drive isn't good. Re-flashing and restoring the config was the way to go.  :)

    Steve


Log in to reply