SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
''An error ocurred during the root file system check you will now be given the chance to log into the system in single user mode...
-----------------------------after i ran e2fsck -v -y /dev/hda :
'' The superblock could not be read or does not describe a correct ext2 filesystem.
If the device is valid and it contains on ext2 filesystem (and not swap or vfs or something else) , then the superblock is corrupt , and you might try running e2fsck with an alternate superblock :
The device /dev/hda is the entire hard disk. It is not a partition. Partitions would be indicated with numbers on the end.
Like the following:
/dev/hda1
/dev/hda2
/dev/hdb1
/dev/hdb2
The "a, b, c, d" are the drive designators and the numbers are the partitions in sequence on the drive. If you specified the incorrect partition during installation then the wrong entry was made in the /etc/fstab file and perhaps also in /etc/lilo.conf.
If you reboot the install CD and login, you can use "cfdisk /dev/hda" to view the drive and the partitions. It will also report the partition type and the boot partition. After the kernel boots you can use [shift][PgUp] to review the kernel messages. The kernel will report all hard disks that it is able to detect.
At this point I would recommend that you reinstall. A corrupted file system can be a source of very unusual problems.
i meant , that computer is still not working , the owner took it to a tech guy cause it was having problems for quite a while and i thought it was windows related , i guess not every computer problem is , right ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.