On Sunday 18 Dec 2016 19:39:36 Alarig Le Lay wrote: > On Sun Dec 18 19:35:43 2016, Alarig Le Lay wrote: > > On Sun Dec 18 18:23:22 2016, Mick wrote: > > > Another thing to try is unmount it, run fsck and then remount it as rw. > > > A > > > dirty unmount can cause this problem. > > > > It was dirty unmounted. This a flash card that is a / for a router at > > home. Its power supply suddenly stopped to work today. > > I will try this, thanks :) > > Well done, an fsck fixed the problem :) > > airmure # umount /dev/sdg2 > airmure # fsck.ufs /dev/sdg2 > ** /dev/sdg2 > ** Last Mounted on / > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > FREE BLK COUNT(S) WRONG IN SUPERBLK > SALVAGE? [yn] y > SALVAGE? [yn] y > > SUMMARY INFORMATION BAD > SALVAGE? [yn] y > > BLK(S) MISSING IN BIT MAPS > SALVAGE? [yn] y > > 17039 files, 176220 used, 1617195 free (371 frags, 202103 blocks, 0.0% > fragmentation) > > ***** FILE SYSTEM MARKED CLEAN ***** > > ***** FILE SYSTEM WAS MODIFIED ***** > airmure # mount -t ufs -o ufstype=ufs2,rw /dev/sdg2 /mnt/drscott > airmure # mount | grep drscott > /dev/sdg2 on /mnt/drscott type ufs > (rw,relatime,ufstype=ufs2,onerror=lock)
Glad you sorted this out. I've been bitten by this problem once or twice. It is a right pain when you are running an OS upgrade and haven't checked first if your fs is *still* mounted as rw. The solution is to get a UPS for this device. Hmm ... one more thing to go on Santa's list. ;-) -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
