When I attempt to access a time machine backup I previously created on a USB share (so it worked before), I get the Time Machine window wanting my name and password. It populates with my mac username, so I change it to “admin” and my EX2Ultra password. It attempts to connect and then goes straight back to the same window with my mac username. Again and again. It seems to recognise the password as correct because when I put in an incorrect password the window shakes, as it does for an incorrect password. This issue came up in a 2014 post, long pre-OS 5 and EX2 Ultra. At that time, logging in as Guest seemed to be the answer, but logging in now as guest just reverts to the window wanting the registered user log-in and password. Any help gratefully accepted.
Hi @sdhog ,
Have you opened a Support Case? If not opened, for more information, please contact the WD Technical Support team for the best assistance and troubleshooting:
https://support-en.wd.com/app/ask
I can confirm this issue, and it seems to be a SAMBA/WD bug.
If you can ssh into your mycloudex2ultra use the top utility and the process will show up with status running not nice (R<) like so:
26919 32271 user R< 114m 11.2 1 0.2 smbd -D
After a backup, that process will linger on and block the access to the sparse bundle. Simply killing the process should solve it.
An alternative to get around this, is not using SMB at all and rather user NFS or some other access mode to the drive. Also Western Digital could dig more and fix whatever is causing SAMBA to keep this process lingering and blocking access.
Hope this helps, because this is a great product and a shame that a lot of Apple users have this issue and WD doesn’t seem to care to fix it.
Best,
Alex
This seems like the solution I need. Could you give slightly more detailed instructions for this?
- You need to enable ssh access (Go to: Settings → Network, turn on the SSH switch and click on the configure link. Use the same password as your admin user to avoid forgetting it and leave the user as the default ssd)
- Find the local IP of your device (Settings → Nework and copy the value of “IPv4 IP Address”)
- Use terminal on macOS or PuTTY in Windows / Mac to ssh into the backup enclosure.
- Use ps to find process called smbd -D but only the one that has R< (see example session below)
- Kill the process using kill (see below)
If you can disable SMB/Samba altogether you can avoid all this. Also, by this time maybe WD has already fixed this ?
This is an example session in ssh. When prompted for the password, type it in and you won’t see echo of it on the screen. Press enter to proceed.
ssh sshd@192.168.1.31
sshd@192.168.1.31's password: [type your password here and press enter]
Last login: Mon Aug 26 11:40:34 2024 from 192.168.1.167
BusyBox v1.30.1 (2023-01-16 16:39:18 UTC) built-in shell (ash)
Enter 'help' for a list of built-in commands.
root@MyCloudEX2Ultra ~ # ps aux | grep smbd
2150 alex 116m R< smbd -D
6637 root 2848 S grep smbd
7302 root 78656 S< smbd -D
7305 root 71264 S< {smbd-notifyd} smbd -D
7306 root 71328 S< {cleanupd} smbd -D
22814 root 79680 S< {smbd-scavenger} smbd -D
root@MyCloudEX2Ultra ~ # kill -9 2150
Only kill the one with R< status
@sdhog any update? 
