Won't boot

vmsv · Mar 7, 2011

My server doesn't boot. I've got some errors saying that the mount points for the lvm are not available.
I have tryied to mount the volumes using a knoppix live cd but when I try to do some commands I always have an error. Bellow you can see some of the errors:

root@Microknoppix:/mnt# pvscan
PV /dev/sda2 VG pve lvm2 [297.59 GiB / 3.99 GiB free]
Total: 1 [297.59 GiB] / in use: 1 [297.59 GiB] / in no VG: 0 [0 ]

root@Microknoppix:/mnt# vgscan
Reading all physical volumes. This may take a while...
Found volume group "pve" using metadata type lvm2

root@Microknoppix:/mnt# lvscan
ACTIVE '/dev/pve/swap' [4.00 GiB] inherit
ACTIVE '/dev/pve/root' [74.50 GiB] inherit
ACTIVE '/dev/pve/data' [215.09 GiB] inherit

root@Microknoppix:/mnt# pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 pve lvm2 a- 297.59g 3.99g

root@Microknoppix:/mnt# vgs
VG #PV #LV #SN Attr VSize VFree
pve 1 3 0 wz--n- 297.59g 3.99g

root@Microknoppix:/mnt# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
data pve -wi-d- 215.09g
root pve -wi-d- 74.50g
swap pve -wi-d- 4.00g

root@Microknoppix:/mnt# mount /dev/mapper/pve-data /mnt/t -t ext3
mount: wrong fs type, bad option, bad superblock on /dev/mapper/pve-data,
missing codepage or helper program, or other error
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
In some cases useful info is found in syslog - try

dmesg | tail
[103816.244512] EXT3-fs (dm-5): error: unable to read superblock

Has you can see it seems like pve-data points to dm-5 which doesn't appear on the fdisk -l list.

I only need to recover 2 virtual machines from the pve-data partition, I can reinstall all after recover these two files.

Any help?

vmsv · Mar 14, 2011

vmsv said:
My server doesn't boot. I've got some errors saying that the mount points for the lvm are not available.
I have tryied to mount the volumes using a knoppix live cd but when I try to do some commands I always have an error. Bellow you can see some of the errors:

root@Microknoppix:/mnt# pvscan
PV /dev/sda2 VG pve lvm2 [297.59 GiB / 3.99 GiB free]
Total: 1 [297.59 GiB] / in use: 1 [297.59 GiB] / in no VG: 0 [0 ]

root@Microknoppix:/mnt# vgscan
Reading all physical volumes. This may take a while...
Found volume group "pve" using metadata type lvm2

root@Microknoppix:/mnt# lvscan
ACTIVE '/dev/pve/swap' [4.00 GiB] inherit
ACTIVE '/dev/pve/root' [74.50 GiB] inherit
ACTIVE '/dev/pve/data' [215.09 GiB] inherit

root@Microknoppix:/mnt# pvs
PV VG Fmt Attr PSize PFree
/dev/sda2 pve lvm2 a- 297.59g 3.99g

root@Microknoppix:/mnt# vgs
VG #PV #LV #SN Attr VSize VFree
pve 1 3 0 wz--n- 297.59g 3.99g

root@Microknoppix:/mnt# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
data pve -wi-d- 215.09g
root pve -wi-d- 74.50g
swap pve -wi-d- 4.00g

root@Microknoppix:/mnt# mount /dev/mapper/pve-data /mnt/t -t ext3
mount: wrong fs type, bad option, bad superblock on /dev/mapper/pve-data,
missing codepage or helper program, or other error
(could this be the IDE device where you in fact use
ide-scsi so that sr0 or sda or so is needed?)
In some cases useful info is found in syslog - try

dmesg | tail
[103816.244512] EXT3-fs (dm-5): error: unable to read superblock

Has you can see it seems like pve-data points to dm-5 which doesn't appear on the fdisk -l list.

I only need to recover 2 virtual machines from the pve-data partition, I can reinstall all after recover these two files.

Any help?

After done more research I have the followin errors.

root@Microknoppix:~# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
data pve -wi-d- 215.09g
root pve -wi-d- 74.50g
swap pve -wi-d- 4.00g
root@Microknoppix:~# lvchange -ay data
Volume group "data" not found
Skipping volume group data
root@Microknoppix:~# lvchange -ay /dev/mapper/pve-data
device-mapper: reload ioctl failed: Invalid argument
root@Microknoppix:~# vgs
VG #PV #LV #SN Attr VSize VFree
pve 1 3 0 wz--n- 297.59g 3.99g
root@Microknoppix:~# vgchange -ay pve
device-mapper: reload ioctl failed: Invalid argument
device-mapper: reload ioctl failed: Invalid argument
device-mapper: reload ioctl failed: Invalid argument
3 logical volume(s) in volume group "pve" now active

