Hello,
I need to image an internal Hard Drive (68 Pin SCSI wide). Does anyone have a way for me to do this? i have looked for old Tableau T4 write blockers with no success. I have a IDE 40 pin fast block from guidance software however but I'm having a difficult time finding a 40 pin male IDE to a 68 pin SCSI Male adapter. Any help would be greatly appreciated. thank you! o
Hello,
I need to image an internal Hard Drive (68 Pin SCSI wide). Does anyone have a way for me to do this? i have looked for old Tableau T4 write blockers with no success. I have a IDE 40 pin fast block from guidance software however but I'm having a difficult time finding a 40 pin male IDE to a 68 pin SCSI Male adapter. Any help would be greatly appreciated. thank you! o
IDE and SCSI are DIFFERENT protocols, you CANNOT connect a SCSI disk to an IDE interface through a "pin adapter" 😯 .
A 40 pin male IDE to 68 pin SCSI adapter is something that does not exist (and if it would exist would not work).
If you really-really need a hardware write blocker, then you need a SCSI one.
Not something that is easily available nowadays unfortunately (
Maybe (just maybe) you can use a (rare) SCSI device to IDE converter card, *like*
http//
or a (more common) SCSI device to USB converter, *like*
http//
they were common enough to connect JAZ, ZIP and similar SCSI devices to non-SCSI PC's, but whether they will work with a write blocker is to be checked, all in all I personally would rather use a WinFE or a Read Only Live Linux.
jaclaz
Thank you for the reply
Jpynes, here are a few solutions
(note that SCSI is referenced as SAS (Serial Attached SCSI)
Two
Or you can use dedicated hardware for imaging (a bit more expensive solution),
such as the
Jpynes, here are a few solutions
(note that SCSI is referenced as SAS (Serial Attached SCSI)Two
scsi write blockers from paralan (internal or external), another internal from Tableau and one external UltraBlock SAS USB3 to SAS Bridge. Or you can use dedicated hardware for imaging (a bit more expensive solution),
such as theDitto Forensic FieldStation with the Ditto Expansion Module for SAS (Serial Attached SCSI) devices (part # 31030-1560-0000).
Which again is not the same thing (though it has many points in common, the SCSI command set is used in SAS, which does not mean AT ALL signal compatibility).
SAS is NOT SCSI, it is Serial Attached Scsi, SCSI in itself is a pretty much PARALLEL protocol (hence the 50 or 68 pin connector).
It'ìs just like ATA devices, Serial ATA is NOT the same as Parallel ATA.
A command set (respectively ATA and SCSI) is transported on a DIFFERENT BUS (respectively Parallel and Serial), or if you prefer
SATAIDE/PATA=SASSCSI
a converter is needed to connect a SCSI device to a SAS bus just like a converter is needed to connect a IDE/PATA device to a Sata bus.
The Paralan SR14a and SR15a are out of production since several years, if you follow the instructions on the page you posted a link to
Visit the Paralan Store and click on Voom page for data duplication and forensics products.
you willl see how they are not listed in the shop. (as well as some old Voom models that did support SCSI and that are not available since a long time).
jaclaz
Thanks for all the help guys, i was able to find a Tableau T4es that is a SCSI write blocker. It has the 68 pin connection i needed. thanks again for all the help, the FF community here is awesome. D D D D D
Which again is not the same thing (though it has many points in common, the SCSI command set is used in SAS, which does not mean AT ALL signal compatibility).
Well, they both use the SCSI command set - the interface is different as you said.
"SAS's backward compatibility with previous generation SCSI software and middleware also makes it easy to incorporate legacy components, hosts and drives, into evolving SAS topologies, eliminating new training or integration costs and the need for modifications to legacy software."
I can see why there may be a bit difficult finding an adapter though roll
Maybe a bootable CD and some digging into the last century closet for an old adaptec scsi card, will be a better and much cheaper option ..
i was able to find a Tableau T4es that is a SCSI write blocker. It has the 68 pin connection i needed.
Great )
I am not sure about the reason why you posted the quote, I bolded a couple words, just in case
"SAS's backward compatibility with previous generation SCSI software and middleware also makes it easy to incorporate legacy components, hosts and drives, into evolving SAS topologies, eliminating new training or integration costs and the need for modifications to legacy software." link
There is NO hardware backward compatibility.
I can see why there may be a bit difficult finding an adapter though roll
Again they would not be adapters, but rather converters, and there is simply no market need for them in the "direction needed".
There are rather easily available converters that allow to mount non-Scsi devices on Scsi buses as there may still exist in operation some oldish hardware with a broken disk or that became too small, ATAPI to SCSI or IDE/PATA to SCSI
http//
http//
or SATA to SCSI
http//
The ones that work in the "direction needed" are more or less of the kind I posted example links to, largely obsolete nowadays, and only produced at the time (let's say circa 2000/2003) when there were still lots of Scsi peripherals (many in the "MAC" world) such as Zip, Jaz, Orb and similar (+ all the various external disk cases for Scsi disks) and USB (2.0) was a new kid on the block built-on on "every" computer, whilst Scsi was slowly fading away even in the "professional" workstations and servers.
Maybe a bootable CD and some digging into the last century closet for an old adaptec scsi card, will be a better and much cheaper option ..
But it wouldn't in any way solve the OP problem, a good ol' Adaptec will have no write blocking, if hardware hard blocking is a requisite a Scsi write blocker would be anyway neededl.
i was able to find a Tableau T4es that is a SCSI write blocker. It has the 68 pin connection i needed.
Good. )
jaclaz
I am not sure about the reason why you posted the quote
You missed the "..also makes it easy to incorporate legacy components, hosts and drives, into evolving SAS topologies" - the fact that it just didn't happen is another story 😉
Maybe a bootable CD and some digging into the last century closet for an old adaptec scsi card, will be a better and much cheaper option ..
But it wouldn't in any way solve the OP problem, a good ol' Adaptec will have no write blocking, if hardware hard blocking is a requisite a Scsi write blocker would be anyway needed.
Why exactly wouldn't a Linux bootable CD such as
all in all I personally would rather use a WinFE or a Read Only Live Linux.
Why exactly wouldn't a Linux bootable CD such as
this and read-only mount of the scsi device work? ?
Is this Live CD really read-only?