Mount USB (for backups only) in VMWare ESX 2.5.3?
Hi, Experts,
I have a VMWare ESX server that - for exotic reasons I am not sure I fully understand - seems limited to running version 2.5.3 --- when I try to upgrade versions, it fails to boot. Since I am running three enterprise-level servers for my company on it, it is thought unwise to experiment further with that hardware (HP ML350, I believe). (We *may* visit that issue later, in another question...)
I offer that explanation up front to head off all of the "Upgrade your Version" answers. If it were only that simple.
I have a burning need to connect my 1TB USB backup drive to the ESX server itself (*not for use with Guest Operating Systems) in the hopes that I might perform a full stateful backup of the servers (at 02:00 or so) and thus be prepared for disaster, if it should present itself. (Again.)
Watching the VMWare Console (I log in at the linux prompt - it reminds me of home) and plug in the drive, I get:
"VMWARE: Device that would have been attached as scsi disk sda at scsi0, channel 0, id 0, lun 0
Has not been attached because this path could not complete a READ command eventhough a TUR worked.
result = 0x0000002 key 0x5, asc = 0x24, ascq = 0x0
VMWare: Device that would have been attached as scsi disk sda at scsci2, channel 0, id 0, lun 0
Has not been attached because it is a duplicate path or on a passive path
scsi register_host starting finish
scsi register_host done with finish
WARNING: USB Mass Storage data integrity not assured
USB MAss Storage device found at 2
USB Mass Storage support registered.
floppy0: unexpected interrupt
floppy0: sensei repl[0]=90
usb.c: USB disconnect on device 2
hub.c: USB new device connect on bus1/2, assigned device number 3
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
usb.c: USB disconnect on device 3
hub.c: USB new device connect on bus1/2, assigned device number 4
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 4"
So, it would appear that the USB drive is seen, recognized, but VMWare doesn't know where to put it. Or am I reading that right? I can't seem to mount it manually, even though I created a USB mount point in /mnt. (Which is where I ->think<- it should go - I'm not fully wedded to my ignorance, though...)
Additional information: the USB drive in question was reformatted from NTFS to EXT3, and thus should make VMWare/Linux very happy. I feel as if we're very close on this.
I'm not sure what to do/where to go at this point. Until two weeks ago, I had only passing acquaintance with VMWare, so I'm still figuring out how to make it all work. I figure that someone, somewhere, knows how to make this happen - it's just not in any of the bulletins, FAQ's, or Knowledge Base Articles yet, possibly because it's so simple as to be "beneath notice". Could someone help illuminate a solution?
I have a VMWare ESX server that - for exotic reasons I am not sure I fully understand - seems limited to running version 2.5.3 --- when I try to upgrade versions, it fails to boot. Since I am running three enterprise-level servers for my company on it, it is thought unwise to experiment further with that hardware (HP ML350, I believe). (We *may* visit that issue later, in another question...)
I offer that explanation up front to head off all of the "Upgrade your Version" answers. If it were only that simple.
I have a burning need to connect my 1TB USB backup drive to the ESX server itself (*not for use with Guest Operating Systems) in the hopes that I might perform a full stateful backup of the servers (at 02:00 or so) and thus be prepared for disaster, if it should present itself. (Again.)
Watching the VMWare Console (I log in at the linux prompt - it reminds me of home) and plug in the drive, I get:
"VMWARE: Device that would have been attached as scsi disk sda at scsi0, channel 0, id 0, lun 0
Has not been attached because this path could not complete a READ command eventhough a TUR worked.
result = 0x0000002 key 0x5, asc = 0x24, ascq = 0x0
VMWare: Device that would have been attached as scsi disk sda at scsci2, channel 0, id 0, lun 0
Has not been attached because it is a duplicate path or on a passive path
scsi register_host starting finish
scsi register_host done with finish
WARNING: USB Mass Storage data integrity not assured
USB MAss Storage device found at 2
USB Mass Storage support registered.
floppy0: unexpected interrupt
floppy0: sensei repl[0]=90
usb.c: USB disconnect on device 2
hub.c: USB new device connect on bus1/2, assigned device number 3
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 3
usb.c: USB disconnect on device 3
hub.c: USB new device connect on bus1/2, assigned device number 4
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 4"
So, it would appear that the USB drive is seen, recognized, but VMWare doesn't know where to put it. Or am I reading that right? I can't seem to mount it manually, even though I created a USB mount point in /mnt. (Which is where I ->think<- it should go - I'm not fully wedded to my ignorance, though...)
Additional information: the USB drive in question was reformatted from NTFS to EXT3, and thus should make VMWare/Linux very happy. I feel as if we're very close on this.
I'm not sure what to do/where to go at this point. Until two weeks ago, I had only passing acquaintance with VMWare, so I'm still figuring out how to make it all work. I figure that someone, somewhere, knows how to make this happen - it's just not in any of the bulletins, FAQ's, or Knowledge Base Articles yet, possibly because it's so simple as to be "beneath notice". Could someone help illuminate a solution?
ASKER
>> Is there any other linux machine in your network ..?
Not yet, but if I'm pressed, I will make it happen. I think I see where you're headed with this approach...
>> Do you have a USB stick lying around ...?
Yes. I have a 4GB stick, and we have 2 GB stick somewhere around the office. I also borrowed/abused another portable USB drive for this purpose: Ubuntu sees it and mounts it properly (automatically - 8.04 is such a wonderful OS!) and claims it as its own - that's where we learned the EXT3 instead of NTFS partition trick.
Not yet, but if I'm pressed, I will make it happen. I think I see where you're headed with this approach...
>> Do you have a USB stick lying around ...?
Yes. I have a 4GB stick, and we have 2 GB stick somewhere around the office. I also borrowed/abused another portable USB drive for this purpose: Ubuntu sees it and mounts it properly (automatically - 8.04 is such a wonderful OS!) and claims it as its own - that's where we learned the EXT3 instead of NTFS partition trick.
I don't remember the exact kernel version of ESX 2.5, but out of memory it's not newer than 2.4.9 and usb mass storage support in the linux kernel started to be useful with 2.4.11...
As you might have guessed already, upgrading the kernel on Esx is not an option.
Do your USB sticks work when plugged into the ESX host or do they produce the same results?
As you might have guessed already, upgrading the kernel on Esx is not an option.
Do your USB sticks work when plugged into the ESX host or do they produce the same results?
ASKER
Actually, I haven't tried the USB sticks. (Yet.) I'm not in the office today - I just couldn't sleep with being "almost there". Naturally, the ESX server is "beyond reach" of the VPN connection - so I thought I'd see if anyone else had tried and succeeded in mounting a USB drive for backup purposes.
I'll try them first thing in the morning, though. What is indicated if they successfully mount?
I'll try them first thing in the morning, though. What is indicated if they successfully mount?
I use my machine at work as a hub for connecting to our datacenter servers...
Check the output of 'cat /proc/partitions' before and after you plugged in the USB device.
Afterwards, you should see additional devices, like f.ex. sdb and sdb1. That would be the device names of your USB sticks.
If there's no change in the output, we have the same problem as with the disk (BTW: it might take a few minutes for the USB device to settle on the bus), oh, and check the 'dmesg' output as you've already done.
Check the output of 'cat /proc/partitions' before and after you plugged in the USB device.
Afterwards, you should see additional devices, like f.ex. sdb and sdb1. That would be the device names of your USB sticks.
If there's no change in the output, we have the same problem as with the disk (BTW: it might take a few minutes for the USB device to settle on the bus), oh, and check the 'dmesg' output as you've already done.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So, basically, I'm beating a dead horse. I need to upgrade to the latest version of VMWare, which is not only gonna' cost some bux, but may not function on the target machine after all. Solution set is shrinking, looking more and more like a proxy backup server or some other network-based solution, right? Because even if/when I force this twonky to accept the 1TB USB drive, it will still take a month (give or take) to actually complete the backup.
Blast!
I was hoping to achieve a nice, portable backup repository - just in case the worst was to happen... ...I guess I could arrange an off-site backup or something. Ah well, VMWare was otherwise perfect there had to be hang-ups hiding somewhere in the mix... And I can't release this to the corporation without a disaster recovery plan in place...
Am i reading this right?
Blast!
I was hoping to achieve a nice, portable backup repository - just in case the worst was to happen... ...I guess I could arrange an off-site backup or something. Ah well, VMWare was otherwise perfect there had to be hang-ups hiding somewhere in the mix... And I can't release this to the corporation without a disaster recovery plan in place...
Am i reading this right?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is one more case where I should have listened more carefully to the initial responses - USB 1.1 is insufficient for the task of mass data backups --- and had I paid more attention to the level supported, I wouldn't have driven this question as far as I had. It turns out that I get better timing connecting to a backup-server, then to the external usb terabyte drive. Thanks for being so patient, guys!!!
Just for testing purposes: Do you have a USB stick lying around we could use for testing USB support at all?