I’ll keep this brief because I’m in disaster recovery mode and this post is really just a “Hail Mary” moment-
I ran a firmware update on one of our 5n2 devices, to the latest firmware version (4.2.2-x) and now the file shares are inaccessible, I can’t stay logged in to the devices as a successful login just immediately logs back out, and I have the constant error in the dashboard “Error while setting up Domain Configuration. Please contact support.”
The device is apparently no longer eligible for DroboCare extended support, and I can’t reach anyone via firstname.lastname@example.org because I don’t have a ticket number in the subject of the emails to them, because I can’t create a ticket because it is no longer under warranty.
This is the kind if thing that sours a person on a brand.
The 5n2 in question is being overnight shipped to me, from the particular location of ours that was using it, and I’ll be trying my hand at getting data from its disks on Friday, but I hope someone here can provide some much needed assistance between now and then.
Not sure what to tell you but join the drobo user group on Facebook. A lot of people there who know a lot… just like here, but no harm in doubling your chances on getting closer to a solution. Sorry I cannot help with that
Today I applied the latest firmware update to my previously reliable Drobo 5N2 and it exhibited the following behavior:
Firmware upgrade using latest version of Drobo Dashboard went smoothly through initial steps
Drobo Dashboard downloaded the new firmware and applied it, and prompted the user to restart the Drobo in order for the new firmware to take effect
Upon restarting the Drobo 5N2, the 5N2 briefly powered up and displayed all LEDs and then completely shut down within 1-2 sec
This behavior is repeatable. The 5N2 never completes the boot process. It simply shuts down almost immediately
I carefully removed all hard drives to protect them and tried to start the Drobo 5N2 without any drives in the device. The same behavior without any observable change is observed
This 5N2 device and power brick has always been protected by a UPS with filtered surge protection. The timing of this problem relative to today’s attempt at a firmware upgrade, especially given what appear to be two other similar recent reports, suggest to me that I am experiencing the same issue and it was triggered by the firmware.
I have submitted a formal support request via the Portal (my Drobo products are registered).
Thank you @dom1 for posting about the pinhole reset procedure. I will likely be attempting to recover my 5N2 this way soon