> -----Original Message-----
> From: Jeff Hill [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, March 25, 2000 9:18 AM
> To: Jakob �stergaard
> Cc: [EMAIL PROTECTED]
> Subject: Re: System Hangs -- Which Is Most Stable Kernel?
>
[snip]
> > > My mdstat reads:
> > > Personalities : [linear] [raid0] [raid1] [translucent]
> > > read_ahead 1024 sectors
> > > md0 : active raid1 sdb2[1] sda2[0] 8739264 blocks [2/2] [UU]
> > > unused devices: <none>
> > Disable translucent mode ! It's not intended to be used yet.
>
> I assume the only way to disable it is to recompile the kernel?
Yep, unless you compiled it as a module, then you could probably just remove
the module without too many adverse affects.
>
> >>--snip--<<
> > It sounds pretty strange what you're seeing. It would be
> very interesting
> > to see if you could reproduce your problems without RAID.
> You're running
> > RAID-1, so you should be able to just don't start the RAID
> devices, and
> > then mount one of the mirrors disregarding the /dev/mdX devices.
>
> Sorry for my ignorance of RAID, but I'm not certain I'm following. How
> do you not start RAID when it is compiled into the kernel to automount
> /dev/md0 at root (I use the RedHat lilo version that allows
> this). Doing
> a "raidstop /dev/md0"? Or reboot to a 2.2.14 kernel without RAID
> compiled in?
I think you could just change the type of those partitions to 0x83 (linux
native), and RAID won't autostart them. The just point lilo to one disk,
and run like that for a while. Not sure how you would go back to RAID after
that....
>
> I would just shoot in the dark at this, but I'm a little
> paranoid as it
> is my main webserver (yes, I should have done more testing
> before making
> it a production machine).
Oops. :-) I'd grab another machine, and start breaking things on that.
You might try to reproduce your software setup on a second machine, and try
anything that you're going to try on the production machine there first, so
that when you hose something, you've done it on a test machine first.
Greg
