An ancient box, groaning under the weight of years of developer abuse, has a failing tape drive. How hard is it to get vendor information out of the OS?
Easy, I thought, just use prtconf and look for the st paragraph:
st, instance #0 (driver not attached)
System properties:
name <lun> length <4>
value <0x00000000>.
name <target> length <4>
value <0x00000000>.
name <class> length <5>
value 'scsi'
Hardware properties:
name <inquiry -revision-id> length <5>
value '1502'
name </inquiry><inquiry -product-id> length <16>
value 'MAN3184M SUN18G'
name </inquiry><inquiry -vendor-id> length <8>
value 'FUJITSU'
name </inquiry><inquiry -device-type> length <4>
value <0x00000000>.
</inquiry></class></target>
Strange, says Google, I’m sure that’s a disk.
Flail ensues. I’m sure I’ve found this information before, but most leads suggest either dropping to OpenPROM and rescanning the SCSI bus or using some tools inside volume management packages
Turns out iostat -E is our man:
st11 Soft Errors: 7 Hard Errors: 51 Transport Errors: 0
Vendor: HP Product: C1537A Revision: L007 Serial No: 62
iostat goes on to show that prtconf is listing this tape as sd#19 – a disk device! Craziness.
Leave a Reply
Recent articles
- cron
(Wednesday, 02. 24. 2010 – 6 Comments) - SOAP in unexpected “actually, quite easy” incident.
(Wednesday, 09. 30. 2009 – No Comments) - ipmitool for OSX
(Tuesday, 09. 29. 2009 – No Comments) - vxargs – visual parallel xargs
(Friday, 09. 18. 2009 – 1 Comment)
Archives
- February 2010
- September 2009
- August 2009
- January 2009
- September 2008
- August 2008
- July 2008
- May 2008
- April 2008
- February 2008
- January 2008
- November 2007
- October 2007
- September 2007
- August 2007
- December 2006
- November 2006
- August 2006
- June 2006
- May 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005