Comment on [deleted]
tal@lemmy.today 6 days agoI’d suspect that too. Try just reading from the source drive or just writing to the destination drive and see which causes the problems. Could also be a corrupt filesystem; probably not a bad idea to try to fsck it.
IME, on a failing disk, you can get I/O blocking as the system retries, but it usually won’t freeze the system unless your swap partition/file is on that drive. Then, as soon as the kernel goes to pull something from swap on the failing drive, everything blocks. Might try swapoff -a before doing the rsync to disable swap.
At first I was under suspicion was temperature.
I’ve never had it happen, but it is possible for heat to cause issues for hard drives. I don’t know if the firmware will slow down operation to keep temperature sane — rotational drives do normally have temperature sensors, so I’d think that it would. Could try aiming a fan at the things. I doubt that that’s it, though.
ZeDoTelhado@lemmy.world 6 days ago
The reason I suspected temps was I changed very recently to a define r6 (got it second hand). And since the start I am a bit suspicious of how it performs thermally (terms of sound is actually quite OK).
I do have a fan on the drives but still one of the drives goes up to 40C still (even with front door open).
Also, when you talk about fsck, what could be good options for this to check the drive?
tal@lemmy.today 6 days ago
I’ve never used proxmox, so I can’t advise how to do so via the UI it provides. As a general Linux approach, though, if you’re copying from a source Linux filesystem, it should be possible to unmount it — or boot from a live boot Linux CD, if that filesystem is required to run the system — and then just run
fsck /dev/sda1or whatever the filesystem device is.