The output of the command is: # dd if=Fotos.zip of=/dev/null dd: error reading ‘Fotos.zip’: Input/output error 328704+0 records in 328704+0 records out 168296448 bytes (168 MB) copied, 0.127723 s, 1.3 GB/s or # cp Fotos.zip /tmp/ cp: error reading ‘Fotos.zip’: Input/output error cp: failed to extend ‘/tmp/Fotos.zip’: Input/output error There is nothing on dmesg after running those commands; []'s Salatiel On Sun, Jan 22, 2017 at 9:18 PM, John Stoffel <john@xxxxxxxxxxx> wrote: > > Salatiel> I am trying to recover a few files from my backup. The > Salatiel> backup is on a raid 5 + ext4. There are several files where > Salatiel> i get I/O error. The raid appears to be clean and fsck shows > Salatiel> no errors. Any ideas what could it be ? > > Salatiel> md1 : active raid5 sdd1[0] sdg1[4] sdf1[2] sde1[1] > Salatiel> 3220829184 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU] > Salatiel> bitmap: 1/8 pages [4KB], 65536KB chunk > > It would help if you could post the error(s) you're getting, along > with any output from dmesg during that time. Have you done a full > scan of the disk looking for errors? You might just have silent > read errors in your array. So as root do: > > # echo check >>/sys/block/md??/md/sync_action > > where md?? is the name of your md array you want to check. You can > get the name from: > > cat /proc/mdstat > > and of course it would help to post that info as well if you want more > help. > > John -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
