Hi all,

 

I'm sure the answer is right in front of me, but I've tried everything and for some reason my Parity Check / Sync won't go much faster than a few hundred kb/s and has an ETA of anywhere from 600 to 5,000 days.

 

It's worked fine in the past, this is a new development. I've run DiskSpeed, nothing looks out of the ordinary. I've tried formatting the parity drive entirely and starting fresh but still running into the same issue. I'm not seeing any major RAM or CPU usage. 

 

I'm on 7.0.0-rc.2 and the parity drive is XFS (as are the array drives).

 

Any help would be greatly appreciated!

1 hour ago, AstroBoy said:

the parity drive is XFS

No it isn't, Parity has no filesystem and doesn't know anything about files.

 

Attach Diagnostics to your NEXT post in this thread.

16 hours ago, trurl said:

No it isn't, Parity has no filesystem and doesn't know anything about files.

 

Attach Diagnostics to your NEXT post in this thread.

 

Thanks trurl, yes, my mistake re: the filesystem.

 

Diagnostics attached. Let me know if there’s anything else I should send, thanks!

 

 

tower-diagnostics-20250105-1030.zip

Connection problems. ata5 mostly in logs, but also some ata4, maybe others.

 

These are on the motherboard controller.

 

Check all connections, all disks, both ends, SATA and power, including splitters.

 

Then try again and post new diagnostics.

Ok so am I simply confirming that everything has a secure connection, or is there something specific I should do to test each connection?

Edited January 5, 20251 yr by AstroBoy

The test will be when you try again.

 

All plugs must sit firmly and squarely on the connector, with no tension in cables. Also don't bundle data cables to make things "neat".

I unplugged and re-plugged all SATA data and power cables and that seems to have done the trick! Getting 50 - 100 MB/s on my parity sync now. Thanks so much, trurl!

 

I've attached a new diagnostics here in case it's helpful.

tower-diagnostics-20250105-1430.zip

Looks like disk1 is unmountable now. It was mounted in your previous diagnostics.

 

Stop parity sync then check filesystem on disk1 from the webUI and post the results.

Also, your system share has files on the array. After you get these more serious problems fixed we can work on that.

Yeah, I caught that after I posted my last response. Thankfully the check fixed it. 

 

New diagnostics attached.

tower-diagnostics-20250105-1451.zip

2 minutes ago, trurl said:

Also, your system share has files on the array. After you get these more serious problems fixed we can work on that.

Oh yes, that would be great.

Disk1 is mounted now. Looks like repair couldn't figure some things out. Go to User Shares page, click Compute... on the new lost+found share, and post a screenshot.

Looks like it's taking up 441kb

 

That's not much. Take a look at the contents and see if you can figure out what it is or if it's important.

 

1 hour ago, trurl said:

your system share has files on the array

We can work on that after parity is synced. Disable Docker and VM Manager until we can work that out.

Ok will do. I'll come back when the parity is synced in a day or so!

Quick update – parity sync slowed down a bit, might be a few days before it’s done. I’ll check in then!

Unfortunately, I was evacuated the last few days as I'm near the fires in LA. Just got back with power so another couple days left on the parity sync.

Hi @trurl, the parity sync completed without issue. Diagnostics attached. If you're still able to help me with the system shares and any other issues you might notice, that would be much appreciated!

tower-diagnostics-20250111-2352.zip