On Saturday February 24, [EMAIL PROTECTED] wrote:
> Eyal Lebedinsky wrote:
> >
> > I have two disks as raid on a BP6 (HPT366) and had one too many
> > lockups on hde+hdg, so I decided to move it down to hdb+hdd.
> >
> > I could not start the raid, it just complained that the disks
> > are not at the major/minor it expected it.
> >
> > The first message said that [21:00] is now hdb, then it said
> > that it cannot access [22:00] (naturally) so it removed a disk
> > from the array, then it said the array expects two disks but
> > only one was found.
> >
> > How do I tell it that the raid pair is just fine but it had to
> > be moved to a new location?
> >
> > I tried 'mkraid --upgrade' hoping it will reconfigure but no dice
> > (same errors as above).
>
> 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.
But congratulations on finding an alternate solutions that hard way.
NeilBrown
> I got a number of replies suggesting I use raidhotadd (which has
> no man page or any doco that I can find). I tried and it will not
> do a thing if raid is not started, but it wont start as I described
> in my original post, so a catch 22.
>
> I think that it will be nice to have a proper recipe for this
> situation, preferably in the standard HOWTO. Whenever someone
> wants to move one (or more) disk in an array from one location
> to another, what should one do? This situation often arise when
> the array is moved between machines. In my case it was a simple
> case of upgrade. I wanted a larger array, so I created md1, copied
> my md0 to it, then wanted to remove md0 and use the new one. I
> could not leave md1 where is twa (hdf+hdh) since this controller on
> the ABIT bp6 is unstable, so I had to move the array to hdb+hdd.
>
> When I realised that this is the end of the road, I did what every
> cornered animal would do. I examined the raid superblock (od), found
> where the major/minor is located, zapped it to what I wanted it to
> be and started the raid. Seems to work just fine. Naturally, one
> (probably most of the people on this list anyway) can program one's
> way out of almost any situation, but most raid USERS will probably
> not want (or will not be able) to do so.
>
> --
> 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]
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
