NeonMinne

Members
  • Posts

    7
  • Joined

  • Last visited

NeonMinne's Achievements

Noob

Noob (1/14)

0

Reputation

1

Community Answers

  1. Oh my god I figured it out. Long story short, I didn't need any new hardware (anyone want some lightly used RAM/Mobo/PSU 😅?). The issue came down to an apparent bug between AMD Ryzen, and LSI HBA cards (Gen2 version). Apparently the CPU and HBA would lose contact with each other and cause a hard reset to happen. I had to turn off Autonegotiation and manually set the lanes in my mobo's PCI-E settings and voila, it worked. I've been hammering it with read/writes to test with no crashes so this seems to be the fix. Thanks to TheArtofServer for tipping me off: https://www.youtube.com/watch?v=b0fAKG3qa6Q
  2. Sorta using this to document troubleshooting in case anyone else hits this issue. After more reboots and no errors at the end of syslog, I double checked all the AMD cstate stuff was off as documented in this thread: Unfortunately, that doesn't help. It seemed stable at first, but then crashes and reboots. I started checking towards the beginning of the logs (in case anything relevant was given), and was given as an error listed. Googling this basically returns "everything under the sun could be the issue but check RAM". At this point I'm running an extended MemTest to see if I can't find the little bug. If not, I honestly don't know next steps aside from trying to RMA the board.
  3. Sorry, that's what I meant by above. Memtest returned no errors (granted, only 1 run). Should I run more?
  4. Little update: Replaced PSU to old, known working one Some settings (mostly around docker) are reverting/changing on reboots sometimes? It "forgot" that I set to IPVLAN It "forgot" i set it to use a folder instead of vdisk Not sure what's going on still, Memcheck also returned good values and temps are normal/CPU cooler is seated properly
  5. It automatically reboots, I'm not even sure if its fully crashing, as its seems to reboot super fast but it takes the whole system down and then resets the uptime timer.
  6. Hey folks! Got a server crashing every few minutes now (not sure why), and immediatly rebooting. I upgraded the CPU/RAM/MOBO/PSU recently, and it was humming along fine until today. I turned on "Mirror Syslog to Flash", and checked the file after the most recent crash/reboot cycle and the last message is never an error, it just seems to reboot randomly and not give an error. I think this is more PSU related than anything (seemed to have issues before but never this specific issue), but can anyone confirm/point me in another direction? Its really starting to worry me something is wrong. fenrir-diagnostics-20240105-1239.zip
  7. Hey ya'll! Trying to get started with Unraid and purchased 2 new Seagate Ironwolves (8 TB each) to start building an array in addition to some existing drives. Since these existing drives have data I want to move over, I haven't tested if the below works on them yet: I can add one of these new drives to an Array and start it, however it constantly says "Unmountable: unsupported partition layout". I can add the other as a parity drive no problem I cannot seem to fix them when I click the "Format" button in the Main > Array section, even after checking the checkbox It seems to start, then exits saying there's an invalid partition I did do this without a parity drive so I could move my data then do a parity sync I booted into a live GParted environment and was able to successfully partition and format these drives, so I know they're not dead/toast Parity Syncing seems to be starting/chugging along but still won't let me format these disks Running FDisk/Parted seems to create the correct partitions/formats, but Unraid still won't do anything with them At this point I've been at this for a few hours and am tearing my hair out what something I may be missing. Anyone run into this before/any tips? Apologies in advance if I'm missing something incredibly obvious fenrir-diagnostics-20221107-1857.zip