I have read that this might be a conflict between mdraid and dmraid is that possible? Do you know how can I resolve this I really need to recover to VM from the data partition.

MrJacK · Mar 15, 2011

What sort of RAID are you using for pve-data ?

vmsv · Mar 15, 2011

I this machine I have two software raid Intel and Nvidia I know they are not real raid. Might this be a conflict between the two? Later today I will post the output of dmsetup info.

vmsv · Mar 17, 2011

vmsv said:
I this machine I have two software raid Intel and Nvidia I know they are not real raid. Might this be a conflict between the two? Later today I will post the output of dmsetup info.

here is the dmsetup info output. Its strange that the pve-data has no tables. I really need some help on this!

Name: pve-swap
State: ACTIVE
Read Ahead: 256
Tables present: None
Open count: 0
Event number: 0
Major, minor: 253, 3
Number of targets: 0
UUID: LVM-EQF3afrMPSJ0wCUVMMsegnFut5NcbK1ShN1QmrrWpZku3cGzfQwDThlc7UFLAxpj

Name: pve-root
State: ACTIVE
Read Ahead: 256
Tables present: None
Open count: 0
Event number: 0
Major, minor: 253, 4
Number of targets: 0
UUID: LVM-EQF3afrMPSJ0wCUVMMsegnFut5NcbK1Sz8pv0nPIJ4WW8Fb0mj2UAQGpveBAJhz7

Name: pve-data
State: ACTIVE
Read Ahead: 256
Tables present: None
Open count: 0
Event number: 0
Major, minor: 253, 5
Number of targets: 0
UUID: LVM-EQF3afrMPSJ0wCUVMMsegnFut5NcbK1SjGC09kZNiQGsheqXOjA2J1PqgRaHyJS0

Name: isw_cbfaheddea_RV12
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 0
Event number: 0
Major, minor: 253, 2
Number of targets: 1
UUID: DMRAID-isw_cbfaheddea_RV12

Name: isw_cbfaheddea_RV11
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 0
Event number: 0
Major, minor: 253, 1
Number of targets: 1
UUID: DMRAID-isw_cbfaheddea_RV11

Name: isw_cbfaheddea_RV1
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 2
Event number: 0
Major, minor: 253, 0
Number of targets: 1
UUID: DMRAID-isw_cbfaheddea_RV1

udo · Mar 17, 2011

vmsv said:
...
root@Microknoppix:~# lvchange -ay /dev/mapper/pve-data
device-mapper: reload ioctl failed: Invalid argument
...

Hi,
what happens if you use

Code:

lvchange -a y /dev/pve/data
fsck /dev/pve/data

the error in the post before say not that /dev/pve/data not exist, but rather that the mount-point (/var/lib/vz) not exist.
If you boot from knoppix, do you can mount pve-root?

Code:

mount /dev/pve/root /mnt
mount /dev/pve/data /mnt/var/lib/vz
df -k

Udo

yellowpin · Mar 17, 2011

...
root@Microknoppix:~# lvchange -ay /dev/mapper/pve-data
device-mapper: reload ioctl failed: Invalid argument
...

well, it seems there is a mistake, but i can't say out where, it's bad~

__________________________________
Ps3 accessories, Wii accessories, Xbox 360 accessories

udo · Mar 17, 2011

yellowpin said:
well, it seems there is a mistake, but i can't say out where, it's bad~

root@Microknoppix:~# lvchange -ay /dev/mapper/pve-data
http://www.egamebiz.com/

and what happens, if you do what i write? /dev/mapper/pve-data and /dev/pve/data must not be the same if the mapper has trouble. The volume group is active?

Udo

vmsv · Mar 17, 2011

The device /dev/pve/data doesn't exist, just the /dev/mapper/pve-data. I have the /dev/mapper/pve-data, /dev/mapper/pve-root and /dev/mapper/pve-swap. On the /dev/mapper dir I also have the isw_cbfaheddea_RV12, isw_cbfaheddea_RV11 and isw_cbfaheddea_RV1 but when I try to mount any of these ones I always get an error its already mounted or busy, But I'm sure this not mounted.

udo · Mar 17, 2011

vmsv said:
The device /dev/pve/data doesn't exist, just the /dev/mapper/pve-data. I have the /dev/mapper/pve-data, /dev/mapper/pve-root and /dev/mapper/pve-swap. On the /dev/mapper dir I also have the isw_cbfaheddea_RV12, isw_cbfaheddea_RV11 and isw_cbfaheddea_RV1 but when I try to mount any of these ones I always get an error its already mounted or busy, But I'm sure this not mounted.

