stenc + CentOS 7.3, 7.4 and 7.5: Sense Code: Illegal Request (0x05) on LTO drive (encryption)

[scsitape]

stenc + CentOS 7.3, 7.4 and 7.5: Sense Code: Illegal Request (0x05) on LTO drive (encryption)

[remcohn]

solves the issue on Debian8 with Quantium LTO6 drive too. thanks a lot!

[bahelit]

Attempting to enable encryption on an IBM tape library 3573-TL from a machine running CenOS 7.4 and receive an identical error even after applying the patch.

# stenc -f /dev/nst0 -a 1 -e on -k /etc/tape.key Provided key length is 256 bits. Key checksum is 4637. Turning on encryption on device '/dev/nst0'... Sense Code: Illegal Request (0x05) ASC: 0x24 ASCQ: 0x00 Additional data: 0x00000001534c4f5430303000000007c7e1000000000080b560000000000000000000000000000000000000000000000000000000000000000000000000000000000000003039355133303439363600000000000000000000 Error: Turning encryption on for '/dev/nst0' failed!

[jonasstein]

@ninthclowd what do you think, should we merge this?

[scsirob]

@bahelit Your error is different. ASC 0x24 means your drive rejects one of the SCSI commands it got from stenc. The original error referred to ASC 0x26 which means the SCSI command was accepted but the data sent by that command wasn't.

[hrubsa]

We also need the patch on Debian 10 amd64.
Our tape drive is Quantum Ultrium LTO-5.

Please merge the patch. I think there can be nothing wrong with zeroing the memory before using it...

[scsirob]

When you zero the entire kad structure, the two lines below it to set kad.type and kad.authenticated to zero can be removed.

[royalmoose]

Adding the line: memset(&kad,0,sizeof(kad)); in scsiencrypt.cpp fix this issue as described here:

What could cause a 'sense error' when setting LTO encryption?
https://serverfault.com/questions/864580/what-could-cause-a-sense-error-when-setting-lto-encryption

Patch for stenc v1.0.7 (https://github.com/scsitape/stenc/archive/1.0.7.tar.gz):

Just tested on Debian 9 and 10 with Quantum LTO5. Patch works perfectly.