I have an old HPE Nimble HF40 running OS 5.2.1. Right now, Controller B shows 'Stale' and it's reporting error type 202, ID 35, indicating that NVRAM Batteries are disabled on Controller B. The system is still operating through Controller A, but the fans are exceptionally loud. Since it's not handling any critical tasks, I decided to shut down the attached VMs and host properly. I initiated a shutdown through the Nimble UI and was warned that I'd need a passphrase to access the encrypted disks after rebooting, which I have. After what I thought was a successful shutdown, I pulled both power cables and reseated Controller B just to ensure everything was secure. However, when the unit restarted, the fans remained extremely loud. The management interface appeared briefly, showing all network connections in good shape, but all data drives displayed a warning. I suspect I need to input the passphrase somewhere to unlock these disks, but before I could do anything, the unit silently rebooted again. I currently have no support for this unit and I'm looking for advice on what might be causing the issue and how to possibly get it running in Solo mode on Controller A temporarily.
4 Answers
Have you tried using a serial cable while it's booting? That might give you access to some diagnostic info and clues.
I haven't dealt with the HF40, but I had a firmware issue that made my fans go wild on a similar model. I faced boot loops after trying to recover from errors. I had to call support to resolve both issues. It looks like the HF40 is still supported until 2028; maybe consider getting a one-off support ticket?
Sounds like you're having a tough time there! First, I'd recommend pulling Controller B out completely. If Controller A is functioning well, that might prevent the constant rebooting. I've dealt with similar situations, and often just running on a single, functioning controller can help things stabilize.
I've experienced this exact issue with my Nimble. We decided to repurpose it for backups and bought a used NVRAM battery off eBay for around $100. It's a large bank of capacitors that sits on top of the unit. Try pulling out the controller, check the product number, and see if you can find a replacement. It might be just what you need!
Let me know if that works for you! I want to do the same. Even though the array doesn't like having a faulty controller, it should still run in solo mode. Thanks for the tips!
I just tried that, and it booted up but the fans are still crazy loud and the management UI isn't accessible. I think it's stuck during the boot process. Tomorrow I'll find the serial cable and check the console for more info. This noise is driving me mad!