Re: jbod + SMART : how to identify failing disks ?

[Craig Lewis <clewis@xxxxxxxxxxxxxxxxxx>]

I use `dd` to force activity to the disk I want to replace, and watch the activity lights.  That only works if your disks aren't 100% busy.  If they are, stop the ceph-osd daemon, and see which drive stops having activity.  Repeat until you're 100% confident that you're pulling the right drive.

On Wed, Nov 12, 2014 at 5:05 AM, SCHAER Frederic <frederic.schaer@xxxxxx> wrote:

Hi,

 

I’m used to RAID software giving me the failing disks  slots, and most often blinking the disks on the disk bays.

I recently installed a  DELL “6GB HBA SAS” JBOD card, said to be an LSI 2008 one, and I now have to identify 3 pre-failed disks (so says S.M.A.R.T) .

 

Since this is an LSI, I thought I’d use MegaCli to identify the disks slot, but MegaCli does not see the HBA card.

Then I found the LSI “sas2ircu” utility, but again, this one fails at giving me the disk slots (it finds the disks, serials and others, but slot is always 0)

Because of this, I’m going to head over to the disk bay and unplug the disk which I think corresponds to the alphabetical order in linux, and see if it’s the correct one…. But even if this is correct this time, it might not be next time.

 

But this makes me wonder : how do you guys, Ceph users, manage your disks if you really have JBOD servers ?

I can’t imagine having to guess slots that each time, and I can’t imagine neither creating serial number stickers for every single disk I could have to manage …

Is there any specific advice reguarding JBOD cards people should (not) use in their systems ?

Any magical way to “blink” a drive in linux ?

 

Thanks && regards

_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com