Neil Brown wrote: > > On Sunday February 25, [EMAIL PROTECTED] wrote: > > Neil Brown wrote: > > > > OK, this time I really want to know how this should be handled. > > > > > > Well. it "should" be handled by re-writing various bits of raid code > > > to make it all work more easily, but without doing that it "could" be > > > handled by marking the partitions as hold raid componenets (0XFE I > > > think) and then booting a kernel with AUTODETECT_RAID enabled. This > > > approach ignores the device info in the superblock and finds > > > everything properly. > > > > I do not use partitions, the whole /dev/hdb and /dev/hdd are the RAID > > drives (mainly because fdisk was unhappy handling the 60GB drives). Is > > there a way to do the above marking in this situation? How? > > No, without partitions, that idea falls through. > > With 2.4, you could boot with > > md=1,/dev/whatever,/dev/otherone > > and it should build the array from the named drives. I will try this next time I need it (or earlier if i get a chance to play). If it works then it will do for me. I expect the superblock will be updated once the system boots so I only need these parameters for one boot. > There are ioctls available to do the same thing from user space, but If there is no tried-and-tested utility then I will be just as happy hacking the superblock myself it worked once so I trust it. I still think the HOWTO should explain how to do this. This list is as good a place as I know to request this. Any takers? -- Eyal Lebedinsky ([EMAIL PROTECTED]) <http://samba.anu.edu.au/eyal/> - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED]
