It is currently Tue Jul 16, 2019 11:58 am
All times are UTC + 8 hours

OneTouch Backup fails with Input/output error(-5). Caused by "Can't copy file to temp file"

OneTouch Backup fails with Input/output error(-5). Caused by "Can't copy file to temp file"

Postby TheBinary1 » Thu May 16, 2019 3:25 am

Just bought the AS6404T and it seems to fail copying from ExternalHDDs using:
1. File Explorer old-fashioned drag-n-drop (no error visible)
2. OneTouchBackup in Copy mode (with error: Input/output error(-5). Caused by "Can't copy file to temp file")
3. SSH command-line "cp -R /share/USB11/* /volume1/Media/ExtHDD/" (no error visible)

In all 3 methods above, a like-for-like copy/backup is not the expected outcome.

I initially thought that ExternalHDDs (formatted in NTFS) had a corrupted filesystem but chkdsk revealed no issues. I then thought that the Asustor's new HDDs might be the issue (unlikely given that they are brand new), but fsck.ext4 revealed no issues. I ran fsck.ext4 using Steps described in viewtopic.php?f=36&t=7761&p=23964&hilit=fsck#p23964 except that I ran fsck.ext4 with the -nf flag.

Sounds like a ridiculous question, but how exactly do I copy / backup external HDDs onto the Asustor NAS?
TheBinary1
 
Posts: 3
Joined: Tue May 14, 2019 6:50 am

Re: OneTouch Backup fails with Input/output error(-5). Caused by "Can't copy file to temp file"

Postby orion » Thu May 16, 2019 10:32 am

So, it sounds that you can list files by "ls /share/USB11/", but copy failed?! That's indeed new for me. By the way, you can check "dmesg" and "cat /var/log/messages" to see if there are any clues.
User avatar
orion
 
Posts: 2274
Joined: Wed May 29, 2013 11:09 am

Re: OneTouch Backup fails with Input/output error(-5). Caused by "Can't copy file to temp file"

Postby TheBinary1 » Fri May 24, 2019 5:40 am

Yes - I was able to do an "ls /share/USB11"

However /var/log/messages does show something interesting:

1. Mounting evidence:
Code: Select all
2019-05-22T16:21:50.002035+02:00 AS6404T-4397 kernel: [548547.746176] usb 1-1: new high-speed USB device number 2 using xhci_hcd
2019-05-22T16:21:50.169004+02:00 AS6404T-4397 kernel: [548547.911459] usb 1-1: New USB device found, idVendor=1058, idProduct=0748
2019-05-22T16:21:50.169047+02:00 AS6404T-4397 kernel: [548547.911468] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
2019-05-22T16:21:50.169052+02:00 AS6404T-4397 kernel: [548547.911473] usb 1-1: Product: My Passport 0748
2019-05-22T16:21:50.169055+02:00 AS6404T-4397 kernel: [548547.911477] usb 1-1: Manufacturer: Western Digital
2019-05-22T16:21:50.169058+02:00 AS6404T-4397 kernel: [548547.911480] usb 1-1: SerialNumber: 575856314335324D37313134
2019-05-22T16:21:50.169061+02:00 AS6404T-4397 kernel: [548547.912392] usb-storage 1-1:1.0: USB Mass Storage device detected
2019-05-22T16:21:50.184009+02:00 AS6404T-4397 kernel: [548547.928197] scsi host8: usb-storage 1-1:1.0


