[Officers] Fwd: SMART error (FailedReadSmartData) detected on host: pegasus.blu.org

[jabr at blu.org (John Abreau)]

Saw this error. Looks like one of the disks we're not currently using,
and which fdisk is unable to read anyway.

I'm not happy to report that "smartctl -H" reports "SMART Health Status: OK"
for /dev/sdc. fdisk reports "Unable to read /dev/sdc", and "smartctl -a"
says "device is NOT READY (e.g. spun down, busy)
A mandatory SMART command failed: exiting."

We currently have two disks that are in use: /dev/sda and /dev/sdd.
/dev/sdb is present but unused, and sdc is showing as present but apparently
failing.

Now that I think of it, last time I was at NEDV, I removed the "new" drive
that I had just installed a couple days before, so I believe there should
only be 3 drives in pegasus. I'm not sure why it thinks there are 4.

Jerry, you have the same hardware at Algorythmics, right? Does this
phantom disk behavior make sense to you? Maybe the BIOS keeps
a cache of what hard drives used to be installed, and it's screwing up
how smartctl sees things?



---------- Forwarded message ----------
From: root <root at blu.org>
Date: Wed, Jun 1, 2011 at 1:11 PM
Subject: SMART error (FailedReadSmartData) detected on host: pegasus.blu.org
To: root at blu.org


This email was generated by the smartd daemon running on:

? host name: pegasus.blu.org
?DNS domain: [Unknown]
?NIS domain: (none)

The following warning/error was logged by the smartd daemon:

Device: /dev/sdc, failed to read SMART values

For details see host's SYSLOG (default: /var/log/messages).

You can also use the smartctl utility for further investigation.
No additional email messages about this problem will be sent.



-- 
John Abreau / Executive Director, Boston Linux & Unix
AIM abreauj / JABBER jabr at jabber.blu.org / YAHOO abreauj / SKYPE zusa_it_mgr
Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9
PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99