Need to handle an error on RSOC

[piste-jp]

Interesting... You might get a very short window.

I think you might insert the tape and start the ltfs command when load operation is almost finished.

In the most case, cartridge load operation is completed after RSOC command, rhish is the command to fetch time out values from the drive. So RSOC command returns good state and the LTFS successfully configure the time out values. But in this case, load operation is finished just before the RSOC command and the drive returns Not Ready to Ready Transition against it. It is unexpected behavior in the current code and the command sequence after the error to capture the drive dump reports a lot of LTFS39802W because of unconfigured time out values.

But finally, LTFS falles back and configure the time out value from preset one, LTFS30294I . So I believe this is minor issue at this time.

Apr 25 12:48:57 archive ltfs[13358]: 342e LTFS30205I RSOC (0xa3) returns -20601.
Apr 25 12:48:57 archive ltfs[13358]: 342e LTFS30263I RSOC returns Not Ready to Ready Transition, Medium May Have Changed (-20601) /dev/sg3.
Apr 25 12:48:57 archive ltfs[13358]: 342e LTFS30262I Forcing drive dump.
Apr 25 12:48:57 archive ltfs[13358]: 342e LTFS39802W Unknown SCSI OP code 0x1d, use default timeout.
Apr 25 12:48:57 archive ltfs[13358]: 342e LTFS30253I Saving drive dump to /tmp/ltfs_C42A857128_2022_0425_124857_f.dmp.
Apr 25 12:48:57 archive ltfs[13358]: 342e LTFS39802W Unknown SCSI OP code 0x3c, use default timeout.
...
Apr 25 12:49:11 archive ltfs[13358]: 342e LTFS39802W Unknown SCSI OP code 0x3c, use default timeout.
Apr 25 12:49:11 archive ltfs[13358]: 342e LTFS30294I Setting up timeout values from vendor and device.

Originally posted by @piste-jp-ibm in #349 (comment)