How can I read and extract information from a DDS-1 tape today?
Clash Royale CLAN TAG#URR8PPP
up vote
2
down vote
favorite
I have a DDS-1 tape (Sony 60M 1.3 GB tape) and am hoping to find a tape drive where I can still read it. The problem is that while I can find the associated compatible tape drives online, I am not sure if the interface would work. The older tape drives all rely on a SCSI connection. I am wondering if I am able to use an adapter like the SCSI to USB iOmega:
and be able to plug and play with a Linux system? Thanks.
scsi tape
add a comment |
up vote
2
down vote
favorite
I have a DDS-1 tape (Sony 60M 1.3 GB tape) and am hoping to find a tape drive where I can still read it. The problem is that while I can find the associated compatible tape drives online, I am not sure if the interface would work. The older tape drives all rely on a SCSI connection. I am wondering if I am able to use an adapter like the SCSI to USB iOmega:
and be able to plug and play with a Linux system? Thanks.
scsi tape
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I have a DDS-1 tape (Sony 60M 1.3 GB tape) and am hoping to find a tape drive where I can still read it. The problem is that while I can find the associated compatible tape drives online, I am not sure if the interface would work. The older tape drives all rely on a SCSI connection. I am wondering if I am able to use an adapter like the SCSI to USB iOmega:
and be able to plug and play with a Linux system? Thanks.
scsi tape
I have a DDS-1 tape (Sony 60M 1.3 GB tape) and am hoping to find a tape drive where I can still read it. The problem is that while I can find the associated compatible tape drives online, I am not sure if the interface would work. The older tape drives all rely on a SCSI connection. I am wondering if I am able to use an adapter like the SCSI to USB iOmega:
and be able to plug and play with a Linux system? Thanks.
scsi tape
scsi tape
asked Sep 11 '17 at 21:54
user321627
1303
1303
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
2
down vote
accepted
Iomega were a common supplier of tape drives and accessories, catering for the home and small company market mostly. USB is not an ideal interface for such an adapter because of adapter software support, I/O speed and latency. If you can use a PCI or PCI-e card interface that would be an improvement. If the adapter you've found has the right specs, then it the USB-SCSI adapter should work....
... however, not all SCSI interfaces are the same. Both the physical connector and the electrical interface have changed over the years, so it is important to match the specs up, especially don't connect LV (low voltage) ports to non-LV ports! Internal (inside system box) cabling was often different to external (separate enclosure) cabling; internal cables are often "IDC" ribbon cables. Finally, a SCSI bus needs terminating, for which terminators (essentially an external dongle) can be obtained, but many devices include internal termination (=internal dongle) which can be switched on and off. Ensure you have exactly one termination dongle active for each bus or you will get errors!
You don't say whether you're using Linux, Windows or something else. I would advise Linux unless you already have drivers and other software: the drivers for Windows are not easy to find and were always fiddly to set up.
If/when you get the hardware connected up and a driver configured, don't stick your current tape in it first: test the drive can read and write properly with a blank tape!
If the data on the tape is valuable it may well be worth finding a company that will read it for you: setting this up will have a cost.
So in summary:
- it can be made to work
- be careful of SCSI cabling and interface standards, so:
- buy drive / cable / interface card as a group, not one-at-a-time.
- then get bus termination right
- linux will almost certainly drive it out the box; older windows boxen may be able to depending on driver support.
- tape drives often care very much about the tape block size. Make sure you know what the important values are for your tape and application.
add a comment |
up vote
0
down vote
In addition to @rivimey's answer,the link below documents the full hardware stack I'm currently using for extracting data from old DDS tapes:
https://github.com/KBNLresearch/forensicImagingResources/blob/master/doc/tape-dds.md
Needless to say this particular setup may or may not work for you, depending on the hardware you're using. The good news is that SCSI controllers are dirt cheap on eBay, so if one doesn't work you can always try another one.
On the software side of things, here's a little Python tool I've written that automates the more tedious bits of tape extraction such as determining the block size (this basically wraps around the dd
and mt
tools):
https://github.com/KBNLresearch/tapeimgr
I should add that so far I've only tested this tool with a limited number of DDS and DLT-IV tapes (and with a virtual tape library), but I haven't come across any major issues yet.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f391693%2fhow-can-i-read-and-extract-information-from-a-dds-1-tape-today%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
Iomega were a common supplier of tape drives and accessories, catering for the home and small company market mostly. USB is not an ideal interface for such an adapter because of adapter software support, I/O speed and latency. If you can use a PCI or PCI-e card interface that would be an improvement. If the adapter you've found has the right specs, then it the USB-SCSI adapter should work....
... however, not all SCSI interfaces are the same. Both the physical connector and the electrical interface have changed over the years, so it is important to match the specs up, especially don't connect LV (low voltage) ports to non-LV ports! Internal (inside system box) cabling was often different to external (separate enclosure) cabling; internal cables are often "IDC" ribbon cables. Finally, a SCSI bus needs terminating, for which terminators (essentially an external dongle) can be obtained, but many devices include internal termination (=internal dongle) which can be switched on and off. Ensure you have exactly one termination dongle active for each bus or you will get errors!
You don't say whether you're using Linux, Windows or something else. I would advise Linux unless you already have drivers and other software: the drivers for Windows are not easy to find and were always fiddly to set up.
If/when you get the hardware connected up and a driver configured, don't stick your current tape in it first: test the drive can read and write properly with a blank tape!
If the data on the tape is valuable it may well be worth finding a company that will read it for you: setting this up will have a cost.
So in summary:
- it can be made to work
- be careful of SCSI cabling and interface standards, so:
- buy drive / cable / interface card as a group, not one-at-a-time.
- then get bus termination right
- linux will almost certainly drive it out the box; older windows boxen may be able to depending on driver support.
- tape drives often care very much about the tape block size. Make sure you know what the important values are for your tape and application.
add a comment |
up vote
2
down vote
accepted
Iomega were a common supplier of tape drives and accessories, catering for the home and small company market mostly. USB is not an ideal interface for such an adapter because of adapter software support, I/O speed and latency. If you can use a PCI or PCI-e card interface that would be an improvement. If the adapter you've found has the right specs, then it the USB-SCSI adapter should work....
... however, not all SCSI interfaces are the same. Both the physical connector and the electrical interface have changed over the years, so it is important to match the specs up, especially don't connect LV (low voltage) ports to non-LV ports! Internal (inside system box) cabling was often different to external (separate enclosure) cabling; internal cables are often "IDC" ribbon cables. Finally, a SCSI bus needs terminating, for which terminators (essentially an external dongle) can be obtained, but many devices include internal termination (=internal dongle) which can be switched on and off. Ensure you have exactly one termination dongle active for each bus or you will get errors!
You don't say whether you're using Linux, Windows or something else. I would advise Linux unless you already have drivers and other software: the drivers for Windows are not easy to find and were always fiddly to set up.
If/when you get the hardware connected up and a driver configured, don't stick your current tape in it first: test the drive can read and write properly with a blank tape!
If the data on the tape is valuable it may well be worth finding a company that will read it for you: setting this up will have a cost.
So in summary:
- it can be made to work
- be careful of SCSI cabling and interface standards, so:
- buy drive / cable / interface card as a group, not one-at-a-time.
- then get bus termination right
- linux will almost certainly drive it out the box; older windows boxen may be able to depending on driver support.
- tape drives often care very much about the tape block size. Make sure you know what the important values are for your tape and application.
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Iomega were a common supplier of tape drives and accessories, catering for the home and small company market mostly. USB is not an ideal interface for such an adapter because of adapter software support, I/O speed and latency. If you can use a PCI or PCI-e card interface that would be an improvement. If the adapter you've found has the right specs, then it the USB-SCSI adapter should work....
... however, not all SCSI interfaces are the same. Both the physical connector and the electrical interface have changed over the years, so it is important to match the specs up, especially don't connect LV (low voltage) ports to non-LV ports! Internal (inside system box) cabling was often different to external (separate enclosure) cabling; internal cables are often "IDC" ribbon cables. Finally, a SCSI bus needs terminating, for which terminators (essentially an external dongle) can be obtained, but many devices include internal termination (=internal dongle) which can be switched on and off. Ensure you have exactly one termination dongle active for each bus or you will get errors!
You don't say whether you're using Linux, Windows or something else. I would advise Linux unless you already have drivers and other software: the drivers for Windows are not easy to find and were always fiddly to set up.
If/when you get the hardware connected up and a driver configured, don't stick your current tape in it first: test the drive can read and write properly with a blank tape!
If the data on the tape is valuable it may well be worth finding a company that will read it for you: setting this up will have a cost.
So in summary:
- it can be made to work
- be careful of SCSI cabling and interface standards, so:
- buy drive / cable / interface card as a group, not one-at-a-time.
- then get bus termination right
- linux will almost certainly drive it out the box; older windows boxen may be able to depending on driver support.
- tape drives often care very much about the tape block size. Make sure you know what the important values are for your tape and application.
Iomega were a common supplier of tape drives and accessories, catering for the home and small company market mostly. USB is not an ideal interface for such an adapter because of adapter software support, I/O speed and latency. If you can use a PCI or PCI-e card interface that would be an improvement. If the adapter you've found has the right specs, then it the USB-SCSI adapter should work....
... however, not all SCSI interfaces are the same. Both the physical connector and the electrical interface have changed over the years, so it is important to match the specs up, especially don't connect LV (low voltage) ports to non-LV ports! Internal (inside system box) cabling was often different to external (separate enclosure) cabling; internal cables are often "IDC" ribbon cables. Finally, a SCSI bus needs terminating, for which terminators (essentially an external dongle) can be obtained, but many devices include internal termination (=internal dongle) which can be switched on and off. Ensure you have exactly one termination dongle active for each bus or you will get errors!
You don't say whether you're using Linux, Windows or something else. I would advise Linux unless you already have drivers and other software: the drivers for Windows are not easy to find and were always fiddly to set up.
If/when you get the hardware connected up and a driver configured, don't stick your current tape in it first: test the drive can read and write properly with a blank tape!
If the data on the tape is valuable it may well be worth finding a company that will read it for you: setting this up will have a cost.
So in summary:
- it can be made to work
- be careful of SCSI cabling and interface standards, so:
- buy drive / cable / interface card as a group, not one-at-a-time.
- then get bus termination right
- linux will almost certainly drive it out the box; older windows boxen may be able to depending on driver support.
- tape drives often care very much about the tape block size. Make sure you know what the important values are for your tape and application.
answered Oct 22 '17 at 21:56
rivimey
1363
1363
add a comment |
add a comment |
up vote
0
down vote
In addition to @rivimey's answer,the link below documents the full hardware stack I'm currently using for extracting data from old DDS tapes:
https://github.com/KBNLresearch/forensicImagingResources/blob/master/doc/tape-dds.md
Needless to say this particular setup may or may not work for you, depending on the hardware you're using. The good news is that SCSI controllers are dirt cheap on eBay, so if one doesn't work you can always try another one.
On the software side of things, here's a little Python tool I've written that automates the more tedious bits of tape extraction such as determining the block size (this basically wraps around the dd
and mt
tools):
https://github.com/KBNLresearch/tapeimgr
I should add that so far I've only tested this tool with a limited number of DDS and DLT-IV tapes (and with a virtual tape library), but I haven't come across any major issues yet.
add a comment |
up vote
0
down vote
In addition to @rivimey's answer,the link below documents the full hardware stack I'm currently using for extracting data from old DDS tapes:
https://github.com/KBNLresearch/forensicImagingResources/blob/master/doc/tape-dds.md
Needless to say this particular setup may or may not work for you, depending on the hardware you're using. The good news is that SCSI controllers are dirt cheap on eBay, so if one doesn't work you can always try another one.
On the software side of things, here's a little Python tool I've written that automates the more tedious bits of tape extraction such as determining the block size (this basically wraps around the dd
and mt
tools):
https://github.com/KBNLresearch/tapeimgr
I should add that so far I've only tested this tool with a limited number of DDS and DLT-IV tapes (and with a virtual tape library), but I haven't come across any major issues yet.
add a comment |
up vote
0
down vote
up vote
0
down vote
In addition to @rivimey's answer,the link below documents the full hardware stack I'm currently using for extracting data from old DDS tapes:
https://github.com/KBNLresearch/forensicImagingResources/blob/master/doc/tape-dds.md
Needless to say this particular setup may or may not work for you, depending on the hardware you're using. The good news is that SCSI controllers are dirt cheap on eBay, so if one doesn't work you can always try another one.
On the software side of things, here's a little Python tool I've written that automates the more tedious bits of tape extraction such as determining the block size (this basically wraps around the dd
and mt
tools):
https://github.com/KBNLresearch/tapeimgr
I should add that so far I've only tested this tool with a limited number of DDS and DLT-IV tapes (and with a virtual tape library), but I haven't come across any major issues yet.
In addition to @rivimey's answer,the link below documents the full hardware stack I'm currently using for extracting data from old DDS tapes:
https://github.com/KBNLresearch/forensicImagingResources/blob/master/doc/tape-dds.md
Needless to say this particular setup may or may not work for you, depending on the hardware you're using. The good news is that SCSI controllers are dirt cheap on eBay, so if one doesn't work you can always try another one.
On the software side of things, here's a little Python tool I've written that automates the more tedious bits of tape extraction such as determining the block size (this basically wraps around the dd
and mt
tools):
https://github.com/KBNLresearch/tapeimgr
I should add that so far I've only tested this tool with a limited number of DDS and DLT-IV tapes (and with a virtual tape library), but I haven't come across any major issues yet.
answered Dec 5 at 17:17
johan
1512
1512
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f391693%2fhow-can-i-read-and-extract-information-from-a-dds-1-tape-today%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown