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.
Partiton types are ony relevant to partitions.
As noted in your closed dupicate thread, mdadm manpage has advice on this - as does the Linux RAID wiki. All easily findable by searching.
Thanks for your reply, syg00 and moderator.
I have read that raid wiki, I'm just a bit slow. So I take it that the paritions that are to make up the raid have to be marked as such before mdadm is employed and will not be re-designated by mdadm's 'create' command?
Actually, they don't have to be marked (i.e., partition type set to 0xfd) at all. In-kernel RAID autodetection using that partition type worked only with RAID superblock version 0.9 and is now deprecated. Userspace RAID detection, the preferred method, does not rely on partition type. https://raid.wiki.kernel.org/index.php/Autodetect
sorry, 0xfd. I see there are many options for software raid and 2 drives, of a similar type, bought at the same time would probably fail at a similar time and so raid1 has limitations but a Debian install with separate /boot partitions (to the dm0) on each drive should work? Not using lvm.
I set up raid1 on 2 disks with 2 partitions each (sda sdb, 1+2) both as raid1, md0 and md1.
md0 was /boot on both sda and sdb
md1 was / on both sda and sdb
sda also contained a swap partition outside the raid1 setup
This was a i386 setup done with gparted disk for the partitions and the raid using mdadm --create with a suffix of --metadata=0.90 (similar) as suggested by the program
I set the mount points from the Debian install disk and rebooted,
all was fine.
To simulate a disk, or lead failure, I disconnected the sda ide lead (each drive on individual leads) and the boot process will not find any drive.
I tried to access what was on the drive using 'supergrub2' cd but it found errors when trying to access raid, presumably because grub is only on sda
is there any means of rectifying this without starting again?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.