Cannot create LVM Group with Network Backing (/usr/bin/file failed with exit code 1)

Tony

Renowned Member
Nov 4, 2010
113
11
83
Hi,

I did the following steps:

- install proxmox VE from proxmox VE 1.6 CD on a new machine
- setup iscsi & multipath for access to a SAN (a Dell MD3000i if that matters)
- follow precisely this guide: http://pve.proxmox.com/wiki/Storage_Model#LVM_Groups_with_Network_Backing
- I could add the expected iscsi target, however when I tried to add a LVM group with Base Storage = iscsi, this step failed with an error:

Error: command '/usr/bin/file -L -s /dev/disk/by-id/scsi-scsi-36a4badb0004b3258000025594ccf6ae2' failed with exit code 1


I did some searching and the closest thread I could find is this: http://forum.proxmox.com/threads/4608-ISCSI-problems-with-md300i

Can someone please give me a hint how to process further?

thanks,
Tony
 
Re: Cannot create LVM Group with Network Backing (/usr/bin/file failed with exit code

what 'storage name' do you try to use?
 
Re: Cannot create LVM Group with Network Backing (/usr/bin/file failed with exit code

for iscsi target: "san-kvm"
for lvm group: "test" (later tried again with "test2")

Regards,
Tony
 
Re: Cannot create LVM Group with Network Backing (/usr/bin/file failed with exit code

many thanks for the hint, it indeed fixed the problem.

Tony
 
Re: Cannot create LVM Group with Network Backing (/usr/bin/file failed with exit code

Hi There, I have a newly installed copy of 1.7 and I'm running into the same error.

When I try the command in the shell, this is the response:


# /usr/bin/file -L -s /dev/disk/by-id/scsi-36842b2b0004c3046000005184cebcdbf
/dev/disk/by-id/scsi-36842b2b0004c3046000005184cebcdbf: ERROR: cannot read `/dev/disk/by-id/scsi-36842b2b0004c3046000005184cebcdbf' (Input/output error)


I'm running libpve-storage-perl 1.0-16:

# pveversion -v | grep "storage-perl"
libpve-storage-perl: 1.0-16

my names are:

iscsi: testiscsi
storage name: stortest
Volume groups name: vgtest


Thanks,
Anthony
 
Re: Cannot create LVM Group with Network Backing (/usr/bin/file failed with exit code

Nevermind, it turned out it was a problem with the controller ownership of the LUN, I think probably a multipath issue I need to sort out. Changing controller ownership on the SAN solved the problem