Hi all,
One of our Dell servers has failed badly, and one of the domU's has been corrupted in the process. It boots up to a point and then gives me a kernel panic:
Loading dm-zero.ko module Loading dm-snapshot.ko module Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!
It shows up as a Zombie:
[root@xen ~]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1439 1 r----- 329.0 Zombie-hfserver2 15 1024 1 ----c- 0.5 hfdns02 10 519 2 r----- 1552.8
I can't mount either:
root@xen ~]# mount /dev/data/hf hfdns02 hfserver2 [root@xen ~]# mount /dev/data/hfserver2 /mnt/cpanel/ mount: you must specify the filesystem type [root@xen ~]# mount -o loop /dev/data/hfserver2 /mnt/cpanel/ mount: you must specify the filesystem type
Here's the output of the LVM partitions:
[root@xen ~]# lvscan ACTIVE '/dev/data/cpanel002' [100.00 GB] inherit ACTIVE '/dev/data/windows2003_web' [30.00 GB] inherit ACTIVE '/dev/data/storage' [50.00 GB] inherit ACTIVE Original '/dev/data/hfserver2' [30.00 GB] inherit ACTIVE '/dev/data/hfdns02' [30.00 GB] inherit ACTIVE '/dev/data/pluto' [30.00 GB] inherit ACTIVE Snapshot '/dev/data/pluto_s' [30.00 GB] inherit ACTIVE '/dev/system/root' [39.06 GB] inherit ACTIVE '/dev/system/swap' [9.75 GB] inherit [root@xen ~]# vgscan Reading all physical volumes. This may take a while... Found volume group "data" using metadata type lvm2 Found volume group "system" using metadata type lvm2 [root@xen ~]#
Does anyone know how to fix a LVM like this?