Subject: Re: Odd dmesg log messages
To: Sarton O'Brien <firstname.lastname@example.org>
From: Brian Buhrow <email@example.com>
Date: 12/04/2007 20:07:34
You're correct if you're still using a raid0a root device. However,
if something has gone terriblywrong, and you need to revert to a raw wd1a
root device, then you'll see this message. My guess is that Michael had a
raid1 miror as his root drive, and then, for some reason, he stopped using
raid0a as his root device, and started using the wd1a device directly.
However, his wd0a device was still there, so the kernel found both devices
could be usable as root filesystems. In any case, it's a message I
wouldn't worry about if I'm working on a machine and it's in transition,
i.e. I'm reconfiguring it or building a new raid set, or something like
that. Only if I saw the message when I was ready to begin production
testing would I really try to investigate what was going on. So far, that
strategy has worked well, as once I've finished building a machine and
getting all the drives partitioned and formatted the way I want, the
message is always gone.
On Dec 5, 12:06pm, "Sarton O'Brien" wrote:
} Subject: Re: Odd dmesg log messages
} Brian Buhrow wrote:
} > This message just means the system found two bootable drives when it
} > was searching for root devices. Or, rather, it found two drives with
} > potential root partitions. I've seen it on machines I've booted where I
} > have a broken raid1 mirror, and I'm using the second broken piece as a
} > root drive while I fix things up.
} > -Brian
} That's strange as I have always, at least in testing, booted from raid0
} no matter which drive is stated as failed, it's just lacking from the
} drive detection phase and replaced with an id rather than a drive
} I've never seen the warning stated in this thread. TBH I've never seen a
} confusing message from raidframe to date.
} I'd be worried that due to the lack of detection, auto-configuration and
} booting from wd0, that the disks may not syncing as you would expect.
} I've neglected to mention I am using grub but I can't see where this
} would change anything except for maybe the patchy disklabels I use to
} coherce grub to boot xen.
>-- End of excerpt from "Sarton O'Brien"