On 2013-08-21 11:10 AM, Neil Bothwick <n...@digimed.co.uk> wrote:
On Wed, 21 Aug 2013 10:40:32 -0400, Tanstaafl wrote:
update LVM2
kernel remains the same
reboot
initramfs finds all PVS and activates VG
main system init
/etc/init.d/lvm2 start
error can't read from USB PVS
login to system with missing PVS
/etc/init.d/lvm2 restart
all PVS listed
reboot several times to verify it wasn't just a stuck service,
exactly the same
now ok but restarting a boot service manually required (!)
I updated the initramfs and rebooted and all problems went away
This sounds like a bug in LVM. If it was down to a version clash, why did
a restart find the PVs?
Sorry, ianap, but I do know that this kind of thing has never happened
to me in my 8+ years of running this old system with a separate /usr
*without* an initramfs...
So, the bottom line is, obviously (to me at least), there are a lot more
things that can go wrong when an initramfs is involved, that simply
don't or can't happen otherwise.
And this is *precisely* what scares me about this.
This simply should not be, period. Support for separate /usr without
initramfs simply SHOULD NOT be dropped unless/until things like this
(updating lvm) can *never* cause a system to fail to boot like this.
This is irrelevant to separate /usr. an initramfs is required if / is on
a VM, whether or not /usr is on the same LV.
Sorry, I don't see where he said that this system was running on a VM...
or did you mean where he had / on an *LVM* partition - which, again, he
did not say he had.
