You are not logged in.
First the story:
I tried to set up pm-utils on my Desktop and ran pm-hibernate. This didn't work; the screen flashed black for a second and I saw the Desktop again. Then I tried pm-suspend, which worked well.
I thought about rebooting, did it, and when the OS was shutting down I got an error stating something about the EXT3 Filesystem, which I couldn't remember.
Now when I am trying to boot into Arch I get the following when the filesystems are checked:
/dev/sda1/ contains a file system with errors, check forced.
Invalid inode number for ' .' in directory inode 897913.
Afterwards I am being told to repair that manually and that therefore the root filesystems is mounted read-only.
How can I fix this? This is rather urgent because I need to work with that system.
Offline
Boot to another OS and fsck sda1.
Offline
Yeah, that's what I am doing rite now... I have booted the Arch live CD, ran fsck and had it correct the erros (like 15 different blocks).
Now it's booting.......
/dev/sda1 has gone 49710 days without being checked, check forced.
Hahaha...
There seem to be no errors... Now it has deteced some non-contiguous blocks....
Rebooting again.....
Shit... Now I am having problems with sda3...
Duplicate or bad block in use!
/dev/sda3: Multiply-claimed block(s) in inode xxx:xxx (random inodes here)
Ah, this is not good ...
EDIT: I gonna boot into my LiveArch again and have it run fsck again... and then save my data.
Last edited by Stalafin (2008-03-01 21:46:28)
Offline