shinta148

Members
  • Posts

    16
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

shinta148's Achievements

Newbie

Newbie (1/14)

4

Reputation

  1. This is resolved. It was an issue with RAM. The new memory is in and the server is running smooth and happy again.
  2. As the title says, I'm replacing an older Marvell 9215 SATA card and I'm considering using an LSI SAS9211-8I. Aside the lack of TRIM support on certain SSDs are there any other negatives or downsides I should be on the look out for? Thanks for reading
  3. @JorgeB Hey man, Thanks for taking the time to look. I've removed the server from the rack and tossed it on my desk and have it hooked up now with all but 2 of the sticks of RAM removed. So far going on 18 hours with 0 error. I'm going to let it sit until Wednesday when some new RAM I ordered comes in, but so far it looks like a hardware issue. If I don't see any crashes until I'm ready to swap the RAM out I'll mark the topic resolved.
  4. So the crashes are back. I've been mirroring the syslog to my flash drive and this is what it's collected (see attached). I've run memtest86 on it multiple times hoping it was a simple memory issue, but it isn't reporting anything. I've been researching everything in the log I don't recognize but I'm coming up blank Edit: Added a diag too syslog asc-unraid01-diagnostics-20210430-1408.zip
  5. Hey @JorgeB, Thanks for your help again. I went ahead and ran XFS_Repair on MD6 and it seems to have resolved that issue. I did find that in that latest set of panics I saw and in some more today that it kept referencing the qbittorrent-nox process from the qbittorrent docker. I stopped that docker and I'm going to let the server run for a few days and see if the crashes stop.
  6. So it hasn't crashed just yet but I can see call traces in the syslog now. Here is the syslog with those call traces (see attached) syslog
  7. Thanks for such a quick response. I'll get that enabled and post that log after the next crash.
  8. Good Morning... I've been getting crashes every 3-4 days for awhile now. I've been trying to figure out what it is on my own but I'm having a little less luck then I thought I would. I've attached a diagnostic. Any help would be awesome! Thank you so much! asc-unraid01-diagnostics-20210419-0853.zip
  9. @limetech That did the trick. Thanks a lot
  10. @Squiggley Would you mind sharing what the modified syslinux.cfg looked like? I've never done this in practice and want to see if this resolves my issue with the same controller.
  11. I'm also having the upgrade issue I think is related to the Marvel controller. Disabling Intel VT-D did not work. This is what I have : 00:11.4 SATA controller: Intel Corporation C610/X99 series chipset sSATA Controller [AHCI mode] (rev 05) 00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset 6-Port SATA Controller [AHCI mode] (rev 05) 81:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 11) Also attached diagnostics. I can't seem to make this work. I can't really afford to replace the controller either yet =/ Anyone have any other ideas? asc-unraid01-diagnostics-20190514-2332.zip
  12. @limetechIt's the onboard controller from this motherboard and also from this PCIe controller: https://www.newegg.com/Product/Product.aspx?Item=N82E16815158365 https://www.newegg.com/Product/Product.aspx?Item=N82E16813182933 Intel Corporation C610/X99 series and Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller Does that help? I'm willing to share w/e you need to see
  13. I updated a few minutes ago, and had to revert. 3 of my Western Digital Drives started reporting errors. I admittedly panicked and reverted the update before collecting anything. Reverting did resolve the issue. The alert I got read this: Event: Unraid Disk 9 error Subject: Alert [servername] - Disk 9 in error state (disk missing) Description: No device identification () Importance: alert These are all WD 8TB Drives model: WDC_WD80EFAX-68LHPN0 and WDC_WD80EMAZ-00WJTA0