<div dir="ltr"><div><font face="monospace, monospace">Loading dm-mem-cache.ko module</font></div><div><font face="monospace, monospace">Loading dm-region_hash.ko module</font></div><div><font face="monospace, monospace">Loading dm-message.ko module</font></div><div><font face="monospace, monospace">Loading dm-raid45.ko module</font></div><div><font face="monospace, monospace">device-mapper: dm-raid45: initialized v0.25941</font></div><div><font face="monospace, monospace">Waiting for driver initialization.</font></div><div><font face="monospace, monospace">Scanning and configuring dmraid supported devices</font></div><div><font face="monospace, monospace">Trying to resume from /dev/vg00/lvol00</font></div><div><font face="monospace, monospace">Unable to access resume device (/dev/vg00/lovl00)</font></div><div><font face="monospace, monospace">Creating root device.</font></div><div><font face="monospace, monospace">Mounting root filesystem.</font></div><div><font face="monospace, monospace">mount: could not find filesystem '/dev/root'</font></div><div><font face="monospace, monospace">Settting up other filesystems.</font></div><div><font face="monospace, monospace">Setting up a new root fs</font></div><div><font face="monospace, monospace">setuproot: moving /dev/ failed: No such file or directory</font></div><div><font face="monospace, monospace">no fstab.sys, mounting internal defaults</font></div><div><font face="monospace, monospace">setuproot: error mounting /proc: No such file or directory</font></div><div><font face="monospace, monospace">setuproot: error mounting /sys: No such file or directory</font></div><div><font face="monospace, monospace">Switching to new root and running init.</font></div><div><font face="monospace, monospace">unmounting old /dev</font></div><div><font face="monospace, monospace">unmounting old /proc</font></div><div><font face="monospace, monospace">unmounting old /sys</font></div><div><font face="monospace, monospace">switchroot: mount failed: No such file or directory</font></div><div><font face="monospace, monospace">Kernel panic - not sycing: Attempted to kill init!</font></div><div><font face="monospace, monospace"><br></font></div><div><font face="arial, helvetica, sans-serif">So here's the last section of the boot log before it panics, I've also tried with 'noresume' in the kernel options, and that gets rid of the resume device error. So it looks like something's wrong at mkrootdev step. Is there a way to debug what devicemapper is doing to tell if it's picking up the logical volumes correctly? </font></div><div><font face="arial, helvetica, sans-serif"><br></font></div><div><div><font face="monospace, monospace">echo "Loading dm-raid45.ko module"</font></div><div><font face="monospace, monospace">stabilized --hash --interval 1000 /proc/scsi/scsi</font></div><div><font face="monospace, monospace">mkblkdevs</font></div><div><font face="monospace, monospace">echo Scanning and configuring dmraid supported devices</font></div><div><font face="monospace, monospace">resume /dev/vg00/lvol00</font></div><div><font face="monospace, monospace">echo Creating root device.</font></div><div><font face="monospace, monospace">mkrootdev -t ext4 -o defaults,ro /dev/vg00/lvol01</font></div><div><font face="monospace, monospace">echo Mounting root filesystem.</font></div><div><font face="monospace, monospace">mount /sysroot</font></div><div><font face="monospace, monospace">echo Setting up other filesystems.</font></div><div><font face="monospace, monospace">setuproot</font></div><div><font face="monospace, monospace">echo Switching to new root and running init.</font></div><div><font face="monospace, monospace">switchroot</font></div></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace"><br></font></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div>--</div>Wyatt Zacharias<div><br></div></div></div></div>
<br><div class="gmail_quote">On Mon, Nov 30, 2015 at 2:19 PM, Adam Thompson <span dir="ltr"><<a href="mailto:athompso@athompso.net" target="_blank">athompso@athompso.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
What's the partition type set to? 0xFD or 0x8E, by any chance?
Should probably be 0x83 for /boot, 0x8e for the PV.<br>
Otherwise, start from scratch instead of trying to "fix" it and
you'll find the problem faster.<br>
VM boots? Yes.<br>
Loads boot sector? Yes.<br>
Loads GRUB? Yes.<br>
Loads kernel? Yes.<br>
Loads initrd? Maybe... probably.<br>
Can pivot_root? Maybe... probably not.<br>
Can achieve multi-user runlevel? No.<br>
<br>
So somewhere between loading initrd (which probably worked) and
pivot'ing root (probably) lies your problem. Extract your initrd
and trace through the behaviour one line at a time.<br>
<br>
Better yet, examine what modules are baked into the original initrd
(from the original physical server) and compare with the P2V'd list
of modules.<br>
<br>
The loading of dm_raid is harmless; your problem is LVM modules or
detection somehow.<br>
<br>
-Adam<div><div class="h5"><br>
<br>
<div>On 15-11-30 01:25 PM, Wyatt Zacharias
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">So I'm attempting to virtualize one of our Redhat 5
boxes using VMWare's P2V functionality, and it's copied all the
data into the VM without any trouble, but now I can't seem to
get the virtual machine to boot because it's not detecting the
virtualized partitions correctly. The physical system was using
LVM on top of dm-raid to local disks. When VMWare virtualized
the disks, it created a single disk, and copied the LVM layout
onto it, so I think what's happening is on boot, the system is
looking for the RAID disks and can't find them. When I try to
boot it, it says that it can't find the logical volumes and goes
into a kernel panic.
<div><br>
</div>
<div>I've booted with a rescue disk, and when I run a pvscan on
the new virtual disk, all the volumes are there and can be
mounted, so the problem must be that the system isn't looking
for the volumes in the right place. I've tried changing the
root device to /dev/sda in the device.map comfig file, and I
rebuilt the initrd file with both the --force-lvm-probe and
--omit-raid-modules and it still loads dm-raid on boot. </div>
<div><br>
</div>
<div>So how do I get the system to completely forget about RAID,
and boot off the new virtual disk? Is there a RAID config
somewhere that I'm missing? </div>
<div><br clear="all">
<div>
<div>
<div dir="ltr">
<div>--</div>
Wyatt Zacharias
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
Roundtable mailing list
<a href="mailto:Roundtable@muug.mb.ca" target="_blank">Roundtable@muug.mb.ca</a>
<a href="http://www.muug.mb.ca/mailman/listinfo/roundtable" target="_blank">http://www.muug.mb.ca/mailman/listinfo/roundtable</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
Roundtable mailing list<br>
<a href="mailto:Roundtable@muug.mb.ca">Roundtable@muug.mb.ca</a><br>
<a href="http://www.muug.mb.ca/mailman/listinfo/roundtable" rel="noreferrer" target="_blank">http://www.muug.mb.ca/mailman/listinfo/roundtable</a><br>
<br></blockquote></div><br></div>