Laurence,
Shane Seymour from HP provided this useful link:
https://docs.oracle.com/cd/E21419_04/en/LTO5_Vol3_E5b/LTO5_Vol3_E5b.pdf
That documents the WRITE BUFFER command on pages 228 and 229 used
by HP LTO-5 drives. For sending new firmware it looks like you need
to use MODE 4 or 5. [That description does not look like the work of
an engineer who understands the subject matter :-)].
And it seems like HP implement the REPORT SUPPORTED OPCODES command
which means you can use the sg_opcodes utility. For the WRITE BUFFER
command, that should break out the MODE numbers that the drive
actually supports. For example, this from a SSD:
...
3b 0 10 Write buffer, combined header and data [or multiple modes]
3b 2 10 Write buffer, data
3b 4 10 Write buffer, download microcode and activate
3b 5 10 Write buffer, download microcode, save, and activate
3b 6 10 Write buffer, download microcode with offsets and activate
3b 7 10 Write buffer, download microcode with offsets, save, and activate
3b a 10 Write buffer, write data to echo buffer
...
Looking back in this thread I see you mention a Quantum Ultrium 5
tape drive; so this HP information may not apply.
Doug Gilbert
On 16-01-14 09:12 PM, Laurence Oberman wrote:
All attempts to get my drive and changer firmware updated have failed.
So I wont be able to add another "tested by" to this thread unless I can find another drive.
Even using Doug's method fails to actually update. Seems to suck up the image and then do nothing.
Lands up in getting hung and needs a full power reset.
The image I have is the correct image.
I dont want to try to many convoluted methods because I dont want to brick the changer.
Its the only one I have for doing all the st driver testing here at Red Hat in the GSS team.
Thanks
Laurence Oberman
Principal Software Maintenance Engineer
Red Hat Global Support Services
----- Original Message -----
From: "Emmanuel Florac" <eflorac@xxxxxxxxxxxxxx>
To: "Laurence Oberman" <loberman@xxxxxxxxxx>
Cc: "Laurence Oberman" <oberman.l@xxxxxxxxx>, "Kai Makisara" <Kai.Makisara@xxxxxxxxxxx>, linux-scsi@xxxxxxxxxxxxxxx
Sent: Wednesday, January 6, 2016 11:07:20 AM
Subject: Re: st driver doesn't seem to grok LTO partitioning
Le Wed, 6 Jan 2016 10:23:34 -0500 (EST)
Laurence Oberman <loberman@xxxxxxxxxx> écrivait:
MaxPartitions: 0
Drive is working fine,
# mt -f /dev/st0 status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 512 bytes. Density code 0x58 (no translation).
Soft error count since last status=0
General status bits on (41010000):
BOT ONLINE IM_REP_EN
This is what I get when I try and partition and I believe this may be
a firmware issue for me.
Yes probably, it reports "MaxPartitions 0", should be 1 for an LTO-5
drive. Weird.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
