On Sun, 12 Dec 2010 00:22:13 -0800, "W"
wrote:
Here is an example of when I needed to mount a SCSI device on a host through
USB or eSATA. Today I had a Windows 2000 box that I needed to virtualize
and bring over to a server. I can run the utility to turn the computer
into a virtual machine image, but how do I get the files from this box to
the destination. I have SCSI on the box and USB 1.0. Using USB 1.0, I
can mount a SATA drive, but the conversion utility tells me it will take 17
hours to run. If I can use a SCSI device that cuts down to two hours.
Assuming I target the files to a SCSI drive, once the conversion finishes,
now I need to get those files over to the virtual server. What I would
like to do is physically remove that SCSI device, attach it to an adapter to
USB or eSATA, and then hot attach it to the virtual server.
My application is simply getting quick connectivity to the drive, in order
to transfer data. I have no requirements for any kind of enclosure, and
this is not long term storage.
Maybe you can do it with two converters, SCSI to IDE and IDE to SATA
Here are a couple of SCSI to IDE.
From Walmart, of all places, with links to a couple of other products
http://www.walmart.com/ip/StarTech.c...i_sku=13214968
This allows use of IDE drive on SCSI controller, if I've read things
correctly. The company also makes a IDE to SATA that allow use of
SATA drives on IDE controllers. (I bought lots of stuff from them
including some IDE to SATA adapters, but not the SCSI to IDE,
but I haven't used the SSCI to IDE.)
http://www.addonics.com/products/io/ide_scsi.asp
Unfortunately, I don't have an easy path to using SCSI. So I'm stuck with
a 17 hour job that will run to a SATA drive.
--
W
"Maxim S. Shatskih" wrote in message
...
What is the need in this?
SCSI drives are much more expensive.
So, you do the following:
- turn off the enclosure
- plug the usual SATA drive to it
- turn on the enclosure
- attach it to the host using USB, 1394 or eSATA. In eSATA case, you
sometimes need to restart the host controller's driver using Windows Device
Manager or the appropriate Linux/FreeBSD command line tools
- go on