What is the exact error messge. What is the output from the log files. What is the exact command sequence you are using to read the tape.
----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[email protected]> Sent: Saturday, August 03, 2002 8:17 AM Subject: Re: Re: [brlug-general] tape backup issue > If I could look at the tape in this drive from Solaris, I would. If Windows could look at a ufsdump, I'd check it on the Windows box where the drive appears fully functional. The tape isn't physically cracked or anything. Where this leaves me is searching for a MS product that can read ufsdumps, given that Windows has already used this actual drive to do a MS Backup run successfully onto another DAT. I'm low on options for just "looking at the tape" in my current state. > > -j > > > > > From: "Byron Como" <[EMAIL PROTECTED]> > > Date: 2002/08/02 Fri PM 08:41:26 EDT > > To: <[email protected]> > > Subject: Re: [brlug-general] tape backup issue > > > > Not to sound droll, but you might want to look at the tape and make sure its > > not broken. > > > > ----- Original Message ----- > > From: "Shannon Roddy" <[EMAIL PROTECTED]> > > To: "BRLUG-general" <[email protected]> > > Sent: Friday, August 02, 2002 3:56 PM > > Subject: Re: [brlug-general] tape backup issue > > > > > > > Possible a dumb question, but when you go to /dev/rmt/ and do an ls, > > > does anything show up? > > > > > > If not, do a reconfigure reboot. I am sure there are other ways, but > > > this is the easiest (IMO). > > > > > > Shannon > > > > > > On Fri, 2002-08-02 at 15:36, [EMAIL PROTECTED] wrote: > > > > I've got a DAT storing a ufsdump of a Solaris 2.5/Intel server. I've > > got a Solaris 2.6/Intel workstation I'm trying to extract into to recover > > /export/home/database and stuff. I've got a Seagate STD24000N (with three > > zeroes, unlike the more common "2400N" label I'm used to seeing) on the 2.6 > > workstation that doesn't even read. That same tape drive will connect to a > > docked Windows laptop and image the HD through MS Backup, but it won't even > > rewind on this 2.6 platform. The drive IS detected during boot as SCSI id 2 > > and as an st driver tape, but I can't read it, write it, or even rewind it. > > 'mt rewind' gets me "I/O error: tape not loaded or offline", paraphrased > > very closely from memory. > > > > > > > > Any thoughts? I don't even find "Seagate" tape drives on the sun.com HW > > compatibility list, which is just bogus. I'm open to suggestions at this > > point, including another DAT brand and model that is known to work on > > Solaris 2.6. Thanks. > > > > > > > > -j > > > > > > > > > > > > _______________________________________________ > > > > General mailing list > > > > [email protected] > > > > http://brlug.net/mailman/listinfo/general_brlug.net > > > -- > > > Shannon Roddy > > > __________________________________________________________________ > > > Systems Administrator California Institute of Technology > > > [EMAIL PROTECTED] LIGO Livingston Observatory > > > ph: (225)686-3106 19100 LIGO Lane > > > fx: (225)686-7189 Livingston, LA 70754 > > > Web Page http://www.ligo-la.caltech.edu/~sroddy > > > Calendar/Schedule See Home Page > > > Wireless Email (255 Chars) [EMAIL PROTECTED] > > > > > > _______________________________________________ > > > General mailing list > > > [email protected] > > > http://brlug.net/mailman/listinfo/general_brlug.net > > > > > > _______________________________________________ > > General mailing list > > [email protected] > > http://brlug.net/mailman/listinfo/general_brlug.net > > > > > _______________________________________________ > General mailing list > [email protected] > http://brlug.net/mailman/listinfo/general_brlug.net >
