serious problem with lvm on iscsi target, solved

robnl

New Member
Oct 19, 2010
8
0
1
I posted before about losing a pv located on an iscsi target after a reboot.

I lack the knowledge to solve it myself, so guys from AboveIT did.

I followed the howto for using iscsi, adding a target, then adding an lvm (called pve-qnap) on the target to place the vm's in.

It appears the lvm was build on /dev/sda 8e Linux LVM

After a reboot fdisk -l showed
/dev/sda1 83 Linux

And pvscan did not show the pv pve-qnap anymore. Somehow a partition sda1 was made afterwards.

The problem was solved by editing the partitiontable. What worries me is how this happend: I only used the interface to make the configuration.

So is this the result of a serious bug in proxmox? Could it have happend after the upgrade from 1.4 to 1.5 ? Or did it happen when I clustered the machine?

More users have reported losing lvm's on iscsi and no adequate solution is in this forum.

I will try to replicate this behavior later, but first I need to put my machines back online.
 
So is this the result of a serious bug in proxmox? Could it have happend after the upgrade from 1.4 to 1.5 ? Or did it happen when I clustered the machine?

I am quite sure that proxmox software does not modify the partition table.
 
Well I don't know. Fact is I configured the storage from the interface only.
And after a reboot all my machines stored on iscsi were gone. That worries me. Proxmox is a great solution.
Just thought I'd mention it.
Rob
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!