Jump to content

baboolian

Members
 View Profile  See their activity

  • Posts

    15

  • Joined

  • Last visited

 Content Type 

Posts posted by baboolian

    System locked out twice in last couple of weeks

    in General Support

    Posted

    Hi, my system has been running smooth for a year until it complete froze up twice in the last two weeks. I have it hooked up to GUI mode as backup in case of networking issues, and GUI was locked out as well as ssh and http access.

     

    I've read other users having stability issues due to macvlan recently, I've been using this since the start and never had an issue until recently so i'm not sure if that's it.

     

    I've attached the two diagnostics logs, which i took immediately after hard rebooting.

     

    Any help would be greatly appreciated!

     

     

    unraid-diagnostics-20240127-1517.zip unraid-diagnostics-20240116-2140.zip

    /var/log/Xorg.0.log filling up with EDID logs

    in General Support

    Posted · Edited by baboolian

    Hi, my Log usage is constantly high, currently at 44% in the Memory panel of dashboard. I narrowed it down to `/var/log/Xorg.0.log` via `du -sm /var/log/*`

     

    The log is full of the following, repeated many many times over: 

    [3629980.717] (II) modeset(0): EDID vendor "SAM", prod id 29098
[3629980.717] (II) modeset(0): Using hsync ranges from config file
[3629980.717] (II) modeset(0): Using vrefresh ranges from config file
[3629980.717] (II) modeset(0): Printing DDC gathered Modelines:
[3629980.717] (II) modeset(0): Modeline "3840x1080"x0.0  266.50  3840 3888 3920 4000  1080 1083 1093 1111 +hsync -vsync (66.6 kHz eP)
[3629980.717] (II) modeset(0): Modeline "2560x1440"x0.0  241.50  2560 2608 2640 2720  1440 1443 1448 1481 +hsync -vsync (88.8 kHz e)
[3629980.717] (II) modeset(0): Modeline "2560x1440"x0.0  497.75  2560 2608 2640 2720  1440 1443 1448 1525 +hsync -vsync (183.0 kHz e)
[3629980.717] (II) modeset(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[3629980.717] (II) modeset(0): Modeline "1920x1080"x0.0  148.50  1920 2448 2492 2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
[3629980.717] (II) modeset(0): Modeline "1280x720"x0.0   74.25  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[3629980.717] (II) modeset(0): Modeline "1280x720"x0.0   74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
[3629980.717] (II) modeset(0): Modeline "720x576"x0.0   27.00  720 732 796 864  576 581 586 625 -hsync -vsync (31.2 kHz e)
[3629980.717] (II) modeset(0): Modeline "720x480"x0.0   27.00  720 736 798 858  480 489 495 525 -hsync -vsync (31.5 kHz e)
[3629980.717] (II) modeset(0): Modeline "1920x1080"x0.0  297.00  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (135.0 kHz e)
[3629980.717] (II) modeset(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[3629980.717] (II) modeset(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[3629980.717] (II) modeset(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[3629980.717] (II) modeset(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[3629980.717] (II) modeset(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[3629980.717] (II) modeset(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[3629980.717] (II) modeset(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[3629980.717] (II) modeset(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[3629980.717] (II) modeset(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[3629980.717] (II) modeset(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[3629980.717] (II) modeset(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[3629980.717] (II) modeset(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[3629980.717] (II) modeset(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[3629980.717] (II) modeset(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[3629980.717] (II) modeset(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[3629980.717] (II) modeset(0): Modeline "1280x800"x0.0   71.00  1280 1328 1360 1440  800 803 809 823 +hsync -vsync (49.3 kHz e)
[3629980.717] (II) modeset(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[3629980.717] (II) modeset(0): Modeline "1600x900"x60.0  119.00  1600 1696 1864 2128  900 901 904 932 -hsync +vsync (55.9 kHz e)
[3629980.717] (II) modeset(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[3629980.717] (II) modeset(0): Modeline "1440x900"x0.0   88.75  1440 1488 1520 1600  900 903 909 926 +hsync -vsync (55.5 kHz e)
[3629980.717] (WW) modeset(0): Output HDMI-2: Strange aspect ratio (1193/336), consider adding a quirk
[3629980.717] (WW) modeset(0): Output HDMI-2: Strange aspect ratio (1193/336), consider adding a quirk
[3629980.717] (WW) modeset(0): Output HDMI-2: Strange aspect ratio (1193/336), consider adding a quirk
[3629980.717] (--) modeset(0): HDMI max TMDS frequency 300000KHz

     

    I'm running in GUI mode for easy debugging on occasion, as well as a windows VM with both connected to two different inputs of an ultra wide 49" curved Samsung G9 neo. I have a macbook hooked up to the third monitor input. Everything works great screen wise, how might I get rid of this repetitive logging that is eating up all my log memory?

     

    Thanks!

    Writes to caches, array, and usb regularly fail checksums

    in General Support

    Posted

    Well that didn't last long. After about 10 minutes downloads began failing again. Ran another memtest and got dozens of failures within 30 seconds. Switched from XMP to stock, same result. 

     

    Trying the Corsair HX1000 PSU again. If this works, the brand new evga 1600w p2 is a couple weeks past the return window, so I'll prob take it out back and go office space on it. 

    Writes to caches, array, and usb regularly fail checksums

    in General Support

    Posted

    Looks like the PSU was the culprit!

     

    I took your advice and upped the voltage, set it to 1.25 and got a memtest pass! I thought that was strange as it ran at stock 1.2v for weeks no problem, so I did some experiments. I also got a second set of matching ram. For the record, prior to all this I was running stock, no XMP. 

     

    I initially only had the 8pin motherboard power connected.

     

    EVGA 1600w P2 PSU:

    2x32 stock: FAIL

    2x32 1.25v: PASS

    2x32 XMP: FAIL

     

    Corsair HX1000 PSU:

    2x32 stock: PASS

    2x32 XMP: FAIL

     

    Connected the secondary 4pin motherboard power.

     

    EVGA 1600w P2 PSU:

    2x32 stock: PASS

    2x32 XMP: PASS

     

    Corsair HX1000 PSU:

    2x32 stock: Didn't Test

    2x32 XMP: PASS

     

    Added in second set of ram, now 4x32gb:

     

    EVGA 1600w P2 PSU:

    4x32 stock: Didn't test

    4x32 XMP: FAIL 

     

    Corsair HX1000 PSU:

    4x32 stock: Didn't Test

    4x32 XMP: PASS

     

    I don't trust this EVGA PSU anymore, but I reeeally don't want to have to swap it out again (I managed to squeeze that monster 1600w psu into a Fractal Node 804 with 8 platters right above it and the max amount of case fans), so I gave it another shot because why not. The second time, it passed, with XMP on, after failing miserably the first time.

     

    I think I'll run it like this with XMP on for a week and see if it survives, and then hit it with another memtest to be sure. With 64gb it took ~8hrs and 128gb ~19hrs to run. I need a break.

     

    Thanks a ton for your help! Without your advice I likely would have lost a month unnecessarily RMA'ing my motherboard.

    Writes to caches, array, and usb regularly fail checksums

    in General Support

    Posted

    I upped the voltage from 1.2 -> 1.25 and got a full memtest pass /w both sticks! 

     

    For fun, I ran memtest with XMP on, and it failed immediately (with 1.35v).

     

    Does this indicate dying RAM or PSU? 1.2v worked fine for months, and i ran XMP for a few days to test it early on with no problem either. I did switch PSU's about a month ago, though the new one is way overkill 1600w EVGA P2 and was brand new. This was around the same time I installed the RMA'd motherboard. Initially everything worked fine at 1.2v no xmpp for a couple of weeks, until about two weeks ago. 

     

    I have another 2 sticks of identical RAM coming Friday I'll test, my hope is to run 4 sticks in the end. 

    Writes to caches, array, and usb regularly fail checksums

    in General Support

    Posted

    Retested with both sticks in their original slots, as well as the previously empty two slots. Both failed, the former right away, and the later a bit later in the test with fewer errors.

     

    I'm rerunning a single stick test, which is almost done with the first pass and no errors so far.

     

    Does this indicate a mobo/psu issue? If so, how can I determine which is the culprit?

     

    Is it safe for me to run Unraid with 1 stick of RAM (assuming it passes the full test) in this situation?

    Writes to caches, array, and usb regularly fail checksums

    in General Support

    Posted

    24 minutes ago, JonathanM said:

    No point in continuing the memtest, any errors are fatal. Check CMOS memory timings, make sure there are no XMP / overclock settings, if needed manually set all the timings. Rerun memtest, if errors continue, test single sticks. If single sticks all pass, then possibly motherboard / PSU issues.

     

    DO NOT ALLOW any data to be read or written to the drives until memtest is all clear.


    Thanks for the tips! XMP is disabled, how do I check the CMOS memory timings? 
     

    I’ll memtest one stick at a time now 

    Writes to caches, array, and usb regularly fail checksums

    in General Support

    Posted

    When updating to 6.11.5 i got a checksum error, I didn't write down the message but it suggested my USB disk was failing. After 5 retires or so, it worked. This was about a week ago I believe. 

     

    When pulling docker containers, some will fail with `docker compose pull failed to register layer: Error processing tar file(exit status 1): archive/tar: invalid tar header`, which a retry then fixes

     

    Starting today, Sabnzbd started failing ~95% of downloads. Tested on both an nvme cache and an ssd cache. Also installed and tested with NZBGet, same result. Installed and tested with NZBVortex on my Mac with the same nzb, and it downloaded successfully. I see lot's of `Error importing NzbFile: filename=...` logs in sab. 

     

    Attached my diagnostics, any helps or ideas of tests to run would be greatly appreciated!

    unraid-diagnostics-20221122-2347.zip

    Macinabox Monterey Installation error

    in VM Engine (KVM)

    Posted

    I'm experiencing this same problem.

     

    Previously it worked, but I was unable to get it to recognize my graphics card (GTX 970). I deleted everything (docker, user scripts., domains, iso, system/custom_ovmf, and the VM) started over from scratch. Now I get this error every single time after many attempts. 

×
×
  • Create New...