WonkoTheSane

@ChatNoir: Thanks, it works now.

The forum seems to be experiencing some problems. The upload of my diagnostics archive keeps failing. I'll try again later.

Hi all, my server has been stable for about a year. After a BIOS update, I'm seeing frequent crashes, meaning the server is completely inaccessible, can't even be pinged anymore. In order to isolate the issue, I've fiddled with a couple of BIOS settings and stopped using my VMs, but the problem remains. I'm attaching my diagnostics to this message, hopefully someone will be able to help. Thanks & best regards Matthias nasferatu-diagnostics-20220130-0834.zip

Thanks for the info. Was really doubting myself there.

Alright, I feel very stupid now. Has this always been the case? Coincidence that I've never bumped into this issue before, I guess.

Hey all, I've got 2 Unraid servers running v. 6.9.2. On both servers, when I click on an array disk in the array devices tab, neither SMART attributes nor capabilities are displayed for any disk. "Can not read attributes" "Can not read capabilities" The information for my cache disks displays fine. I've checked the system log and was unable to find any entries regarding SMART issues. Thanks for your time!

Thanks for your answer. As you can see, the free space and the capacity of the share differ by several terabytes in each case. Just as a test, I invoked the mover and checked again after it completed. I'm seeing exacly the same numbers alternating when refreshing the directory on that share. I've got another share that also uses the cache disk for new files. There the numbers don't alternate.

Hi all, this is probably a minor issue, but I've noticed for quite some time that the free space reported for an SMB share sometimes differs dramatically between refreshs of said share. See attached screenshots of the same share taken before and after a refresh/reload of the current directory on the SMB share. Best regards Matthias

Hi Johnnie, I just tried that, doesn't seem to make a difference. Still 'no exportable user shares', access denied for disk shares. BUT, I compared ownership and access right flags under /mnt/ to my other Unraid server. Turns out, everything except for /mnt/disks was set to 'rw-rw-rw-' whereas on my working Unraid instance, it is 'rwxrwxrwx'. I'm not really sure how this happened, but it looks like everything is okay for now. Thanks & best regards Matthias

Hi all, as of this morning, all of my user shares have disappeared. Rebooting the server did not fix this issue. The only share I'm seeing is 'flash'. The share configuration on the flash drive is present and looks fine. The disk shares seem to be configured correctly but when trying to access them I get an access denied error. I attached my diagnostics to this message. Any help is appreciated. bignas-diagnostics-20200324-0848.zip

Hi Johnnie, diagnostics attached to this post. Thanks! lochnas-diagnostics-20200222-1145.zip

Hi all, I'm facing a problem I'm not sure how to solve. I have two parity drives and have just replaced 2 data drives in my array. Shortly after starting the server to do a data rebuild, one of my parity drives was marked as disabled. What options do I have now? Any help is appreciated.

Hi again, what I don't understand is this. When I go to the unraid main tab, I see the "Please wait, retrieving information ..." message from unassigned devices. This takes forever, in the syslog I see this: These are obviously all timing out, so something is definetly up. When I connect to the unraid server running unassigned devices via ssh and manually mount one of those NFS shares, it works without a problem in these situations. I can list the contents of the share and copy stuff to/from it. So the server is not offline but somehow the mounts done by unassigned devices become inaccessible after a while. I'm not sure where to go from here. Adding to this: When I do a lazy unmount of the unassigned devices mounts I'm afterwards able to remount them again with the mount buttons on the unraid main page.

Alright, here's the diagnostics. Thanks for looking into it. diagnostics.zip

Update: I downgraded both my servers back to v. 6.5.3 and the problem persists. Let me know if you need specific information/logs.