Data Rescue Error Reading Block
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 error reading block short read need some help recovering data from a disk that I error reading block invalid argument believe either is completely broken already or it will soon be.It started when trying to browse
Error Reading Block Force Rewrite
a 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
Fsck Error Reading Block
folder.I unmounted 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 e2fsck error reading block Units = 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 160563
Knowing the basics about the types of data loss and how to recovery your files from a failing or failed hard drives can help you be better prepared
Input Output Error Hard Drive Mac
on how to deal with the situation. Types of Hard Drive Failures - ubuntu input output error external hard drive Physical and Logical Physical failures typically mean that the drive has experienced some sort of physical damage and the "dd: /dev/rdisk3: input/output error" mechanical parts of the drive are malfunctioning or no long working correctly. Logical failures mean the file system has experienced some sort of corruption. What Causes Hard Drive Failures? Physical failures are https://bbs.archlinux.org/viewtopic.php?id=165237 generally a result of the drive being mishandled (dropped, bumped). If the drive is shorted out by an electric surge, if power is cut while the drive is writing data, or if dust/debris manages to make it inside the drive housing can all cause physical failures. Physical failures can eventually occur overtime an extended period of time as the drive is used or, while https://www.prosofteng.com/blog/failed-hard-drive/ not as common, can result from a manufacturing defect which is the reason many drive manufacturer provide a warranty. Logical failures are caused by deletion of critical system files or the system not being able to find those critical files. It can also be caused by improper shutdown of the machine, including power loss, as well as malware attacks and software conflicts. Symptoms of Failing Hard Drives Clicking, grinding, or rattling noises coming from the drive OS, system, or applications become slow (beach balls) Disappearing data and disk errors (unable to read/write to/from the drive) Drive doesn’t mount or randomly unmounts while in use Computer crashes, kernel panic, drive won’t boot Drive regularly needs to be “repaired” using disk utility Recovering File from a Failing or Failed Hard Drive When a drive fails there are two methods of data recovery available. Software data recovery such as Data Rescue 4, and physical data recovery that requires the drive be sent into a Data Recovery lab such as The Data Rescue Center where the drive will be repaired to a state in which the data can be extracted from the drive. Typ
10 iPad Air 2 iPad mini 4 (2015) iPad Pro iPhone 6s iPhone 7 iPhone 8 (2017) iPhone SE iPod nano iPod shuffle iPod touch Mac mini Mac Pro MacBook Air MacBook Pro macOS Sierra Retina MacBook Thunderbolt Display tvOS 10 watchOS 3 Buyer's Guide Forums Forums Front Page Roundups Buyer's Guide Forums Roundups OS X Yosemite MacBook Air iOS 8 Apple Watch Log in Sign up Recent Posts Spy Support Support Quick Links General FAQ MacRumors Theme FAQ Contact Us Lost Password Menu Search titles only Posted by http://forums.macrumors.com/threads/data-rescue-ii-urgent-question.380396/ Member: Separate names with a comma. Newer Than: Search this thread only Search this forum only Display results as threads More... Useful Searches Recent Posts Options Please select a forum to jump to News and Article Discussion MacRumors.com News Discussion Mac Blog Discussion iOS Blog Discussion iPhone, iPad, and iPod Touch iOS http://hints.macworld.com/article.php?story=20110216112523818 iOS 9 (Beta) iOS 8 iOS 7 Older iOS Versions iOS 6 iOS 5 and earlier error reading iPhone iPhone iPhone Tips, Help and Troubleshooting iPhone Accessories iPhone Launch Meetups iPad iPad iPad Tips, Help and Troubleshooting iPad Accessories iOS Apps iPod touch iOS Programming iPod Jailbreaks and iOS Hacks Alternatives to iOS and iOS Devices Apple Watch Apple Watch Apple Watch error reading block Accessories Apple Watch Apps Macs OS X OS X OS X El Capitan (10.11, Beta) OS X Yosemite (10.10) OS X Mavericks (10.9) Older OS X Versions OS X Mountain Lion (10.8) Mac OS X Lion (10.7) Desktops iMac Mac Pro Mac mini Notebooks MacBook MacBook Pro MacBook Air Mac Basics and Help Mac Programming Buying Tips and Advice PowerPC Macs Mac Accessories Windows, Linux & Others on the Mac Mac Apps and Mac App Store Mac OS X Server, Xserve, and Networking Apple TV Apple TV and Home Theater Apple TV Apps tvOS Programming Apple and Apple Services Apple, Inc and Tech Industry Apple Music, Apple Pay, iCloud, Apple Services Special Interests Design and Graphics Digital Audio Digital Photography Digital Video Apple Collectors Web Design and Development Distributed Computing Console Games Mac and PC Games UI Customization Mac Community Community Discussion Picture Gallery Current Events Site and Forum Feedback Politics, Religion, Social Issues Archive Wasteland Archives of Old Posts MacRumors New
Miniguide to fixing Volume-Filesystem errors Apr 29, '11 07:30:00AM • Contributed by: santa97298 There are many drive/filesystem errors that can occur on a Mac. Here are some common symptoms that are indicative of some of them: Not able to boot the system: You tried to boot. Apple logo appeared, and wheel spun for about 15-20 seconds, then machine turned off. This repeated every time you tried to boot the system. (REASON: The system does not find your HD and thus the OS to boot). Everything seems to work fine till your system hangs briefly and in an unpredictable way. You wait for a while, and the system magically comes back to normal. But after another while, the same thing re-occurs! (This cycle repeats in the current session). You can do these simple things to check for other possible causes: Run Activity Monitor to see that this is NOT due to temporarily high CPU and/or Memory usage. Check the system log using Console.app or running tail -f /var/log/system.log in Terminal. If your system is having some I/O error then it is sure that there is an HD failure issue. I don't claim to be an expert on this subject matter, just an (over)enthusiast Mac user. This guide is purely based on my personal experience and is bound to contain errors. So, USE IT AT YOUR OWN RISK! [crarko adds: Consider this hint to also serve as a reminder to check your backups...]Possible problems: Your HD Volume/FileSystem is corrupted Verification: Use Disk Utility and run "verify" to check it. 2. Your HD is dying. Verification: Use Disk Utility and see the SMART status of your HD, although this isn't always reliable. Before making any repair of the disk, make sure that you have the latest backups. Repair might let loose the volume/filesystem info all together and then there will be no other choice than to recover the data by some data rescue s/w like Data Rescue! If you don't have a current backup, you can try booting in Single-User mode by holding Command+S on startup. Then try doing a manual backup using commandline tools like cp or ditto. Note: The disk usually gets mounted in read-only. This could be good to get a manual backup by cp. But if everything else fails and you want to remove the important/personal data before sending it to