> > > > That sounds like a bug. But it could be CAM not understanding that the > > 8200 firmware went to Nowhere-land. If I got a dime for each Exabyte > > lockup.. > > Yep, been there done that. But these drives have been rock solid. It is > not the case of putting in a new, unknown drive and finding out that > it is a little strange. It is the case where I have a hardware configuration > that has been stable that suddenly isn't. > > The original change is the upgrade to 4.0-CURRENT. After that drive > "failed" I took our back up drive and put it into production and got exactly > the same failure mode. > > Here is the sequence that I just did: > Old working tape. > mt erase & > 1hr 30minutes or so later > Drive makes sounds of tape stopping. > Amber light comes on > mt erase reports done (no errors) > mt rewind > mt: /dev/nrsa0: Device busy > push button on face plate > amber light goes out, tape noises. > Green light comes on. > mt rewind > tape is ejected at the same place as all the other failures. > push tape back into drive > Drive is ejected. > manually rewind tape (Yeah Yeah, I know don't do it but the exabyte > ejects the tape each time it is reinserted until I have > it mostly rewound) > repeat with new tapes old tapes and almost new tapes.... Same thing > Chris
I'm sorry- I missed the front end of this. I've had pretty good luck with getting the 8200 to work. What f/w level are you at for the 8200? -matt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
