[Bug 264450] ufs: Partition recognized on 12.3 not recognized on CURRENT (2573e6ced996): Cannot find file system superblock .. Invalid fstype: Invalid argument

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264450

Dennis <dn@arbor.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dn@arbor.de

--- Comment #19 from Dennis <dn@arbor.de> ---

I stumbled across this problem after a system update from 12.3-STABLE (pfsense
2.6.0) to 14.0-CURRENT (pfsense 2.7.0).
After that the systems cannot mount the root ufs anymore and will not boot.

-----------------------------------

UFS2 superblock failed: CGSIZE(fs) (16388) > fs->fs_bsize (16384)
Attempted recovery for standard superblock: failed
Attempted extraction of recovery data from standard superblock: failed
Attemp to find boot zone recovery data
Finding an alternate superblock failed.
Check for only non-critical errors in standard superblock
UFS2 superblock failed: CGSIZE(fs) (16388) > fs->fs_bsize (16384)
Failed, superblock has critical errors
Mounting from ufs:/dev/da0s1a failed with error 22; retrying for 3 more seconds
[repeating]

-----------------------------------

I have a few identical virtual systems of this kind. So I can reproduce this
problem on multiple machines.
They were set up from a common image some years ago, underwent several
sucessfull updates since then and worked flawlessly up till 12.3-STABLE.

I'm not sure whether the above fix is already in 14.0-CURRENT (pfsense 2.7.0)?
Apparently I have a difference of 4 in the blocksizes.

When I look at dumpfs before the update (on 12.3), bsize and cgsize match:

-----------------------------------
#dumpfs da0s1a | grep bsize
bsize   16384   shift   14      mask    0xffffc000
maxbsize 16384  maxbpg  2048    maxcontig 8     contigsumsize 8
sbsize  2048    cgsize  16384   csaddr  3000    cssize  4096
-----------------------------------

So 14.0 is calculating this differently?

Can this be corrected somehow without reformatting the drives?
These systems are remote, so this is problematic for me.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.