topic Re: B1000 Workstation tape drive errors in Operating System - HP-UX

B1000 Workstation tape drive errors

Nick D'Angelo — Mon, 03 Mar 2003 20:10:45 GMT

All,
The external DAT drive has been a pain lately.
I have tried to remove the /dev/rmt/files and tried to iscan -fnC tape and mksf -e to recreate them etc, but no go.

The last thing I tried was mksf -d stape -I i -a -b BEST /rmt/0m and it came back with:

Couldn't find driver matching arguments.

Now what?

Re: B1000 Workstation tape drive errors

Pete Randall — Mon, 03 Mar 2003 19:43:42 GMT

Nick

Try insf -e.

Pete

Re: B1000 Workstation tape drive errors

Steven E. Protter — Mon, 03 Mar 2003 19:44:53 GMT

The command you are looking for is rmsf to get rid of them.

Then boot the box and they should recreate.

But first.

dmesg

check /var/adm/syslog/syslog.log

If there are lbolt errors associated with the SCSI ID of the tape drive, your drive, cabling, termination or scsi card could be a trouble.

SEP

Re: B1000 Workstation tape drive errors

Nick D'Angelo — Mon, 03 Mar 2003 20:23:12 GMT

Negative - insf -e did nothing and the rmsf removed the directory I specified and then i ran insf -e again and it did not create new device files.

Re: B1000 Workstation tape drive errors

Nick D'Angelo — Mon, 03 Mar 2003 20:25:16 GMT

Actually, the message desc is wrong. There are no errors reported at this time.

No messages no Lbolts in /var/adm/syslog/syslog.log

Re: B1000 Workstation tape drive errors

Ross Zubritski — Mon, 03 Mar 2003 20:27:05 GMT

Did you ioscan -F, then insf -e?

Regards.

RZ

Re: B1000 Workstation tape drive errors

Helen French — Mon, 03 Mar 2003 20:27:38 GMT

what type of DAT drive? Is it listed under ioscan -fn as UNCLAIMED? Did you try using a different tape driver (tape2)? Are these drivers (stape, tape2) are included in the Kernel? Do you have the device connected properly?

Re: B1000 Workstation tape drive errors

Nick D'Angelo — Mon, 03 Mar 2003 20:41:20 GMT

Yes, I did the ioscan -F, first, then the insf -e and not stape devices created in /dev/rmt.

Nickd

Re: B1000 Workstation tape drive errors

Nick D'Angelo — Mon, 03 Mar 2003 20:43:18 GMT

stage is in the /stand/system file.
tape2 is not.

Re: B1000 Workstation tape drive errors

Ross Zubritski — Mon, 03 Mar 2003 20:52:53 GMT

Does the "ioscan -funC tape" show anything, such as NO_HW?

Also, check termination, etc.

Regards,

RZ

Re: B1000 Workstation tape drive errors

KapilRaj — Tue, 04 Mar 2003 08:22:35 GMT

Steps,

1. Boot the workstation and interrupt the boot process.
2. Type "search " Press enter u should see a sequencial device ---->that is the tape and H/W is getting detected by the system

"if [ $? -ne 0 ];then exit 127;fi "

3. run sam --- > kenerl config--->drivers ---> locate "stape" in that and find out whether it is "in the kernel" / "out of the kernel"

"if [ OUT ] then;
make in from there and rebuid the kernel
fi"

If all these chekc points are clear then the tape drive should work.....

After making it in you may use insf / mksf to create device files ..............

Can you post ioscan -fn o/p ?.

kaps

Re: B1000 Workstation tape drive errors

Eugeny Brychkov — Tue, 04 Mar 2003 09:03:35 GMT

Looks like it's a connectivity problem. First step should you take is to run 'ioscan -fn' and examine its output for unknown devices and devices having 'tape-like' inquiry string ("HP C1537A"). If you'll find this entry and check inquiry string and make sure that this is device you're looking for then machine sees this device and 'insf -e' should work creating device files. If not, then try:
- replacing cables/terminators;
- connecting drive to another machine to see if it will see drive;
- connecting drive to another compatible SCSI interface (remember: DAT40 is LVD, another - DAT24/DAT8 are SE)
Eugeny

Re: B1000 Workstation tape drive errors

Frank Slootweg — Fri, 07 Mar 2003 11:06:58 GMT

Please post the output from "ioscan -fn -H ..." where "..." is the hardware path of the *interface* ("INTERFACE" in the "H/W Type" field of the ioscan output).

Re: B1000 Workstation tape drive errors

Nick D'Angelo — Mon, 10 Mar 2003 13:35:44 GMT

It looks like it is indeed a h/w issue with the drive. I replaced the cable and same, intermittant.

We replaced the drive with another Seagate drive (or something close to that) and voila, no problems.

THanks.