3 Jul
2005
3 Jul
'05
12:59 p.m.
On Sun, 3 Jul 2005, Dennis Boone wrote:
The block and record sizes are written on the tape label: 80 and 3200
respectively. However, adding these to the command line options don't fix
anything.
The dd command I used is simple:
dd if=/dev/st0 of=tape.img
I've since learned that I want to use the /dev/nrst0 device handle so that
the tape does not rewind after every file operation. That's handy, but
doesn't solve the problem.
I tell ya, I can understand that complicated shit will take time, but when
something that should be easy gives me more grief than the most difficult
things I've ever worked on, it makes you wonder.
--
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger http://www.vintage.org
[ Old computing resources for business || Buy/Sell/Trade Vintage Computers ]
[ and academia at www.VintageTech.com || at http://marketplace.vintage.org ]
However, if I
try to READ a file, and I've tried this with dd and
Eric Smith's tapedump utility and whatnot, it always returns with
0 files read. It apparently sees the file marks as it will say its
reading file 1, file 2, etc., but it never actually dumps anything.
I've tried the multiple tapes at multiple densities and they are
tapes I've read before on another system.
Any idea what block size was used to write the tapes? Any relevant
messages in the kernel log (i.e. output of "dmesg")? Which /dev/device
are you using to access the drive? What's the dd command you're using? WTF???
Sounds like _my_ life. :-)