Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #228636 > unrolled thread

OT: amanda/tape drive problem

Back to article view | Back to linux.debian.user

Contents

  OT: amanda/tape drive problem ghe2001 <ghe2001@pm.me> - 2020-11-13 20:30 +0100
    Re: OT: amanda/tape drive problem Dan Ritter <dsr@randomstring.org> - 2020-11-13 21:00 +0100
      Re: OT: amanda/tape drive problem ghe2001 <ghe2001@protonmail.com> - 2020-11-13 21:30 +0100
        Re: OT: amanda/tape drive problem Dan Ritter <dsr@randomstring.org> - 2020-11-13 22:00 +0100
          Re: OT: amanda/tape drive problem ghe2001 <ghe2001@protonmail.com> - 2020-11-13 22:40 +0100
    Re: OT: amanda/tape drive problem Charles Curley <charlescurley@charlescurley.com> - 2020-11-13 21:10 +0100
      Re: OT: amanda/tape drive problem ghe2001 <ghe2001@pm.me> - 2020-11-13 21:40 +0100

#228636 — OT: amanda/tape drive problem

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I know this is way OT, but the amanda-users list isn't working, not for me anyway, and this list is full of knowledgeable people.

The problem is that my Quantum LTO-5 drive (4 or 5 years old) is writing for a while, then failing.  It reads, does 'mt' things, and amcheck just fine.  Amreport says something like:

"sbox.slsware.net:/home                    20201113082312 0  75940100k dump done, terminated while waiting for writing"

I can't find what that means.  There's nothing in the logs or on the web.

According to amcheckdump --verbose:

...
Validating image srv.slsware.net:/lib dumped 20201113081545 level 0
Reading volume sls-6 file 39
270528 kb
application stderr: /bin/tar: Unexpected EOF in archive
application stderr: /bin/tar: Error is not recoverable: exiting now
275456 kb
/bin/tar exited with status 2
38 images successfully validated.
37 images not validated.

It seems to have successfully written things, then quit with a fatal, unrecoverable error.

Anybody seen this before?

--
Glenn English


-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJfrtmmACEJEObKK1bRaqt3FiEExEbtoeXBeE9fruv35sor
VtFqq3ekegf/byKCaCoijtslWTefVj1mikWtBIT/5gx8tSWp48Iokdtzv7Ge
7nW17tpAi4wXAY0m7EJ7OSCqCuXqzwqAKMsE77Ozyx9jPlFEkjsHQrLGu8Qp
aVgER+yMyA5M1h8CG+eKMTJN/9DxCZfDNos6+1/RSXXwDc5kS5ALYGNnL6am
p6LKT+qMYDvTcXvvZstXy8VSfQIdazHoJ7zkDJ2D4Rl2pM73Po5Mm1NVqFu3
/ydtfIuQu4VPNYt+c6ntJxlcpcbUd4ZzZ5coklRpCcZUpJWuebqrgdIECt8T
sYhiqP41mRreZhEN2aUxrKdhUsovlimgWXoY/qdXY4fie/TLFIXUYQ==
=S1Aw
-----END PGP SIGNATURE-----

[toc] | [next] | [standalone]

#228637

ghe2001 wrote: 
> I know this is way OT, but the amanda-users list isn't working, not for me anyway, and this list is full of knowledgeable people.
> 
> The problem is that my Quantum LTO-5 drive (4 or 5 years old) is writing for a while, then failing.  It reads, does 'mt' things, and amcheck just fine.  Amreport says something like:
> 
> "sbox.slsware.net:/home                    20201113082312 0  75940100k dump done, terminated while waiting for writing"
> 
> I can't find what that means.  There's nothing in the logs or on the web.
> application stderr: /bin/tar: Unexpected EOF in archive
> application stderr: /bin/tar: Error is not recoverable: exiting now
> 275456 kb
> /bin/tar exited with status 2
> 38 images successfully validated.
> 37 images not validated.
> 
> It seems to have successfully written things, then quit with a fatal, unrecoverable error.

It doesn't ring a bell, but did you do the diagnostic steps of:

- get a dump of what's on the problem tape now, confirm which
  part is good
- write a different file to a new tape
- read it back and confirm MD5 or SHA1/256 hash matches
- write your file to the new tape, read it back and confirm hash
  matches
- try writing your file to the problem tape again

-dsr-

[toc] | [prev] | [next] | [standalone]

#228640

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, November 13, 2020 7:51 PM, Dan Ritter <dsr@randomstring.org> wrote:

> It doesn't ring a bell, but did you do the diagnostic steps of:
>
> -   get a dump of what's on the problem tape now, confirm which
>     part is good
>
> -   write a different file to a new tape
> -   read it back and confirm MD5 or SHA1/256 hash matches
> -   write your file to the new tape, read it back and confirm hash
>     matches
>
> -   try writing your file to the problem tape again

It's not a bad tape, it's a hardware/software problem, I think.  This shows up on every tape in the pile.

--
Glenn English


