ONTAP Discussions
ONTAP Discussions
Hello All,
We have clustered netapp solution running on FAS3240 with NetApp Release 8.1RC3 7-Mode. Recently we lost a hard drive and we want to replace it. The new device which was shipped to us is having disk firmware version NA02 while all other DISKs Have NA01. Please let know that the drive will work or not. I am also attaching a screen shot for your reference.
Solved! See The Solution
If it has the same part number it will work. It is always recommended to use latest disk firmware for all drives, so you may consider update other disks as well.
Yes part number is same. How ever if you see the sceen shot carefully it says STATE as PARTNER ? what it means I expect to see it as DATA or SPARE ?
You have autoassign enabled and the partner had assigned the disk to his sysid.
If you want to see DATA/SPARE then you have to remove the ownership from the disk and assign it to the controller where you want use it.
netappctrl1 owns the disk at the moment and open the disk view on netappctrl2
The firmware is no problem, but it's recommended to use the same FW revision on all disks with the same part number.
Download and install the Disk Qualification Package and the FW package from 2015-May.
How can you gurantee that netappctrl1 is owning the disk right now ?
It's an HA system (with two nodes) and the disk is owned by one of both nodes otherwise you wouldn't see the state "partner".
Check the partner side and decide what you want to do with that disk.
Thanks for the answer. Please see the screen shot of netappctr2 which is not having any spare disk. How can I put the spare disk ?
Hello,
You are missing spares because all disks were added to an aggregate or a disk was assigned to the false controller, right ?
Please send me following output from "sysconfig -r" and "disk show -n".
If you want to reassign a disk then use following commands:
Identify the actual sysid owner:
> disk show
Remove the ownership using disk assign:
> disk assign <disk_id> -o unowned -s <sysid>
Reassign disk to new controller:
> disk assign <disk_id> -o <ownername/systemname>
Best regards
Hello Mark,
Please see the output of the command you have asked
netappctrl1> sysconfig -r
Aggregate sasaggr (online, raid_dp) (block checksums)
Plex /sasaggr/plex0 (online, normal, active, pool0)
RAID group /sasaggr/plex0/rg0 (normal, block checksums)
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
dparity 4a.11.0 4a 11 0 SA:B 0 SAS 10000 560000/1146880000 572325/1172123568
parity 4a.11.1 4a 11 1 SA:B 0 SAS 10000 560000/1146880000 572325/1172123568
data 4a.11.2 4a 11 2 SA:B 0 SAS 10000 560000/1146880000 572325/1172123568
data 4a.11.11 4a 11 11 SA:B 0 SAS 10000 560000/1146880000 572325/1172123568
data 4a.11.4 4a 11 4 SA:B 0 SAS 10000 560000/1146880000 572325/1172123568
data 4a.11.5 4a 11 5 SA:B 0 SAS 10000 560000/1146880000 572325/1172123568
data 4a.11.6 4a 11 6 SA:B 0 SAS 10000 560000/1146880000 572325/1172123568
data 4a.11.7 4a 11 7 SA:B 0 SAS 10000 560000/1146880000 572325/1172123568
data 4a.11.8 4a 11 8 SA:B 0 SAS 10000 560000/1146880000 572325/1172123568
data 4a.11.9 4a 11 9 SA:B 0 SAS 10000 560000/1146880000 572325/1172123568
data 4a.11.10 4a 11 10 SA:B 0 SAS 10000 560000/1146880000 572325/1172123568
Aggregate sataaggr (online, raid_dp) (block checksums)
Plex /sataaggr/plex0 (online, normal, active, pool0)
RAID group /sataaggr/plex0/rg0 (normal, block checksums)
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
dparity 3a.01.0 3a 1 0 SA:B 0 BSAS 7200 1695466/3472315904 1695759/3472914816
parity 3a.01.1 3a 1 1 SA:B 0 BSAS 7200 1695466/3472315904 1695759/3472914816
data 3a.01.2 3a 1 2 SA:B 0 BSAS 7200 1695466/3472315904 1695759/3472914816
data 3a.01.3 3a 1 3 SA:B 0 BSAS 7200 1695466/3472315904 1695759/3472914816
data 3a.01.4 3a 1 4 SA:B 0 BSAS 7200 1695466/3472315904 1695759/3472914816
data 3a.01.5 3a 1 5 SA:B 0 BSAS 7200 1695466/3472315904 1695759/3472914816
data 3a.01.6 3a 1 6 SA:B 0 BSAS 7200 1695466/3472315904 1695759/3472914816
data 3a.01.7 3a 1 7 SA:B 0 BSAS 7200 1695466/3472315904 1695759/3472914816
data 3a.01.8 3a 1 8 SA:B 0 BSAS 7200 1695466/3472315904 1695759/3472914816
data 3a.01.9 3a 1 9 SA:B 0 BSAS 7200 1695466/3472315904 1695759/3472914816
data 3a.01.10 3a 1 10 SA:B 0 BSAS 7200 1695466/3472315904 1695759/3472914816
Pool1 spare disks (empty)
Pool0 spare disks
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
Spare disks for block checksum
spare 0b.10.7 0b 10 7 SA:A 0 SAS 10000 560000/1146880000 572325/1172123568 (not zeroed)
spare 4a.11.3 4a 11 3 SA:B 0 SAS 10000 560000/1146880000 572325/1172123568
spare 3a.01.11 3a 1 11 SA:B 0 BSAS 7200 1695466/3472315904 1695759/3472914816
Partner disks
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
partner 0b.10.10 0b 10 10 SA:A 0 SAS 10000 0/0 572325/1172123568
partner 0b.10.11 0b 10 11 SA:A 0 SAS 10000 0/0 572325/1172123568
partner 0b.10.5 0b 10 5 SA:A 0 SAS 10000 0/0 572325/1172123568
partner 0b.10.8 0b 10 8 SA:A 0 SAS 10000 0/0 572325/1172123568
partner 0a.00.5 0a 0 5 SA:A 0 BSAS 7200 0/0 1695759/3472914816
partner 0a.00.8 0a 0 8 SA:A 0 BSAS 7200 0/0 1695759/3472914816
partner 0b.10.3 0b 10 3 SA:A 0 SAS 10000 0/0 572325/1172123568
partner 0a.00.1 0a 0 1 SA:A 0 BSAS 7200 0/0 1695759/3472914816
partner 0b.10.9 0b 10 9 SA:A 0 SAS 10000 0/0 572325/1172123568
partner 0a.00.6 0a 0 6 SA:A 0 BSAS 7200 0/0 1695759/3472914816
partner 0b.10.1 0b 10 1 SA:A 0 SAS 10000 0/0 572325/1172123568
partner 0a.00.7 0a 0 7 SA:A 0 BSAS 7200 0/0 1695759/3472914816
partner 0a.00.10 0a 0 10 SA:A 0 BSAS 7200 0/0 1695759/3472914816
partner 0b.10.2 0b 10 2 SA:A 0 SAS 10000 0/0 572325/1172123568
partner 0a.00.0 0a 0 0 SA:A 0 BSAS 7200 0/0 1695759/3472914816
partner 0b.10.4 0b 10 4 SA:A 0 SAS 10000 0/0 572325/1172123568
partner 0a.00.2 0a 0 2 SA:A 0 BSAS 7200 0/0 1695759/3472914816
partner 0a.00.9 0a 0 9 SA:A 0 BSAS 7200 0/0 1695759/3472914816
partner 0b.10.6 0b 10 6 SA:A 0 SAS 10000 0/0 572325/1172123568
partner 0a.00.3 0a 0 3 SA:A 0 BSAS 7200 0/0 1695759/3472914816
partner 0a.00.11 0a 0 11 SA:A 0 BSAS 7200 0/0 1695759/3472914816
partner 0b.10.0 0b 10 0 SA:A 0 SAS 10000 0/0 572325/1172123568
partner 0a.00.4 0a 0 4 SA:A 0 BSAS 7200 0/0 1695759/3472914816
netappctrl1> disk show -n
disk show: No disks match option -n.
netappctrl1>
Reassign the disk 0b.10.7 to controller netappctrl2 and you will be fine.
Please notice that the maintenance center only work if a minimum of two spares from the same typ are available.
I think your question is answered, right ?
Thanks once again for the answer. Please let me know the steps to do the work.
I want to assign the disk to netapp controller2 as a spare.
I am waiting for you update..
Hellp,
Please consult your partner so that he can assist you.
I already wrote in a post before what you have to do. Did you try it already ?
If you want to reassign a disk then use following commands:
Identify the actual sysid owner:
> disk show
Remove the ownership using disk assign:
> disk assign <disk_id> -o unowned -s <sysid>
Reassign disk to new controller:
> disk assign <disk_id> -o <ownername/systemname>
Please bear with me , I am really thankful that you have already provided me with the solution. I just need to know after assigning the disk to controller2 how can I make it as a spare ?
If the option for auto-assign is only enabled on one controller then this one assign new disks to themselves...
Type "options disk.auto_assign" and check if its enabled or not. Enable it after reassign the one disk manually.
Display the available/unowned disk: disk show -n
Following disk should be displayed: 0b.10.7
Assign the disk:
All fine now ? 🙂