Mario Marietto
2024-Dec-23 18:00 UTC
rsync: [sender] read errors mapping "file" : Input/output error (5)
>Almost certainly your drive is going bad. On Linux I'd tell you to checkdmesg 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 the USB disks that I use. And I have a lot of USB disks,10 disks. No,I don't see disk errors on dmesg. I see the errors on Linux and FreeBSD. Don't know if I see them also using Windows. Now I'm trying to transfer some files using Windows 11 because I want to exclude some variables from the equation. On Mon, Dec 23, 2024 at 7:49?PM Robin Lee Powell < rlpowell at digitalkingdom.org> wrote:> 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". > > On Mon, Dec 23, 2024 at 12:56:09PM +0100, Mario Marietto via rsync wrote: > > Using the parameters below the file hasn't been removed at 100% even if I > > got the same error : > > > > root at 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 > > "/mnt/zroot-133/A_FILES/Backup/FreeBSD/FreeBSD-141-UFS-sdc-DarkMatt > > er.img": Input/output error (5) > > ^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at > > rsync.c(701) [sender=3.2.4dev] > > rsync error: received SIGUSR1 (code 19) at main.c(1598) > [generator=3.2.4dev] > > > > Can I know the reasons why I get those errors ? > > > > On Mon, Dec 23, 2024 at 11:30?AM Mario Marietto <marietto2008 at gmail.com> > > wrote: > > > > > Happened again : > > > > > > root at 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,072,933,376 *100%* 80.31MB/s 1:03:20 (xfr#1, to-chk=0/1) > > > > > > rsync: [sender] read errors mapping > > > "/mnt/zroot-133/A_FILES/Backup/FreeBSD/FreeBSD-141-UFS-sdc-DarkMatt > > > er.img": Input/output error (5) > > > > > > WARNING: FreeBSD-141-UFS-sdc-DarkMatter.img failed verification -- > update > > > discarded (will try again). > > > FreeBSD-141-UFS-sdc-DarkMatter.img > > > 2,391,146,496 0% 183.65MB/s 0:28:09 ^C > > > > > > > > > > > > On Mon, Dec 23, 2024 at 11:14?AM Mario Marietto < > marietto2008 at gmail.com> > > > wrote: > > > > > >> >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 disks,but I still see the error. > > >> > > >> On Mon, Dec 23, 2024 at 11:07?AM Paul Slootman via rsync < > > >> rsync at lists.samba.org> wrote: > > >> > > >>> 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 at 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 > > >>> > > > >>> > sending incremental file list > > >>> > FreeBSD-141-UFS-sdc-DarkMatter.img > > >>> > > > >>> > 320,072,933,376 100% 83.57MB/s 1:00:52 (xfr#1, to-chk=0/1) > > >>> > rsync: [sender] read errors mapping > > >>> > > > >>> > "/mnt/zroot-133/A_FILES/Backup/FreeBSD/FreeBSD-141-UFS-sdc-DarkMatter.img": > > >>> > Input/output error (5) > > >>> > > >>> Input/output error (5) usually indicates some hardware problem, not > > >>> related to the application. > > >>> > > >>> 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. > > >>> > > >>> You could use --inplace --append --partial with rsync and repeat the > > >>> command until it finally completes. > > >>> > > >>> > > >>> Paul > > >>> > > >>> -- > > >>> Please use reply-all for most replies to avoid omitting the mailing > list. > > >>> To unsubscribe or change options: > > >>> https://lists.samba.org/mailman/listinfo/rsync > > >>> Before posting, read: > http://www.catb.org/~esr/faqs/smart-questions.html > > >>> > > >> > > >> > > >> -- > > >> Mario. > > >> > > > > > > > > > -- > > > Mario. > > > > > > > > > -- > > Mario. > > > -- > > Please use reply-all for most replies to avoid omitting the mailing list. > > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/rsync > > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html > >-- Mario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20241223/083ffe3f/attachment.htm>
Mario Marietto
2024-Dec-23 18:05 UTC
rsync: [sender] read errors mapping "file" : Input/output error (5)
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 7:00?PM Mario Marietto <marietto2008 at gmail.com> wrote:> >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 the > USB disks that I use. And I have a lot of USB disks,10 disks. > No,I don't see disk errors on dmesg. I see the errors on Linux and > FreeBSD. Don't know if I see them also using Windows. > Now I'm trying to transfer some files using Windows 11 because I want to > exclude some variables from the equation. > > On Mon, Dec 23, 2024 at 7:49?PM Robin Lee Powell < > rlpowell at digitalkingdom.org> wrote: > >> 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". >> >> On Mon, Dec 23, 2024 at 12:56:09PM +0100, Mario Marietto via rsync wrote: >> > Using the parameters below the file hasn't been removed at 100% even if >> I >> > got the same error : >> > >> > root at 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 >> > "/mnt/zroot-133/A_FILES/Backup/FreeBSD/FreeBSD-141-UFS-sdc-DarkMatt >> > er.img": Input/output error (5) >> > ^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at >> > rsync.c(701) [sender=3.2.4dev] >> > rsync error: received SIGUSR1 (code 19) at main.c(1598) >> [generator=3.2.4dev] >> > >> > Can I know the reasons why I get those errors ? >> > >> > On Mon, Dec 23, 2024 at 11:30?AM Mario Marietto <marietto2008 at gmail.com >> > >> > wrote: >> > >> > > Happened again : >> > > >> > > root at 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,072,933,376 *100%* 80.31MB/s 1:03:20 (xfr#1, to-chk=0/1) >> > > >> > > rsync: [sender] read errors mapping >> > > "/mnt/zroot-133/A_FILES/Backup/FreeBSD/FreeBSD-141-UFS-sdc-DarkMatt >> > > er.img": Input/output error (5) >> > > >> > > WARNING: FreeBSD-141-UFS-sdc-DarkMatter.img failed verification -- >> update >> > > discarded (will try again). >> > > FreeBSD-141-UFS-sdc-DarkMatter.img >> > > 2,391,146,496 0% 183.65MB/s 0:28:09 ^C >> > > >> > > >> > > >> > > On Mon, Dec 23, 2024 at 11:14?AM Mario Marietto < >> marietto2008 at gmail.com> >> > > wrote: >> > > >> > >> >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 disks,but I still see the error. >> > >> >> > >> On Mon, Dec 23, 2024 at 11:07?AM Paul Slootman via rsync < >> > >> rsync at lists.samba.org> wrote: >> > >> >> > >>> 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 at 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 >> > >>> > >> > >>> > sending incremental file list >> > >>> > FreeBSD-141-UFS-sdc-DarkMatter.img >> > >>> > >> > >>> > 320,072,933,376 100% 83.57MB/s 1:00:52 (xfr#1, to-chk=0/1) >> > >>> > rsync: [sender] read errors mapping >> > >>> > >> > >>> >> "/mnt/zroot-133/A_FILES/Backup/FreeBSD/FreeBSD-141-UFS-sdc-DarkMatter.img": >> > >>> > Input/output error (5) >> > >>> >> > >>> Input/output error (5) usually indicates some hardware problem, not >> > >>> related to the application. >> > >>> >> > >>> 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. >> > >>> >> > >>> You could use --inplace --append --partial with rsync and repeat the >> > >>> command until it finally completes. >> > >>> >> > >>> >> > >>> Paul >> > >>> >> > >>> -- >> > >>> Please use reply-all for most replies to avoid omitting the mailing >> list. >> > >>> To unsubscribe or change options: >> > >>> https://lists.samba.org/mailman/listinfo/rsync >> > >>> Before posting, read: >> http://www.catb.org/~esr/faqs/smart-questions.html >> > >>> >> > >> >> > >> >> > >> -- >> > >> Mario. >> > >> >> > > >> > > >> > > -- >> > > Mario. >> > > >> > >> > >> > -- >> > Mario. >> >> > -- >> > Please use reply-all for most replies to avoid omitting the mailing >> list. >> > To unsubscribe or change options: >> https://lists.samba.org/mailman/listinfo/rsync >> > Before posting, read: >> http://www.catb.org/~esr/faqs/smart-questions.html >> >> > > -- > Mario. >-- Mario. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20241223/42cb3490/attachment.htm>
Maybe Matching Threads
- rsync: [sender] read errors mapping "file" : Input/output error (5)
- rsync: [sender] read errors mapping "file" : Input/output error (5)
- Re: rsync: [sender] read errors mapping "file" : Input/output error (5)
- rsync: [sender] read errors mapping "file" : Input/output error (5)
- rsync: [sender] read errors mapping "file" : Input/output error (5)