3 hours ago, flyize said:

Will that work?

Yes but you will have to 

 

4 hours ago, trurl said:

New Config without it and check the box saying parity is valid

or it will still think the disk is parity2

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

Currently it's moving to disk9, which is also SMR, configure the share or a test share to move data to one of the non SMR disks and see if that makes any difference.

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?

There have been other reports of very bad performance with that specific model, just with some, not all, so it's not just because they are SMR, if the other disks are performing nominally you should replace it, or exclude it from writes.

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...

Do the other drives perform normally?

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.

4 minutes ago, flyize said:

The parity rebuild has now sped up to about 40MB/sec

That could be SMR, though during rebuilds SMR effect is not usually felt, at least for most drives I tested with.

 

Unlikely a new cable would help if there are no ATA errors logged.

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

38 minutes ago, flyize said:

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

The fact that the drive is empty should be irrelevant to a parity check/rebuild - it simply processes every sector on the drive in turn regardless of its contents.

If it's an option I would test with a non SMR drive in that slot.

I just ordered some. Will report back!

On 4/14/2021 at 2:13 PM, flyize said:

Any ideas here?

 

I notice that the SMART report for Disk9 in the diagnostics dated 20210414-0910 is incomplete. There was definitely something wrong with it. Here it is, unedited: ST8000DM004-2CX188_ZCT0A49C-20210414-0910 disk9 (sdh).txt

 

@flyize

Did you ever get to the bottom on this? in experiencing the Exact same behavour.

 

the only way to reliably empty out my cache is to disable Docker/Vm's and Reboot, most of the time uncleanly then after reboot its flying thro the whole 300Gb plus no problems at all.

Edited September 16, 20214 yr by Puregreen59

4 minutes ago, Puregreen59 said:

Exact same behavour

Often this is the beginning of a discussion that reveals significant differences in the details.

 

Post diagnostics.

Hah! i love it!

well do let me know if you find anything strange.

 

i have just done a reboot, and i should have grabbed the diagnostics but i didn't  but these logs are from the last time.

jarvis-diagnostics-20210904-2120.zip

I notice you are using Mover Tuning plugin instead of the built-in mover. That is the first suspect for any mover problems.

Yes cheers for pointing it out I had assumed that may have bee causing a problem and have already removed it, but unfortunately no dice, I've got another log for you, it's doing it right as we speak, 

jarvis-diagnostics-20210918-1321.zip

Edited September 18, 20214 yr by Puregreen59

If you have issues with the mover you need to enable mover logging, run the mover, then post new diags.

Hey guys having major issues with the mover process. it seems to keep hanging and the only thing I can see in its logging is "move: stat: cannot statx xxxxxxxxxx cannot be found" it would apprear that after a while the "find" process then disappears for from the open files plugin but the move button is still grayed out.

Mover seems to be a pretty buggy. I have been struggling to move everything off my cache drives to change them out with the mover and have had to resort to doing it manually as the mover keeps stalling or getting hung up on something.

No disc activity or cache activity happens

This does not seem to directly related to any particular type of file or file in general as it has happened or stalled on quite a number of different appdata files/ folders.

I'm happy to help out trying to improve the mover however I am limited time wise.
 

Enable mover logging and post the diagnostics after the problem.

16 hours ago, IronBeardKnight said:

struggling to move everything off my cache drives

Nothing can move open files. You have to Disable Docker and VM Manager in Settings to get everything moved.

 

Also, mover won't replace files, so if something already exists on the array it won't be moved from cache. You will have to see which copy you want to keep and clean that up yourself. Dynamix File Manager can help with this.