u/Glittering_Cheek3235

Similar to some others here, my 2 year old Asustor backup just suddenly failed. This wasn't after any sort of external event I know about, and it wasn't during a normal backup time.

I'm sure there was *some* trigger, but nothing obvious. It just happened mid-day yesterday. It's been running in my house since late 2024, with 8x Seagate IronWolf Pro 24TB drives in RAID 6 config, and 2x WD_BLACK 2TB NVMe drives for cache, handling daily and weekly backup, plus pulling down files from OneDrive. It's connected to the network and also USB-C.

Now, during boot, when it gets to "Starting Service" it flashes red/orange/green with a beep for each cycle. It shows an IP address, so this is fairly far along in the boot cycle, it would seem. However, it doesn't appear in the client app on my PC, and I cannot reach the browser "desktop" configuration by IP address.

Reading the posts here yesterday, I powered it down after the failure and let it stay powered down and unplugged all night. Not sure why that's a thing (I'm assuming for some sort of capacitor discharge?) Powered it back on late this afternoon.

I noticed one drive (top right) didn't have its light on in the same cadence as the others, so I pulled that and tried booting. No change in behavior, so I put it back in place.

I haven't opened it, pulled the cmos battery, etc. that others recommend. It's also not in a location where it would work any connections loose.

Any suggestions for obvious things to consider? Given placement up on the top shelf of a utility rack in my basement, getting this within range of a monitor is going to be super annoying, so don't want to do that unless there's proven need to. Of all the random mini PCs I have in that room, this was the last thing I had expected to fail, so I didn't make it easy to move. :P

Lockerstor 8 up on a high shelf

Edit. The steps shown on the LCD are
- Starting-System Please wait ...
- Booting-Storage Please wait ...
- Booting-Service Please wait ...

The error beeps start with Booting-Service.

I also verified, through the front panel, that the one disk volume it shows has tons of free space. This isn't a capacity / disk full issue.

Thanks

Pete

The workarounds for inMusic (AKAI, m-audio, Rane, Numark, old Avid, etc.) drivers, and for dynamic ports (loopMIDI, rtpMIDI, SSL, NI, etc.) which have been available on our Discord server for a couple months now, started rolling out into retail Windows 11 24h2, 25h2, and 26h1 on April 30th.

The release uses the CFR (Controlled Feature Rollout) process, so installing the KB is not enough to have the feature enabled. It will be enabled *after* KB install, within the next 30 days.

This process is explained on our Discord server https://aka.ms/mididiscord (please read the full #start-here pinned post). The full list of fixes is also on the Discord server.

If you have rolled back / uninstalled updates, or previously used third-party tools to block updates, you will need to first fix your PC using the Settings > System > Recovery > "Reinstall Windows from Windows Update keeping your files, settings, and apps" option. If you don't do that, chances are you will have missing registry entries.

If you need the fixes for dynamic ports and/or inMusic drivers now, and they are not yet enabled on your PC, you can still use the previews from that Discord server. Follow the instructions pointed to from the #start-here post. There's also information about what to do for those after updates, and after the end of the month.

If you run into issues, please follow the instructions in the #start-here post for where and how to post questions. I'm traveling to Berlin for the next week and will not be checking Reddit or most other forums other than our Discord server.

Thanks.

Pete
Microsoft