-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJfruvEACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDLkhwgAxwdgAVvq+MyFiKYnb7VGb4rnLr4N0nEF2GSEpZQA80tdAb+4
3SFLGjwmZolSDY2xBTF10P7uJTkHpw2apwr6sAr5QfNR9NUTaice+pm0am6v
Ky/QGtV94tzFgTxmi1EywDkgTV0mIedxsIvvWf73zIOKbeE92k3j2ZUW2B55
5XJ1zOP0UV5tCB1+vbUm6F8h2GGNt9adQyvX8rAMBqUMX4UI32XAXrqwMz+O
mm7imCIElyZtzyvs0IZXWKBYXG5ZucWM7yqfeCWJPhmEPxEA2aZMOXDdy1I8
0TzEgsuzt7f+YcACjqTIA9O+japIPfPEkvGDLDzWuyW+YvE9jA/WiA==
=sMGo
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#228642

ghe2001 wrote: 
> On Friday, November 13, 2020 7:51 PM, Dan Ritter <dsr@randomstring.org> wrote:
> 
> > It doesn't ring a bell, but did you do the diagnostic steps of:
> >
> > -   get a dump of what's on the problem tape now, confirm which
> >     part is good
> >
> > -   write a different file to a new tape
> > -   read it back and confirm MD5 or SHA1/256 hash matches
> > -   write your file to the new tape, read it back and confirm hash
> >     matches
> >
> > -   try writing your file to the problem tape again
> 
> It's not a bad tape, it's a hardware/software problem, I think.  This shows up on every tape in the pile.

Right, that routine is to establish whether you have a tape
problem or a hardware problem.

It won't be a software problem. The tape interface hasn't
changed for decades.

Sorry. Are you committed to tape? 2TB spinning disks are
remarkably cheap these days.

-dsr-

[toc] | [prev] | [next] | [standalone]

#228643

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, November 13, 2020 8:52 PM, Dan Ritter <dsr@randomstring.org> wrote:

> Right, that routine is to establish whether you have a tape
> problem or a hardware problem.

OK. I'm almost positive I have a hardware problem.  But the programmer's mantra == "It's never a hardware problem"...

> Sorry. Are you committed to tape? 2TB spinning disks are
> remarkably cheap these days.

Well, I was until this morning :-)

--
Glenn English
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJfrvv7ACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDJEVwgApDbkge0D+gEBWeQ0tdOE3JdLqrd4+OeCOiL2/rs6YfHR6AUa
h3+VkmKFl22QpsDqNnb44a3ocAHuCVWrw0kScd88ooxO6PecPOioJxA7CKA1
w05NKoohOcXjBF5iCrBL+EpFDxgSoS4PDhHrw/ZmdCAxqGbgEG1Fn4QKtzff
hH/zvfZRkJW6mYeV41Rw3su0YDUja8S0cv4A7qrBGQJaOgDQHtNNH6bEBHrn
zJ9NEt0tCebVCUr6IH8QDwwYHoGeZWQR2VIXlT9z3aGrXzElnQFjjoqpO9bE
MBvie7GGIWAZW6MApYU6L+0WD28NhumtAphP7Eu7MMo0ZJnHJ7UZlw==
=UAL8
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#228638

[Multipart message — attachments visible in raw view] — view raw

On Fri, 13 Nov 2020 19:08:24 +0000
ghe2001 <ghe2001@pm.me> wrote:

> The problem is that my Quantum LTO-5 drive (4 or 5 years old) is
> writing for a while, then failing.  It reads, does 'mt' things, and
> amcheck just fine.

Have you cleaned the drive lately? (Or is that still necessary? It's
been a while since I've used physical tapes.)

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#228641

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, November 13, 2020 8:07 PM, Charles Curley <charlescurley@charlescurley.com> wrote:

> Have you cleaned the drive lately? (Or is that still necessary? It's
> been a while since I've used physical tapes.)

Yup, several times.  And cleaning does seem to be necessary, from time to time.

--
Glenn English
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJfrulHACEJEObKK1bRaqt3FiEExEbtoeXBeE9fruv35sor
VtFqq3fS6ggA0e8RO5DoyGk2jjCDocFPjDv+FolrAFkJCBYmAIHxsr9hX4KN
wY2mS2N0q38oJ/zbZwW0QuRJ1rbHKPmu6g2nsnxFD4ScF32aeH5ngqW2LnfG
vrjlELn02dxGLYeH9KM9Tucl9la7P3cXUAlxMeLarfumFbNxl6gsv+WF92rR
JyxznURS1qDobppkDHawzzUhZnZXpTWivOpXjqmr2r+pI4iCptP5nb72ppCx
JkFj5MtAyYl3V8PasM/22CiYLWjF3BazufFqptJGg4dxHkNalxXMuYNmEhwk
7bl/yRroSPHn36T9jIDsI4YElT/R+BzbqBr+ylH2I7G+i208OzlMyg==
=argD
-----END PGP SIGNATURE-----

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web