flyize

This seems to indicate that v4 is ready! They've already updated the mobile app, which doesn't seem to work with v3.

I know we're getting way off topic here, but doesn't it seem like it should? If parity1 is wrong, then won't parity2 be calculated incorrectly as well?

I'll be adding a second parity drive after I remove this data drive. Is it safe to assume that parity is checked when parity2 is added?

LOL I think I'm safe. Thanks!

I can't just restart dd? edit: That's what I did yesterday anyway. It took about 24 hours to zero out an 8TB drive.

Is there a log kept of this somewhere? I let it run overnight. It seems that my Unraid browser window disconnected though. It doesn't seem that dd is running anymore. Obviously I need to know if it completed successfully though before pulling the drive.

I just ordered some. Will report back!

It's so weird. This slow performance, mover hanging, and reboot issues just came out of nowhere. I can't explain it. So far I have: * Removed the SMR parity drive and added it as a data drive * Completely replaced that drive Is there anything obvious that I might be missing? Just for fun, I've attached new diagnostics. truffle-diagnostics-20210416-0917.zip

Yes, they do. The parity rebuild has now sped up to about 40MB/sec. I think that's because it's gotten to the empty portion of the drive. If the times are correct, it will be about 2.5 days for parity to rebuild the drive. I'd love to try another cable for the drive, but obviously that would start everything back over.

So I put a new drive in there and its still running very slowly. The new drive is SMR as well, but the rebuild is running at about 250 KB/sec. Since its using the same SAS cable as the old drive, could that channel on the cable be bad? I'm not seeing any CRC errors...

So I tried to write a 1GB file via dd to disk9. It was still writing about 10 minutes later. I ran an xfs_repair to see if it would find anything and got nothing. SMART all checks out okay. Obviously, I've pulled that drive. Is there anything I can attempt to do to the drive, other than try to get a warranty repair on it?

Okay, I moved the shingled drive out of parity, but I'm still having issues with the Mover running *very* slowly, or maybe even hung. Any ideas here? truffle-diagnostics-20210414-0910.zip

My plan was going to be to move parity2 into the array, unbalance data off a non-SMR drive, then add that drive as parity2. Will that work?

As for just ripping parity2 out, I get this message [quote]Start will disable the missing disk and then bring the array on-line. Install a replacement disk as soon as possible.[/quote] Can someone confirm that parity will be maintained by the other parity drive?

It *was* moving files, just very slowly. With Docker/VMs disabled, its moving them much faster.

Can I just remove the 2nd parity drive without having to rebuild parity? edit: Also, I just disabled Docker and VMs, and now the Mover is flying again. Any chance that would offer clues as to what is going on?

Well that's interesting. Is it worth moving disks around so that I don't an SMR drive in parity? edit: Mover is still running from this morning. It looks like its taking about 1.5 hours to move a ~2GB file.

Attached. Although after some thought, I have an idea what the issue might be. I added a new drive. Unfortunately its a shingled drive. I think when Mover runs, it very quickly overwhelms the cache on the SMR drive (cache drive is 1TB). Does that seem logical? If so, would that somehow prevent the machine from properly rebooting? truffle-diagnostics-20210406-1522.zip

It appears that it took the Mover about 3 hours to move a 2GB file. What could be going on here?

Looks like my Sonarr updated last night and now can't connect to any indexers, but Radarr seems fine. Anyone seen this? 21-4-6 08:27:54.6|Error|X509CertificateValidationService|Certificate validation for https://*REMOVED* failed. RemoteCertificateChainErrors

Okay, I'm still seeing this issue. I was unable to reboot last night and had to power the server off and back on. Now I turned on the Mover, and it's hung. Can anyone help? truffle-diagnostics-20210406-0841.zip

Apparently you see what I'm getting at here. Yeah, a min/max with FIFO would be AWESOME. I wrote a PowerShell script for DrivePool that did that back when I was still on Windows. Maybe I'll have to dust off my scripting hat.

Possible to request that as a feature then? 😁

If I set 'Move files off cache based on age?' to yes, and set days to 0, will it simply move whatever the oldest file is, FIFO style?

I didn't see any obvious errors to suggest file system corruption, no. edit: This suggests that I have ECC enabled in the BIOS. The server doesn't have KVM, should I drag it down and check to see if ECC is enabled? http://forums.debian.net/viewtopic.php?f=5&t=141551