gjkthx

I might have corrupted a file while it was turning off and on during the trouble shooting. I should have that fixed now. It also turns out that both sas card and pci slot are still good, but my case seems to pull the card out at an angle when I screwed it down. I have no idea what happened to cause this, but I now have it fixed. You have been a massive help and I can’t thank you enough. THANK YOU.

I made a new config and started the parity reconstruction again this time with the card in the top pci slot. It so far seems to be alright and hasn’t crashed yet. So maybe that pci slot is gone for me. On a side note, I have noticed thought that I will hit 100% usage on one of my cores for 20 seconds its always followed by Aug 24 14:00:51 Cube kernel: usb 1-6: reset high-speed USB device number 3 using xhci_hcd Aug 24 14:00:52 Cube kernel: sd 0:0:0:0: [sda] 62656641 512-byte logical blocks: (32.1 GB/29.9 GiB) Aug 24 14:02:32 Cube kernel: usb 1-6: reset high-speed USB device number 3 using xhci_hcd Aug 24 14:02:33 Cube kernel: sd 0:0:0:0: [sda] 62656641 512-byte logical blocks: (32.1 GB/29.9 GiB) Aug 24 14:06:06 Cube kernel: usb 1-6: reset high-speed USB device number 3 using xhci_hcd Aug 24 14:06:06 Cube kernel: sd 0:0:0:0: [sda] 62656641 512-byte logical blocks: (32.1 GB/29.9 GiB) Any idea of what would be causing this?

I pulled the gpu and moved it into that slot since it was the only other one that could hold it. Once it was on it seemed to have set 2 of the other disks to disabled. The cable that those are on has 4 drives and the other 2 show up. I replaced the cable with a spare I had to rule it out, but now I can’t enable those disks. When I try to run a check on them I get Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error While the SMART reports on them still seem to be fine. I feel as though I have made it worse. I did move it back down to another slot just so i could get into the bios if needed. cube-smart-20230824-1214.zip cube-smart-20230824-1211.zip

It looks like its running for a little bit but then will start to hit many of my cpu cores to 100%. I noticed in my log that it seems the mpt2sas_cm0: fault_state(0x2622)! keeps happening resets and then will fault again. Did i miss something in the bios? Could it be that the card is failing and i should just replace it? cube-syslog-20230824-1659.zip

I popped the card out and it seemed the thermal paste on it turned to a dry cement. Seems like it could be overheating. I gave the card a good clean and reapplied new paste. I reseated it a few times to make sure the pins were making better contact as well. I’ll give it a shot and see if that was the culprit.

So for a little bit of context I recently flashed a new bios on my motherboard to get it ready for an upgrade I was planning on doing, new cpu and ram. I thought everything was working but after about 6 hours my cpu hard locked up and became unresponsive while transferring some files. I was unable to get any logs of what happened, but after looking at some other forum posts I thought it might be not having reset some of the settings on the motherboard after the bios flash. I have now hopefully set the bios up properly with “power supply idle control” set to “typical current idle” and disabling the C-states globally. I went to run a parity check after it was stable for about a day only to have it completely crash at around 40ish%. I also unfortunately didn’t get the logs for that either. Upon reboot I saw that both my parity drives have been disabled and figured I would just rebuild them. However…. Now when I try to rebuild the drives I am getting “Alert [CUBE] - parity2 in error state (disk dsbl)” and “Alert [CUBE] - parity in error state (disk dsbl)” along with a warning that 6 of my disks have read errors. Any ideas of how to get this fixed and my server back to running normal again? Hopefully saving as much of the data as possible. I will try to be as responsive as I can while at work. I uploaded 2 diagnostics files. one is before the second failed attempt, the other after with the errors. For reference my system is a AMD Ryzen 5 3600 6-Core @ 3600 MHz ASRock B550M Steel Legend American Megatrends International, LLC., Version P2.80 BIOS dated: Fri 05 May 2023 12:00:00 AM MDT with 32gig of ram I am running version 6.11.1 cube-diagnostics-20230823-2351.zip cube-diagnostics-20230823-2318.zip

So I'm 14% of the way done with the check and they are now showing back up as healthy. I will still look at getting another drive for the parity since I imagine this wont be the last time I have a problem like this. thank you both so much for your help!

ok ill run a check now and see what I get back. I'll also look at replacing the parity drive if there are no problems. If they persist ill replace them both.

So I'm new to Unraid and just started to get a SMART error on 2 of my drives, one is a parity drive the other is a data drive. I have had issues with both the drives before when I first set up my system but after pulling them, and running a disk check on both of them nothing came up. after I reinstalled them and reinstalled Unraid I had no problems with them until today, a little over a year from when that first happened. I'm wondering what steps I should take next. I'm not sure if from the SMART reports if I should try to rebuild the drives onto themselves or just go strait to replacing them. If I rebuild, should I do the parity drive or data drive first? Would that do anything to effect the smart report? If I replace them, should I rebuild them one at a time? Should I start with the parity or data drive? Thanks for any help or advise you can offer. parity-cube-smart-20220127-1053.zip data-cube-smart-20220127-1033.zip

thank you both.

I'm looking at doing an unraid build really soon and was wondering if I should get a NVIDIA Quadro P2000 or just build a new system for unraid? I currently have an intel 6700k with 32gig of ram that I would be using with the P2000, but am unsure if this would be enough power for my use cases or if this would work. The new build would just be built around an AMD 3600 or 3700. I ideally would like to have this be primarily a plex server for at least 4 people to stream simultaneously at once maybe at most 2 more and 1 or 2 VMs. Thanks