ONTAP Hardware

Disks replacement

band20
5,756 Views

Hi

We had two disks in a failed state on NetApp V3270

the disks were replaced physically and now I don't see them when I run the command "disk show -n"

 

netapp> disk show -n

disk show: No disks match option -n.

 

What am I missing ?

 

Thanks

 

 

1 ACCEPTED SOLUTION

pedro_rocha
5,629 Views

those "new" disks were on another system before. So just remove their previous owners and assign them to your controllers.

View solution in original post

12 REPLIES 12

pedro_rocha
5,733 Views

Hi

 

You should first assign them, did you do that?

 

command: disk assign DISK -o CONTROLLERNAME

 

Then it should appear as a spare disk.

 

Regards,

Pedro.

pedro_rocha
5,728 Views

which disk are you using? Was it provided by NetApp?

 

When you inserted it, did you see any message on the syslog?

 

do you see the disks with disk show -v?

 

 

band20
5,645 Views

The disk array is not under support anymore, we use second hand disks.

I've not seen any messages in the log after the they were replaced.

 

>> do you see the disks with disk show -v?

yes,  I see them like this

DISK OWNER POOL SERIAL NUMBER CHKSUM
------------ ------------- ----- ------------- ------
0b.05.0 PRISTG010094(1573991370) Pool0 6SL2000456K9D -
0b.08.14 PRISTG010094(1573991370) Pool0 6SL10004361H1 -

Have no idea what the owner indicated mean, this is not the name of any controller.

 

failed disks models were 

0b.08.14          X412_S15K7560A15

0b.05.0            X412_HVIPC560A15

 

inserted disk models are

0b.08.14          X412_S15K7560A15

0b.05.0            X412_S15K7560A15

 

Regards,

Alexey

 

andris
5,639 Views

Check the System IDs of both nodes in your HA pair (sysconfig will tell you). Does 1573991370 match either of the System ID of your nodes?

 

Review "sysconfig -r" output for those two disks to see what ONTAP is doing with them.

pedro_rocha
5,630 Views

those "new" disks were on another system before. So just remove their previous owners and assign them to your controllers.

AlexeyF
5,529 Views

ok, that works. thank you.

AlexeyF
5,653 Views

I can't figure out what is wrong with the forum, but I posted two replies yesterday which have disappeared and I can't post under my username band20...

 

Anyway, to unswer your questions : 

>> do you see the disks with disk show -v?

yes

>>When you inserted it, did you see any message on the syslog?

no

>>Which disk are you using? Was it provided by NetApp?

no

AlexeyF
5,653 Views

These are the disks. Have no idea what PRISTG010094 means, this is not the name of a controller.

 

DISK OWNER POOL SERIAL NUMBER CHKSUM
------------ ------------- ----- ------------- ------
0b.05.0 PRISTG010094(1573991370) Pool0 6SL2000456K9D -
0b.08.14 PRISTG010094(1573991370) Pool0 6SL10004361H1 -

band20
5,729 Views

No, I've not done that. But as I understand I should see all unassigned disks with the command "disk show -n" 

 

Use the disk show -n command to view all disks and array LUNs that do not have assigned owners

 

and I see nothing

 

I could try your command, could please indicate what is the rule to select Controller to which assigne the disk?

band20
5,645 Views

the disk array is out of support

I think that the disks inserted were taken from the stock of second-hand disks.

 

I can see these disks with disk show -v command

 

DISK OWNER POOL SERIAL NUMBER CHKSUM
------------ ------------- ----- ------------- ------
0b.05.0 PRISTG010094(1573991370) Pool0 6SL2000456K9D -
0b.08.14 PRISTG010094(1573991370) Pool0 6SL10004361H1 -

 

failed disk in the position 0b.08.14 was X412_S15K7560A15 and was replaced by X412_S15K7560A15

failed disk in the position 0b.05.0 was X412_HVIPC560A15 and was replaced by X412_S15K7560A15

 

>>When you inserted it, did you see any message on the syslog?

nothing regarding new disks in messages logfile

Drew_C
5,644 Views

@band20 

Your posts got eaten by the automatic spam filter. It's a bit aggressive at times. I've released the messages.

Sorry!

Community Manager \\ NetApp

liuh
606 Views

Your disk autoassignment should be on. Enter the command: disk option modify-node * -autoassign off The disk autoassignment is off, then kick the disk out and add the controller you need to add

Public