jbardlett

I figured out the original issue... The problem was with this script that I was using to replicate one server to another.... Once I edited the GO file back to normal and rebooted, I was able to access my shares. Still can't gracefully shutdown or reboot either server, but I can at least stop the array and power down mechanically.

The device with the HBA issue wasn't booting from USB despite everything being set to ONLY boot from USB. I found the solution in the forum that with that particular combination of SuperMicro mainboard and HBA, the BIOS on the HBA can randomly take over and try to boot from the HBA... Took me a couple days of searching and reading and trying things to find that solution.... I can connect to both severs via the webgui at this point. The arrays are starting correctly; however, the original device (the one I accidentally yanked the USB stick out of while running) won't gracefully shut down or reboot. It is also not running a scheduled script from the User Scripts plugin. Krusader runs on both units. I also added Plex on both and it works, and can see the data. I've changed all the shares to Public for both NFS and SMB on both devices. Permissions in nas3200 mnt/user all folders show nobody users except for the Music folder which shows root root Permissions in coraid mnt/user all folders show nobody users coraid-diagnostics-20210202-1611.zip nas3200-diagnostics-20210202-1611.zip

Greetings all, It's been a terrible day for Unraid and I. Last night my rsync backup job failed for some unknown reason. After checking the logs on the job, I realized the server had become unavailable. The backup Unraid server now won't boot from ANY USB drives... That is not the worst part. While I was trying to fix that, I mistakenly removed the USB from my primary Unraid server... I put it back in immediately, though I don't know that I put it in the same USB port. Now, I can access the GUI from a web browser. I can stop or start the array. I cannot, however shutdown or restart the box, nor can I access any of the shares from other devices. Any help would be greatly appreciated. Update: I got the second Unraid server to start back up. Apparently the HBA bios needed to be disabled.... Not sure why that affected things 2 weeks into use... Of course the machine is performing a parity sync that is slated to finish in just over 2 days, but the interesting thing is, I cannot access shares on that unraid server either... Same error message in the topic from my win10 laptop, my windows server 2016, or ( albeit with a more Apple message) on my iPhone via FileBrowser. I also realized that a scheduled user script no longer runs. (rsync backup job) Update #2: I used one of my old Buffalo WSS5400 units to create a new Unraid server. I added all the same plugins and security, and created a share. SMB and NFS are set up identically, as near as I can tell, on the 3 servers. I can access the share on the new server, but on the old servers, as soon as I try to access them either by name or IP, I get the error Network Error Windows cannot access \\<IP Address> You do not have permission to access \\<IP Address> Contact your network administrator to request access. Both offending Unraid server can talk to each other via rsync in the terminal, but not via script. I am replicating data so that everything is on both servers. Once that process is complete, I will be able to engage in more destructive fixes... Any assistance would be appreciated.