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

[w4kh]

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?

[ruwolf]

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.

[w4kh]

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.

[w4kh]

Still no answer and no clue what these i/o errors mean, but some digging turned up a bit more to chew on:

Code: Select all

[color=#008000]root@BigMutt:~# openssl errstr e0000
error:000E0000:lib(0):func(224):reason(0)
root@BigMutt:~# openssl errstr 10000
error:00010000:lib(0):func(16):reason(0)
root@BigMutt:~# openssl errstr b0000
error:000B0000:lib(0):func(176):reason(0)[/color]

Now, the mystery has shifted to what do the arguments to "lib":"func":"reason" signify or mean?
Clearly they apply to the LTO-5 tape drive (/dev/st0 - Serial Attached SCSI), but what are these errors telling me?
Is the issue with the drive? (I have cleaned it using a cleaning cartridge)
Is the issue with the tape cartridge? It has only been loaded and written to 8-10 times
Is the issue with the SAS cable? The drive does function correctly from time to time, but when it errors, the error happens between 170GB and 230GB into the backup ( a simple tar backup of six (large) files in a directory:

Code: Select all

[color=#008000]total 1275962052
drwxr-xr-x 24 root root         4096 Sep 25 11:21 ..
-rw-r--r--  1 root root      1144694 Oct 21 22:32 2019-10-21_SDA1.img
-rw-r--r--  1 root root 223999950848 Oct 21 23:21 2019-10-21_SDA2.img
-rw-------  1 root root 439696103266 Oct 22 01:17 2019-10-21_SDA4.img
drwx------  2 root root        16384 Oct 26 22:20 lost+found
-rw-r--r--  1 root root      1144694 Oct 26 22:32 2019-10-26_SDA1.img
-rw-r--r--  1 root root 223999950848 Oct 26 23:20 2019-10-26_SDA2.img
drwxr-xr-x  3 root root         4096 Oct 26 23:21 .
-rw-------  1 root root 439540069646 Oct 27 01:08 2019-10-26_SDA4.img
 
X----X----X----X----X----X----X----X----X----X----X----X
Filesystem     Type  Size  Used Avail Use% Mounted on
/dev/sda5      ext4  1.9T  1.2T  534G  70% /look-back[/color]

Surely SOMEONE here knows what the arguments to "lib", "func", and "reason" signify or mean?

I am trying to set a more frequent backup schedule, but before I do, I want to know what these errors mean and what my options are for solutions.

[trinidad]

Obviously one is a string error for a color hex-designation. Also SSL is reporting here not Debian per/se.

https://www.openssl.org/docs/manpages.html
https://www.feistyduck.com/books/openssl-cookbook/

TC

[w4kh]

trinidad says:

Code: Select all

"Obviously one is a string error for a color hex-designation"

"Obviously"? Where is that found? I kinda believe what you say, but where can I find that documentation? Google didn't turn up anything like that looking for "Debian 10 i/o error *0000"

And, I understand that SSL is reporting... however, even at the openssl.org website, there is NO explanation I have been able to find for what "lib", "func", "reason" mean, nor what the codes at each category mean. I can make some pretty close assumptions as to what the categories mean, but the values are a total mystery and may well hold the keys to solving the real issue of what is causing TAR to fail -- is it tape media? the tape drive? the SAS cable? the SAS controller card?

After all, swapping out tape media, an SAS cable, or the SAS controller card isn't such a big deal, but swapping out a tape drive costs 20 to 100 times a cable, controller card, or tape cartridge.

[trinidad]

See this link. Been a while since I used it. May or may not report a clearer error message. Sorry for the comment I was browsing quickly at the time. The error number to use is the one after error: in the syntax as follows: # openssl errstr 000E0000

https://www.openssl.org/docs/man1.0.2/m ... rrstr.html

TC

[reinob]

I don't know how the error codes of the kernel st module have ended up being mixed up with openssl.

As to the (SCSI) error codes, you can look here:
https://www.tldp.org/HOWTO/archived/SCS ... TO-21.html

This appears to explain the format/meaning of SCSI error codes as well:
https://support.hpe.com/hpsc/doc/public ... -c00996785

(Note, this is as far as I can help).