problems with fsck
I'm trying to execute a fsck (e2fsck) on my system. Though I boot into single-user mode I'm not able to umount my /dev/sda1 root filesystem. Of course I can't run a fsck on my root partition (/dev/sda1 with / as mountpoint) without my root filesystem being unmounted.
When I try (in single-user mode of course) to run umount /dev/sda1 I get "device is busy". After I ran fuser -km /dev/sda1 my system doesn't give any error when I execute umount -l /dev/sda/1. Unfortunately, I don't notice any difference when I execute mount. When I try to fsck my /dev/sda1 I see a warning that contains: Quote:
|
Quote:
If you cannot get / mounted in read only mode then I suggest that you use a live CD to run fsck. --------------------- Steve Stites |
Use mount with "remount,rw" as options - no umount.
|
syg00, don't you mean
mount /dev/sda1 / -oremount,ro |
Nope - the OP wants to fsck root - needs (should) be rw.
This works fine BTW - been there, done that. Of course, fsck can trash files whilst doing it's job; that applies equally with root. Problem is (with root) you can wind up with a dead system. That is the OPs choice - presumably s/he has read my sigline. |
Thanks for the clarification syg00. Nice sigline by the way, my own is inspired by yours.
|
Quote:
Quote:
mount -o remount,ro / didn't make any difference. I'm starting to believe it should be mounted as rw, though this sounds very dangerous to me. I executed touch /forcefsck in /root and after I rebooted I have removed it. |
Quote:
-------------------- Steve Stites |
All times are GMT -5. The time now is 02:31 AM. |