I reported today the issue to WD technical support.
2 Likes
Workaround #1 : Reboot the NAS MyCloud EX
Workaround #2 (without reboot) : connect with SSH to the MyCloud, and kill the process nasAdmin
( “top | grep nasAdmin”, note the PID_number, and then “kill PID_number”
Workaround #3 (permanent) : downgrade firmware to 5.30.103 as previously explained.
The problem is that I don’t want to restore my NAS configuration and I need the Transmission application.
I’ve downgraded to version 5.30.103 and have no problems. So the latest version of the software does have a bug.
1 Like
Please notice what WD declare on its >> answer 30054<<:
Western Digital Support cannot help with third-party software or hardware.
Please note also, that the website for >>transmisson download<< links to the website of WD mentioned above.
So this is a closed loop without any anchor and the version, which my NAS downloads, is at least nine years old according the website for >>transmission releases<<.
Just in case the last error I see in logs:
2025-05-25T02:56:35.808339+03:00 di= err nasAdmin[4797]: {“corid”:“nad:”,“error”:“recovered panic: internal/sync.HashTrieMap: ran out of hash bits while inserting”,“errorType”:“*errors.fundamental”,“msgid”:“PANIC recovered”,“origin”:“server/ServeHTTP.func1/3821”,“request”:“GET /”,“status”:500}
I have removed two encoded fields because I am not sure they dont contain anything I should not share.
For now I am restarting nasAdmin manually from time to time, but probably will downgrade soon if no fix is available.
1 Like
This seems to work for a quick access to reboot:
most of the time. Sometimes you may need to select the reboot link.
[link to reboot MyCloud] (My Cloud)
Set this as a favorite or workspace in Edge. I’m not sure why I didn’t do this earlier.
I AM SOOOO HAPPY!!! I’m not the only one having this terrible issue!!! (trying to be funny). Yes, since the most recent update I’'m getting it periodically on both of the WD PR4100’s I own. I did everything I could possible think of. Cables, router settings, reboots, PR4100 system restores, bypassing the ethernet switch and connecting directly to the router, you name it and I tried it. And finally, to no avail. I saw a thread from back in 2013-14 where people were having this issue and the unproven common denominator then was an over worked CPU in the units locking up and causing this. People were noting that it was more prevalent during times of high usage like indexing and thumbnail creation. Let’s hope there’s a patch or update to correct this. I fear however that with the end of service of these units coming up in the near future that WD isn’t going to be breaking their necks trying to fix it.
Same issue for me. Did WD staff know about this issue?
This same behavior happens to me, but only once I enable SSH and leave it enabled. I have a Plex Server on my PR4100 that I need to access specific items, and if I leave SSH open, it then flames out to the 500 error. It stays stable if SSH isn’t enabled and I never see the 500 error. Not sure if that’s been covered here already, or just another symptom of the larger firmware issue.
I will downgrade for now to see if I have the same results on the previous firmware.
I also have problem with HDD random wake up despite doing nothing. Anyone noticed this on latest firmware?
1 Like
After updating the NAS firmware from 5.30.103 to 5.31.101, the system becomes inaccessible after reboot, showing a 500 Internal Server Error. Logging in works once immediately after the update, but subsequent attempts fail. Reinstalling 5.30.103 resolves the issue, confirming that the latest firmware introduces a problem.
This type of error usually points to a web server or backend service failing to load properly. If SSH access is available, logs like /var/log/apache2/error.log or /var/log/messages can provide more detail. Restarting the web server or disabling certain services (e.g., media indexing) may offer a temporary fix.
For users with WD My Cloud NAS, this issue has been reported by others after installing firmware 5.31.101. WD has not released a fix yet, and the safest option is to roll back to 5.30.103. Community forums have confirmed this as the most stable solution.
To avoid repeat issues, it’s best to stay on 5.30.103 and disable automatic updates until a new version is released that addresses the problem. Check the vendor’s support pages periodically for firmware updates or official fixes.
1 Like
Once you’ve rebooted, it should be possible to log back in (at least for some period of time), during that window, enable SSH access; the next time it happens, you can run to recover:
# kill $(pidof nasAdmin) && nasAdmin -configPath /etc/nasAdm
Hopefully WD get this fixed and an update pushed ASAP.
Thanks to @Jumbo333, for the pointer.
If anyone from WD reads the forums, here’s the relevant error log detail:
2025-05-02T08:51:49.108917-07:00 di=v7fVTbU3qK err nasAdmin[4448]: {"corid":"nad:O6ftG232R3y055jMzyK1","error":"recovered panic: internal/sync.HashTrieMap: ran out of hash bits while inserting","errorType":"*errors.fundamental","msgid":"PANIC recovered","origin":"server/ServeHTTP.func1/3821","request":"POST /nas/v1/auth","status":500}
…and I see that @jenik also posted this error, I guess I’m late to the party on all fronts!
1 Like
I only see the 500 error if SSH remains enabled. I have had it disabled on 5.31.101 and don’t see any 500 errors. Are others seeing the issue while SSH is disabled?
Does someone know how to downgrade via SSH? I’ve downloaded the firmware file, but I’m struggling with the installation command.
Can you restart the server and then immediately GUI into it that way to do the firmware downgrade via Settings/Firmware Upgrade?
Thanks! It worked and flushed cookies data may helped too.
During the installation, I’ve found these commands in the ps which may be related to the upgrade process:
- nandwrite
- upload_firmware -a -m -n fw.bin
However, I think, there could be some extra steps, and it is preferable to downgrade via the UI. The link for the previous working firmware is: https://updates.mycloud.com/os5/prod/5.30.103/WDMyCloudEX4100_5.30.103_prod.bin. It can be downloaded via a browser or wget/curl.
GOOD NEWS!!! Just got off the phone with WD Support and they are aware of the 500 error problem and are currently rolling out an update to address the issue. All units should receive it by 5/30/2025. So watch your units for an available up date. It is 5.31.102
1 Like
Do you have link to this update? My EX2 says it is up to date with 101 fw.
Hello! How do I install the firmware (5.30.103) if I can’t access the NAS (EX2 Ultra)…?
Hi there,
Glad to see the message of dsfenton. I have the same problem since half hour ago.
No access for my laptop, web browser Firefox. I can connect with my iPad to the dashboard.
All access to the shares is possible from my devices. So I can live with it until the update comes.
No need to complain to WD as the process is running.
