On 04/03/20 22:53, David C. Rankin wrote: > On 03/02/2020 12:57 AM, David C. Rankin wrote: >> On 03/02/2020 12:51 AM, Roman Mamedov wrote: >>> Yes, replace the drive ASAP, and see if that solves it. >> >> Will do, thank you! >> > > Drive replaced and rebuilding: > > md4 : active raid1 sdc[3] sdd[2] > 2930135488 blocks super 1.2 [2/1] [_U] > [>....................] recovery = 1.5% (46390912/2930135488) > finish=276.0min speed=174102K/sec > bitmap: 1/22 pages [4KB], 65536KB chunk > > Things are looking good, speed=174102K/sec, which is a far-sight better than > speed=2022K/sec. This will give a 4.5 hour rebuild (instead of a 26 day > scrub). I suspect the virtualbox problems will disappear as well once the > rebuild is done. > > Thank you to everyone for helping get me pointed in the right direction. I'll > let you know if I have any further issues here, but I don't anticipate any > (fingers-crossed...) > Raid 1 - look at dm-integrity. That should make scrubbing (hopefully) redundant :-) I might at last soon get my new system up and running (got a shop to look at it - dud motherboard :-( Of course it's now out of warranty and my supplier has gone bust, but if the shop say it was dud from the start I might be able to claim something ... But that means I'll have a test system - I've acquired about 6 x 1TB drives - so I shall be playing with some slightly more heavy-duty raid configs :-) Cheers, Wol