Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
mdadm --create --level 1 -n2 /dev/md1 /dev/hda2 /dev/hdb2
(both hda2 & hdb2 have ext3 fs on them)
This works fine, eventually copies over everything and /proc/mdstat finds the array. This is going to be mounted as root.
Then, as I did for the /boot partition (which seems to mount fine), I did:
fsck -f /dev/md1
and it eventually finished. Then according to the HOWTO, I ran:
to get the superblock to say the right thing for raid. Everything fine so far, I can mount /dev/md1 no problem (running rescue).
I change lilo.conf to have:
and chroot/lilo, and it tells me it's updating two disks (correct).
But when I reboot, it fails the fsck, complaining about wrong superblock info! This didn't happen with /boot (/dev/md0). I can't figure it out.
Yes, both hda2 and hdb2 (and hda1/hdb1, the /boot partitions) are set to 'fd' in fdisk. They get detected at boot, but the fsck just fails.
Being a Newb myself I can only throw a guess, But I think i remember reading something about the /boot partition not being able to accept a RAID, I set my /boot to /dev/hda1 and on /dev/hdb1 I backup the Kernel info. The other partitions are set up with a RAID1 but the superblock is a special sector (I think, and could very well be wrong) and won't sync with the RAID. The fsck fails because of the inconsistancy between the two parititons super/lack of superblock diff.
Hey, I am having the same problem myself. Its very irritating. Hope someone has an answer. I followed the HOWTO on tldp.org and its just a mess. Tried it like 5 times with some slight variations. If anyone is running a completely mirrored system drive on FC3 please help...
where .... is 2.6.9-1.667 in my case. This I learned *after* having copied the whole system to a spare drive, which I think I wouldn't have needed to do if I had tried this in the first place (could have just done as the rest of the HOWTO says and it would automatically mirror my existing disk over to disk2).
Don't forget to run lilo (I don't use grub) after you make the new initrd if you're a lilo user.