Error loading Slack 10.1

carlosinfl · 02-25-2005, 08:57 PM

Just installed SLACK 10.1

An error occured during the root filesystem check.
You will now be given a chance to log into the system in a single user mode to fix the problem

If you're using ext2, filesystem, running e2fsck -v -y <partition>' might help

This happened right after I finished the slack install on my notebook and I have no idea what to do or how to fix something of this nature.

I am not logged in as root in a terminal window

root@(none):/#

Thanks for any help.

killerbob · 02-25-2005, 09:18 PM

You're right, it isn't a terminal window. It's a terminal.

What filesystem did you use at install time? Was it ext2 or ext3? As far as I understand it, you will never see that error with ReiserFS.

in any event, what you need to do is run e2fsck or e3fsck (depending on your filesystem) on /dev/hda1. Usually, you're supposed to do this without it being mounted, so you might want to boot off the install disc and do it from there.

You could also try the windows fix: reboot and see if the problem is still there.

carlosinfl · 02-25-2005, 09:33 PM

I used ext3 if I recall.

I booted from disk and I am at root@slackware:/#

Code:

root@slackware:/#  e3fsck /dev/hda1
e3fsck: No such file or directory

I rebooted many times and it seems to read the same error over and over so I assume something is rotten in denmark. Is there a command that will show me all my partitions and if they are ext2 or 3?

killerbob · 02-25-2005, 09:38 PM

Hmm... ok. Use "fsck -t ext3" instead of e3fsck. That's probably just a link I've made on my own system.

Also, /dev/hda1 might not be the right partition. Type "fdisk -l" to display the partition tables and be sure.

carlosinfl · 02-25-2005, 09:41 PM

I don't know if this helps but when I was in terminal and typed:

Code:

root@slackware:/# df <enter>
Filesystem    1k-blocks    Used Available   Use% Mounted On
/dev/fd2            6340      5947           70    99%    /

...and that is all I see!!!??? Should I not see any more partitions?

carlosinfl · 02-25-2005, 09:44 PM

Quote:

Originally posted by killerbob
Also, /dev/hda1 might not be the right partition. Type "fdisk -l" to display the partition tables and be sure.

Device Boot Start End Blocks ID System

/dev/hda1 1 6000 48194999+ 83 Linux
/dev/hda2 6001 7296 10410120 82 Linux swap

carlosinfl · 02-25-2005, 09:49 PM

Code:

fsck -t ext3 /dev/hda1
The filesystem size according to the superblock is 14651279 blocks
The physical size of the device is 12048749 blocks
Either the superblock or the partition table is likely to be corupt!
Abort<y>?

killerbob · 02-26-2005, 07:27 AM

Hmm... yeah, I'd abort at that point. Looks like your partition table is borked. If you had a windows bootdisk, I'd suggest running "fdisk /mbr", but unfortunately I don't think the unix version of fdisk supports that.

I know you can do the same with "lilo -m", but I'm not 100% sure it'll fix the problem. Doesn't hurt to try.

You might also try loading up cfdisk and then writing the partition table and quitting. That might also solve the problem.

Anti-virus control is turned off in the BIOS, right? If it's on, it can screw up c/fdisk and prevent them from being able to write the partition table.

Failing that, since you've just installed the system, you can also use cfdisk from the install CD to wipe out the partitions again, and reinstall. If you go that route, I'd suggest 10gb for /, 512mb for swap, and the rest of the hard drive for /home. cfdisk has a graphical user interface which can make the creation/deletion of partitions pretty easy. As much as I loathe the "Windows" solution, that might actually be your best bet.