jbquintal

Thank you... I just upgraded from an APC Smart UPS (SUA1500) and thought it would be plug and play. Luckily, I was able to get my SRV2KRI-E up and running using the steps you outlined.

Thanks!

thank you! Will try this out. Thanks as well. Happy Holidays!

I'm having the same issue. I'm just stuck at this page for hours on end. I can access the flash drive and manually copy files off of it. What's a good way to manually back things up and create the zip? Is there a

@JorgeBI tried doing the restore option as suggested, but I'm running into this error. Same problem using the -i option. Any other thoughts?

I had the exact same problem... drives were throwing random read errors (mostly when I try accessing a spun down drive). Extended SMART tests didn't show any problem with the drives, and all the unreadable sectors were never the same. I tried swapping out two drives, two controllers, and another set of cables... it ended being a bad PSU and now one of my drives have an unmountable FS. If the drives are good, it's probably the cable, controller, or in my case, the PSU.

Thanks... I'm about 60% done with the rebuild. I'll update my post after.

Thanks... so do I stop the rebuild or just let it finish? Can I run the btrfs restore now?

So I had a failing power supply that messed up my array that I just diagnosed earlier. Some back story first, this all started out with certain drives throwing read errors after spinning up from sleep. All the errors never pointed to the same sectors, all different sectors. All the drives cleared SMART extended tests and work fine after rebooting. I swapped two drives out, two controllers, and a set of cables and the issue still occurred. I then cleaned the entire system out and redid cabling and everything. Since then I've been running fine for about 4 days until earlier. When I woke up, there were massive errors across several drives. The server reported that Disk1 was disabled, with contents emulated. I shut it down and I did some checking and I found out that my +5v rail was dropping to +4.6v which would explain my drive issues when spinning them up. I swapped out the PSU and booted back up again. My miss was that I didn't dump diags before shutting down the first time. Since my array isn't set to autostart, I took off disk1, started the array. Then I stopped the array, and re-enable Disk1. I see that the parity rebuild has started and the contents have been supposedly emulated, but it isn't mounted. What can I do to fix this? Have I lost all files on Disk1? cosmos-diagnostics-20211203-1619.zip

Any ideas as to when we could potentially see this natively supported in unRAID?

I rebooted the server as soon as my parity check finished. I'm able to access the WebGUI now. I'll update this post if it acts up again.

Thanks!

Thanks. I did notice the Unassigned Devices error keep cropping up. I did a quick search before and it just says that it's caused by having multiple browsers open. In any case, i'll just finish the parity check and reboot the server and observe if it'll happen again. "powerdown -r" is the proper way to do it, right?

Apologies for not outlining what I've tried. In any case, here's what I've looked at so far. https://forums.unraid.net/topic/87876-500-internal-server-error-solved/ <--- Doesn't seem to apply. I don't have any VLANs or any load balancing set up... https://forums.unraid.net/topic/70428-unraid-500-internal-server-error/ <--- Doesn't seem to apply. Plex and other Dockers seem to work just fine. I can play vides on Plex... https://forums.unraid.net/topic/86364-500-internal-server-error-nginx/ <--- Doesn't seem to apply. Different error codes in /var/log/nginx... https://www.reddit.com/r/unRAID/comments/7ygav2/webgui_500_internal_server_error/ <--- Tried this...

Hi Everyone, for some reason I can't seem to access the webGUI. I took a look at a few threads with the same issue and tried some of the solutions, but nothing worked or isn't applicable. I'm currently doing a pre-clear of two drives and a parity check. I'm able to access the machine via SSH and things seem to be working... All docker apps seem to be working just fine and are reachable via their respective webGUIs. That being said, I've attached my diagnostics file to see if anyone can help figure out what's wrong. I'll keep it up until the parity check finishes and I'll do a reboot to see if that resolves the issue. By the way, is "powerdown -r" the right way to gracefully shutdown? cosmos-diagnostics-20210106-0037.zip

Hey Ben, Thanks... I resolved mine by fixing permissions. Works great now.

First up, thanks for the docker! I've been waiting for a docker app that supports Omada Controller v4. Right now, I'm running a windows vm just to get the controller. Anyway, I tired installing your docker but I must be doing something wrong. Any thoughts?