[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Can't start VM after latest kernel update: weird mount failure

After the recent kernel updates one of my virtual machines won't start.  GRUB runs and messages indicate the kernel is loaded and the initial ramdisk is loading.  Then it says it can't find the root device (identified by correct UUID, though it wouldn't be visible until the logical volumes are activated).  In busybox the logical volumes are visible, but when I make a directory and attempt to mount to it I get
mount: mounting /dev/markov02/root on r failed: No such file or directory.
The same thing happens if I try to mount the boot partition (/dev/vda1).
This is weird because both the device and the directory are present.  I can change into the directory and create a file in it

When I attach the virtual hard drives to another VM I have no problem mounting either the boot partition or the logical volume.

I would appreciate any assistance figuring out what's going on or what I can do to correct it.

If my initrd got corrupted, is there a way to regenerate it?

Ross Boylan

The host and guest are running Debian 7.9 wheezy.  I have another wheezy VM that is fine, and a jessie VM that I used to read the virtual disks.  The virtual disks look like this (vdc=vda on original vm; vdd=vdb on original):
Model: Virtio Block Device (virtblk)
Disk /dev/vdc: 21.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type      File system  Flags
 1      1049kB  256MB   255MB   primary   ext2         boot
 2      257MB   21.0GB  20.7GB  extended
 5      257MB   21.0GB  20.7GB  logical                lvm

Model: Virtio Block Device (virtblk)
Disk /dev/vdd: 16.1GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name     Flags
 1      10.5MB  16.1GB  16.1GB               primary  msftdata

vdc5 and vdd1 are part of a volume group markov02 which includes the root file system and swap space.  vdc1 appears to have /boot; the timestamps of its files indicate it was recently updated.

Running using kvm under libvirt.  The virtual disks are logical volumes on the host system. amd64 architecture.

Reply to: