UFS FreeBSD 13.0 ufs no longer mounts rw, even after fsck

S

solvixnet

GENERIC kernel
no custom loader.conf values
Boot on 1 SATA
2 NVMe 2T drives on different controllers - both have same issue - 1 is heavily used, the other not as much.
Code: 
fsck_ufs -y /dev/nvd0a
mount /dev/nvd0a  /n0
mount: /dev/nvd0a: Operation not permitted

Info:
Code: 
 gpart show nvd0
=>         0  3907029168  nvd0  BSD  (1.8T)
           0  3898605568     1  freebsd-ufs  (1.8T)
  3898605568     8388608     2  freebsd-swap  (4.0G)
  3906994176       34992        - free -  (17M)

nvme0: <Generic NVMe Device> mem 0xf7c00000-0xf7c03fff irq 16 at device 0.0 on pci1
nvme1: <Generic NVMe Device> mem 0xf7b00000-0xf7b03fff irq 17 at device 0.0 on pci2
nvd0: <Samsung SSD 970 EVO Plus 2TB> NVMe namespace
nvd0: 1907729MB (3907029168 512 byte sectors)
nvd1: <Samsung SSD 970 EVO Plus 2TB> NVMe namespace
nvd1: 1907729MB (3907029168 512 byte sectors)
 
Somebody messed up when installing this system. You're not supposed to put the BSD label directly on the disk, that's a 'dangerously dedicated' installation.

Really old FAQ:
docs.freebsd.org

FreeBSD Documentation Portal

FreeBSD Documentation Portal
docs.freebsd.org docs.freebsd.org

So why it is called ``dangerous''? A disk in this mode doesn't contain what normal PC utilities would consider a valid fdisk table. Depending on how well they have been designed, they might complain at you once they are getting in contact with such a disk, or even worse, they might damage the BSD bootstrap without even asking or notifying you. In addition, the ``dangerously dedicated'' disk's layout is known to confuse many BIOSsen, including those from AWARD (eg. as found in HP Netserver and Micronics systems as well as many others) and Symbios/NCR (for the popular 53C8xx range of SCSI controllers). This isn't a complete list, there are more. Symptoms of this confusion include the "read error" message printed by the FreeBSD bootstrap when it can't find itself, as well as system lockups when booting.
Click to expand...
 
Yes. fsck is all good.
FYI
The other 2TB drive does have the "normal" partition config as noted by other comenter, but it is behaving the same. I can only mount readonly.
gpart status shows OK.
Interestingly though, there is some notice from gpart regarding CORRUPT something or other, but status reports OK.
 
solvixnet said:
Interestingly though, there is some notice from gpart regarding CORRUPT something or other, but status reports OK.
Click to expand...
Was it copied with dd(1) to a different disk? If the 'destination' disk is bigger than the source the partition info is missing at the end of the disk (there should be a backup copy). When the disk is bigger that copy isn't at the 'end' of the disk. Run gpart recover

Code: 
     recover       Recover a corrupt partition's scheme metadata on the geom
                   geom.  See the section entitled RECOVERING below for the
                   additional information.

                   The recover command accepts these options:

                   -f flags    Additional operational flags.  See the section
                               entitled OPERATIONAL FLAGS below for a
                               discussion about its use.

Also read the RECOVERING section in gpart(8).
 
You must log in or register to reply here.
Back
Top