I've just made a fresh install of slackware 10.2 in my old crappy computer:
Pentium 133MHz with 32 MB RAM
hda1 => swap, 64 MB
hda2 => reiserfs, 1GB
hdd => cdrom
I've installed slackware for two times (picking the packages through the menu driven option of the installation), the first I used ext2 filesystem, but that annoying error occurred (see below) and as it seemed to me that the filesystem was the guilty, I changed it to reiserfs. I was wrong, the same error is still here.
The only problem I had with the installation, came when writting lilo to the MBR (I can't, I can't), but it seemed to be written ok at the end. I used liloconf through the expert mode, and after all, executed lilo to apply changes.
The error occurs after rebooting for the first time the system, once the installation is finished. Before this point, the system seemed to run ok (the few things I could do).
Then, I rebooted the system. Lilo loads correctly but the following appears:
Checking root filesystem
/sbin/e2fsck: Is a directory while trying to open /
The superblock could not be read or does not describe the corrected ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or nfs or something else), then the superblock
is corrupted and you migth try e2fsck with an alternative superblock
e2fsck -b 8193 <device>
An error ocurred during the root filesystem check.
You will now be given a chance to log into
the filesystem in single-user mode to fix the problem
If you are using the ext2 filesystem, runnnig
'e2fsck -v -y <partition>' might help.
Once you exit the single-user shell, the system will reboot.
Type control-d to proceed with the normal startup,
(or give root password for system maintenance):
If I type my root password, I got access (single-user, as said) but also read-only, so it seems to me that I cannot change anything
I also noticed that my lilo.conf was modified, don't know how, don't know why, but now it's like the following:
#generated by lilo.conf
lba32 #Allow booting pasr 1024th cylinder with a recent BIOS
boot = (IN
message = /boot/boot-message.txt
timeout= = 1200
#Override dangerous defaults that rewrite the partition table:
#Normal VGA console
vga = normal
#End of Global section
#Linux bootable partition config begins
image = /boot/vmlinuz
root = (IN # should be /dev/hda2
label = Linux
read-only # should be read-write??
#Linux bootable partition config ends
Device problem? I don't think so, I've overwritten a DSL install and it seemed to run ok.
Any clue about what should be my next step?
I can always try a new installation, but it seems to me that this is not going to solve my problem.
what do you think, guys?
Thank you very much in advance!!