Hi,
I followed your discussion a little bit, having a question to the fdisk: what
did you mean by "changing the partition type for sda2 to fd"?
Is it an option to fdisk or does it mean to "fdisk" the drive again (building a
"new" partition sda2)?
Dietmar
Stephen Denny wrote:
> > Check if you'v
> The only other mystery right now is why I can't raidhotremove a disk.
The spec of "raidhotremove" ...
> It says it is busy (it is).
Yup.
> I was expecting raidhotremove to be able to yank it out anyway.
I have heard that it isn't done (yet) because of the fear of not getting the
checks that
Thanks for the info. Its information like this that helps
me understand how to go about debuggin.
I hadn't changed the type to "fd" which was the real problem.
But with the info you've given me, I'm going to do a little
poking around and see what I can learn from it. I've been
listening to you
> Check if you've changed the partition type for sda2 to fd - the disk won't
> be recogniced by the kernel if you obmit this and you get exactly the
> symptoms described.
Bingo!
Many thanks.
Stephen Denny mailto:[EMAIL PROTECTED]
Hex.Net Superhighway
At 23:20 27.03.99 -0600, Stephen Denny wrote:
>Then changed sda2 to raid-disk and did a raidhotadd. It
>worked fine.
>
>My problem is that whenever I boot now, the array comes
>up without sda2. I can raidhotadd sda2 and things are happy
>until the next reboot.
Check if you've changed the partit
> My problem is that whenever I boot now, the array comes
> up without sda2. I can raidhotadd sda2 and things are happy
> until the next reboot.
Hmm -- sounds to me like "raidhotadd" isn't re-writing the SB -- sorry, I don't
know how that code works :-(
What does a "mkraid --debug" give you in
I'm running linux 2.2.3 with raid0145-19990309-2.2.3,
with raid0145-19990309-2.0.36.mabene patch for failed-disk option,
along with raidtools-199900309-0.90
Started out with
raiddev /dev/md0
raid-level 5
nr-raid-disks 3
nr-spa
