Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
Being a raid 1 this means the drives are mirrored. So data is written to both drives identically. So if software issue both have the same issue unless one drive fails but the data is still written to the other and keeps going.
Now what might help is explain in detail the issue you are having and when it happens during the boot process.
Do you have true hardware RAID (through a raid card), or was this just 2 drives plugged into a motherboard, which is software RAID?
The simple solution would be to stick a live CD/DVD in (knoppix for example), and see if all of your data is still on the mirrored disk. If it is, install grub to the mirror, bring it up, then rebuild mdadm with a replacement disk for the one that failed. If it is hardware RAID, then all you have to do is reboot with a replacement drive, and the controller will take care of everything.
Do you have true hardware RAID (through a raid card), or was this just 2 drives plugged into a motherboard, which is software RAID?
The simple solution would be to stick a live CD/DVD in (knoppix for example), and see if all of your data is still on the mirrored disk. If it is, install grub to the mirror, bring it up, then rebuild mdadm with a replacement disk for the one that failed. If it is hardware RAID, then all you have to do is reboot with a replacement drive, and the controller will take care of everything.
Peace,
JimBass
it's software raid.
so, all i have to do is to connect new disk instead of old one, and boot system from rescue disk? after that to install grub and to mirror disks with mdadm. and that's all?
No, you first have to see what (if any) data is safe. As Brian1 said, RAID1 is a mirror, so if you did something that erased things or screwed them up, it is going to be the same on both disks. If it is a "simple" failure, like the disk itself screwed up somehow, then follow the very detailed instructions on this page:
thank you for your answers. it was a great help to recover system.
now (it looks) that it works well, but...
on a fdisk -l command, i got list od 3 partitions, with following errors:
Disk /dev/md1/ doesn't contain a valid partition table
Disk /dev/md2/ doesn't contain a valid partition table
Disk /dev/md0/ doesn't contain a valid partition table
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.