May 31, 20224 yr Hello, I had a drive failure in my unraid box last week. Upon receiving the warning I ran a read test that completed with 0 errors. I can see the drive is disabled, and after shutting down the machine I was able to pull the drive and confirm that it would not mount on any of my other machines. I replaced the drive and started up the system. I immediately received an error that my USB stick was not read/write enabled. I downloaded a backup of the drive (I had foolishly not setup automatic backups). I shut down the raid and plugged the USB into a windows machine. As recommended on other threads in this forum. Windows attempted to repair the drive and did make some corrections. After running the repair the drive would no longer mount on any of my computers nor would the unraid boot from it. I assumed failed USB. I built a new Unraid USB using the same version as the previous setup (unraid 6.9.2). I copied my config from the backup I had downloaded earlier in this process, and moved the license to the new USB. Fired up the server and no more read/write error. I re assign the replacement drive to the same slot as the field drive (both drives of equal capacity) and restore from parity. Once the parity check/rebuild completed I assigned a 2nd parity drive that was not present int he system. I ran a 2nd parity check and now have 2 drives parity drives and no parity errors. I have now run into an issue where none of my clients will connect to the unraid. MacOS states: "this server will not allow any additional users to log on. Try to connect again later" Windows: "An error occurred while reconnecting to <share> Microsoft Windows Network: the local device name is already in use the connection has not been restore" As far as I can tell I have copied the configuration of the pre-failed state precisely. My theory is that the migration to the new USB boot stick has caused this issue. After going through my network settings, rebooting the router, and rebooting all of my devices I'm not sure where to look next. I have also created a new user and was unsuccessful in connecting to shares over the network with Mac or Windows. Same goes for SSH with the new user. SSH continues to work with the root user. Connecting using SMB://ip does not find the server. ssh root@ip and ping <ip> both work as expected. edit: I have finished the parity checks for both parity drives and have upgraded the server to 6.10.2. Unfortunately the issue persists. edit: I have tried changing the static ip to another open address. The UI moved as expected. SSH root@ip updated as expected. Issue with Windows/Mac clients persists. This is my first post so I apologize if I have missed any pertinent information and will upload anything required to assist. storasaurus-diagnostics-20220530-1655.zip Edited June 2, 20224 yr by Stackk added more information regarding USB replacement. Edit2: added information regarding unraid update. Edit3: added additional troubleshooting steps performed, formatting
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.