nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Entire FAS8020 SAN goes down when hard drive (HGST 450GB 10K HUC109045CSS600) is added to disk shelf

-G-

Hello!

I have a FAS8020 SAN cluster with two DS2246 shelves running ONTAP 9.1P19. This thing is out of warranty and we currently just use it for backups. I had a bad drive happen the other day. Didn't think much of it as I've replaced drives dozens of times. Popped the drive into the shelf; went into the OCSM GUI; saw the new drive and added it to the node. It sat there infinitely trying to add the drive. I thought it was just taking awhile, until an hour later, I finally realized I lost the entire SAN!

I manually consoled into the cluster, sure enough both nodes went completely down hard. Saw this error on both nodes:

PANIC: Illegal Disk Configuration in SK process config_check on release 9.1P19

Naturally, I removed the disk and manually booted the nodes one at a time in the CLI (via console). Everything came back up ok. Luckily we bought 2 drives so I thought maybe we had a DOA. Nope. 2nd one did the same exact thing.

So my question here is, do I have a hardware incompatibility issue or a san configuration issue? Based on this error, I would assume it would be an incompatible drive. We tried to buy the same drive as what was in there (HGST SAS 450GB 10K Model: HUC109045CSS600). I'm not sure if there is a different spec I need to check? Fits perfectly. I think the shocking thing is that it takes the whole SAN down. I would have thought it would take one node down but not the whole thing at the same time! So I'm not sure if there isn't a configuration issue somewhere too.

Appreciate any help. Let me know if I am missing any details. Thanks!

Find more posts tagged with

Accepted answers

andris

It appears that you did not purchase NetApp-sourced drives. ONTAP requires specific custom formats and drive labeling for it to be considered supported.

As for the panic/disruption you see, see: Bug ID 1185571 - ONTAP disruption occurs when an unsupported hard disk drive (HDD) or solid-state disk (SSD) is detected

All comments

andris

It appears that you did not purchase NetApp-sourced drives. ONTAP requires specific custom formats and drive labeling for it to be considered supported.

As for the panic/disruption you see, see: Bug ID 1185571 - ONTAP disruption occurs when an unsupported hard disk drive (HDD) or solid-state disk (SSD) is detected

-G-

Thanks Andris! At least I know its the drive. As well as probably upgrading ONTAP will prevent it from completely going down in the future.

So, how can I buy a NetApp sourced drive? What specs do I need to follow? Do I just need to just look for drives that are labeled for NetApp?

andris

Since the FAS8020 (and its drives) have not been supported for a few years, it's unlikely you can source the drive from NetApp. You can certainly discuss the situation with your NetApp account team or partner.

You can determine the existing drive marketing "X" part numbers and the manufacturing part numbers (Format: XXX-YYYYY) by looking at the physical label of the NetApp drive or from the CLI: What is the ONTAP CLI command to find a drive part number?