PeeBee

Problem: Internal Server Error When Opening WebUI This problem started a few months ago but it hasn't been a priority to fix because everything still syncs fine to my other computers. When I open the WebUI I get an Internal Server Error. The error then states "The server was unable to complete your request". I made a video of the problem, shown below. Any thoughts? (diagnostics attached) tower-diagnostics-20200219-2126.zip

Thanks, I assume you mean here:

This problem started a few months ago but it hasn't been a priority to fix because everything still syncs fine to my other computers. When I open the WebUI I get an Internal Server Error. The error then states "The server was unable to complete your request". I made a video of the problem, shown below. Any thoughts?

Thanks, I'll remember that if the problem reoccurs and troubleshoot accordingly. Thanks again for your help.

To troubleshoot this I moved one of my Google Wifi access points next to the server and plugged the server into it. Still 10 Mb/s. Just for fun I rebooted the server and it reverted to 1000 Mb/s! I moved the network cable back to the switch and it stayed at 1000 Mb/s, which I confirmed with a network test. In hindsight I should have rebooted the server as part of my initial troubleshooting process. I still wonder though why the server suddenly lowered the network adapter speed to 10 Mb/s. It's very odd. Thanks johnnie.black for your help on this. Crisis averted.

Further to my problem... Here are the results of the ethtool command, confirming that the port is only running at 10 Mb/s: sudo ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 10Mb/s Duplex: Half Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: on (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: yes

Yes, I first suspected the cable and swapped it with no change. Also tried different ports on the switch, again with no change.

I suddenly started seeing really slow transfer speeds (1 MB/s) to my UnRAID shared folders. A network test using a LAN Speed Test utility (from https://totusoft.com/lanspeed) confirmed that the server network adapter is only running at 10 mbps. Why would the network adapter suddenly drop its speeds to 10 mbps? Is that something that can be changed within UnRAID? (According to the specs it's supposed to be a 10/100/1000 adapter.) If the network adapter has suddenly flaked out can I install a PCIe network card? Any thoughts? I've attached the diagnostics if it will help. tower-diagnostics-20200120-0409.zip

Are you connecting to a USB 3 port? Have you tried it on a USB 2 port instead? I have one device that only works on USB 2, so I wonder if that might also be your problem.

Congratulations on the 100k user milestone. That's pretty impressive. I love that I was able to set up and maintain UnRAID fairly easily with the help of the amazing support community. As an improvement for 2020, I'd like to see a simplified report on the health of the drives so I know when to start thinking about replacements. I'd also like to see Unassigned Device shares show up under the Shares tab on the web interface.

I saw that you uploaded a new UD update. It fixed the problem! I guess I can return the external drive I ordered to back up the Drobo before deleting that extra partition. It seems to work just fine the way it is. Thank you so much! I really appreciate the time you took to diagnose and fix this. The UnRAID community is luck to have you in it.

Screenshot attached.

No luck. See attached diagnostics. tower-diagnostics-20191220-1717.zip

I'll watch for the update and let you know how it works. Thanks for the amazing service!

I hooked the Drobo up to a PC and it took at least two minutes to show up. That would confirm what you are suspecting, that it's timing out while mounting.

Will do, thanks.

It's strange that it's been working for over a year and then stopped suddenly with one the updates. Did you shorten the timeout period for mounting? Was that the only significant thing that changed that could have affected it?

Hmm, shows for me. You might need to refresh. Here's the direct link to where I posted it: I've also uploaded it to Dropbox, if you're still having troubles: https://www.dropbox.com/s/q60375scvs8g42j/tower-diagnostics-20191219-1642.zip?dl=0

Done! (Attached to my post)

I have a Drobo installed on my UnRAID server via USB. The problem is, about two weeks ago, after an Unassigned Devices update that prompted me to restart the server (not sure which version this was), my Drobo would no longer mount. My UD plugin is up-to-date and I have tried rebooting the server, to no avail. Any hints on how I can get this working, short of moving the Drobo to another computer? Thanks. tower-diagnostics-20191219-1642.zip

Did you ever get it working? I'm getting the same "wait..." message.

Found it... Good catch, thanks. Some users remarked that Marvell may have patched this problem in later versions of its firmware. I'll give it a shot and report back.

Thank you to those that replied about me using external USB enclosure for parity drives. I've ordered a PCIe SATA card so I can use the drives internally.

It's an old machine that can't recognize drives bigger than ~2 TB. I didn't think a SATA controller would get around that problem, but you think it will? I will definitely get a SATA controller if that's the case. What's the problem with using USB 3 drives for parity? Is it a speed issue or something else? (For my reference only; I'm not disputing you.)

Thank you, that helps me tremendously. Like I mentioned, I'm a noob to unRAID so the concept of dockers and how they fit in is completely alien to me. Before I give you the /dev/disk/by-id, I should mention that I now have one of my two 6 TB drives mounted as a parity drive. I was able to do this by taking the array offline and mounting it under the Array Devices section of the Main tab. You'll now see my old 2 TB parity drive in the unassigned section as well as the 6 TB drive which UD can't recognize. I plan on mounting the 2nd 6 TB drive as a parity drive as well but I wanted to give you an opportunity to continue troubleshooting why the drive isn't being recognized by UD (if you want). Here is the result of ls -l /dev/disk/by-id: root@Tower:/dev/disk/by-id# ls -l total 0 lrwxrwxrwx 1 root root 9 Jan 9 17:21 ata-ST1500DM003-9YN16G_W240RMHQ -> ../../sde lrwxrwxrwx 1 root root 10 Jan 9 17:21 ata-ST1500DM003-9YN16G_W240RMHQ-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Jan 9 17:21 ata-ST2000DL003-9VT166_6YD06G63 -> ../../sdd lrwxrwxrwx 1 root root 10 Jan 9 17:21 ata-ST2000DL003-9VT166_6YD06G63-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Jan 9 17:21 ata-ST31000333AS_9TE20Q9W -> ../../sda lrwxrwxrwx 1 root root 10 Jan 9 17:21 ata-ST31000333AS_9TE20Q9W-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 Jan 9 17:21 ata-Samsung_SSD_850_EVO_500GB_S3PTNF0JB81726B -> ../../sdb lrwxrwxrwx 1 root root 10 Jan 9 17:21 ata-Samsung_SSD_850_EVO_500GB_S3PTNF0JB81726B-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Jan 8 17:36 ata-TSSTcorp_CDDVDW_TS-H653N -> ../../sr0 lrwxrwxrwx 1 root root 9 Jan 9 17:21 usb-SanDisk_Cruzer_Fit_4C530001281025115022-0:0 -> ../../sdc lrwxrwxrwx 1 root root 10 Jan 9 17:21 usb-SanDisk_Cruzer_Fit_4C530001281025115022-0:0-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Jan 9 17:57 usb-WDC_WD60_02FZWX-00GBGB0_000000000000-0:0 -> ../../sdf lrwxrwxrwx 1 root root 9 Jan 9 17:21 usb-WDC_WD60_02FZWX-00GBGB0_000000000000-0:1 -> ../../sdg lrwxrwxrwx 1 root root 10 Jan 9 17:21 usb-WDC_WD60_02FZWX-00GBGB0_000000000000-0:1-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 Jan 9 17:21 wwn-0x10612510827581820928x -> ../../sdd lrwxrwxrwx 1 root root 10 Jan 9 17:21 wwn-0x10612510827581820928x-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Jan 9 17:21 wwn-0x11153183416998973440x -> ../../sda lrwxrwxrwx 1 root root 10 Jan 9 17:21 wwn-0x11153183416998973440x-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 Jan 9 17:21 wwn-0x14622698090324119554x -> ../../sdb lrwxrwxrwx 1 root root 10 Jan 9 17:21 wwn-0x14622698090324119554x-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Jan 9 17:21 wwn-0x2843550472478937088x -> ../../sde lrwxrwxrwx 1 root root 10 Jan 9 17:21 wwn-0x2843550472478937088x-part1 -> ../../sde1