pulseOXE

That's exactly what I was trying to do that caused this mess in the first place and for some reason it is trying to do a rebuild. Do you have the link to those instructions handy? I want to make sure I'm following the right steps on re-do since I must have screwed something up.

Got it. I just swapped some cables to try it after reading another one of your posts JorgeB, and no errors so far, so fingers crossed. Assuming everything works - I'm getting this error on multiple disks: "Tower root: xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: No space left on device" I assume the only way to fix this is to format the offending drives. Assuming that's true, I want to systematically format all of my drives one by one without losing data. What is the best way to do this? Unbalance to shift data, then what? I want to make sure I'm formatting these disks the right way so I don't have to do a parity rebuild every time.

tower-diagnostics-20220816-0959.zipDiagnostics attached,

I'm in a nasty situation with Unraid. I've been plagued by no free space messages that I think is from a disk formatting bug. In an effort to try to fix these, I decided my best option was to use UnBalance to move the data from one of the disks that needed formatted, then change the format twice to wipe the disk. I thought that this wouldn't trigger a Parity rebuild of the disk since it had no data when I wiped it. This does not seem to be the case, and it is trying to rebuild parity on the disk.. (this was disk8) This has led me to another HUGE problem. During parity rebuild of the drive (which again, I don't think needs to or should even happen) my Disk5 is just erroring out like crazy. This disk has only been in use for a few months and has never been an issue so seeing it throw thousands of errors is throwing me for a loop. Also, I try to look at the system log, and I get this: "Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 134062112 bytes) in /usr/local/emhttp/plugins/dynamix/include/Syslog.php on line 18" Is there some way to say that Drive8 should be empty, and then like wipe Disk5 and do a Parity rebuild of 5? I assume that's not possible with a single parity drive, but I don't know what other options I have if any. I've taken the array totally offline for now, and am a bit lost as to next steps and trying to figure out where to go from here. Sorry if the post is confusing, it's hard to articulate how bad I screwed up

Well, I hit my first ever major Unraid issue today. I was running 6.10.3 RC3? Whatever the last one was before 6.10.3 stable. I've been running now for several months, and always on the next channel with no issues. Today, I updated to 6.10.3 final, got the message that the plugins were all up to date, and clicked reboot. The server never came back online. After hooking up KVM, I saw the CPU is unsupported message during Unraid boot. I tried booting in safe mode, and received the same error. I'm running a Ryzen Threadripper 1950X on a Gigabyte X399 Arous Gaming 7 motherboard. It's worked flawlessly with Unraid up until this point. I did a forum search and tried disabling C-States to see if it would make a difference and it did not. The hardware was never physically touched before or after the update, so I have no idea why I'm suddenly getting a CPU unsupported error. I'm new to troubleshooting, but I really want my server online, so I'm going to try a fresh USB stick, and see if that will let me at least boot? Any other suggestions or any clue in the world why this happened?