Hey everybody,

I just had the pleasure to try to replace a faulty disk in a filer which is out-of-service with a „new“ one from after market.

Of course, this didn’t work out as easy as it should, so maybe some could help me get this disk going.

Here are the facts:

FAS2040

NetApp Release 8.1.4P8 7-Mode

The disk at 0d.01.13 was broken, so I pulled it a few days ago – now that the replacment disk has arrived, I tried to plug it in and this is what happens:

Thu Oct 22 14:30:10 CEST [riddler:scsi.cmd.notReadyCondition:notice]: Disk device 0d.01.13: Device returns not yet ready: CDB 0x1b: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x28)(2).

The interesting thing, I can see the disk by using `storage show disk`:

riddler> storage show disk

DISK                  SHELF BAY SERIAL           VENDOR   MODEL      REV

--------------------- --------- ---------------- -------- ---------- ----

0d.01.13                1   13  J838WSRL         NETAPP   X302_HJUPI NA04

But I cannot see it in disk show.

riddler> disk show 0d.01.13

  DISK       OWNER                      POOL   SERIAL NUMBER         HOME

------------ -------------              -----  -------------         -------------

Sysconfig –v tells me, that there is a newer firmware on the „new“ disk:

                01.13: NETAPP   X302_HJUPI01TSSM NA04 847.5GB (1953525168 512B/sect)

                01.14: NETAPP   X302_WVULC01TSSA NA03 847.5GB (1953525168 512B/sect)

So I first tried to downgrade firmware using:

disk_fw_update –R 0d.01.13

but that did not really work out, no error message, but just no change on the firmware of the disk – also nothing in the logs.

So I read somewhere that this might be due to a bad/incompatible label on the disk and found out that the only way to get rid of the label is to boot into maintenance mode (thus having a downtime of parts of the HA-pair :-/) and recreate the label there.

So I booted into maintenance mode and have run the following command:

*> label makespare 0d.01.13

*********************************************************

Label editing is highly dangerous and should be attempted

ONLY by NetApp Customer Support Engineers.

Misuse can cause ALL data to be permanently lost.

*********************************************************

'Label save': Error while trying to save Label 1 on disk 0d.03.22: error 15.

Label save: 1 of 35 disks could not save Label 1.

'Label save': Error while trying to save Label 2 on disk 0d.03.22: error 15.

Label save: 1 of 35 disks could not save Label 2.

The current set of labels on the disks have been saved. You can

use the 'label restore' command to revert to these labels, the

'label keep' command to erase these labels, or 'label save' to

preserve the current set of labels.

*********************************************************

        *** Run WAFL recovery tools (wafliron or wafliron_oc) after this. ***

Disk 0d.01.13 does not exist.

The last line suggests, that the disk still does not get recognized properly – and additionally, it (for whatever reason) claims to not be able to write the label 1 on disk 0d.03.22, although this is there and online:

riddler> disk show 0d.03.22

  DISK       OWNER                      POOL   SERIAL NUMBER         HOME

------------ -------------              -----  -------------         -------------

0d.03.22     riddler   (142248200)    Pool0  N002XRML              riddler   (142248200)

I’ve stopped my expiriments at this point and am very thankful for fresh ideas J

Best,

Alexander Griesser

Head of Systems Operations

ANEXIA Internetdienstleistungs GmbH

E-Mail: AGriesser@anexia-it.com

Web: http://www.anexia-it.com

Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt

Geschäftsführer: Alexander Windbichler

Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601