Ellis34771

I had three of these go bad on me in under 7 months (all as my parity drive). I am done with them. Just ordered a new 12TB Toshiba N300 Pro to replace it.

I may have figured this out. There is a toggle setting. :-( Thanks everyone. :-)

Reads and Writes keep resetting to 0.0B/s. When the disks are active, the numbers increase. When the disk activity stops, they reset to 0.0B/s. Is there a setting that I'm missing? I am attaching the diagnostics. elsa-diagnostics-20251118-0120.zip

I managed to fix this. It turns out that the SATA port was failing (slowly). I finally just threw an HBA card in there and moved the drives to that. MUCH better.

Guys, My third parity drive is again showing errors. (Replaced the first two, and now on # 3). During last night's parity check it found 312,000+ errors. (And ran crazy slow, like it estimated it would need weeks to finish). So I stopped the run. I did a SMART TEST on the drive. It came up with ZERO errors. As far as I can tell, I see no errors on the drive. What else could be causing this? For the most part, the system appears to be running fine. I'm just starting to think this isn't the drive at this point. Is that possible? Thank you.

Since I put something over the power switch, I haven't had a problem. I'm guessing the cat found a new hobby. I never even considered that until you said "cat" in your reply earlier. I was just "that a$$ hat ..." Thank you. Most appreciated.

Thank you so much for the time to review this. It's been driving me insane. I was also concerned about a thermal failure, but I can't imagine how that would happen after running solid for so long.

SO this is absolutely a power button shutdown? Not a crash? If so, I'm going to have to cat proof that server. (The power button is on top).

No. I wasn't even home when that happened.

For over a decade this server ran solid. Now at least once a month, sometimes more frequently, my server just shuts off. I went into the diagnostic logs, and I saw a few segmentation faults. Ideally I'd like to find out what's wrong and stabilize this thing. I've attached my diagnostic dump. Thanks for any insight that anyone can provide. elsa-diagnostics-20250115-2234.zip

Disregard. Fixed it with "Docker Safe New Perms"

What was the problem? I'm having the same issue.

Wouldn't that inadvertently pick up files meant for the mover as well?

MDD, but the model number is a Seagate, so yes. Thank you.

The main dashboard shows 0 errors on this drive. Both rows say "NEVER" failed, but those raw values are something I've never seen on any of my other drives (that all say 0) Is this bad? This is a new 12TB I just put in. (Although I suspect it is refurbished).

I want to replace an 8TB parity disk with a 10TB disk. (That's straightforward enough, remove / replace, let it rebuild) But: I want to re-use the 8TB old parity disk to replace a 4TB drive. When I plug it in, will un-raid re-recognize it as the old parity disk? Will it (hopefully) prompt me to re-format it and re-use it? Or ... is there another procedure I'm missing here. Thanks in advance.

I buy used drives all the time. (Someones with many hours on them). The amount I save is insane over a new drive. (Enough to justify if one fails, I'd have to replace it.). Thus far I've only had one drive failure, and that was ironically one of the rare brand new drives I purchased.

Agreed, and a poor choice of words on my part. What I mean is that the parity makes it a lot easier to replace if the single drive goes down. (Rebuild). I have other backup solutions in place for critical data. (Including an older QNAP server that mirrors many critical files thru RSYNC).

I think I may have solved this. I had the spin down time at 2 hours. My Time Machine backup on my work MBP was hourly. I've lowered the spin down time to 15 minutes. It seems OK for the moment. (I also cleaned up the AppData mess). Also: Turned turbo-writes off for the moment. I may turn that back on, but I'm doing this one step at a time. Currently my doctor is on disk1, and my thinking at the time was then it is backed up on the parity disk. Wondering if I should move that to the cache disk and Implement a separate backup for that? (Any thoughts?) Thank you all !!

Yeah, that's been bugging me for a while. I'm not sure how they got that way, and mover doesn't touch them. That's on my list of things to look at. It appears that *most* of the appdata stuff is old and long since deprecated, but I want to take a methodical approach to deleting it so I don't accidentally shoot myself in the foot. Good catch though, I appreciate it. I'm going to resolve this. It's become a quest at this point.

The docker image is located at /mnt/disk1/docker.img I can probably move it to the cache drive. But that's still just a single disk. Turbo writes are in fact enabled.

Oh, even more interesting. If I stop the docker SERVICE, I can spin the drives down. But if I start the service (even with zero (0) dockers running, ALL the drives spin up again. This is beyond weird.

OK, I shut down all VMs (Normally not running anyway). I shut down ALL dockers. Same issue. What else can I shut down?

Well, I tried this in maintenance mode, and the drives all still spun up. Bizarre. I'm at a loss on how to troubleshoot this beyond here.

Thanks. Appreciate that. So all it's doing is confirming the immediate spin up. (sigh). Maintenance mode it is.