Boot Drive Crash

[cheeks]

I have a Proxmox 4.4 that boots from a 1TB Seagate Drive

The System has a 4 Drives in RAID 10 Megaraid Controller

All the VM Machines are on the RAID 10 Volume

The 1TB Seagate Boot Drive has crashed

I have reinstalled Proxmox 4.4 on a SSD 250GB Drive and need to get the VM Machines working from the RAID Volume

I can see the Raid Drive Volume and need to " mount " it to recover my raw files from it

when i do the following:

mount /dev/Big-Storage/vm-100-disk-2 /mnt/testhdd

I get an error: mount: wrong fs type, bad option, bad superblock on /dev/mapper/Big--Storage-vm--100--disk--2

WHAT DO I NEED TO DO TO MOUNT THE VOLUME TO RECOVER THE DATA

I can give you remote access to assist if required including payment for support

Any help greatly appreciated

 

[Sunfish_CA]

seems you are using zfs on RAID
zpool import -a
then check if your old zpool is returning
zfs mount -a will mount your zfs volumes
sometimes it would only mount some of your volumes, export the zpool then re-import, redo the zfs mount,
everything should be fine.
Good luck.

 

[cheeks]

Sunfish_CA thank you for trying to help, much appreciated

On my Storage option i can see the Content = vm-100-disk-2 ( Format = raw Size = 500gb )

The " Big-Storage " volume is on sdb1 MY RAID VOLUME

That is where the Volume is that i want to back up

Why is it so hard to mount a separate volume in Proxmox to recover data from it?

 

[Sunfish_CA]

Sorry, maybe I've made a mistake...
You are trying to mount a volume directly, maybe you should try to find its partitions within
usually there would also be some vm-100-disk-2-partX there, please try mounting them instead.

 

[lifespirit]

Try this:
vgscan
vgchange -ay
mount /dev/mapper/Big-Storage/vm-100-disk-2 /mnt/image

 

[LnxBil]

Why is it so hard to mount a separate volume in Proxmox to recover data from it?

It is really not, it's a plain old Debian. I never experienced a system with more supported filesystems than linux, so must be doing something wrong

Your biggest fault is to store PVE not on a RAID system, because you have a lot of trouble reregistering your machines including failing windows licences if you have not backed up any smbios entries and uuids. You should learn from this mistake and install PVE on your hardware RAID, not aside.

Now to your problems at hand:

Please post the output of the command lsblk inside a CODE-tag.

 

[cheeks]

Sunfish_CA, lifespirit and LnxBill thank you.

vgscan
Found volume group "Big-Storage" using metadata type lvm2
Found volume group "pve" using metadata type lvm2

vgchange -ay
2 logical volume(s) in volume group "Big-Storage" now active
3 logical volume(s) in volume group "pve" now active

ls /dev/mapper
control pve-data_tdata pve-root Big--Storage-vm--100--disk--1
pve-data pve-data_tmeta pve-swap Big--Storage-vm--100--disk--2

lsblk
NAME                                MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                                   8:0    0 149.1G  0 disk
├─sda1                                8:1    0     1M  0 part
├─sda2                                8:2    0   256M  0 part
└─sda3                                8:3    0 148.8G  0 part
  ├─pve-root                        251:0    0    37G  0 lvm  /
  ├─pve-swap                        251:3    0     5G  0 lvm  [SWAP]
  ├─pve-data_tmeta                  251:4    0    92M  0 lvm
  │ └─pve-data                      251:6    0  90.8G  0 lvm
  └─pve-data_tdata                  251:5    0  90.8G  0 lvm
    └─pve-data                      251:6    0  90.8G  0 lvm
sdb                                   8:16   0 931.5G  0 disk
└─sdb1                                8:17   0 931.5G  0 part
  ├─Big--Storage-vm--100--disk--1 251:1    0   120G  0 lvm
  └─Big--Storage-vm--100--disk--2 251:2    0   120G  0 lvm
sr0                                  11:0    1  1024M  0 rom

What do i do now?

 

[LnxBil]

Please post also your storage configuration:

cat /etc/pve/storage.cfg

Then we might have a clue.

How many VMs did you have? Your output suggests one with VM ID 100. You need to recreate the storage (LVM named Big-Storage) first and then add a VM without any disks, reattach the disks and try to boot your VM.

Next time, do regular backups!

 

[cheeks]

LnxBil thanks for your help

I have tried to make backups but Proxmox keeps telling not enough space and now this happens

I have two VM.s but i critcally need the VM ID 100

cat /etc/pve/storage.cfg

dir: local

        path /var/lib/vz
        content vztmpl,iso,backup

lvmthin: local-lvm
        thinpool data
        vgname pve
        content images,rootdir

lvm: big-storage
        vgname Big-Storage
        content images,rootdir
        shared 0

 

[cheeks]

LnxBil

You mentioned " add a VM without any disks, reattach the disks "

How do i reattach the disks ?

 

[LnxBil]

I have tried to make backups but Proxmox keeps telling not enough space and now this happens

And therefore you didn't do backups? Very negligent. You should only run a system if you know how to restore it.

I have two VM.s but i critcally need the VM ID 100

You mentioned " add a VM without any disks, reattach the disks "

As I said, you need to recreate the config by hand (because you do not have any backup) and attach the disks to the newly created VM in the GUI afterwards. We cannot help you there, because we do not know what kind of VM you used.

 

[cheeks]

LnxBil thanks again, much appreciated

I have recreated the storage big-storage

Ok i have manually created the 100.conf file without any hard drives

#WINDOWS 2008 R2 SERVER
#Hostname%3A SERVER02
#IP%3A 192.0.0.105
#2 x 500 GB IDE Drives
#10GB Ram
#Syspro 7
bootdisk: ide0
cores: 4
memory: 12288
name: SYSPRO
net0: e1000=62:9F:BA:BF:6A:E2,bridge=vmbr0
numa: 0
onboot: 1
ostype: win7
scsihw: virtio-scsi-pci
smbios1: uuid=9e48c235-eb25-459e-8fc4-730baaa842c2
sockets: 1
startup: order=1,up=320
usb0: host=1058:25a2

Do i place the file in " /etc/pve/nodes/pve/qemu-server " ?

Then reboot?

 

[LnxBil]

You do not need to reboot. The VM should be just there. It should also bootup if the settings are correct.