Skip to main content
9 events
when toggle format what by license comment
Apr 14, 2021 at 0:00 vote accept Dmitry Brant
Apr 14, 2021 at 0:00 answer added Dmitry Brant timeline score: 1
Apr 12, 2021 at 8:54 comment added Kevin Nakamoto It is almost impossible to read data beyond EOD, because this is controlled by drive firmware level. I found an interesting way to do this though it is very risky: pages.cs.wisc.edu/~plonka/sysadmin/backup.html
Apr 11, 2021 at 22:25 comment added Mark Plotnick I don't know how to read past EOD. Are there any error messages in the system logs? Might try mt -f /dev/rst0 setblk 0 to ensure the drive is in variable block size mode, and try to read the tape again.
Apr 11, 2021 at 20:40 comment added Dmitry Brant @MarkPlotnick Yep, the status at file 1 is EOD, which I suppose means that the drive believes that the data ends there. But this is very strange because there are four tapes that have the same behavior. I'm starting to suspect that the backup software that wrote these tapes somehow corrupted them (e.g. reinitialized the tape, causing the EOD marker to be written at the beginning)? I don't suppose there are ways to make the drive read past EOD?
Apr 11, 2021 at 19:07 comment added Mark Plotnick Does mt -f /dev/nrst0 eod; mt -f /dev/nrst0 status show you're at file 1 or something else?
Apr 10, 2021 at 12:24 comment added Dmitry Brant I wasn't specifying a block size, but even if I try various different block sizes the result is the same. If it was an issue of block sizes, wouldn't I be getting different types of errors than an end-of-tape condition?
Apr 10, 2021 at 7:53 comment added Kevin Nakamoto What block size ("bs" argument) you used when "dd" command? As you might know, the actual value of bs depends on the software that was used to write the tape.
Apr 10, 2021 at 3:55 history asked Dmitry Brant CC BY-SA 4.0