Red HatThis forum is for the discussion of Red Hat Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
in a nutshell... after a motherboard upgrade, boot drive is on a different drive letter and doesn't get past fsk.
i have upgraded my server from an ABIT BP6 to an ASUS CUV4XD. in doing this, the CentOS 4.2 boot drive is now on /dev/hda instead of /dev/hde. when it boots, it gets past the first part, then starts running the rc3 scripts.
Setting hostname kaneda [ OK ]
Checking root filesystem
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
No such file or directory while trying to open /dev/hde4 [FAILED]
the last line shows it is trying to fsk the partition in it's old drive, hde, when it is now hda.
i have modified grub.conf and devices.map in /boot/grub, as well as changing the labels in fstab to all point to /dev/hda...
it seems that i am missing something simple that is causing the fsk to look in the wrong place. any ideas??
WHY? the BP6 has 2x ATA33 and 2x ATA66 drive connectors, while the CUV4XD only has 2x ATA100. the hard drive was originally on the third (but first ATA66) connector as the master (/dev/hde). now it is on the first connector as primary master (/dev/hda).