caelar900

So I have been having an issue for a while now with drives in my system either dropping off entirely or throwing up "Power-on or device reset occurred" warnings/errors in the log. This usually occurs during a parity check, though I would guess that the issue is not necessarily occurring then, but rather only showing itself then since this is the only time a lot of the drives in my system get any real use. It isn't a specific drive, or set of drives, that it is happening with. It can randomly happen with any of them, but also only really seems to happen with one at a time from what I can tell. I initially thought it was a cable issue based on other related threads, so when it would occur I'd disconnect the affected drive, reseat the cables and all was usually fine. But it kept happening and more and more frequently so I took ended up taking all the drives out, redid all the wiring, and retaped all the 3.3v pins as I used shucked drives, and while that seemed to fix things for a while, it seems like it has started again. If someone wouldn't mind taking a look at my Diag it would be much appreciated because at this point I'm at a bit of a loss. Currently its drive sde that seems to be having the Power-on or device reset occurred issue, and my parity drive that dropped off completely. This occurred during a read test after updating to Unraid 7 (though I don't think that has anything to do with it). Thanks! Tower Diagnostics Jan 26 2025.zip

Hey there, So I had a power outage and my boot drive failed (really need to get a UPS). To boot I made the mistake of solely backing up my USB to the Array (also need to rectify that fact when I get everything back up and running)... Im wondering if there is any way that I can get access to the array by making a clean boot drive and pull that backup to make a new boot drive from? Took a look at the troubleshooting docs and think I get the general gist of whats necessary here but wanted to throw this question out none the less just to be sure. Thanks

Ive been plugging away at it all day and I think I might have solved the issue without needing to move everything off. Does this look right? Would it be safe to remove the drive now? Tower Diagnostics Mar 24 (1).zip

Damn alright, that is pretty much what I feared. Appreciate you taking a look. Whats the best way to get the data out of the pool and to the array in this case? Can I just use the mover for that or should i be doing it manually? Also given the logs are making it look like my docker image is corrupted should I deal with that first before moving it anywhere or will that not really matter.

Ive got a pool of cache drives and one is failing I'd like to remove the failing drive and just use the single drive going forward if possible but am a little unsure how to go about this I'm getting an error that says too many BTRFS profiles on my pool. Output from btrfs fi df /mnt/cache is: Data, single: total=742.01GiB, used=71.04GiB Data, RAID1: total=886.00GiB, used=103.21GiB System, RAID1: total=32.00MiB, used=240.00KiB Metadata, RAID1: total=5.00GiB, used=1.25GiB GlobalReserve, single: total=512.00MiB, used=0.00B WARNING: Multiple block group profiles detected, see 'man btrfs(5)' WARNING: Data: single, raid1 When I balance Im gettin these errors And when I scrub Im getting these. Based on this my docker image is part of the problem so I probably need to recreate that. But it also seems there is something happening with the drive itself (possible the metadata?). If that is the case Im not entirely sure how to proceed. Any help would be appreciated Thanks so much. Tower Diagnostics Mar 22.zip Tower Diagnostics Mar 23 (3).zip

Okay I was being silly and it did end up being the parity drives cables and not my screwy drive!! Rebuilding at 200MB/s now.

Also is anyone able to confirm for me is this the drive ending in 49LK that causing things to go slow or is this my parity drive ending in V2BA?

So Ive got a bit of a sticky situation with my server at the moment. My parity drive failed and I need to rebuild parity but I also have a drive that I messed up when trying to remove my parity drive. Managed to break the data connection port on it. Was able to get the port and cable kind connected anyway but now its rebuilding VERY slowly. My thought is that I have an extra 14TB drive (broken drive is also 14TB) that I could swap the PCB's on but I'm not sure if that is going to screw with unraid seeing it as the same drive (I'm guessing that it might) which since I don't have parity at the moment would be a death sentence. Maybe could just replace the data port but I think that might be beyond my area of expertise. Any help or insight would be greatly appreciated. Thanks! tower-diagnostics-20240314-1941 (2).zip

Okay! Ill go ahead and check all the cables on that drive. Thanks so much!

Ive got two new hard drives ready to put in to help rectify the problem if necessary but I just don't know how to go about that from this point. Feels very precarious.

Okay edited with diag

During a recent parity check my parity drive became disabled. I restarted and unmounted and remounted to attempt to rebuild but now it is rebuilding VERY slowly. I assume it is an issue with one of the drives. But without parity I'm very concerned about what to do right now. Any help would be greatly appreciated. Thanks. I have full system diag and log but not sure if its "safe" to just upload that here, or if I should just upload a portion or whatever.... tower-diagnostics-20240314-1941.zip

So managed to repair the SATA port and fix the power issues with the original disk. Disk rebuild running now so should be good. Will check back in if it does not complete successfully for whatever reason. Appreciate the help!

So things just went bad from worse in replacing the cables I managed to break the sata connector on another drive... If I only have on parity drive am I going to be SOL. Replacing the sata port on the drive shouldnt be an issue but is that going to make things show as out of sync and prevent me from being able to recover the data and restart the server?

Will do, can I safely cancel the current parity sync, spin down the array and power down? I assume so. And then when I boot back up will I need to do any of the removing the disk from the array starting, and then putting it back and starting. Or will the parity sync just start back up when the array is started if the disk is now being recognized properly?