2. Surprise Unmounting
Code: Select all
2019-05-22T21:34:36.593077+02:00 AS6404T-4397 kernel: [567313.810705] usb 1-1: USB disconnect, device number 2
2019-05-22T21:34:36.594042+02:00 AS6404T-4397 kernel: [567313.811880] invalidate_partition: scsi device is invalid
2019-05-22T21:34:39.461018+02:00 AS6404T-4397 kernel: [567316.678523] invalidate_partition: scsi device is invalid
2019-05-22T22:29:34.628039+02:00 AS6404T-4397 kernel: [570611.752972] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc004e
2019-05-22T22:29:34.628072+02:00 AS6404T-4397 kernel: [570611.753008] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc0114
2019-05-22T22:29:34.628077+02:00 AS6404T-4397 kernel: [570611.753031] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc1fb7
2019-05-22T22:29:34.628080+02:00 AS6404T-4397 kernel: [570611.753053] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc00bf
2019-05-22T22:29:34.628084+02:00 AS6404T-4397 kernel: [570611.753074] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc0050
2019-05-22T22:29:34.628087+02:00 AS6404T-4397 kernel: [570611.753095] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc0091
2019-05-22T22:29:34.628090+02:00 AS6404T-4397 kernel: [570611.753116] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc52cf
2019-05-22T22:29:34.628094+02:00 AS6404T-4397 kernel: [570611.753137] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc526d
2019-05-22T22:29:34.628097+02:00 AS6404T-4397 kernel: [570611.753158] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc004f
2019-05-22T22:29:34.628100+02:00 AS6404T-4397 kernel: [570611.753180] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc52bf
2019-05-22T22:33:28.726024+02:00 AS6404T-4397 kernel: [570845.844349] ufsd_printk: 11 callbacks suppressed
2019-05-22T22:33:28.726057+02:00 AS6404T-4397 kernel: [570845.844359] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc004e
2019-05-22T22:33:28.726062+02:00 AS6404T-4397 kernel: [570845.844382] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc0114
2019-05-22T22:33:28.726066+02:00 AS6404T-4397 kernel: [570845.844399] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc1fb7
2019-05-22T22:33:28.726069+02:00 AS6404T-4397 kernel: [570845.844415] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc00bf
2019-05-22T22:33:28.726072+02:00 AS6404T-4397 kernel: [570845.844431] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc0050
2019-05-22T22:33:28.726075+02:00 AS6404T-4397 kernel: [570845.844447] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc0091
2019-05-22T22:33:28.726079+02:00 AS6404T-4397 kernel: [570845.844464] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc52cf
2019-05-22T22:33:28.726082+02:00 AS6404T-4397 kernel: [570845.844481] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc526d
2019-05-22T22:33:28.726085+02:00 AS6404T-4397 kernel: [570845.844497] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc004f
2019-05-22T22:33:28.726107+02:00 AS6404T-4397 kernel: [570845.844513] ufsd: "fileExplorer.cg" (sdc1): failed to read block 0xc52bf
2019-05-22T22:35:52.661025+02:00 AS6404T-4397 kernel: [570989.693907] __sync_blockdev bdev not exist, don't sync


I connected the external HDD to the USB-port at the back of the machine instead of using the one at the front of the machine where the One Touch Backup button is located - and the issue went away. I was able to copy data from the external HDD without any of the disconnects seen above.

I am afraid that I might either have a defective USB-port on the NAS, or maybe the cable of the external HDD is defective. I have tested the external HDD's cable with my laptop and cannot re-produce the issue so I am doubtful that the cable is defective.

Can you tell me what tests I can do on the USB-ports of the NAS?
TheBinary1
 
Posts: 3
Joined: Tue May 14, 2019 6:50 am

Re: OneTouch Backup fails with Input/output error(-5). Caused by "Can't copy file to temp file"

Postby orion » Fri May 24, 2019 11:10 am

I don't know the exact test method. However I think you can try another USB thumb drive (no cable) on the front USB port. If it's working fine, I think you can find another shorter USB cable to connect your external HDD to NAS.
User avatar
orion
 
Posts: 2274
Joined: Wed May 29, 2013 11:09 am

Return to [Official] For AS63XX/64XX Series

  • You cannot post new topics in this forum
    You cannot reply to topics in this forum
    You cannot edit your posts in this forum
    You cannot delete your posts in this forum
    You cannot post attachments in this forum
  • Who is online

    Users browsing this forum: No registered users and 1 guest

cron