coolspot

Members
  • Posts

    113
  • Joined

  • Last visited

Everything posted by coolspot

  1. Thanks disabling Netbiis fixed my Tailscale Connection.
  2. 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.
  3. 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.
  4. Is there an update on this error? I'm seeing it in my logs, it doesn't look to be critical, just a nuisance? What is interface 2 - is that ETH1? In my case, ETH1 is bonded to ETH0, so it won't have it's own IP address?
  5. 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.
  6. 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.
  7. 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?
  8. 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?
  9. 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...
  10. 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.
  11. 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)
  12. I assume only NFSv3 is still only supported?
  13. That might do! Let me check it out - I primarily want a way to monitor my HDD Power On hours so I know which drives to swap out.
  14. Is there a way to generate a smart report of ALL drives... I want a way to see my key SMART attributes on a single page (i.e. power on time, error counts, etc.). Is there a plug-in or report? If not, any good console commands to generate such a report? Thanks.
  15. I'm also having a similar issue - 6.7.2 didn't have this problem, but starting 6.8.x bonded LACP DHCP is having trouble on a SuperMicro board. The current workaround is to use a static IP address and this does fix the issue for now.
  16. I just upgraded 6.8.2 and it looks like it broke my networking entirely ... I can no longer get an IP address even in GUI mode.
  17. Interestingly I did not need to disable anything in GUI mode - it just works. Meanwhile in non-GUI mode, the adapters are detected, just that DHCP is not working. On my Netgear switch, it says the LACP LAG is up, so the link is working, but for some reason the IP stack in non-GUI mode refuses to obtain an IP.
  18. Does this reset the networking back to default? I'll give it a try over the holidays.
  19. SuperMicro with LACP LAG stopped working with 6.8.0 upgrade in non-GUI mode. In GUI mode I'm able to get an IP address. Very odd. 6.7.2 and older had no networking issues with LACP. I'm using a SuperMicro X10-SLF7 which has IMPI, but I believe it's on a dedicated port.
  20. My bond with LACP failed as well, but I'm using a SuperMicro board. Weird - I rebooted into GUI mode, and now I have an IP address? DHCP not working in console mode, but ok in GUI mode???
  21. How do I add additional paths to crawl, i.e. SMB, NFS, local? Where are those paths stored? I can't seem to find this very obvious answer in the documentation 😐 Thanks!
  22. 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?
  23. Typically means version control, a copy of the file is stored in the metadata and can be restored at will. It's a feature of BTRFS and most major OSes like Windows can support them (i.e. right click, choose previous versions, etc.) They're great for preventing ransomware because you can take snapshots frequently without incurring a lot of space with BTRFS and can roll back chances en masse very easily. Personally I like to see multiple arrays as well, because I'm going to be hitting the 30 drive limit soon. Going beyond 30 drives with only 2 parity drives isn't really safe, so might as well have multiple arrays/volumes. In the future, volumes could be amalgamated with something like glusterfs similar to what Synology does with Petaspace.