:strip_icc():strip_exif()/u/8430/logo.jpg?f=community){kind=logo}
Om te beginnen, dit is een hobbyprojectje en ik ben me er van bewust dat er niet zo veel parate kennis zal zijn, maar ik probeer het toch even.
Mijn systeem:
IBM RS/6000 43P Model 140
AIX 5.1 ML10
IBM FRU 59P6670 (Seagate STD2401LW) DDS4 20/40 tape drive
HP C5718A DDS4 tapes (nieuw)
Probleem:
Het schrijven van data naar tape geeft een foutmelding, zowel met backup als mksysb.
Hieronder de troubleshooting en informatie die ik verzameld heb, in het Engels.
/usr/bin/mksysb '-i' '-X' /dev/rmt0::
find /tmp | backup -ivf /dev/rmt0.1:
lscfg -vpl rmt0:
lsattr -E -l rmt0:
lslpp -l | grep Tape:
diag -d rmt0:
Tried:
- Using a different tape
- Change block size from 512 to 0
- Set the streamer dip switches to all on, except 6, 8 and 9
- Checked the free space on /tmp, added -X to mksysb to automatically expand
None of the above made any difference. Noticed that the drive is recognized as 'Other SCSI Tape Drive' so reviewed the configuration. All looks well, except I don't know the proper value for density_set_1 and density_set_2, the current value of 0 indicates the highest possible value for this drive which should work. Shouldn't it?
Also tried to download and install a the Atape drivers but wasn't able to obtain a version 9.x.x.x which is the latest that was supported with AIX 5.1.
Currently having no other hardware or operating system available to test the tape drive in a different system.
At this point I'm out of options. The drive was sold to me as operable and seeing many others had similar issues with perfectly fine hardware I'm believing this is rather a configuration issue than a hardware problem. A bad tape would be possible, but two bad tapes form a new package? Not likely.
Mijn systeem:
IBM RS/6000 43P Model 140
AIX 5.1 ML10
IBM FRU 59P6670 (Seagate STD2401LW) DDS4 20/40 tape drive
HP C5718A DDS4 tapes (nieuw)
Probleem:
Het schrijven van data naar tape geeft een foutmelding, zowel met backup als mksysb.
Hieronder de troubleshooting en informatie die ik verzameld heb, in het Engels.
/usr/bin/mksysb '-i' '-X' /dev/rmt0::
code:
1
2
3
4
5
6
7
8
9
| root@localhost:/root>/usr/bin/mksysb '-i' '-X' /dev/rmt0
Creating information file (/image.data) for rootvg....
Creating tape boot image....................................
bosboot: Boot image is 14686 512 byte blocks.
0301-161 bosboot: dd failed to copy /dev/rmt0.1.
0301-165 bosboot: WARNING! bosboot failed - do not attempt to boot device.
0512-016 mksysb: Attempt to create a bootable tape failed:
bosboot -d /dev/rmt0.1 -a failed with return code 48. |
find /tmp | backup -ivf /dev/rmt0.1:
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
| Mount volume 1 on /dev/rmt0.1.
Press Enter to continue.
Backing up to /dev/rmt0.1.
Cluster 51200 bytes (100 blocks).
Volume 1 on /dev/rmt0.1
a 0 /tmp
a 0 /tmp/lost+found
a 0 /tmp/.strload.mutex
a 0 /tmp/block
a 157 /tmp/rc.net.out
a 0 /tmp/rc.net.serial.out
a 0 /tmp/.X11-unix
backup: /tmp/.X11-unix/X0 socket is not backed up.
a 0 /tmp/xlogfile
backup: /tmp/.PMDV1 socket is not backed up.
a 0 /tmp/sh8776.1
a 1120 /tmp/rpcbind.file
a 0 /tmp/sh15312.1
a 0 /tmp/.oslevel.datafiles
a 0 /tmp/.oslevel.datafiles/.oslevel.hold
backup: 0511-432 A write error occurred: There is an input or output error.
backup: 0511-079 The backup media may be damaged.
Use a different disk to run the backup. |
lscfg -vpl rmt0:
code:
1
2
3
4
5
6
| DEVICE LOCATION DESCRIPTION
rmt0 04-C0-00-5,0 Other SCSI Tape Drive
Manufacturer................SEAGATE
Machine Type and Model......DAT 9SP40-000 |
lsattr -E -l rmt0:
code:
1
2
3
4
5
6
7
8
9
10
11
| mode yes Use DEVICE BUFFERS during writes True block_size 0 BLOCK size (0=variable length) True extfm yes Use EXTENDED file marks True maxlun 31 LVD SCSI Tape Drive True res_support no RESERVE/RELEASE support True var_block_size 0 BLOCK SIZE for variable length support True density_set_1 0 DENSITY setting #1 True density_set_2 0 DENSITY setting #2 True delay 45 Set delay after a FAILED command True rwtimeout 144 Set timeout for the READ or WRITE command True ret_error no RETURN error on tape change or reset True |
lslpp -l | grep Tape:
code:
1
2
3
| devices.scsi.tape.diag 5.1.0.50 COMMITTED SCSI Tape Device Diagnostics devices.scsi.tape.rspc 5.1.0.0 COMMITTED RISC PC SCSI Tape Device devices.scsi.tape.rte 5.1.0.54 COMMITTED SCSI Tape Device Software |
diag -d rmt0:
code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
| A PROBLEM WAS DETECTED ON Sat Jan 1 03:45:07 NFT 2000 801014
The Service Request Number(s)/Probable Cause(s)
(causes are listed in descending order of probability):
973-320: Error Log Analysis indicates a permanent hardware failure.
rmt0 FRU: n/a 04-C0-00-5,0
Other SCSI Tape Drive
n/a FRU: n/a 04-C0-00-5,0
Test media.
ADDITIONAL INFORMATION FOR TAPE DRIVE (rmt0) IN LOCATION 04-C0-00-5,0 973016
This tape drive is not recognized by diagnostics.
For this reason, the SRN may be invalid. |
Tried:
- Using a different tape
- Change block size from 512 to 0
- Set the streamer dip switches to all on, except 6, 8 and 9
- Checked the free space on /tmp, added -X to mksysb to automatically expand
None of the above made any difference. Noticed that the drive is recognized as 'Other SCSI Tape Drive' so reviewed the configuration. All looks well, except I don't know the proper value for density_set_1 and density_set_2, the current value of 0 indicates the highest possible value for this drive which should work. Shouldn't it?
Also tried to download and install a the Atape drivers but wasn't able to obtain a version 9.x.x.x which is the latest that was supported with AIX 5.1.
Currently having no other hardware or operating system available to test the tape drive in a different system.
At this point I'm out of options. The drive was sold to me as operable and seeing many others had similar issues with perfectly fine hardware I'm believing this is rather a configuration issue than a hardware problem. A bad tape would be possible, but two bad tapes form a new package? Not likely.
:strip_icc():strip_exif()/u/11942/001.jpg?f=community)