Did a bunch of research on-line, and read that the power supply (which is a desk wart style) can cause that. There's enough power left to run the chassis, but not the drives. I was able to update the firmware even with it in generally useless mode, and I ordered a new power supply. It's supposed to be in sometime on Monday.
Fingers crossed.
But the drobo will be replaced. Not sure which Synology I'll be getting, but this is my second drobo failure, without a hard-drive failure.
My fingers are crossed for you as well.
I have an old 4-bay Synology NAS that’s worked reliably for me for almost 10 years, with just two disk replacements (3 TB) over that time. I don’t really trust it anymore for critical data, or at least data that isn’t backed up elsewhere. It’s handy still because I run my local NTP time server there (for my telescopes to use) as well as for some background frame grabs and posts from my weather cams.
I know new Synology firmware allows you to use btrfs to add extra data integrity, which is very useful, but I’m baffled by their choice to still use LVM and MDRAID underneath it, rather than letting btrfs do the RAID work. I’ve seen too many folks have really difficult times recovering when their LVM setups had issues (RedHat used to default to LVM for Linux installs, so lots of folks at my former place of employment had Linux laptops and desktops with LVM, which, frankly, makes no sense for single drive systems).
I’m still a ZFS guy, although btrfs would be a fine substitute. Last week I got around to doing my periodic backups of my various ZFS filesystems to my two big ZFS boxes, and was reminded how powerful serialization (send/receive, available for both ZFS and btrfs) is. So easy to do incremental backups. I’ve had the experience of a failed system when all I had to do was move the ZFS hard drives to the new system and do a “zfs import” to fully recover the filesystems.
I finally pulled the trigger today on an LTO6 tape drive purchase, which will be used as an additional backup for those serialized ZFS filesystems. I’ll finally have a true 321 backup strategy (3 copies, on 2 distinct media, with one copy in a different physical location).