coolspot

I do not have any containers or proxmox running, only file sharing services. I do have a bunch of plug-ins (most which I don't really use) but I can't see anything that would affect networking except for TailScale?

Downgrading to 6.12.8 fixed NFS for me - so something was broken between 6.12.8 and the newest release.

I just found this thread, my NFS shares stopped working and I suspected it was due to a recent unRAID upgrade. I am also on 6.12.13.

Weird error - if I use Chrome, which is already signed into Plex, it does not fetch a token correctly. I used a new Browser - edge, did a fresh login and it retrieved a working token.

Did you ever figure this out, I have the same 36 bay enclosure with the same SAS2-846EL2 controller, and fully loaded I'm maxed out at ~90MB/s using SATA drives.

I'm already running a LSI SAS2308 card and my Ironwolf 8TB drives were dropping, so not sure if going to a newer LSI chipset would make a difference. It's definately related to wake up however.

I got an RMA of my Ironwolf and it was replaced with a ST8000VN004-2M2101 and it just dropped off It seems the 2M2101 seem to be most prone to the this error. My other ST8000VN004 are different revisions and don't seem to drop off.

Hi all, This is still happen with 6.11.1 right? I turned on spindown on my drives and my ST8000VN004-2M2101 dropped off. I see others mentioning the same revision (2M2101). My other ST8000VN0004 seemed to be fine ... but perhaps it's just time?

Did you ever figure this out? After enabling spin down, two of my drives died - a ST8000VN04 dropped and also a WD 10TB Red completely died. The ST8000VN04 doesn't have any SMART errors, and I was able to add it back to the array, but on array shutdown, I got a sector error in the logs (but nothingin SMART). Very weird. Nov 5 20:02:07 nasserv kernel: XFS (md1): Unmounting Filesystem Nov 5 20:02:07 nasserv kernel: md: disk22 read error, sector=3907717616 Nov 5 20:02:07 nasserv kernel: sd 1:0:6:0: Power-on or device reset occurred Nov 5 20:02:07 nasserv kernel: md: disk22 write error, sector=3907717616 Nov 5 20:02:07 nasserv kernel: md: disk22 read error, sector=0 Nov 5 20:02:07 nasserv kernel: md: disk22 write error, sector=0 UPDATE... Looks like there maybe a compatiblity issue with the ST8000VN04 and Unraid?

It worked, the cert came through as expected.

I'm having the same issue with 6.10.3...

Hi all, same error - I just upgraded to 6.10.3, clicked the "Upgrade Certificate" button and lost my Cert. I tried to reprovision the certificate but I see the following error in my logs: Jul 17 02:24:11 nasserv emhttpd: shcmd (312): /usr/bin/php -f /usr/local/emhttp/webGui/include/ProvisionCert.php Jul 17 02:24:12 nasserv root: Error: Server was unable to provision SSL certificate Jul 17 02:24:12 nasserv emhttpd: shcmd (312): exit status: 1 Jul 17 02:24:12 nasserv emhttpd: shcmd (313): /etc/rc.d/rc.nginx reload Jul 17 02:24:12 nasserv root: Checking configuration for correct syntax and Jul 17 02:24:12 nasserv root: then trying to open files referenced in configuration... Jul 17 02:24:12 nasserv root: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok Jul 17 02:24:12 nasserv root: nginx: configuration file /etc/nginx/nginx.conf test is successful Jul 17 02:24:12 nasserv root: Reloading Nginx configuration...

I just noticed this in my logs with unRAID 6.9.2. Apr 4 21:14:02 nasserv Parity Check Tuning: Pause Apr 4 21:14:02 nasserv Parity Check Tuning: Following drives overheated: disk23(108C) However, checking the SMART values, the disk never exceeded 53C. This is the first time I've seen such an error... anyone ever have this issue before? Checking the disk's SMART values, it seems, Attribute 2 is 108, could it be that it mis-read the value? 2 Throughput performance 0x0004 128 128 054 Old age Offline Never 108 I just updated the plugin to the latest version to see if it'll resolve the issue, and now it's stopping the parity at a lower temperature: Apr 4 22:35:02 nasserv Parity Check Tuning: Paused Parity Sync/Data Rebuild (2.5% completed): Following drives overheated: disk19(42C) disk23(42C) Apr 4 22:35:02 nasserv Parity Check Tuning: Paused Parity Sync/Data Rebuild (2.5% completed): Following drives overheated: disk19(42C) disk23(42C) My warning temp is 45 and critical is 55c.

I noticed tabbed view doesn't stay on the proper tab when switching drives - it will flip the tab back to the Settings Tab rather than stay on the tab I selected (i.e. Attributes)

What's the best way to crawl multiple paths and remote paths - how do I pass paths into diskover? Should I just run the treewalk client on each remote device to crawl? What about devices that don't support Pyton?