I gather that you're using devfs here. Although it seems that mounting
devfs gives me a system without /dev/lvm, nevertheless running lilo -t -v 3
here on an all-LVM system doesn't give me the errors you describe. Can you
reproduce this problem on your own system when running lilo -t -v 3, or does
it only manifest when not in test mode?
You comment in the bug report that this is grave because the bootloader is
screwed up in the process. Did lilo actually overwrite the MBR, in spite of
the LVM errors? Or was this error caused by the reshuffling of /boot files
between the woody and sarge versions of lilo? lilo could run without the
'|| true' on install to make the errors more apparent; I'm just not sure if
this is the most appropriate fix.
Cheers,
--=20
Steve Langasek
postmodern programmer
--3Pql8miugIZX0722
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
Message-ID: <email address hidden>
Date: Sun, 24 Apr 2005 03:29:40 -0700
From: Steve Langasek <email address hidden>
To: <email address hidden>, <email address hidden>
Subject: Re: Fatal: LVM_GET_IOP_VERSION failed on /dev/lvm
--3Pql8miugIZX0722 Disposition: inline Transfer- Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Content-
Content-
Hi Eduard,
I gather that you're using devfs here. Although it seems that mounting
devfs gives me a system without /dev/lvm, nevertheless running lilo -t -v 3
here on an all-LVM system doesn't give me the errors you describe. Can you
reproduce this problem on your own system when running lilo -t -v 3, or does
it only manifest when not in test mode?
You comment in the bug report that this is grave because the bootloader is
screwed up in the process. Did lilo actually overwrite the MBR, in spite of
the LVM errors? Or was this error caused by the reshuffling of /boot files
between the woody and sarge versions of lilo? lilo could run without the
'|| true' on install to make the errors more apparent; I'm just not sure if
this is the most appropriate fix.
Cheers,
--=20
Steve Langasek
postmodern programmer
--3Pql8miugIZX0722 pgp-signature; name="signature .asc" Description: Digital signature Disposition: inline
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
ufymYLloRApiTAK C2KT3bLT1Nk7Pbg 7w0Nr4zsw1JpQCf UACI OsF/5YTs=
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFCa3UQKN6
WxY2JrkHJZdW0TP
=nTAW
-----END PGP SIGNATURE-----
--3Pql8miugIZX0 722--