Proxmox 1.5 install on MSA1000 whit disk failover

P

pchoque

New Member
Nov 19, 2009
5
0
1
Proxmox 1.5 install on MSA1000 with disk failover

Hello, I want to install and configure Proxmox 1.5 in cluster with disk failover. We have:

2 Server Proliant DL380 G5
2 HBA qlogic qla2xx per Server
1 MSA 1000 with 2 controllers
2 switch HP FC

Proxmox is installed on each server, but after install multipath-tools the system not boots fine.

Boot:
....
Checking file systems...fsck 1.41.3 (12-Oct-2008)
/dev/pve/data: clean, 20/655360 files, 79705/2621440 blocks
fsck.ext3 : Device or resource busy while trying to open /dev/sda1
Filesystem mounted or opened exclusively by another program?
fsck died with exit status 8
failed (code 8).
File system check failed. A log is being saved in /var/log/fsck/checkfs
....


Proxmox is compatible with disk failover on HBA's?

Is it possible to store all virtual machines in a MSA LUN?

Thanks.

Pablo Choque
 
Last edited:
Hi,
perhaps your sda is'nt yet your boot-disk but in the san.
Look with
Code: 
fdisk -l
and if so, try the uuid in the fstab (you get the uuid with blkid) like this:
Code: 
UUID=89f4b106-93a2-402b-9249-ca2e8462205c /boot           ext3    defaults        0       1

I had multipath on one server running, but now i have change this server.

Udo
 
Thanks for your reply. The results of commands are there, but I dont now how to repair in /etc/fstab.

nodo02#fdisk - l

Disk /dev/sda: 21.4 GB, 21474508800 bytes
64 heads, 32 sectors/track, 20479 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 * 1 513 524288 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 513 20479 20446176 8e Linux LVM
Disk /dev/sdb: 428.5 GB, 428523110400 bytes
255 heads, 63 sectors/track, 52098 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0fcb9eb0
Device Boot Start End Blocks Id System
/dev/sdb1 1 52098 418477153+ 83 Linux
Disk /dev/sdc: 21.4 GB, 21474508800 bytes
64 heads, 32 sectors/track, 20479 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 513 524288 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sdc2 513 20479 20446176 8e Linux LVM
Disk /dev/sdd: 428.5 GB, 428523110400 bytes
255 heads, 63 sectors/track, 52098 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0fcb9eb0
Device Boot Start End Blocks Id System
/dev/sdd1 1 52098 418477153+ 83 Linux
Disk /dev/dm-0: 428.5 GB, 428523110400 bytes
255 heads, 63 sectors/track, 52098 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0fcb9eb0
Device Boot Start End Blocks Id System
/dev/dm-0p1 1 52098 418477153+ 83 Linux
Disk /dev/dm-1: 21.4 GB, 21474508800 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/dm-1p1 * 1 66 524288 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/dm-1p2 66 2611 20446176 8e Linux LVM
Partition 2 does not end on cylinder boundary.
Disk /dev/dm-2: 428.5 GB, 428520605184 bytes
255 heads, 63 sectors/track, 52097 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-2 doesn't contain a valid partition table
Disk /dev/dm-3: 536 MB, 536870912 bytes
255 heads, 63 sectors/track, 65 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-3 doesn't contain a valid partition table
Disk /dev/dm-4: 20.9 GB, 20936884224 bytes
255 heads, 63 sectors/track, 2545 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-4 doesn't contain a valid partition table
Disk /dev/dm-5: 2550 MB, 2550136832 bytes
255 heads, 63 sectors/track, 310 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-5 doesn't contain a valid partition table
Disk /dev/dm-6: 5100 MB, 5100273664 bytes
255 heads, 63 sectors/track, 620 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-6 doesn't contain a valid partition table
Disk /dev/dm-7: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-7 doesn't contain a valid partition table

