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.
I get back from the Ohio LinuxFest last night to find my home server unresponsive. I hard reboot the machine, and upon boot up it attempts to check the root filesystem (hda1), with reiserfsck. When it does this, reiserfsck immediately errors out, saying that it cannot find /dev/hda1.
I then boot my system with SystemRescue CD, and I can mount all of my drives easily, with no issues. I've chrooted into hda1 with no issues. The root directory structure is there, and intact. I exit chroot, unmount hda1, and manually ran reiserfsck with and without the --rebuild-tree option. All checks out perfectly.
But when I boot into my normal slackware installation, it still gives me the reiserfsck error (saying "hda1, no such file or directory), and prompts me for superuser maintenance login. I've tried four different known working kernels.
I've gone so far as chroot into my installation and edit /etc/rc.d/rc.S to remove the FORCEFSK variable checking. No luck.
Of course, I literally have three papers due in the next three days, one is nearly done (and solely stored on this server), and I haven't started the other two.
So, I need desperate help, thy Community. Google has failed me.
I'm not sure on the HDD age, but it can't be more than a year or so. It's not making any whirring, nor clicking sounds.
I've tried my default kernel (2.6.17.8) that I've used since that version of the kernel was released, along with other known working kernels that I've used in the past, down to 2.6.12.
Again, I can access the drive just fine via a Live CD, but reiserfsck is killing the boot process.
I'm not sure on the HDD age, but it can't be more than a year or so. It's not making any whirring, nor clicking sounds.
I've tried my default kernel (2.6.17.8) that I've used since that version of the kernel was released, along with other known working kernels that I've used in the past, down to 2.6.12.
Again, I can access the drive just fine via a Live CD, but reiserfsck is killing the boot process.
Hi,
Try booting your system as single user mode then do your reiserfsck.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.