Computers |
|
| | #1 (permalink) |
| Member (again) | Whenever you bring up my dad's computer in Linux (SuSe 9.1), it boots about halfway and then i get the message: Code: fsck failed. Please manually repair and reboot. Any suggestions??? Thanks! |
| | |
| | #4 (permalink) |
| Member (again) | OK, I booted off a Knoppix CD and ran fsck, and there were no problems. Started SUSE again and it did the same thing. It's not a new install, and the only thing I did before it stopped working was to add a modem. I took it out but the comp still didn't work. The filesystem is ext2. One thing I just realized though; this thing used to have about 300 meg of swap space that has just dissappeared for some reason. Could this cause fsck to whack out?? |
| | |
| | #6 (permalink) |
| Master Techie Join Date: Apr 2004
Posts: 2,532
| If youve got a boot floppy made from when you installed Suse Id use that and boot up and run all the fsck options you can to fix it, doing it with knoppix or anything else probably doesnt change the log file and fsck flag Suse is seeing when it boots.........or you can erase the fsck flag and see what happens, if you can find it. When the filesystem screws up a flag is generated, but the ext2 filesystem doesnt keep a journal like ext3 or reiserFS so rebuilding the filesystem tree isnt very foolproof. |
| | |