UFS FSCK question

[dr_grid]

Greetings all,
Forgive me for asking what may be a stupid question. I recently moved a system which is known to have some flaky SATA cables. Upon
rebooting in the new location I did get some disk errors associated with a ZFS scrub ( a different story ).

Inspected cables, made sure they were well seated. Rebooted and failed FSCK on my non-ZFS disks. Rebooted single user mode with the
intent to fsck all the disks. What I have never seen before when running FSCK is the following first line:

** /dev/ada1p2 (NO WRITE)

Of course, if it is NO WRITE, fsck cannot correct any errors. I have never seen the NO WRITE note.

What is up with that message, and how do I finally clean up fsck errors on these drive?

Thanks for any help.

 

[Tieks]

** /dev/ada1p2 (NO WRITE)

This means that the file system on device ada1p2 is already mounted for read and write operations. Command mount will show you. Unmount it first, then start fsck.

 

[SirDice]

Yep, fsck(8) can only fix issues if the filesystem is unmounted, or at most mounted read-only. That should be the case if you booted to single user mode though, unless you mounted it yourself before doing the fsck(8). You might be, incorrectly, assuming it has to be mounted?