blocker85

Just closing the loop on this. After the comment by JorgeB, I re-seated all sata power connectors and replaced the sata cables connected to the motherboard. I then reassigned the parity drive to parity2. Everything has been running fine for the last week. Thanks!

Thanks for responding! After the Drive entered an error state a couple of times, I assigned it to Parity1, not realizing that the parity drives are not interchangeable. Good to know. I'll assign it back to Parity2 I'll swap out the Sata cables to see if that changes anything. I can also grab a new sata power connector as well to see if that's the issue. I'm currently running the power connector off of a molex port, for two drives only. The remaining six drives are on a dedicated Sata power cable. Not sure if that creates a potential issue.

So, my unraid array has been running nearly issue free for years. But, it was time to expand storage, so I recently bought three 16TB drives, one to replace my aging parity drive, one to replace an old 2tb drive, and a third for when another drive goes bad. All my drives currently run off of a pcie SATA breakout board, but the new parity drive is utilizing one of the on-board SATA ports. When adding the new parity drive, I stopped the array, assigned the new parity drive as "Parity 2" and started the array. It took about two days, but it looks like it successfully completed the parity operation to make the 16tb drive a party drive. I then stopped the array, unassigned the old "Parity 1" drive, added the old parity drive as an array disk and started the array again. Within minutes, the new parity drive showed tens of millions of errors and the drive fell into an error state. Since then, any time I try to bring the array online, the drive errors out and I typically cannot even bring the array offline without doing a hard reset. I feel like I'm probably missing something obvious, but I'm still a relative noob on server maintenance, so I'm here to consult the experts. Help! Diagnostics attached. Appreciate any insight you can provide. Thanks all. tower-diagnostics-20231111-1025.zip

I have a dual E5-2650 server and when I check the available features of the cpu via the unraid terminal, it does not indicate that it supports SSE4.2. Am I basically out of luck for creating a Mojave VM?

I did both and still having some trouble booting but it did eventually boot. Now I'm getting call trace errors in Fix Common Problems...here are my diagnostics. Anything stick out? tower-diagnostics-20180426-0737.zip

Here's what I see (cursor is blinking at bottom): It looks like the UNRAID usb drive isn't booting, obviously, but I can't seem to get into the motherboard BIOS either. Thoughts? I haven't previously had any issues booting to the USB drive. My Hardware: Intel S2600CP 2x Intel E5-2650 32GB (8x 4GB) Micron RAM Software Setup: unRAID 6.4.1 plugins: Community Apps Dynamix SSD TRIM Fix Common Problems Nerd Tools rclone Unassigned Devices User Scripts Dockers Couchpotato lidarr sabnzbd sonarr deluge headphones krusader netdata ombi plexserver plexpy qbittorrent rutorrent VMs macOS High Sierra

So just to put a bookend on this thread, I had the Ebay reseller send me all new modules (different brand this time), and I'm now at 24 hours of uptime without a single error in the logs. I think I may be in good shape. Thanks for all the help.

@pwm: memory errors continued after pulling the module. Also, unless I'm mistaken, from the time stamp it appears that the error you quoted occurred DURING the 24 hour memtest run. The test ran from about 7pm on 3/9 through 7 or 8pm on 3/10. In any event, the ebay seller has agreed to swap out all 8 memory modules, so we'll see what happens. It would be awful if it turned out to be an issue with the ram terminals on the motherboard. Is that unlikely?

OK. This will be the second RMA with this Ebay reseller. I think I'll just ask him to just send me all new modules instead of playing the "find the bad RAM stick" game any longer :/.

OP from the linked thread here, I happened to stumble across this thread. I used the guide from Intel here, which worked like a charm. You need to load the software onto a thumb drive and run it from the internal EFI shell. You can then save the output as a .sel file back onto the thumb drive and open from Notepad++ in Windows or whatever. Hope that helps. EDIT: words.

Good call. Here it is. From a cursory review, it looks like I also need a new power supply. I'll take care of that today. I also see a mix of correctable and uncorrectable ECC memory errors. What should I do? SYSTEMEVENTLOG.sel

Well, this was genuinely surprising. I was finally able to shut down the server and run MemTest86+ for 24 hours. Not a single error (see screen shot attached). Next steps?

Good catch. I pulled one of the RAM modules out to see if I could stop the errors. Not sure why it's reporting 27 instead of 28. How long is a good long time?

I hope this is the appropriate forum for this. If not, feel free to move it or let me know where to repost. I'm an unRAID newb, but I've spent countless hours tinkering and watching Spaceinvader's tutorials, etc. Most issues I have been able to work out on my own, EXCEPT for this one. Here is my relevant server hardware setup: Intel S2600CP 2x Intel E5-2650 32GB (8x 4GB) Micron RAM Software Setup: unRAID 6.4.1 plugins: Community Apps Dynamix SSD TRIM Fix Common Problems Nerd Tools rclone Unassigned Devices User Scripts Dockers Couchpotato lidarr sabnzbd sonarr deluge headphones krusader netdata ombi plexserver plexpy qbittorrent rutorrent VMs macOS High Sierra On boot, the 2600CP shows no error LEDs and the unRAID syslog is clean. However, after about 30min - 3 hours (depends on the reboot), the 2600CP throws a blinking error amber led and one or two ram slots throw error amber LEDs. The unRAID syslog then starts reporting MCE errors. I have already RMA'd a couple of the RAM sticks on the slots, but the problem persists, and the error LEDs do not seem to follow particular ram modules. The modules and/or RAM slots reporting errors are not always consistent, which is confusing. Is this a 2600CP issue? Software? Would love some insight from the experts. Server diagnostics attached. Thanks in advance. lockerserver-diagnostics-20180302-1410.zip