Where are the I/O Error Codes listed? What is b0000 or e0000

If none of the more specific forums is the right place to ask

Where are the I/O Error Codes listed? What is b0000 or e0000

Postby w4kh » 2019-08-23 14:45

Yes, I am old school (and old) so I backup onto tape (LTO-5) using:
Code: Select all
TAPE=/dev/st0
tar --create --file $TAPE --verbose --totals ./*

or the more terse, but basically the same command
Code: Select all
tar -cvf /dev/st0 ./*


The backup fails and syslog reports:
Code: Select all
Aug 22 08:06:19 BigMutt kernel: [ 3675.545780] st 6:0:0:0: [st0] Block limits 1 - 16777215 bytes.
Aug 22 08:15:50 BigMutt kernel: [   19.740080] scsi host0: ahci
Aug 22 08:15:51 BigMutt kernel: [   29.871777] st 2:0:0:0: Attached scsi tape st0
Aug 22 08:15:51 BigMutt kernel: [   29.871779] st 2:0:0:0: st0: try direct i/o: yes (alignment 4 B)
Aug 22 10:49:17 BigMutt kernel: [ 9236.751396] st 2:0:0:0: [st0] Block limits 1 - 16777215 bytes.
Aug 22 11:11:53 BigMutt kernel: [10592.876275] st 2:0:0:0: [st0] Error b0000 (driver bt 0x0, host bt 0xb).
Aug 22 11:11:53 BigMutt kernel: [10592.894148] st 2:0:0:0: [st0] Error b0000 (driver bt 0x0, host bt 0xb).
Aug 22 11:11:53 BigMutt kernel: [10592.894151] st 2:0:0:0: [st0] Error on write filemark.
Aug 22 11:11:53 BigMutt kernel: [10592.894852] st 2:0:0:0: [st0] Error b0000 (driver bt 0x0, host bt 0xb).
Aug 22 11:11:53 BigMutt kernel: [10593.012651] st 2:0:0:0: [st0] Error b0000 (driver bt 0x0, host bt 0xb).
Aug 22 11:12:00 BigMutt kernel: [10599.894369] st 2:0:1:0: Attached scsi tape st0
Aug 22 11:12:00 BigMutt kernel: [10599.894374] st 2:0:1:0: st0: try direct i/o: yes (alignment 4 B)
Aug 22 11:45:57 BigMutt kernel: [12637.145680] st 2:0:1:0: [st0] Block limits 1 - 16777215 bytes.
Aug 22 11:57:44 BigMutt kernel: [13344.051386] st 2:0:1:0: [st0] Error e0000 (driver bt 0x0, host bt 0xe).
Aug 22 11:57:46 BigMutt kernel: [13346.301193] st 2:0:1:0: [st0] Error 10000 (driver bt 0x0, host bt 0x1).
Aug 22 11:57:46 BigMutt kernel: [13346.301203] st 2:0:1:0: [st0] Error on write filemark.
Aug 22 11:57:46 BigMutt kernel: [13346.301234] st 2:0:1:0: [st0] Error 10000 (driver bt 0x0, host bt 0x1).
Aug 22 11:57:51 BigMutt kernel: [13350.317604] st 2:0:2:0: Attached scsi tape st0
Aug 22 11:57:51 BigMutt kernel: [13350.317606] st 2:0:2:0: st0: try direct i/o: yes (alignment 4 B)


I have tried looking in the Debian Wiki, Documentation, Support, User Forums.... Nada :(

Where can I find a listing of I/O error codes?

I need to know what the problem is... it writes 160+GB and then fails... is it the drive (HP EH957SB StorageWorks LTO-5 Ultrium 3000 SAS Internal Tape Drive)? a SAS cable? a LTO-5 cartridge (QUANTUM LTO 5 Tape Cartridge - MR-L5MQN-01)? Software?
Last edited by w4kh on 2019-09-03 20:43, edited 1 time in total.
GNU/Linux 4.9.0-8-amd64 #1 SMP Debian
Motherboard: Gigabyte 970A-D3P
CPU: AMD FX-8350 8-Core Processor @4000.000 MHz cache: 2048 KB
RAM: 32GB (4x8GB) Unbuffered (Unregistered)
LTO-5 Tape
Video: GeForce 8400 GS
Monitor: VIZIO E320VA
User avatar
w4kh
 
Posts: 77
Joined: 2006-09-09 19:10
Location: Tennessee, USA

Re: Where are the I/O Error Codes listed? What is b0000 or e

Postby ruwolf » 2019-08-24 14:34

Here was similar question, but nobody was able to answer.
It is defined somewhere in the kernel driver.
I would try to ask at first in forum.KernelNewbies.org.
User avatar
ruwolf
 
Posts: 392
Joined: 2008-02-18 05:04
Location: Slovakia, Banovce nad Bebravou, Matice slovenskej 1260/4-7

Re: Where are the I/O Error Codes listed? What is b0000 or e

Postby w4kh » 2019-08-25 14:08

ruwolf suggested:
Code: Select all
Here was similar question, but nobody was able to answer.
It is defined somewhere in the kernel driver.
I would try to ask at first in forum.KernelNewbies.org.


It seemed very odd that no one knew where error codes were listed...

So, I looked and queried in both ruwolf's suggested sites and drew a blank...

Apparently, rather than list errors in an appendix on the web, Debian would prefer that I stick my head into the kernel and root about in search of the truffle that would answer my question.

My issue seems very simple - to me...
I use "partclone.[vfat|ext2|ext4]" or "dd if=/dev/sda2 of=$OUTF conv=sparse,sync,noerror bs=4096" to create an image of disk partitions, and then use "tar -cvf /dev/st0 /backup_images" to write the images to LTO-5 tape.

I am trying to determine if the errors that occur during "tar" are related to the drive, the cartridge, or the cable (some of my searching found instances of a cable fault causing an LTO write to fail)... replacing the cable or the cartridges can be done, but randomly substituting new for older in hopes of having it work violates EVERYTHING I have learned in 60+ years (yes, I am old, and the first computer that I wrote a program for - and was paid - was a hybrid discrete solid-state and vacuum tube machine!) of programming and using computers. I want to know WHAT is causing the error and to WHAT piece of equipment, so I can develop a solution that doesn't involve random pecking in hopes of finding a seed.
GNU/Linux 4.9.0-8-amd64 #1 SMP Debian
Motherboard: Gigabyte 970A-D3P
CPU: AMD FX-8350 8-Core Processor @4000.000 MHz cache: 2048 KB
RAM: 32GB (4x8GB) Unbuffered (Unregistered)
LTO-5 Tape
Video: GeForce 8400 GS
Monitor: VIZIO E320VA
User avatar
w4kh
 
Posts: 77
Joined: 2006-09-09 19:10
Location: Tennessee, USA


Return to General Questions

Who is online

Users browsing this forum: No registered users and 9 guests

fashionable