Jump to content

blurb2m

Members
  • Content Count

    83
  • Joined

  • Last visited

Community Reputation

3 Neutral

About blurb2m

  • Rank
    Advanced Member
  • Birthday January 27

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. blurb2m

    RAM Speed understanding dmidecode

    I'm sorry, but I don't follow? I'm stable at 1.35V and 3066 MHz. I think if I wanted to try and achieve 3200, I would need to learn more about overclocking RAM.
  2. blurb2m

    RAM Speed understanding dmidecode

    I have been slowly increasing the clock speed and got up to 3066 stable on the 4 sticks. If I try going up to 3200, it freezes up on me after about 10 seconds into unRAID boot. I'll stick with 3066 for the time being until I can learn more about clocking these monsters.
  3. blurb2m

    RAM Speed understanding dmidecode

    I might try messing with the timings tomorrow to see if I can get higher speeds. Its back at 4 sticks @ 2133 for the time being. I was going by this for B-Die for TR builds. https://benzhaomin.github.io/bdiefinder/ This is the thread that lead me there. https://www.reddit.com/r/Amd/comments/8clf15/bdie_finder/dxgd1d9/
  4. blurb2m

    RAM Speed understanding dmidecode

    Changed Load XMP setting to XMP 2.0 Profile 1 (3200) and voltage to 1.35. Voltage auto-set when I changed to XMP 2.0 Profile 1. Unraid froze about halfway through bootup. Stopped at: sev command 0x4 timed out, disabling PSP SEV: failed to get status. Error: 0x0 So, I think when I changed to AUTO it had not updated yet the other day to show 2133 and 1.20v. It has been stable for a day at those lower clock settings. Not sure of what else to change to get it to run 4 sticks at 3200. What my limited knowledge has gathered so far: 2 sticks @ 3200 and 1.35V = stable 4 sticks @ 3200 and 1.35V = unstable 4 sticks @ 2133 and 1.20V = stable.
  5. blurb2m

    RAM Speed understanding dmidecode

    No I'm running 4 sticks. Let me take some new pictures from BIOS. That second picture might have been prior to switching profiles now that I think about it.
  6. blurb2m

    RAM Speed understanding dmidecode

    Would being quad channel make it report 2133? Should I move 2nd set to different slots?
  7. BLUF: How to understand dmidecode to see if RAM is running at full clock speeds. (output of dmidecode --type 17 attached) Server has been running smoothly with 2x16GB sticks of GSkill Ripjaws (F4-3200C15D-32GVR) in dual channel mode with XMP Profile 1. ASRock X399 Taichi | TR4 2950X Windows VM was eating up a ton of RAM for Blue Iris NVR, so I decided to buy 2 more sticks. Popped them in the slots according to the x399 Taichi motherboard chart (D2,C2,B2,A2). BIOS is showing Quad Channel now and it was freezing like crazy on POST, so I went in and switched the Memory profile to "Auto" and it seems stable and showed DDR4-3200 for the speed. Does the information attached (txt) support what BIOS is reporting? Is there a better setting I should be using? Any help is greatly appreciated! tr4-ram-dmidecode.txt
  8. blurb2m

    Upgraded to 6.6 and drive failures

    I think I was on P20 20.00.07(?) It was 0.5 - 2.9% into a disk rebuild that it would kill the disk and disable it. Couple hours later the other 3 disks on that SAS port would get bazillions of read/write errors. They just stopped communicating through the card. Since moving to the 9207-8i, it has been flawless. Wroks out of the box with no flashing and uses PCIe 3.0 instead of 2.0 (not that it matters bandwidth-wise but seems more compatible with my x399 Taichi.
  9. blurb2m

    Upgraded to 6.6 and drive failures

    seems stable after changing the setting in BIOS.
  10. blurb2m

    Upgraded to 6.6 and drive failures

    I knowwww I should start a new thread... but @johnnie.black Thoughts on Fix Common Problems suggestion of: You have a Ryzen CPU, but Zenstates not installed
  11. blurb2m

    Upgraded to 6.6 and drive failures

    Mounted! You sir are a round candy with a hole in the middle.
  12. blurb2m

    Upgraded to 6.6 and drive failures

    Phase 1 - find and verify superblock... - block cache size set to 1512192 entries Phase 2 - using internal log - zero log... zero_log: head block 2356505 tail block 2356499 ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... sb_fdblocks 489295541, counted 490033385 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 1 - agno = 3 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (2:2356527) is ahead of log (1:2). Format log to cycle 5. XFS_REPAIR Summary Wed Sep 26 11:52:28 2018 Phase Start End Duration Phase 1: 09/26 11:48:25 09/26 11:48:25 Phase 2: 09/26 11:48:25 09/26 11:49:42 1 minute, 17 seconds Phase 3: 09/26 11:49:42 09/26 11:49:46 4 seconds Phase 4: 09/26 11:49:46 09/26 11:49:46 Phase 5: 09/26 11:49:46 09/26 11:49:46 Phase 6: 09/26 11:49:46 09/26 11:49:50 4 seconds Phase 7: 09/26 11:49:50 09/26 11:49:50 Total run time: 1 minute, 25 seconds done
  13. blurb2m

    Upgraded to 6.6 and drive failures

    @johnnie.black So, system has been stable. Just updated again to 6.6.0 and everything seems ok except for Disk4 status on "Main" shows 'Unmountable: No file system'. This is after the successful rebuild. Thoughts?
  14. blurb2m

    Upgraded to 6.6 and drive failures

    Happy to report 7.5 hours later that it completed with zero errors! Disk4 is fully operational and its the old 3TB disk. The speed picked up a bit and went over 100MB/s but averaged around 80 - 85MB/s. Not sure why History shows over 280MB/s... (I think that would have finished in 3 hours).
  15. blurb2m

    Upgraded to 6.6 and drive failures

    @johnnie.black got the new HBA card in and it is rebuilding. I did change the PCIe Mode to Auto instead of Gen2 (options are Auto, Gen1, Gen2) in mobo BIOS since this card is PCIe 3.0. Rebuilding at 2.9 - 41MB/sec though.... (avg about 30MB/sec)