Hi,
ok - mapper came first. /dev/pve/data link to /dev/mapper/pve-data.

Do you change something with your fake-raid? Normaly the bios-raid-function should be disabled (it's not realy a raid) and the raid is done in your case with linux software-raid?!
If you first switch on the bios-raid-function and install something (see not an raid but single disks) and then you switched off the bios raid function your installation is gone...

Udo

vmsv · Mar 17, 2011

udo said:
Hi,
ok - mapper came first. /dev/pve/data link to /dev/mapper/pve-data.

Do you change something with your fake-raid? Normaly the bios-raid-function should be disabled (it's not realy a raid) and the raid is done in your case with linux software-raid?!
If you first switch on the bios-raid-function and install something (see not an raid but single disks) and then you switched off the bios raid function your installation is gone...

Udo

I didn't anything on BIOS, the strange thing is that the dmsetup info, command give me diferent raid and says that the tables are ok. But the pve-data don't have tables.

udo · Mar 17, 2011

vmsv said:
I didn't anything on BIOS, the strange thing is that the dmsetup info, command give me diferent raid and says that the tables are ok. But the pve-data don't have tables.

Hi,
to guess what's happen you must supply more infos.
Please post the output of following commands:

Code:

cat /proc/mdstat
mdadm -D /dev/md0      # and from the other md-devices, which you have in /proc/mdstat
fdisk -l
blkid

Udo

vmsv · Mar 17, 2011

udo said:
Hi,
to guess what's happen you must supply more infos.
Please post the output of following commands:

Code:

cat /proc/mdstat mdadm -D /dev/md0 # and from the other md-devices, which you have in /proc/mdstat fdisk -l blkid

Udo

root@debian:~# blkid
/dev/sda1: UUID="8511ce30-b8a5-4984-b0ad-df293f0cf57e" TYPE="ext3"
/dev/sda2: UUID="rHi2ET-tetw-i1OJ-jtbR-POj2-tnc9-SyVqa5" TYPE="LVM2_member"
/dev/sdb1: UUID="df4ddc65-8618-4489-aba6-986ce59d0155" TYPE="xfs"
/dev/sdb2: UUID="d1242105-9367-4dea-a3b2-e7611b4be17a" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb3: UUID="76905bff-7a6d-4e2e-99f8-853f0b7d60fc" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/isw_cbfaheddea_RV11: UUID="8511ce30-b8a5-4984-b0ad-df293f0cf57e" TYPE="ext3"

root@debian:~# mdadm -D /dev/dm-0
mdadm: /dev/dm-0 does not appear to be an md device
root@debian:~# mdadm -D /dev/md0
mdadm: cannot open /dev/md0: No such file or directory
root@debian:~# ls -la /dev/md/
total 0
drwxr-xr-x 2 root root 40 Mar 17 20:33 .
drwxr-xr-x 16 root root 3280 Mar 17 20:33 ..

root@debian:~# cat /proc/mdstat
Personalities :
unused devices: <none>

udo · Mar 18, 2011

vmsv said:
root@debian:~# blkid
/dev/sda1: UUID="8511ce30-b8a5-4984-b0ad-df293f0cf57e" TYPE="ext3"
/dev/sda2: UUID="rHi2ET-tetw-i1OJ-jtbR-POj2-tnc9-SyVqa5" TYPE="LVM2_member"
/dev/sdb1: UUID="df4ddc65-8618-4489-aba6-986ce59d0155" TYPE="xfs"
/dev/sdb2: UUID="d1242105-9367-4dea-a3b2-e7611b4be17a" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb3: UUID="76905bff-7a6d-4e2e-99f8-853f0b7d60fc" SEC_TYPE="ext2" TYPE="ext3"
/dev/mapper/isw_cbfaheddea_RV11: UUID="8511ce30-b8a5-4984-b0ad-df293f0cf57e" TYPE="ext3"

ok, "fdisk -l" is missing, but this show:
1. you have two plain disk (no softwareraid).
2. First disk is proxmox (boot + lvm). Normaly the lvm should be the volumegroup pve.
3. The second disk has tree partitions with xfs and two ext3.
4. Now the strange part: what is isw... ??
A posting before, it's show this is a dm-raid. But from which devices?? I see no raid-member.
This can only be done be you - so i think you must also help yourself! I guess this is not an standard proxmox installation, so i don't know what you have done...

best luck

Udo

Search

Search

Won't boot

vmsv

New Member

vmsv

New Member

MrJacK

Guest

vmsv

New Member

vmsv

New Member

udo

Famous Member

yellowpin

Guest

udo

Famous Member

vmsv

New Member

udo

Famous Member

vmsv

New Member

udo

Famous Member

vmsv

New Member

udo

Famous Member