Error Occurred Reading Sector Data
Contents |
are UTC - 8 hours [ DST ] Powered by phpBB Forum Software © phpBB Group
Gaming Smartphones Tablets Windows 8 PSUs Android Your question Get the answer Tom's Hardware>Forum>Storage>Solution for "A disk read error occurred."> Closed Solution for "A disk read error occurred." Tags: Hard Drives Disk Read Error Storage Last response: 2 April 2011 22:05 in Storage Share pbarney 17 June 2009 22:13:43 This is one of the most frustrating error messages you can ever deal with. Sometimes the fix is simple, sometimes it's a complete pain. Having recently dealt with this again, I thought I'd post my https://www.terabyteunlimited.com/ucf/viewtopic.php?f=4&t=2214 thoughts in the hopes that it helps someone else out there. So you receive the dreaded "a disk read error occurred. Press Ctrl+Alt+Del to restart". Multiple restarts result in the same error message. If you put your drive into another computer, or connecting it as a slave on your own computer, it will typically work fine, and no data http://www.tomshardware.com/forum/250364-32-solution-disk-read-error-occurred is missing. Because this error is not usually associated with data loss, DO NOT RE-PARTITION THE DRIVE. Your data is likely safe and sound. Here's how we'll recover your data. Try each step below, in order, and see if your drive becomes accessible after each step. In my experience, you won't start seeing results until step 5 or so. 1. Run CHKDSK /R /P from the recovery console (it will typically find no error) 2. run FIXBOOT from recovery console (typically has no result) 3. run FIXMBR from recovery console (typically has no result) 4. Run the manufacturer's diagnostic utility, downloaded from their website (it will typically find no error) 5. Changing the drives from cable select to Master/Slave may fix it. 6. Replacing the data cable may fix it, but usually not. 7. Setting the BIOS to use defaults may fix it, but usually not. 8. Changing the BIOS drive settings from auto to user-specified, ensuring that LBA is selected may fix it. 9. Pulling the CMOS battery to let the BIOS lose it
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed http://askubuntu.com/questions/568360/error-failure-reading-sector-0x7c3c00-from-hd0 answers to any questions you might have Meta Discuss the http://www.diydatarecovery.nl/kb_badsectors_article.htm workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question error occurred and answer site for Ubuntu users and developers. 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 error: failure reading sector 0x7c3c00 from “hd0” up vote 0 down there are some vote favorite After using Boot Repair (recommended options) from an Ubuntu 14.10 Live System (USB) grub fails with the following error: error: failure reading sector 0x7c3c00 from "hd0". Entering rescue mode... Boot Repair exits with errors and here is the paste-url: http://paste.ubuntu.com/9659889/ I assume to find the relevant error in the last lines: cp: error reading ‘/mnt/boot-sav/sda7/boot/grub/grub.cfg’: Input/output error cp: failed to extend ‘/var/log/boot-sav/log/2015-01-02__16h22boot-repair08/sda7/grub.cfg_old’: Input/output error cp: error reading ‘/mnt/boot-sav/sda7/boot/grub/grub.cfg’: Input/output error cp: failed to extend ‘/var/log/boot-sav/log/2015-01-02__16h22boot-repair08/sda7/grub.cfg_new’: Input/output error cat: /mnt/boot-sav/sda7/boot/grub/grub.cfg: Input/output error An error occurred during the repair. Afterwards I tried to reinstall Ubuntu 14.10 newly from the live system. There are also different options like - delete and reinstall Ubuntu 14.10, etc. The installation didn't finish fully (after 10 hrs of no progress) so I broke it up @ Jan 3 15:51:00 ubuntu wpa_supplicant[3680]: wlan0: CTRL-EVENT-SCAN-STARTED /usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:18: Warning: Source ID 30729 was not found when attempting to remove it GLib.source_remove(self.timeout_i
surface scan. Repair bad sectors in-place (if there are few) or clone a disk (if there are many). Disk Read Errors Data can be lost due to unreadable or 'bad' sectors. If a file occupies a sector that returns an error on read, the file will become unusable. If there are too many bad sectors you may even be unable to access an entire volume. If the MBR or a sector that contains a partition table or boot sector can not be read, the entire disk or drive will become inaccessible. Bad sectors in a system area are a recipe for disaster. There are 2 ways of dealing with data loss due to read errors: 1. Clone the disk to a "known to be good" disk 2. Repair bad sectors in-place If you have reason to believe a disk's condition is rapidly deteriorating, always clone the disk! If a partition was lost because the partition table sector could not be read, apart from repairing the bad sector you will also need to rebuild the information that was in that sector. Cloning a bad or corrupt hard disk To be able to clone a disk with read errors or logical corruption you will need a data recovery utility that is designed to cope with this type of error. The tool of choice must gracefully handle read errors and get as much data from the source disk as possible. It should ignore any (corrupt) logical structures on the disk. A successful strategy to copy as much data of a disk as possible is doing multiple passes. In a first pass try to avoid disk hangups by not trying too hard and skip over errors. The cloning software keeps track of the areas it skipped and processes those areas during the next pass. DiskPatch clones disk to disk using a 2 pass clone. iRecover writes a raw image file that can later be processed, also using a 2 pass clone. Repairing corrupt or bad sectors If a sector's data is corrupt, it can often be reconstructed using ECC (error correction). If the sector is too unreliable to store data again, it will be reallocated; the sector is taken out of service and replaced by one from the 'spare pool'. The spare pool is a group or multiple groups of spare sectors available on any modern hard disk. You can detect unreliable sectors by scanning your disk's surface with DiskPatch. You can check the state of the disk b