<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16481" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>Hi
Folks,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>I'm wondering if
somebody can point me in the right direction:</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>A problem
occurs very early in the boot process on a Fedora 7 system: mdadm
can't find the devices needed to assemble /dev/md1 which contains an LVM
volume group. The specific problem appears to be the "mdadm: no devices found,"
which is followed by a few related problems and ends with a Kernel
Panic:</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007>...</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>Red Hat nash 6.0.9
starting</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>insmod: error
inserting '/lib/raid456.ko': -1 File exists</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>mdadm: no devices
found for /dev/md1</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007> Reading
all physical volumes. This may take a while...</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007> No
volume groups found</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007> Volume
group "vg0" not found</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>Unable to access
resume device (/dev/vg0/lv0)</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007>...</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>(The system used to
work fine even though the raid456.ko message always
appeared.)</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>The system was
working fine up to last night when I think the temperature rose too high and it
crashed. The funny thing is that if I boot the F7 DVD in rescue mode the system
image is discovered and mounted without any trouble.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>I may have messed
things up at some point by booting the F7 rescue mode and
executing</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007># grub-install
/dev/sda1 </SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>when I should have
used</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007># grub-install
/dev/sda</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>I'd really
appreciate it if somebody could point me to some documentation on this stage of
the boot process (mounting raid/lvm file systems.)</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>I'd also appreciate
any help understanding why mdadm can't figure out what devices to use for
an array - there must be a way to fix that. The way the system is now, I need to
create an mdadm.conf file before the --assemble command will work (isn't
mdadm supposed to be able to figure out what devices to use without the
conf file?) Perhaps there's a solution hiding in that
direction.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>Thanks very
much,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007>All the
best,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007>Sam.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=093201802-12072007></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=093201802-12072007></SPAN></FONT><FONT
face=Arial size=2><SPAN class=093201802-12072007></SPAN></FONT><FONT face=Arial
size=2><SPAN class=093201802-12072007></SPAN></FONT> </DIV></BODY></HTML>