coolspot

Members
  • Posts

    113
  • Joined

  • Last visited

Posts posted by coolspot

  1. On 7/7/2023 at 12:01 PM, dorgan said:

    I'll try looking at this in firefox, but if you encounter this again before refreshing can you see if there are any errors in the developer console for firefox??

     

    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.

  2. On 1/3/2023 at 7:21 AM, ReLe said:

    Just an update, after moving to LSI9207, from LSI2008 on 3.11.2022, no errors after switch to this date. But, who knows what it really was in my case and when the Ironwolf disks start to act again.



    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.

  3. On 11/6/2022 at 3:42 AM, ReLe said:

    My latest fails were on H310 crossflash LSI 2008 based card and Unraid version 6.11.1. On 3.11.2022 switched to LSI9207 and time will tell if this helps.

     

    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.

     

     

  4. On 4/10/2021 at 11:58 AM, Mason736 said:

    So I woke up this morning, and two of the ST8000VN04 drives had dropped from the array with read errors.  They are both brand new drives from Seagate.  
     

    I'm convinced is the issue with the ERC and low voltage spin up, so I followed the above instructions.  We will see if they, or any of the other VN04 drives drop out of the array again.

     

    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?

     

     

  5. 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...

    • Like 1
  6. 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. 

  7. On 1/5/2018 at 3:02 AM, bonienl said:

     

    Use "Tabbed" view, see Settings -> Display Settings -> Page View

     

    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)

  8. On 11/16/2020 at 5:26 PM, falconexe said:

    You mean like this?

     

    Yeah you can install the Ultimate UNRAID Dashboard I developed. It has this functionality and more.

     

    You can find it here:

    https://forums.unraid.net/topic/96895-ultimate-unraid-dashboard-uud/

    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.

  9. 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.

  10. On 2/6/2020 at 12:05 AM, bonienl said:

    There seems to be some trouble to get the bonded interface up and ready.

    
    Feb  5 15:50:42 Beanstalk dhcpcd[1527]: br0: carrier lost
    Feb  5 15:50:42 Beanstalk kernel: br0: port 1(bond0) entered disabled state
    Feb  5 15:50:44 Beanstalk kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
    Feb  5 15:50:44 Beanstalk dhcpcd[1527]: br0: carrier acquired
    Feb  5 15:50:44 Beanstalk kernel: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex
    Feb  5 15:50:44 Beanstalk kernel: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond
    Feb  5 15:50:44 Beanstalk kernel: bond0: first active interface up!

    Does your switch/router have proper support for LACP (802.3ad)?

     

    Instead of using mode 4, try mode 6 as bonding protocol. This requires no special configuration on your switch/router

    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.

  11. 2 hours ago, ksarnelli said:

     

    This is exactly the issue I was seeing - I was able to get it working in GUI mode by disabling/re-enabling bonding *and* bridging, but upon rebooting into normal (console) mode it wouldn't work again.  Still have not had a chance to investigate further, but just wanted to make sure I noted it here.  The only difference is that I'm using an older Supermicro board (an X8DTN).  In the meantime I disabled LAG on my switch and in unraid.

    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.

  12. On 12/20/2019 at 10:35 AM, Frank1940 said:

    One thing to try.  Rename (in the   config   folder)  network.cfg   to network.cfg.old     Now restart the server.  You will probably have to shut the server down and do the rename on a PC (or use the command line, if you are comfortable with it).

    Does this reset the networking back to default? 

    I'll give it a try over the holidays.

  13. 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.

  14. On 12/17/2019 at 8:04 AM, treos33 said:

    My switch does support LACP. This exact configuration was working perfectly for months on 6.7.2.

    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???

  15. On 12/8/2018 at 2:49 AM, shirosai said:

    I'm developing diskover and it has been recently released on linuxserver.io docker image. If you are looking for something to index your files and be able to search and manage them, check out diskover.

    https://shirosaidev.github.io/diskover/

    https://forums.unraid.net/topic/75763-support-linuxserverio-diskover/

    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!

  16.  

    42 minutes ago, cpl said:

    what does snapshots mean? building parity at set intervals like snapraid?

    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.

    • Like 1
    • Thanks 3
  17. On 10/15/2019 at 11:49 PM, cyberspectre said:

    Could you elaborate? Is that some setting in UnRaid? My memory is rated at 3000 but the default profile in the BIOS is 2133, so I leave it at that. 

     

     

    You need to enable the XMP 2.0 profile in the bios to use 3000 mhz. 3000mhz isn't a "standard" speed, so it's configured via Extended Memory Profiles. Technically you paid for a 3000mhz stick, so it should be stable at 3000mhz, but if not, you can always just use the sub-stock speed of 2133 which is fine. I doubt you'll notice any performance difference in unRAID.

  18. On 10/15/2019 at 3:21 AM, cyberspectre said:

    I'm wondering if it's an issue with the disk at all, or if it's an(other) issue with BTRFS. Based on some threads I'm reading, people tend to choose XFS for SSDs after suffering repeated failures similar to this one. Once I was finished with all the recovery options that worked, I was able to reformat the disk as XFS with no errors. Not going to put anything on it without testing it extensively, though.

     

    I see you quoted my thread ... I had a similar issue last year, but it was due to corruption on a StarTech PCI 2.5" HDD/SSD hotswap slot I was using. I removed the slot, connected the drive directly to my motherboard, and no more corruption. I guess the StarTech adapter had poor QC ... I had two of them and both exhibited this issue after extended use.