This content has been marked as final. Show 8 replies
Set up Details :
- 2 static ip's
a. VM Server 3.2.1 ( RAM : 4GB Storage : 80GB + 500GB )
b. VM Manager 3.2.1 ( RAM : 4GB Storage : 150GB )
- I was able to identify the VM Server from VM Manager successfully,
but unable to identify the storage.
Post the output of multipath -ll
# multipath -ll
SATA_WDC_WD800JD-75HWD-WMAJ96303246_ dm-0 ATA,WDC WD800JD-75HK
size=75G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
`- 1:0:0:0 sdb 8:16 active ready running
Can you see the 80G sdb?
But how about my additonal storage of 500GB / dev/sda ?
Man...we have been over this dozens of time in this forum. You can't use any of the free space on the disk that is used for the VM Server installation itself. That "disk" is dedicated to the the VM Server installation ONLY.
use the 80G LUN for the installation and you will able to the use the 500 GB sda.. or reconfigure your storage taking this into consideration.
thanks for your prompt response.
I am aware of that we can't use any free spaces where the VM is installed.Hence the additional storage added to the server.
1. Install VM Server on 80GB HD ( /dev/sdb)
2. Later, i added 500GB to the storage ( no installation - just the disk ) ( /dev/sda)
Same configuration worked fine in 3.0, now i am not able to identified the additional disk which was added later with 3.2.1.
Why are there partitions on /dev/sda ?
/dev/sda1 1 13 104391 83 Linux
/dev/sda2 14 405 3148740 83 Linux
/dev/sda3 406 536 1052257+ 82 Linux swap / Solaris
Sorry I missed the partitions on /dev/sda
I you don't need anything on /dev/sda remove the partitions from /dev/sda. Reboot and see if you can then see /dev/sda as being available