SLES10sp4
ZCM10sp3
ESXi5
Client needs more space for imaging....OK that seems pretty easy as I already did this once on this server.
So I created a new mount point under the content-repo directory (images2)
added a hard drive in the machine config larger than the client wants, set it as controller 0, drive 3 (also tried controller 1 drive 0 with no success).
ran a echo "- - -" > /sys/class/scsi_host/host0/scan (and echo "- - -" > /sys/class/scsi_host/host1/scan just to be sure)
no 3rd drive (sdc) in /dev
rebooted
still no third drive.
I am at a loss here, not quite understanding the issue.
Was thinking about expanding the original 2nd drive but that is greyed out (VM issue? so that is an option if there is a VM guy that can tell me where to fix that)
I did not setup the VM environment, so am still discovering things done in a way different than I would normally, so that might be one of the reasons things are not working like I think they should on that side.
Any and all thoughts appreciated!
WO
ZCM10sp3
ESXi5
Client needs more space for imaging....OK that seems pretty easy as I already did this once on this server.
So I created a new mount point under the content-repo directory (images2)
added a hard drive in the machine config larger than the client wants, set it as controller 0, drive 3 (also tried controller 1 drive 0 with no success).
ran a echo "- - -" > /sys/class/scsi_host/host0/scan (and echo "- - -" > /sys/class/scsi_host/host1/scan just to be sure)
no 3rd drive (sdc) in /dev
rebooted
still no third drive.
I am at a loss here, not quite understanding the issue.
Was thinking about expanding the original 2nd drive but that is greyed out (VM issue? so that is an option if there is a VM guy that can tell me where to fix that)
I did not setup the VM environment, so am still discovering things done in a way different than I would normally, so that might be one of the reasons things are not working like I think they should on that side.
Any and all thoughts appreciated!
WO