Hard Drive Input Output Error Linux
Contents |
#1 2013-06-15 11:24:02 epaaj Member Registered: 2011-08-10 Posts: 5 [SOLVED] Disk crash - Input/output error - Error reading blocks Hi guys,I ubuntu input output error external hard drive need some help recovering data from a disk that I believe input output error hard drive mac either is completely broken already or it will soon be.It started when trying to browse a dd error reading dev sdb input output error specific folder. When i ran "ls" in it I got "Input/output error" for all folders in it. I could not list anything within the folder.I unmounted
How To Fix Input Output Error In Linux
the hard drive immediately.I noticed several rows with these in dmesg:"[607277.950354] Buffer I/O error on device sdb1, logical block 23320""dd if=/dev/sdb1 of=/mnt/backup/location" gives me about 44kB and then it thinks it is done. The drive is 500GB and almost full. Only one partition.Disk /dev/sdb: 500.1 GB, 500107862016 bytes, 976773168 sectors Units = input/output error centos sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x000621d7 Device Boot Start End Blocks Id System /dev/sdb1 * 63 976768064 488384001 83 Linux"sudo e2fsck -f /dev/sdb1" gives:e2fsck 1.42.7 (21-Jan-2013) e2fsck: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdb1 Could this be a zero-length partition?Ran "sudo dumpe2fs /dev/sdb1 | grep -i superblock" to find the superblock locations:Primary superblock at 0, Group descriptors at 1-30 Backup superblock at 32768, Group descriptors at 32769-32798 Backup superblock at 98304, Group descriptors at 98305-98334 Backup superblock at 163840, Group descriptors at 163841-163870 Backup superblock at 229376, Group descriptors at 229377-229406 Backup superblock at 294912, Group descriptors at 294913-294942 Backup superblock at 819200, Group descriptors at 819201-819230 Backup superblock at 884736, Group descriptors at 884737-884766 Backup superblock at 1605632, Group descriptors at 1605633-1605
here for a quick overview of the site Help Center Detailed answers to any questions you might input/output error ubuntu have Meta Discuss the workings and policies of this site About Us
"dd: /dev/rdisk3: Input/output Error"
Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with
Dd Writing To ‘/dev/sdb’ Input/output Error
us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and https://bbs.archlinux.org/viewtopic.php?id=165237 other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top “Input/output error” when accessing a directory up vote 39 down vote favorite 9 I want to list and remove the content http://unix.stackexchange.com/questions/39905/input-output-error-when-accessing-a-directory of a directory on a removable hard drive. But I have experienced "Input/output error": $ rm pic -R rm: cannot remove `pic/60.jpg': Input/output error rm: cannot remove `pic/006.jpg': Input/output error rm: cannot remove `pic/008.jpg': Input/output error rm: cannot remove `pic/011.jpg': Input/output error $ ls -la pic ls: cannot access pic/60.jpg: Input/output error -????????? ? ? ? ? ? 006.jpg -????????? ? ? ? ? ? 006.jpg -????????? ? ? ? ? ? 011.jpg I was wondering what the problem is? How can I recover or remove the directory pic and all of its content? My OS is Ubuntu 12.04, and the removable hard drive has ntfs filesystem. Other directories not containing or inside pic on the removable hard drive are working fine. Added: Last part of output of dmesg after I tried to list the content of the directory: [19000.712070] usb 1-1: new high-speed USB device number 2 using ehci_hcd [19000.853167] usb-storage 1-1:1.0: Quirks match for vid 05e3 pid 0702: 520 [19000.853195] scsi5 : usb-storage 1-1:1.0 [19001.856687] scsi 5:0:0:0: Direct-Access ST316002
CatWeaselLinux drivers for MK3/4 PCI pg_trompePostgreSQL replication trycatchC exception/signal handling lib Patchesto various software Toolsand small scripts Docsmisc documents Linksto lighting stuff > llg.cubic.org > docs > hdrescue.html http://llg.cubic.org/docs/hdrescue.html How to rescue a partially damaged hard disk The HD of my work computer was broken. It failed to read some sectors, while working ok otherwise. The following text shows, how I recovered the filesystem. A couple of years later Florian Hackenberger pointed out, that dd can cope with read errors if you supply the correct options. So you output error could also use something like: dd if=/dev/hdc1 of=disk.img bs=512 conv=noerror,sync. Even more comfortable rescue is possible with the specialized tools ddrescue or dd_rescue. My completely manual method I got myself a second computer with a big empty harddisk and a running linux. I installed the broken HD on the secondary IDE channel. My plan was to get a raw image input output error of the main partition, mount it again with linux's loop option and copy the data onto a new HD. The broken HD is /dev/hdc . Partition 1 is the / file system. Partition 2 was my swap device. I read in blocks of 1024 bytes. [root@base /tmp]# dd if=/dev/hdc1 of=1 bs=1024 dd: /dev/hdc1: Input/output error 7332+0 records in 7332+0 records out The first part of the disc was read. Obviously the 7333th sector of the HD is damaged. I tried a dd if=/dev/hdc1 of=tmp bs=1024 skip=7332 count=1 and got the IO error again. So we just skip this sector and proceed with the area after. [root@base /tmp]# dd if=/dev/hdc1 of=2 bs=1024 skip=7333 dd: /dev/hdc1: Input/output error 385907+0 records in 385907+0 records out We encountered another broken sector. We just skip it. Be carefull about the new skip value. You have to sum up all previous skip values: 7333 + 385908 = 393241 ! [root@base /tmp]# dd if=/dev/hdc1 of=3 bs=1024 skip=393241 1219527+0 records in 1219527+0 records out Now we finally managed to read up to the end of