-> Are you running windows on the same hardware as Linux/BSD ? Is it a
dual-boot system?
I have a lot of disks connected to the PC (USB,Sata.M1,SSD) where I have
installed different OS,like Linux (Ubuntu 24.04),FreeBSD (14.1 and
14.2),Windows (11).
---> If you have different systems for windows
Mario,
Are you running windows on the same hardware as Linux/BSD ? Is it a dual-boot
system?
If you have different systems for windows vslinux, it's possible there is a HW
issue with one of them.
Tom
On 24 December 2024 7:44:16 am GMT+12:00, Mario Marietto via rsync
wrote:
> What would yo
-> Did you re-read the data and compare checksums ?
Don't know how to do this.
-> 2nd thought: What file systems do you use, and is there a peculiar size
of the file, hitting a limit?
Do I read this correct, rsync throws the error at
320,072,933,376, then continues to
640,302,152,539 bytes (file
On 23.12.24 20:44, Mario Marietto via rsync wrote:
What would you think if I told you that using Windows I no longer had that
problem ?
Would you still think that there are hardware problems ?
And if so, why would they only manifest themselves using Linux and FreeBSD and
not using Windows?
What would you think if I told you that using Windows I no longer had that
problem ?
Would you still think that there are hardware problems ?
And if so, why would they only manifest themselves using Linux and FreeBSD
and not using Windows?
On Mon, Dec 23, 2024 at 9:38 PM Robin Lee Powell <
rlpow.
And I forgot to mention that I see the error even when trying to transfer
files from and to a new disk,not an USB disk,bought some days ago,model
Crucial BX500 SATA SSD 480GB,SSD. So,I'm not able to believe that even this
disk is damaged. This is a very strange situation.
On Mon, Dec 23, 2024 at
>Almost certainly your drive is going bad. On Linux I'd tell you to check
dmesg for drive errors, I don't know what the FreeBSD
equivalent is. But I strongly recommend that you treat that drive as
"going to fail any second".
I'm not sure that this is the reason. I see the error regardless of t
Using the parameters below the file hasn't been removed at 100% even if I
got the same error :
root@Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# rsync
--inplace --append --partial Free
BSD-141-UFS-sdc-DarkMatter.img /mnt/sdj1/OS/Backup/BSD/FreeBSD
rsync: [sender] read errors mapping
Happened again :
root@Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# sudo rsync
-azvvP FreeBSD-141-UFS-sdc-DarkMatter.img /mnt/sdj1/OS/Backup/BSD/FreeBSD
sending incremental file list
delta-transmission disabled for local transfer or --whole-file
FreeBSD-141-UFS-sdc-DarkMatter.img
320,
>As it's just a single file you're trying to copy, why not use cp?
>Although I expect that cp will also throw an IO error at some point.
Yes,I tried cp and I got the same error,that usually happens before
rsync,that is able to complete the transfer until 99%.
I've detached and reattached the USB d
On Mon 23 Dec 2024, Mario Marietto via rsync wrote:
>
> Everytime I try to copy a file from one USB disk to another one (does not
> matter which one),I get this kind of error :
>
>
> mario@Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# rsync
> -avxHAXP FreeBSD-141-UFS-sdc-DarkMatter.
Hello.
Everytime I try to copy a file from one USB disk to another one (does not
matter which one),I get this kind of error :
mario@Z390-AORUS-PRO-DEST:/mnt/zroot-133/A_FILES/Backup/FreeBSD# rsync
-avxHAXP FreeBSD-141-UFS-sdc-DarkMatter.img
/mnt/sdj1/OS/Backup/BSD/FreeBSD --ignore-existing
send
12 matches
Mail list logo
