Edge9028

Thanks guys, followed @Edge9028 advice, and everything went according to plan!

Thanks, I have unassigned the old parity, in the process of upgrading parity drive now, as recommended. I will wait until this finished (looks to be roughly a day) and then I will report back. Hopefully there's no issues bringing the the previous parity drive into the array for storage. Thanks for your help.

Hello, Unraid Community, I'm facing a challenging issue while attempting to reconfigure my Unraid disk setup and would greatly appreciate any insights or suggestions you might have. My current setup includes two 16TB drives: one designated as a parity drive and the other used for storage. My goal is to repurpose the current 16TB parity drive as an additional storage drive and introduce a new 18TB drive as the new parity drive. Here's a step-by-step breakdown of what I've tried: With the Unraid array offline, I attempted to remove the existing 16TB parity drive from its role and subsequently add it back as a standard storage drive. Following this, I tried to add the new 18TB drive as the new parity drive. However, at each attempt, regardless of the array being offline and performing these actions in distinct steps with restarts in between (i.e., removing the parity drive, restarting, and then trying to add the new 18TB drive as parity), I encounter the following error message: "You may not add new disk(s) and also remove existing disk(s)." I made sure to attempt these changes with the array stopped to avoid any data integrity issues. Despite this precaution and attempting the removal and addition of drives as separate actions, the error persists, preventing me from completing the reconfiguration. Could someone please provide guidance on where I might be going wrong, or if there's a specific procedure I should follow to achieve this configuration without triggering the error? Any advice on steps I might have missed or alternative approaches to successfully swap the parity drive and expand storage would be greatly appreciated. Thank you in advance for your time and assistance! Thanks

UPDDATE: After much pain and troubleshooting, this seems to have been a case of dying CPU. Once the CPU was replaced, stability has been restored to the server. This is literally the first time I have ever experienced a dying CPU - I'm not even sure what causes this to happen 😑. Thanks very much for you support. I will mark this matter as resoved, now.

Hello, Not long after I posted this message, the server rebooted again. I am determined to get to the bottom of this, so I will flash a clean install of 6.12.4 to a usb and try it. Downloads are going exceptionally slow from the unraid website right now, but I will persist. And, yes, @JackieWu this is a Ryzen processor (Ryzen 5 5600G). Thanks,

Update: Ok, so this is interesting: I have never had to mess around with the syslinux.cfg file, but after adding rcu_nocbs=0-11 into the syslinux.cfg file, I've not seen any restarts for more than double the maximum time I usually get. I've had two months of stability since using Unraid at version 6.12.4. I did upgrade to 6.12.5 and shortly after, this is when the issue began. I missed this part out in my initial message: I actually went from 6.12.5 > 6.12.6 in a bid to address the issue at hand. I will monitor closely, but if stability resumes after having made this change, it might suggest that a previous patch/fix has been missed during a merge - as this is the first time I've needed to do this. It's early days, and it could fail again, soon Regardless, I will update the thread when a more significant amount of time has passed. Thanks

Update: I have now replaced the motherboard. The issue persists with the same pattern of consistent restarts at approximately the two hour mark. Before going ahead and replacing the cpu, I had a thought to try a different OS: I have been running Ubuntu from a live usb for many hours now, without a single restart. This would lead me to belive that there is a chance that this is not hardware related and may be related to a recent update to the the Unraid OS considering i still get restarts with a fresh UNRAID USB. Interested to hear your thoughts.

Ok, So, issues persist with fresh, new USB with no hard drives connected. So, I think we can safely say that this is a hardware issue that relates to either the cpu or the motherboard. It's just unfortuante that without buying replacements, it's going to be almost impossible to conclude which one is the culrpit.

I backed up the exisiting drive, and move it to another flash drive. The restarts are still an issue. As a last ditch attempt to diagnose this, I would like to boot the server with a fresh usb drive, just to rule out any configuration/corruption being loaded into the ram. The plan is to start it up, and see if it reboots happen. If it reboots - which I am almost certain it will - I will drop the cash on the new parts, and then update this thread. If I boot the sever with a fresh drive, I understand that this will have no impact on the data stored on the array, is this correct? Thanks for your help

Thanks, I have already replaced both ram sticks that are in the system - sorry, that was not clear in the information I provided. Second power supply is good - less than a month old and has been reliable in another system. I think I am just going to go ahead and buy a new mobo + cpu - spent a lot of time on this, and would have likely been more cost efficient to replace them in the end. Before I do, can you advise on whether it's worth restoring the flashdrive/trying a new one? My feeling is that it's not the issue (lack of any mention of it in the logs that are available) given the problem - just want to be reasonably sure i have ruled out everything before dropping the cash on new motherboard and cpu. Thanks for your help,

Hello everyone, I've been encountering a perplexing issue with my Ryzen 5600 build, which until recently, has been performing flawlessly. Over the past few weeks, I've been plagued with random restarts, and despite my best efforts, I can't seem to pin down the cause. Here's what I've tried so far: · Replacing RAM: I ran memtest, but it returned no errors. · Replacing the PSU: Thought it might be a power issue, but the problem persists. · Reseating the CPU and reapplying thermal compound: No change in the restart behavior. · Disabling Docker and VMs: I thought these might be contributing factors, but disabling them had no effect. · BIOS Tweaks: Following Ryzen-specific forum guides, I disabled C-states in the BIOS, but this didn't resolve the issue, XMP is also disabled and the ram is running and its default speed. · All drive passing SMART checks The frustrating part is that the system crashes have become more frequent. Sometimes, it restarts just minutes after booting, leading to a visible "unclean shutdown" message next to the button in the GUI to start the array. I've combed through the logs, adjusted numerous settings, but nothing seems to point to a clear culprit. When the server reboots, nothing is written to the logs, which would make me inclined to believe this is a hardware issue, but I am not convinced. At this point, the only things I haven't tried are replacing the SATA cables and the flash drive, though these seem like long shots. For additional context, I upgraded from Version 6.12.4 to 6.12.6, hoping for a fix, but to no avail. Most recently, I have ran in in safe mode with GUI enabled, and reboots happen shortly after the array is started. These issues do suggest to me some kind of hardware issue, but given the hardware changes I have made, it’s difficult to conclude. Perhaps this is also worth mentioning: this started to happen after I ran CA Appdata Backup for the first time - I am not suggesting this is the cause (given that this is happening in safe mode now, too), likely just coincidence. Has anyone else experienced similar issues with their Ryzen-based machines? Any advice or suggestions would be greatly appreciated!