nodo02:~# blkid
/dev/sda1: UUID="d16eebda-c9c1-4421-999d-362f7e17ffa1" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda2: UUID="rezTt7-qj7J-c965-8LN9-hbMb-NUDe-3seH2h" TYPE="lvm2pv"
/dev/sdc1: UUID="d16eebda-c9c1-4421-999d-362f7e17ffa1" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc2: UUID="rezTt7-qj7J-c965-8LN9-hbMb-NUDe-3seH2h" TYPE="lvm2pv"
/dev/dm-3: UUID="d16eebda-c9c1-4421-999d-362f7e17ffa1" SEC_TYPE="ext2" TYPE="ext3"
/dev/dm-4: UUID="rezTt7-qj7J-c965-8LN9-hbMb-NUDe-3seH2h" TYPE="lvm2pv"
/dev/dm-5: UUID="92e09347-e56b-47cb-81b9-04c8ae66d46f" TYPE="swap"
/dev/dm-6: UUID="d374c929-ea69-456c-8c90-eff1a3ea7a22" TYPE="ext3"
/dev/dm-7: UUID="a5ba261e-d838-4248-909d-18c72e3ed534" TYPE="ext3"
 
Hi,

nodo02:~# blkid
/dev/sda1: UUID="d16eebda-c9c1-4421-999d-362f7e17ffa1" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda2: UUID="rezTt7-qj7J-c965-8LN9-hbMb-NUDe-3seH2h" TYPE="lvm2pv"
/dev/sdc1: UUID="d16eebda-c9c1-4421-999d-362f7e17ffa1" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc2: UUID="rezTt7-qj7J-c965-8LN9-hbMb-NUDe-3seH2h" TYPE="lvm2pv"
/dev/dm-3: UUID="d16eebda-c9c1-4421-999d-362f7e17ffa1" SEC_TYPE="ext2" TYPE="ext3"
/dev/dm-4: UUID="rezTt7-qj7J-c965-8LN9-hbMb-NUDe-3seH2h" TYPE="lvm2pv"
/dev/dm-5: UUID="92e09347-e56b-47cb-81b9-04c8ae66d46f" TYPE="swap"
/dev/dm-6: UUID="d374c929-ea69-456c-8c90-eff1a3ea7a22" TYPE="ext3"
/dev/dm-7: UUID="a5ba261e-d838-4248-909d-18c72e3ed534" TYPE="ext3"
Click to expand...

you see at the same uuid, that sda1, sdc1 and dm-3 the same partition is.
Linux see the partion twice (dual path) and multipath make on new device for you, so if one path is going down the device is accessible.
You can use /dev/dm-3 instead /dev/sda1 in /etc/fstab. Or, what i prefer, use the uuid:
Code: 
UUID=d16eebda-c9c1-4421-999d-362f7e17ffa1 /boot  ext3 defaults 0 1
The uuid is at all time the same - until you make a new filesystem on this partition.

Udo
 
You can use /dev/dm-3 instead /dev/sda1 in /etc/fstab. Or, what i prefer, use the uuid:
Code: 
UUID=d16eebda-c9c1-4421-999d-362f7e17ffa1 /boot  ext3 defaults 0 1
The uuid is at all time the same - until you make a new filesystem on this partition.
Udo
Click to expand...

Hi Udo, thanks for your help, but this change in fstab don't work correctly, boot fails. I make this steps:

1.- Install Proxmox 1.5
2.- Update Proxmox
Code: 
apt-get update
3.- Upgrade Proxmox
Code: 
apt-get upgrade
4.- install multipath
Code: 
apt-get install multipath-tools multipath-tools-initframfs
5.- Modify fstab. Change /dev/sda1 with UUID.
Code: 
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext3 defaults 0 1
UUID=708bc87a-4bc1-4275-869d-7ccdd4b0b6d0 /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
6.- Reboot

File /var/log/fsck/checkfs:

nodo01:/var/log/fsck# more checkfs
Log of fsck -C -R -A -a
Tue Jan 26 09:16:49 2010
fsck 1.41.3 (12-Oct-2008)
/dev/pve/data: clean, 20/655360 files, 79705/2621440 blocks
fsck.ext3: Device or resource busy while trying to open /dev/sda1
Filesystem mounted or opened exclusively by another program?
fsck died with exit status 8
Tue Jan 26 09:16:49 2010
----------------

Thanks
 
udo said:
Hi,
it seems that linux take the first device with that uuid (i don't know before) - so you must use the /dev/dm-3 in the fstab (if /dev/dm-3 points to /dev/sda1 after the new installation).

Udo
Click to expand...

Thank you so much, now the server boots fine.:D:D
 
udo said:
Hi,
it seems that linux take the first device with that uuid (i don't know before) - so you must use the /dev/dm-3 in the fstab (if /dev/dm-3 points to /dev/sda1 after the new installation).

Udo
Click to expand...

Thank you so much, server boot fine now.;):D
 
You must log in or register to reply here.
Top Bottom