dmesg

[khilari]

Hi people, well i am posting a dmesg output.Can anybody make some sense out of it for me. Kindly, tell me what i should be looking for and what should i do about errors.
Thanks alot.


DMESG OUTPUT:


...
02 00
00 ee 00 00 00 00
sense key: (03) Medium Error
additional sense code: (3b)
additional sense code qualifier: (00)

SCSI: bp: 033bf480
dev: cd023000 (8/16/5.3.0)
cdb: 0a 00 00 08 00 00
residual: 800
status: (02) Check Condition
sense data: f0 00 03 00 00 08 00 0e 00 00 00 00 0c 00 00 00
00 85 00 00 00 00
sense key: (03) Medium Error
additional sense code: (0c)
additional sense code qualifier: (00)
info (lba): 800

SCSI: bp: 060c5400
dev: cd023000 (8/16/5.3.0)
cdb: 10 00 00 00 02 00
residual: 0
status: (02) Check Condition
sense data: f0 00 03 00 00 00 00 0e 00 00 00 00 0c 00 00 00
00 85 00 00 00 08
sense key: (03) Medium Error
additional sense code: (0c)
additional sense code qualifier: (00)
info (lba): 0
SCSI TAPE: dev = 0xcd023000 I/O error during close
8/0.1.4 sdisk
8/4.0.4 sdisk

SCSI: bp: 033b9900
dev: cd023000 (8/16/5.3.0)
cdb: 0a 00 00 80 00 00
residual: 8000
status: (02) Check Condition
sense data: f0 00 03 00 02 00 01 0e 00 00 00 00 0c 00 00 00
00 84 00 00 00 00
sense key: (03) Medium Error
additional sense code: (0c)
additional sense code qualifier: (00)
info (lba): 20001

SCSI: bp: 0e1c6000
dev: cd023000 (8/16/5.3.0)
cdb: 10 00 00 00 02 00
residual: 0
status: (02) Check Condition
sense data: f0 00 03 00 00 00 04 0e 00 00 00 00 0c 00 00 00
00 84 00 00 00 08
sense key: (03) Medium Error
additional sense code: (0c)
additional sense code qualifier: (00)
info (lba): 4
SCSI TAPE: dev = 0xcd023000 I/O error during close

SCSI: bp: 0d288000
dev: cd023000 (8/16/5.3.0)
cdb: 01 00 00 00 00 00
status: (02) Check Condition
sense data: 71 00 04 00 00 00 00 0e 00 00 00 00 44 00 02 00
00 15 00 00 00 00
sense key: (04) Hardware Error
additional sense code: (44)
additional sense code qualifier: (00)

SCSI: bp: 033b9300
dev: cd023000 (8/16/5.3.0)
cdb: 08 00 00 02 00 00
residual: 200
status: (02) Check Condition
sense data: f0 00 04 00 00 02 00 0e 00 00 00 00 44 00 02 00
00 15 00 00 00 00
sense key: (04) Hardware Error
additional sense code: (44)
additional sense code qualifier: (00)
info (lba): 200

SCSI: bp: 033bc600
dev: cd023000 (8/16/5.3.0)
cdb: 08 00 02 00 00 00
residual: 20000
status: (02) Check Condition
sense data: f0 00 04 00 02 00 00 0e 00 00 00 00 44 00 02 00
00 15 00 00 00 00
sense key: (04) Hardware Error
additional sense code: (44)
additional sense code qualifier: (00)
info (lba): 20000

SCSI: bp: 0ac8a000
dev: cd023000 (8/16/5.3.0)
cdb: 01 00 00 00 00 00
status: (02) Check Condition
sense data: 71 00 04 00 00 00 00 0e 00 00 00 00 44 00 02 00
00 15 00 00 00 00
sense key: (04) Hardware Error
additional sense code: (44)
additional sense code qualifier: (00)

SCSI: bp: 033b6300
dev: cd023000 (8/16/5.3.0)
cdb: 08 00 00 02 00 00
residual: 200
status: (02) Check Condition
sense data: f0 00 04 00 00 02 00 0e 00 00 00 00 44 00 02 00
00 15 00 00 00 00
sense key: (04) Hardware Error
additional sense code: (44)
additional sense code qualifier: (00)
info (lba): 200

SCSI: bp: 033a9a00
dev: cd023000 (8/16/5.3.0)
cdb: 08 00 02 00 00 00
residual: 20000
status: (02) Check Condition
sense data: f0 00 04 00 02 00 00 0e 00 00 00 00 44 00 02 00
00 15 00 00 00 00
sense key: (04) Hardware Error
additional sense code: (44)
additional sense code qualifier: (00)
info (lba): 20000

SCSI: bp: 0ce45a00
dev: cd023000 (8/16/5.3.0)
cdb: 01 00 00 00 00 00
status: (02) Check Condition
sense data: 71 00 04 00 00 00 00 0e 00 00 00 00 44 00 02 00
00 15 00 00 00 00
sense key: (04) Hardware Error
additional sense code: (44)
additional sense code qualifier: (00)

SCSI: bp: 033a9a00
dev: cd023000 (8/16/5.3.0)
cdb: 08 00 00 02 00 00
residual: 200
status: (02) Check Condition
sense data: f0 00 04 00 00 02 00 0e 00 00 00 00 44 00 02 00
00 15 00 00 00 00
sense key: (04) Hardware Error
additional sense code: (44)
additional sense code qualifier: (00)
info (lba): 200

[A. Clay Stephenson]

dev: cd023000

This decodes to /dev/rmt/c2t3d0BEST. The major and minor device numbers will also match the shorter versions of the tape device nodes. In any event, you have a problem with the tape drive. Try cleaning the drive and using another tape. Check cabling and termination. If that fails then you have a failing drive.

[Jeff Schussele]

Hi,

I agree w/Clay.
This is a tape drive problem.
Could be as simple as a bad tape or the drive needs to be cleaned.
So clean it & try another tape.
If it persists you probably have a bad drive.

Rgds,
Jeff

[Jeff Schussele]

Oh _ I forgot to add that it could also be that the write-protect tab is set on the tape.
Do a
mt status
with the tape in to verify.

Rgds,
Jeff

[Sandman!]

How is the tape device being accessed? Are you using the raw, no-rewind Berkley style tape device file e.g. /dev/rmt/0mnb.

Most likely cause of such an error is when the above convention for the device file is not used for manipulating the tape.

cheers!

[Kent Ostby]

ll /dev/rmt/* | grep 023000

will give you the device file for the device in question.

lssf /dev/rmt/[whatever] will give you the path code.

[Yogeeraj_1]

hi,

also use STM to query your hardware.

what is the output of the following command giving?:
ioscan -fknC tape



kind regards
yogeeraj

[Sยภเl Kย๓คг · Accepted solution]

Hi,
This seems to be a problem with the tape drive. May be the problem can be solved by using a cleaning cartridge. What's the LED(Color) indications on the drive, I mean clean.

Whatâ s the status of the drive in ioscan -fnC tape, is it showing â CLAIMEDâ

If clean LED indication is orange, use a good cleaning cartridge to clean the drive. Still the clean LED indication doesn't go off, replace the drive. Never attempt to open the drive and clean manually..

How about connectivity, check the connectivity and scsi terminations etc

Regards,
Sunil