Start of bittest from command line has initial errors HDIO_DRIVE_CMD

[snang]

Hello,

Just curious why the bit_cmd keeps starting like this , but then it goes into the test successfully


HDIO_DRIVE_CMD(identify) failed: Input/output error
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
HDIO_DRIVE_CMD(identify) failed: Input/output error
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
HDIO_DRIVE_CMD(identify) failed: Input/output error
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
HDIO_DRIVE_CMD(identify) failed: Input/output error
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
HDIO_DRIVE_CMD(identify) failed: Input/output error
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
HDIO_DRIVE_CMD(identify) failed: Input/output error
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
HDIO_DRIVE_CMD(identify) failed: Input/output error
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
HDIO_DRIVE_CMD(identify) failed: Input/output error
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00
SG_IO: bad/missing sense data, sb[]: 72 05 20 00 00 00 00 1c 02 06 00 00 cf 00 00 00 03 02 00 01 80 0e 00 00 00 00 00 00 00 00 00 00

[Tim (PassMark)]

This output is likely being caused by the 'hdparm' tool (eg hdparm -I /dev/sdb) which BurnInTest calls to gather system information, so it looks like one of the hard drives isn't responding very well when being queried for this information.

[snang]

Is this from the binary hdparm command from bit_cmd or usage of the tool by CentOS? it works fine after the initial inquiry.

[snang]

What version does the Linux version of bit_cmd_line_x64 use for hdparm?


https://access.redhat.com/solutions/446713
hdparm -I /dev/sdc /dev/sdc: HDIO_DRIVE_CMD(identify) failed: Input/output error

• This was fixed in hdparm-9.37.
• The latest hdparm from FC18 works as expected

Sethih

[Tim (PassMark)]

We use whatever version is available on the system, we don't ship a compiled version with BurnInTest.

[snang]

Thanks for the response. I am running the latest version. Is there a way i can change the parameter switches? or set debug mode on the bit_cmd_line_x64 ?

# md5sum bit_cmd_line_x64
b3335cad5d1752d029c47c01a5e47b79 bit_cmd_line_x64

I am running latest version of hdparm
# rpm -qa | grep hdparm
hdparm-9.43-5.el7.x86_64

Thanks.

Sethih

[Tim (PassMark)]

What version of CentOS are you using?
We'll see if we can reproduce it on a system here.

[snang]

We are using a range of OS of CentOS 7.5 to 7.7

[Tim (PassMark)]

We can't seem to reproduce the behavior on CentOS 7 (using hdparm 9.43), could you please generate a debug log using the command line parameter '-d' and email it to us.