http://bugzilla.novell.com/show_bug.cgi?id=525237
User rccj@ricreig.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=525237#c54
--- Comment #54 from Richard Creighton 2009-10-14 10:27:21 MDT ---
What, if any additional information would you need from me? I believe this
bug came closest to describing the problem I experienced, ie, it is not about
LVM,or RAID specifically, it is about mkinitrd when either or both of those are
used to store all or part of the root of the file system. In my case, / is on
a RAID 1, but /boot is on a normal primary partition, not part of either a LVM
or a RAId, but directories needed for building a new module or load image
certainly reside on (in my case) a RAID or LVM or possibly both in my case
because /usr is on the LVM for instance, however, at the time things are being
updated or being built, this tree is (or should be) fully available as the
system hasn't been rebooted yet as it is still being updated by the update
scripts and fwiw, the failure also fails when run from YAST as opposed to
zypper dup. Previous updates have not failed using YAST (update all with
newer) (only factory enabled) (from M8 to RC1) and with zypper dup as an effort
to repair the failure as a last resort with no positive effect.
I hope this does not become a pissing match about technicalities about raid
version or lvm vs raid, It is a failure of mkinitrd when using one or both of
those in some or any combination that causes a failure that needs to be
identified and I will do my best to help identify the cause if you remember, I
am NOT a technical person (anymore), I am a stroke victim that USED to be a
systems engineer/programmer that hasn't programmed in 'modern' low level
languages in many years.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.