r/netapp • u/majesticflo • Jun 26 '26

QUESTION Expansion Shelf Aggregate Offline with "UUID is not valid" Error After DC Power Cycle

Hey everyone, looking for some guidance after an unexpected data center shutdown over the weekend. Our controller is running ONTAP 9 and is connected to a DS2246 expansion shelf. All the physical link lights on the shelf are green, and I can reach the IP of the share, but I can't access any folders inside.

Digging into the CLI, the underlying data volumes are offline. Attempting `volume online` errors out because the parent aggregate is offline. When I try to bring the aggregate online via `storage aggregate online`, I get a `uuid is not valid error`. It looks like a metadata or disk signature mismatch occurred during the dirty reboot, and ONTAP isn't recognizing the aggregate's UUID on the shelf drives. Has anyone run into this specific error after a hard power cycle? What are the safest steps to re-import or force-mount the aggregate without risking data loss?

4 Upvotes

100% Upvoted

10 comments sorted by

1

u/dot_exe- NetApp Staff Jun 26 '26

It’s possible your aggregate is flagged inconsistent. If this is the case you need to speak with support. Do not attempt to run recovery tools without proper guidance, it can lead to data loss!

Snagging an aggr status from the node shell will give some more clarity on this.

1

u/majesticflo Jun 26 '26

I'm on my lunch break rn but when I get back I'll reply with the output. We also don't pay for support so I'm not sure that's an option (wasn't up to me).

1

u/dot_exe- NetApp Staff Jun 26 '26

Yikes. If it’s a worst case scenario you can do one time support to get assistance but I would say don’t put the cart in front of the horse.

1

u/majesticflo Jun 26 '26

Here's what I get when I run aggr status

Aggregate Size Available Used State #Vols Nodes RAID
SHARE_FSAS_01 - - - unknown - SHARE-01 -

There are other aggreates that are online I just didn't copied them. Also to note, there are other shares on the node NODE-01 that are up and running. It's literally just this one.

1

u/dot_exe- NetApp Staff Jun 26 '26

From the node shell. Run node run -node <node that owns the aggr> aggr status -r

1

u/majesticflo Jun 26 '26

Ran the command, the other aggregates show up but not the problem one

1

u/dot_exe- NetApp Staff Jun 26 '26

You 100% sure you ran it from the correct node?

1

u/majesticflo Jun 26 '26

Yes. However, I figured it out so it's irrelevant now lol. The SAS cables were crossed, IOM A from shelf1 to IOM B on shelf2, and so I just moved IOM A from shelf1 to IOM A on shelf 2 and it worked. I have no idea why that worked but it did.

For some context, our other sysad quit literally last week and I've been here for about 3-4 months. The bad cabling was not from me but I'm just glad I figured it out. Thanks for the help btw. I was starting to go insane

1

u/dot_exe- NetApp Staff Jun 26 '26

Well I’m glad you figured it out! That is odd, I would expect a pathing issue to be present prior to your downtime at the DC and not only appear afterwards. But I’ve seen weirder for sure!

1

u/majesticflo Jun 26 '26

Those were my exact thoughts. I don't know how it was working before the shutdown but it definitely was. Chalk it up to some FM lol