Solved error issuing SMART RETURN STATUS command

J

Jaehak Lee

Hi all.

I got repeated message like below.

Code: 
ata0: timeout waiting to issue command
ata0: error issuing SMART RETURN STATUS command
ata0: timeout waiting to issue command
ata0: error issuing SMART RETURN STATUS command
ata0: timeout waiting to issue command
ata0: error issuing SMART RETURN STATUS command
ata0: timeout waiting to issue command
ata0: error issuing SMART RETURN STATUS command
ata0: timeout waiting to issue command
ata0: error issuing SMART RETURN STATUS command
ata0: timeout waiting to issue command
ata0: error issuing SMART RETURN STATUS command
ata0: timeout waiting to issue command
ata0: error issuing SMART RETURN STATUS command
ata0: timeout waiting to issue command
ata0: error issuing SMART RETURN STATUS command
ata0: timeout waiting to issue command
ata0: error issuing SMART RETURN STATUS command


And these messages reported by daily security run output email

Code: 
kernel log messages:
+ata0: timeout waiting to issue command
+ata0: error issuing SMART RETURN STATUS command
+ata0: timeout waiting to issue command
+ata0: error issuing SMART RETURN STATUS command
+ata0: timeout waiting to issue command
+ata0: error issuing SMART RETURN STATUS command
+ata0: timeout waiting to issue command
+ata0: error issuing SMART RETURN STATUS command
+ata0: timeout waiting to issue command
+ata0: error issuing SMART RETURN STATUS command
+ata0: timeout waiting to issue command
+ata0: error issuing SMART RETURN STATUS command
+ata0: timeout waiting to issue command
+ata0: error issuing SMART RETURN STATUS command
+ata0: timeout waiting to issue command
+ata0: error issuing SMART RETURN STATUS command
+ata0: timeout waiting to issue command
+ata0: error issuing SMART RETURN STATUS command


What these messages mean?
Is some hardware going wrong?

Thanks.
 
What version of FreeBSD is this? And do you have smartd(8) running? These messages typically appear when a disk fails to respond to SMART queries, that's usually an indication the drive is going bad.
 
My FreeBSD version is 11.0-RELEASE-p7 FreeBSD 11.0-RELEASE-p7 #1.

Yes, I'm running smartd.
And my machine is HP Micro Server N54L.
 
Use smartctl(8) to query each of your drives. For example: smartctl -a /dev/da0. This should provide a bunch of output with the various SMART data points. Do this for each drive in the system and you should be able to find the drive that's causing it.

Oh, and I just remembered, on some BIOS/UEFI implementations you can actually turn off SMART support. So verify this on your system and make sure it's enabled.
 
Thanks SirDice.
I found the cause.

Actually I knew that one of my hdd has dying.
So I unmounted that hdd and removed from /etc/fstab file.
But I forget detach cable from board.
That was cause(I read ata0 as ada0).
Died hdd was ada4.
smartctl -a /dev/ada4 shows a lot of error status.

Thanks a lot.
Best regards.
 
Jaehak Lee said:
Actually I knew that one of my hdd has dying.
So I unmounted that hdd and removed from /etc/fstab file.
But I forget detach cable from board.
Click to expand...
Yeah, a disk that's not used but still attached can definitely cause problems. It's possible for the disk to put garbage data on the bus causing communication issues between the controller and the other drives. If you have a dodgy drive it's best to completely remove it from the system.
 
You must log in or register to reply here.
Back
Top