no, the md doesn't exist at all. Only physical disks, using paths in /dev/discs. What I did is to use alt-f2 before I hit that portion of the rescue and tried to start the md array, which then failed with the "device or resource busy" error.
Looks like rescue isn't really designed to rescue a root part on a md device - it doesn't seem to be trying to start the md device. I had to modprobe raid1 and mdrun by hand, but I still ended up with the busy error. On 7/28/06, Geert Stappers <[EMAIL PROTECTED]> wrote:
On Thu, Jul 27, 2006 at 12:21:48PM -0700, Ryan Rawson wrote: > Rescue mode doesn't work for me. When I try to start the md array I > end up with the same "device or resource" busy error. Which device was detected/suggested by "rescue"? The md?
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
