BLU Officers list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Officers] Fwd: SMART error (FailedReadSmartData) detected on host: pegasus.blu.org
- Subject: [Officers] Fwd: SMART error (FailedReadSmartData) detected on host: pegasus.blu.org
- From: gaf at blu.org (Jerry Feldman)
- Date: Thu, 02 Jun 2011 19:46:12 -0400
- In-reply-to: <BANLkTimNLCmK0tPWzm88=GN=0y-d1OB3zQ@mail.gmail.com>
- References: <20110601171120.107416D685@pegasus.blu.org> <BANLkTimNLCmK0tPWzm88=GN=0y-d1OB3zQ@mail.gmail.com>
The way this works is that the hardware must first spin up the drives. What Pegasus sees is what was in the drive at boot time. On 06/02/2011 07:40 PM, John Abreau wrote: > 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. > > > -- Jerry Feldman <gaf at blu.org> Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
- References:
- [Officers] Fwd: SMART error (FailedReadSmartData) detected on host: pegasus.blu.org
- From: jabr at blu.org (John Abreau)
- [Officers] Fwd: SMART error (FailedReadSmartData) detected on host: pegasus.blu.org
- Prev by Date: [Officers] Fwd: SMART error (FailedReadSmartData) detected on host: pegasus.blu.org
- Next by Date: [Officers] Most of the listservs have been set up
- Previous by thread: [Officers] Fwd: SMART error (FailedReadSmartData) detected on host: pegasus.blu.org
- Next by thread: [Officers] Most of the listservs have been set up
- Index(es):