Read Error Code
Contents |
in the future... /usr/include/asm-generic/errno-base.h #ifndef _ASM_GENERIC_ERRNO_BASE_H #define _ASM_GENERIC_ERRNO_BASE_H #define EPERM 1 /* Operation not permitted */ #define ENOENT 2 /* No such file or directory */ #define ESRCH 3 /* No such process */ #define EINTR 4 /* Interrupted system
Errno
call */ #define EIO 5 /* I/O error */ #define ENXIO 6 /* No such device enoent or address */ #define E2BIG 7 /* Argument list too long */ #define ENOEXEC 8 /* Exec format error */ #define EBADF 9 /* Bad file number */ #define ECHILD 10 /* No child processes */ #define EAGAIN 11 /* Try again */ #define ENOMEM 12 /* Out of memory */ #define EACCES 13 /* Permission denied */ #define EFAULT 14 /* Bad address */ #define ENOTBLK 15 /* Block device required */ #define EBUSY 16 /* Device or resource busy */ #define EEXIST 17 /* File exists */ #define EXDEV 18 /* Cross-device link */ #define ENODEV 19 /* No such device */ #define ENOTDIR 20 /* Not a directory */ #define EISDIR 21 /* Is a directory */ #define EINVAL 22 /* Invalid argument */ #define ENFILE 23 /* File table overflow */ #define EMFILE 24 /* Too many open files */ #define ENOTTY 25 /* Not a typewriter */ #define ETXTBSY 26 /* Text file busy */ #define EFBIG 27 /* File too large */ #define ENOSPC 28 /* No space left on device */ #define ESPIPE 29 /* Illegal seek */ #define EROFS 30 /* Read-only file system */ #define EMLINK 31 /* Too many links */ #define EPIPE 32 /* Broken pipe */ #define EDOM 33 /* Math argument out of domain of func */ #define ERANGE 34 /* Math result not representable */ #endif /usr/include/asm-generic/errno.h #ifndef _ASM_GENERIC_ERRNO_H #define _ASM_GENERIC_ERRNO_H #include
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 http://www.tomshardware.com/forum/250364-32-solution-disk-read-error-occurred 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 thoughts in the hopes that it helps someone else out there. read error 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 is missing. Because this error is not usually associated with data loss, DO NOT RE-PARTITION THE DRIVE. read error code 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 settings may work. At this point, you may be feeling some frustration. :-) If all that fails, here's what will usually work: Ghost your data to a new drive, and use the ori