Hi, I'm testing with delay_use=10 now on the WD Red disks.
I'm really confused as I still have the same error below. The funny thing is that I run a backup script and I got the error almost immediately, but after 7-8 files.
Then I run the backup again and it started working. It copied several hundreds of Mb, maybe a few Gb, then again the error.
- Code: Select all
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: close failed on "/share/1000/192.168.0.148-smb-data1/mdi/Backup_Acer/D/SAUER/.DatiAvanzamento.mdb.Z09SLQ": Bad file descriptor (9)
rsync error: error in file IO (code 11) at receiver.c(752) [receiver=3.0.9]
rsync: connection unexpectedly closed (77890 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
So apparently this is not related with the data or their size/quantity.
The disks are ok even when checked by e2fsck and now they are MBR ext4 (no GPT). :thinking
No errors within dmsg at this time. Only later (maybe 15/20m later), I got this in dmsg:
- Code: Select all
[ 3699.568386] usb 1-1.2: reset high-speed USB device number 6 using dwc_otg
[ 3715.748956] usb 1-1.2: reset high-speed USB device number 6 using dwc_otg
[ 3715.928978] usb 1-1.2: reset high-speed USB device number 6 using dwc_otg
[ 3726.109367] usb 1-1.2: reset high-speed USB device number 6 using dwc_otg
[ 3726.210658] sd 2:0:0:1: Device offlined - not ready after error recovery
[ 3726.210748] sd 2:0:0:1: rejecting I/O to offline device
[ 3726.210775] sd 2:0:0:1: [sdc] killing request
[ 3726.210810] sd 2:0:0:1: rejecting I/O to offline device
[ 3726.210920] sd 2:0:0:1: [sdc] Unhandled error code
[ 3726.210942] sd 2:0:0:1: [sdc]
[ 3726.210955] Result: hostbyte=0x01 driverbyte=0x00
[ 3726.210969] sd 2:0:0:1: [sdc] CDB:
[ 3726.211006] cdb[0]=0x28: 28 00 6f 00 09 08 00 00 08 00
[ 3726.211052] end_request: I/O error, dev sdc, sector 1862273288
[ 3726.212663] sd 2:0:0:1: rejecting I/O to offline device
[ 3726.212741] EXT4-fs error (device sdc1): __ext4_get_inode_loc:3697: inode #58
195969: block 232783904: comm smbd: unable to read itable block
[ 3726.319510] sd 2:0:0:1: rejecting I/O to offline device
[ 3726.319593] Aborting journal on device sdc1-8.
[ 3726.319641] sd 2:0:0:1: rejecting I/O to offline device
[ 3726.319678] JBD2: Error -5 detected when updating journal superblock for sdc1
-8.
I found the initial reset message, so, I tried to "ls" one of the disks while those errors started to appear.
Above is the full list of messages I got.
I'm thinking of using a dd if=/dev/zero all over the disk and format again. Do you think it could be a chance to have it working?
:hammerhead