Legacy Product Discussions
Legacy Product Discussions
Hi,
I have FAS270 with 146GB FC disks. Unfortunately one disk failed and I provided a replacement - exact model.
Drive was used somewhere else and had data on it. When I inserted the disk, system rejected it and marked as failed (unknown data on disk).
I managed to bring it as a spare with disk unfail -s <disk_id>, however disk has lower size than other disks (0b.26).
I tried with disk zero spares command, but that didn't change anything.
Sysconfig -r output:
Aggregate aggr0 (online, raid_dp) (block checksums)
Plex /aggr0/plex0 (online, normal, active)
RAID group /aggr0/plex0/rg0 (normal)
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
dparity 0b.16 0b 1 0 FC:B - FCAL 10000 136000/278528000 137422/281442144
parity 0b.17 0b 1 1 FC:B - FCAL 10000 136000/278528000 137422/281442144
data 0b.18 0b 1 2 FC:B - FCAL 10000 136000/278528000 137422/281442144
data 0b.19 0b 1 3 FC:B - FCAL 10000 136000/278528000 137422/281442144
data 0b.20 0b 1 4 FC:B - FCAL 10000 136000/278528000 137422/281442144
data 0b.21 0b 1 5 FC:B - FCAL 10000 136000/278528000 137422/281442144
data 0b.22 0b 1 6 FC:B - FCAL 10000 136000/278528000 137422/281442144
data 0b.23 0b 1 7 FC:B - FCAL 10000 136000/278528000 137422/281442144
data 0b.24 0b 1 8 FC:B - FCAL 10000 136000/278528000 137422/281442144
data 0b.25 0b 1 9 FC:B - FCAL 10000 136000/278528000 137422/281442144
data 0b.29 0b 1 13 FC:B - FCAL 10000 136000/278528000 137422/281442144
data 0b.27 0b 1 11 FC:B - FCAL 10000 136000/278528000 137422/281442144
data 0b.28 0b 1 12 FC:B - FCAL 10000 136000/278528000 137422/281442144
Spare disks
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
Spare disks for block or zoned checksum traditional volumes or aggregates
spare 0b.26 0b 1 10 FC:B - ATA 10000 68000/139264000 124457/254888432
What is really strange in here is that TYPE = ATA, while the rest of the disks = FCAL. Why is that so?
What can I do to make this new disk as a real spare?
Thank you in advance.
Hi! Check output of storage show disk and sysconfig -v command.
Maybe you need update Disk Qualification Package file.
https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb50298
http://now.netapp.com/NOW/download/tools/diskfw/
It helps for me.
Thanks for the proposal.
I checked these qual_devices* files on my filer and I what is really strange here is that size of these files is bigger than sizes of the files downloaded from now.netapp.com.
Is this correct? (files on my filer are quite old = 2007)
sysconfig -v output:
ID Vendor Model FW Size
16: NETAPP X274_HPYTA146F10 NA03 136.0GB (281442144 520B/sect)
17: NETAPP X274_HPYTA146F10 NA03 136.0GB (281442144 520B/sect)
18: NETAPP X274_HPYTA146F10 NA03 136.0GB (281442144 520B/sect)
19: NETAPP X274_HPYTA146F10 NA03 136.0GB (281442144 520B/sect)
20: NETAPP X274_HPYTA146F10 NA03 136.0GB (281442144 520B/sect)
21: NETAPP X274_HPYTA146F10 NA03 136.0GB (281442144 520B/sect)
22: NETAPP X274_HPYTA146F10 NA03 136.0GB (281442144 520B/sect)
23: NETAPP X274_HPYTA146F10 NA03 136.0GB (281442144 520B/sect)
24: NETAPP X274_HPYTA146F10 NA03 136.0GB (281442144 520B/sect)
25: NETAPP X274_HPYTA146F10 NA03 136.0GB (281442144 520B/sect)
26: HITACHI HUS103014FLF210 MS04 68.0GB (286749486 512B/sect)
27: NETAPP X274_HPYTA146F10 NA03 136.0GB (281442144 520B/sect)
28: NETAPP X274_HPYTA146F10 NA03 136.0GB (281442144 520B/sect)
29: NETAPP X274_HPYTA146F10 NA03 136.0GB (281442144 520B/sect)
26 is the new disk. Any new ideas how to make it visible as the rest of the disks?
What's the source of the disk 26? It shows Hitachi, not NetApp. Are you sure it's the correct disk? If so, maybe you need to update disk firmware.
Thanks,
Wei
It looks like original Hitachi disk:
HITACHI HUS103014FLF210 ULTRASTAR 10K300 147GB 10KRPM 16MB FIBER CHANNEL 40PIN SCA-2 3.5" HARD DRIVE
Of course you can download latest fw pack for drives and manualy update fw (disk_fw_update).
But i think it doesn't help.
If you get this drive from NetApp you need contact with support.
Hi ,
Please try upgrading the Ontap , it should take care of the issue.
regards
moncy
This is older so you may have solved it. One thing I noticed... the replacement disk is 512 block, original disks are 520 block.
Can't replace 520B drives with 512B drives.