On Tue, Feb 14, 2006 at 08:43:16PM +0000, Mike Crowe wrote:
> On Feb 14, Mike Crowe <[EMAIL PROTECTED]> wrote:
> >> I don't think this issue is limited to network devices.
>
> On Tue, Feb 14, 2006 at 01:46:30PM +0100, Marco d'Itri wrote:
> > You are showing some totally unrelated issue which is obviously a
> > bug in lvm2.
>
> I admit that the log excerpt I provided was rather confusing and did
> not contain the pertinent information. The issue I was aiming to
> describe is unrelated to LVM as far as I can determine. That vgchange
> not found error occurs in both successful and unsuccessful boots.
the vgchange issue is due to the hexstyle fashion you passed
the root param, not yet catched by this
-- snipp /usr/share/initramfs-tools/local-top/lvm
vg=${ROOT#/dev/mapper/}
case ${vg} in
/dev/root)
unset vg
;;
/*)
exit 0
;;
esac
--
harmless error message
this will be easily solved once this hook is moved to lvm2
> I've attached two separate logs - one from a successful boot and one
> from a failed boot. It hope it is clear that these two logs show sata,
> megaraid, aic79xx and USB modules scanning for devices in a different
> order. This means that on some boots the boot disk on megaraid is sda
> and on others it's sdb. I see no reason why this randomness could not
> also occur between SATA, and on/off board SCSI devices but don't have
> the hardware available to prove this at the moment.
did you try to regenerate the image with latest udev 084-4
can you still reproduce it with it?
(use update-initramfs -t -u to regenerate your image)
it includes the device ordering features of udev,
they produce different error messages which are mostly harmless.
should help on your setup.
but gave as trouble on working setups that need ide-generic..
regards
--
maks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
