Talk and ask questions about NetApp FAS and AFF series unified storage systems. Talk with other members how to optimize these powerful data storage systems.
Talk and ask questions about NetApp FAS and AFF series unified storage systems. Talk with other members how to optimize these powerful data storage systems.
Hi Everyone, As we know, vmware has vSAN stretched cluster function to build a dual active data center architecture. Howerver, customer would like to build stretched cluster without vSAN. Is it possible to implement vmware stretched cluster through MCCP or SM-BC? Thank you all. Albert
... View more
Yes, nice to meet you all. I have hardly touched NETAPP Storage and suddenly the person in charge quit and I have to deal with it. Therefore, I would like your help as my knowledge is limited. The DISK broke and was replaced with a HDD that was used elsewhere in a hurry. At that time, it displayed "badlabel" and I was in a hurry, but I found out that it was displayed like that because the disk was used in another chassis. Then, with the following command, the badlabel was corrected and the disk was recognized. storage disk unfail -s 1.1.15 Up to this point, there was no problem, but the disk was recognized as a spare, and I think it is different from the original state. Can you please tell me how to restore this to its original state? What is the original state? 1.1.13 3.63TB 1 13 FSAS aggregate aggr2 main-01 1.1.14 3.63TB 1 14 FSAS aggregate aggr2 main-01 1.1.15 3.63TB 1 15 FSAS aggregate aggr2 main-01 1.1.16 3.63TB 1 16 FSAS aggregate aggr2 main-01 It is believed to be. The current status is 1.1.13 3.63TB 1 13 FSAS aggregate aggr2 main-01 1.1.14 3.63TB 1 14 FSAS aggregate aggr2 main-01 1.1.15 3.63TB 1 15 FSAS spare Pool0 main-01 1.1.16 3.63TB 1 16 FSAS aggregate aggr2 main-01 And for information on spares, main::*> storage disk zerospares aggr status -s Original Owner: main-01 Pool0 Spare Pool Usable Physical Disk Type Class RPM Checksum Size Size Status ---------------- ------ ----------- ------ -------------- -------- -------- -------- 1.1.15 FSAS capacity 7200 block 3.63TB 3.64TB zeroed Original Owner: main-01 Pool0 Root-Data Partitioned Spares Local Local Data Root Physical Disk Type Class RPM Checksum Usable Usable Size Status ---------------- ------ ----------- ------ -------------- -------- -------- -------- -------- 1.0.15 FSAS capacity 7200 block 3.58TB 53.88GB 3.64TB zeroed Original Owner: main-02 Pool0 Root-Data Partitioned Spares Local Local Data Root Physical Disk Type Class RPM Checksum Usable Usable Size Status ---------------- ------ ----------- ------ -------------- -------- -------- -------- -------- 1.0.22 FSAS capacity 7200 block 0B 53.88GB 3.64TB zeroed 3 entries were displayed. The information of the spares is as follows. What is wrong? I often maintain RAID on servers, so I did it in the same way. And I am not good at English, so I am using translation software.
... View more
Hi guys, Recently i bought DE6600 but can not make it work . It is connected to lsi 9207 8e with one 8088 sas cable. I load all trays with hdds but linux mint does not show any disks . Any advice ?
... View more
We need to perform an ONTAP upgrade and we have several broken disks that are in EOS. It’s clear that we cannot have broken disks before performing the upgrade. The idea is to pull the disks off or remove them from the shelves. The shelf model is DS4486 and it has 24 carriers with 2 disks each. We have verified that all the broken disks are grouped by carrier, and in every carrier we have a failed disk and an evacuated disk. Before pulling out the carriers we will unassign the failed disks. As we will remove the entire carriers with broken disks we would like to know if we do need to pull back the empty carrier (after removing the disks) for cooling reasons or for any other reason. Or can we have an operating shelf with some empty bays without any cover? Thanks in advance for your help.
... View more
We're preparing a FAS9000 for an ONTAP upgrade and we have several broken disks that belong to pool NONE and therefore they do not have an owner. The disk model is EOS and it's not going to be replaced. We wanted to unassign those disks but as they do not have an owner we don't know what we should do. Would it be possible to add them to FAILED pool? Would that assign an owner to the disk? Is it safe to remove the disks as they are (pool NONE, no owner) without doing anything to guarantee the ONTAP upgrade must be performed? Thanks in advance for your help.
... View more
