Muath

Members
  • Posts

    33
  • Joined

Posts posted by Muath

  1. I ran the test for more than a 24h and no errors. but still, I'm kind of facing the same issue.
    now I'm on 6.7v which at least I could use it before it hangs but then after less than a 24h it hangs but now I can navigate UNRAID page but I can't run firefox also when I command (reboot) it doesn't respond and reboot the system!.

    Maybe the USB flash what causing this issue? even though it's new and USB 2v which is the recommended.

     

     

    when I logged out it showing me UNRAID logo without option to log in (as the photo attached) 

     

    15732147533695674143192493355682.jpg

  2. 20 hours ago, John_M said:

    That's a symptom of UEFI booting. You need to legacy boot to be able to select MemTest86+ from the boot menu.

    thank you for the notifying, it worked.

     

    so now based on the photo did my RAMs passed the test? or should i leave it for more time? or is there some specific test i should try?

     

    15730514591055211147593278438042.jpg

  3. 1 hour ago, Squid said:

    Have you run a memtest yet?

    Sent from my NSA monitored device
     

    thank you for your quick reply,

    i have run it after you mentioned, but it won't work i have change the ram and used different slots but it doesn't work.

    once i select memtest86+ it goes black for 2sec then returns to motherboard manufacturer's logo!

  4. Hi all, 

     

    This week i was struggling with my system and could't find the issue! but also i'm new to unraid so maybe there's some kind of investe and digonaste error i don't know.

    Anyhow .. my issue is .. a weird one i think, 
    my system keep shutdown without the pc itself so only the OS and the USB flash light stop blinking, when i was on version 6.7 it happen but after a while of use (less than 24h), but now after upgrading the system to 6.8 rc5 since i was thinking the issue may fix itself but it got worse now after i start the array by 10 minutes first the system getting very slow then it shut itself down (only the OS but the PC still running). 

    Diagnostics file before the system got shut down attached.

     

     

    also i notice something in the logs: 

     

    System Log
    Nov  5 19:42:09 MoathCenterr kernel: ACPI: Early table checksum verification disabled
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:05:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:05:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:03:02.0: BAR 14: failed to assign [mem size 0x00600000]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:05:00.0: BAR 6: failed to assign [mem size 0x00080000 pref]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:05:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:05:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:05:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:05:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:02:00.0: BAR 14: failed to assign [mem size 0x00c00000]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:03:01.0: BAR 14: failed to assign [mem size 0x00100000]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:03:02.0: BAR 14: failed to assign [mem size 0x00600000]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:03:03.0: BAR 14: failed to assign [mem size 0x00100000]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:03:08.0: BAR 14: failed to assign [mem size 0x00200000]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:03:09.0: BAR 14: failed to assign [mem size 0x00100000]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:03:0a.0: BAR 14: failed to assign [mem size 0x00100000]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:04:00.0: BAR 0: failed to assign [mem size 0x00004000 64bit]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:05:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:05:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:05:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:05:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:06:00.0: BAR 14: failed to assign [mem size 0x00100000]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:07:05.0: BAR 14: failed to assign [mem size 0x00100000]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:0a:00.0: BAR 0: failed to assign [mem size 0x00020000]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:0a:00.0: BAR 3: failed to assign [mem size 0x00004000]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:0c:00.1: BAR 0: failed to assign [mem size 0x00100000 64bit]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:0c:00.3: BAR 0: failed to assign [mem size 0x00100000 64bit]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:0d:00.0: BAR 5: failed to assign [mem size 0x00000800]
    Nov  5 19:42:09 MoathCenterr kernel: pci 0000:0e:00.0: BAR 5: failed to assign [mem size 0x00000800]
    Nov  5 19:42:09 MoathCenterr kernel: floppy0: no floppy controllers found
    Nov  5 19:42:09 MoathCenterr kernel: random: 7 urandom warning(s) missed due to ratelimiting
    Nov  5 19:42:09 MoathCenterr kernel: ccp 0000:11:00.1: SEV: failed to get status. Error: 0x0
    Nov  5 19:42:10 MoathCenterr rpc.statd[2043]: Failed to read /var/lib/nfs/state: Success
    Nov  5 19:42:10 MoathCenterr ntpd[2073]: bind(19) AF_INET6 fe80::dcb6:50ff:fe5a:f97b%10#123 flags 0x11 failed: Cannot assign requested address
    Nov  5 19:42:10 MoathCenterr ntpd[2073]: failed to init interface for address fe80::dcb6:50ff:fe5a:f97b%10
    Nov  5 19:42:17 MoathCenterr ntpd[2073]: bind(22) AF_INET6 2001:16a2:953:5d00:7285:c2ff:fed3:fabb#123 flags 0x11 failed: Cannot assign requested address
    Nov  5 19:42:17 MoathCenterr ntpd[2073]: failed to init interface for address 2001:16a2:953:5d00:7285:c2ff:fed3:fabb
    Nov  5 19:42:33 MoathCenterr avahi-daemon[6713]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!

     

     

    now I will return to the previous version 6.7 at least I could watch one or two movies 🙄.

     

    Thank you for helping in advance. 

    moathcenterr-diagnostics-20191105-1444.zip

  5. Hi, 

     

    I have a small question, What triggers parity check?
    for me, I set it up to work every 2 months but it keeps working every time and then!
    first time when I had a power outage and it's good to trigger it 
    but also it's worked after I stopped the array two consecutive times since I was playing with some setting that needs the array to be stopped

    Is this what caused the parity to be checked?
    Are there other causes to trigger parity check?

     

    Thanks 🌹 
     

  6. 5 hours ago, dalben said:

    I bought an ASROCK for my UnRAID a while back.  Due to the senors chip not being supported I ended up using it as my desk top.  In my case it used a Nuvoton NCT6683D eSIO chip which only ASROCK seem to use and wasn't supported very well.  When I contacted ASROCK they were very firm and clear that they don't support Linux so they wouldn't help.

    Oh :(, thank you for the information. is there any configuration needed if i replaced my motherboard? or just buy one then swap it?

    thank you again 

  7. Hi, 

    does this plugin detect the new AMD CPU zen2 temp? if so then my current PC have the 3700x with ASRock X570 STEEL LEGEND and it could not detected.

    i think the issue is with perl 

    This is perl 5, version 30, subversion 0 (v5.30.0) built for x86_64-linux-thread-multi

     

    i tried to detect the drivers through the terminal but no luck :(.  

     

    * Since i'm new to UNRAID it's likely that I've done something stupid :ph34r: *