On Sat, Feb 11, 2017 at 2:12 PM, Harry Putnam <rea...@newsguy.com> wrote: > > Again I get a kernel panic but this time its different. It seems to > mount the disks ok but then fails to find a working `init' command. > > Checking that with sysrescueCD I see /sbin/init does exist on that new vm. > and is executable. > > The disk setup is sda1=/boot sda2=swap sda3=/home sda4=/ >
My guess is that it is mounting the wrong filesystem as root. It might be detecting /dev/sdb as /dev/sda. Also, the root device might be named /dev/xda4 depending on the kernel/etc. Systemrescuecd isn't using the same kernel/etc so it might not see the disks the same way. An initramfs with root=UUID="505f850e-b26a-4d0f-a02f-6ba573a48ad8" (or a label) would be a more reliable way to handle this, or you can probably just fiddle with the device names until you stumble on the right one. -- Rich
