Date: Wed, 20 Jan 1999 10:10:36 -0700 (MST) From: "Mark J. Sommer" <msommer@argotsoft.com> To: kpielorz@tdx.co.uk (Karl Pielorz) Cc: freebsd@netsys.h, freebsd-questions@FreeBSD.ORG Subject: Re: Amrecover error message deciphered. Message-ID: <199901201710.KAA28285@argotsoft.com> In-Reply-To: <36A5FED5.2522261@tdx.co.uk> from Karl Pielorz at "Jan 20, 99 04:05:41 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> "Mark J. Sommer" wrote: > > > Sorry to interject, but this may or may not be of use. > > Please do! - I was hoping someone would... If you'd seen the previous > messages, density codes etc. have been mentioned - I had a similar problem > _ages_ ago (with a drive I no longer had), so long ago I forgot how I fixed it > :) My only experience with tape problems has been with 1/4" QIC and DAT. I've always solved them by using /dev/rst?.1 (usually because .1 seems to be correct for the block size, fixed, 512, etc) and experimenting with the denisty codes until I hit the right one. 0x13 for DAT seems to always be right for DAT, QIC usually takes a bit of effort to figure out. I wish I could be of more help, but that's the best I can do for now. I will mention it usually takes me several days to know when I've got the right combo. With an HP SureStore DAT (8 GB compressed), I found that /dev/nrst1.1 for amanda with a density code worked fine. Often, the backup seemed to go just fine, but after taking the tape out and putting it back in, I found that amanda could tell that the tape was an amanda tape. Doing the following: amlabel -f <config> <label> eject tape re-insert same tape amcheck <config> often complained it wasn't an amanda tape. That puzzled me for a long time until I hit on the density code for DAT tapes. Since then, it works flawlessly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901201710.KAA28285>