I have disabled Docker if i remember i have done this in past and its helped speed up the process

 

I have a script set to run hourly to check for corruption due to nearly loosing everything in past 

 

Script Starting Jan 31, 2025 11:47.01

Full logs for this script are available at /tmp/user.scripts/tmpScripts/checkcachedrives/log.txt

[/dev/sdd1].write_io_errs 0
[/dev/sdd1].read_io_errs 0
[/dev/sdd1].flush_io_errs 0
[/dev/sdd1].corruption_errs 0
[/dev/sdd1].generation_errs 0
[/dev/sde1].write_io_errs 0
[/dev/sde1].read_io_errs 0
[/dev/sde1].flush_io_errs 0
[/dev/sde1].corruption_errs 0
[/dev/sde1].generation_errs 0
Script Finished Jan 31, 2025 11:47.01

Full logs for this script are available at /tmp/user.scripts/tmpScripts/checkcachedrives/log.txt
 

 

Scrub cant run cause mover is running 

 

Daigs attached

 

FYI the reason be hide this is due to upgrading hardware 

 

noticed the following in logs could this be related ? 

vault101-diagnostics-20250131-1201.zip

Edited January 31, 20251 yr by LoyalScotsman

Jan 31 11:27:29 Vault101 kernel: BTRFS error (device sdd1): incorrect extent count for 30408704; counted 1349, expected 1337
Jan 31 11:27:29 Vault101 kernel: BTRFS: error (device sdd1: state A) in convert_free_space_to_extents:466: errno=-5 IO failure
Jan 31 11:27:29 Vault101 kernel: BTRFS info (device sdd1: state EA): forced readonly

 

The pool has filesystem issues, with btrfs I recommend backing up and reformatting.

What would you say is best way off doing this ? 

just remembered i have appdata backup setup and it has backups.

 

So i would be good just to recover from that then

 

will be replacing with 2x m.2 drives so will restore to them and see how goes

Edited January 31, 20251 yr by LoyalScotsman

You can also just copy anything important to another pool or array disk, then copy back.