Approved: Fortect
If you see usr bin df I / O error on your computer, check out these troubleshooting tips. g.I / O errors during command execution for two main reasons. Either it could be bad blocks on your hard drive, or someone has hacked your tools. In this situation, the first suggestion is to check / var / log / messages for any relevant warnings on disk (important necessary warnings may appear).
An I / O error is a global error message that constantly occurs in various situations. This is often a problem at the file system level, especially the operating system cannot access any part of the hard disk (or virtual disk).
g.
I noticed that my server cannot execute the command and it says “Input capacity error”
How do I fix input output error in Linux?
boot, which creates an Ubuntu Live DVD / USB in Try Ubuntu mode.Open a terminal window by pressing Ctrl + Alt + T.Enter sudo fdisk -l.Define this special device nameproperty / dev / sdXX for its “Linux filesystem”Enter sudo fsck -f / dev / sdXX and replace sdXX with the number you found earlier.If there are specific errors, reissue the fsck command.
Error code EIO
(I / O error) when running a command can occur if your filesystem is badly damaged; or worse if you have a bad memory.
Cross your fingers; In any case, please note that you should NOT try to force the server at this point unless you need to. 1
Challenge
There is a good way to distinguish between two main reasons: reading at the block level to scan your system and looking for kernel messages.
- Boot the system using the GNU / Linux System Recovery Boot Disk.
- Change the system to the old text console (Ctrl + Alt + F1); (Do not click on the graphical terminal to do this.
- Log in as root.
- Run
dmesg -E
to enable live message notificationkernels on the console. - Run
dmesg -n debug
to see a low-level kernel message. - Run
blkid
to find out which hard drive contains the partitioning system. (Note that it lists theblkid
sections; cross out the end of the section path, you will also get a hard drive) - Run
time -delaware dd if = / dev / sda of = / dev / null bs = 4M
to perform a read test on the entire hard drive (please enter this excellent text carefully). Your system drive may not be/ dev / sda
, please replace it accordingly. - Look at the screen (it takes a long time) …
Results
-
At best,
dd
completed successfully and without incident, most likely due to a file system problem.- If you have a proven track record of checking the filesystem from a boot disk, do so now (recommended).
- If a person would prefer to let the system sort the application (remove the hard drive from the trunk on restart) and boot your system normally, but with
fsck.mode = force
inat the end, attach the linked kernel command line. (See details of this request) - Discussion of the results of the file system check, however, may raise another question.
Approved: Fortect
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
- 1. Download Fortect and install it on your computer
- 2. Launch the program and click "Scan"
- 3. Click "Repair" to fix any issues that are found
However, in the worst case, you will see kernel messages like this on the screen:
How do you fix input output error?
What is an I / O device failure? I / O device errors can be quite common.RebootStart your computer.Check your cables and connections.Try a real alternate USB port.Run CHKDSK on this SFC.Update the device driver.Change the drive letter.Use Speccy to check the status of the disk.
ata2.00: misc 0x0 emask SAct 0x0 SErr 0x0 activity 0x0ata2.00: irq_stat 0x40000001ata2.00: command failed: READ DMA EXTata2.00: cmd 25/00: 08: 78: 15: c5 / 00: 00: 6c: 00: 00 / e0 day 0 dma 4096 in res 51/40: 00: 78: 15: c5 / 00: 00: 6c: 00: 00 / e0 Emask 0x9 (media error)ata2.State: 00: DRY ERRORata2.00: Error: UNCata2.00: configured for UDMA / 100sd 1: 0: 0: 0: [sda] Discovery code not processedSD 1: 0: 0: 0: [SDA]Result: hostbyte = DID_OK driverbyte = DRIVER_SENSESD 1: 0: 0: 0: [SDA]Semantic key: mean error [current] [description]Reason for data descriptor with semantic descriptors (in hexadecimal format): 48 03 11 04 00 00 50 0c 0a 00 80 00 00 00 double zero 00 6c c5 15 77SD 1: 0: 0: 0: [SDA]Add to. Meaning: misunderstanding not resolved - automatic reassignment failedsd 1: 0: 0: 0: [sda] CDB:Read (10): 28 00 6c c5 22 78 00 00 08 00end_request: I / O error, dev sda, 1824855416SDA device buffer sector I / O error, logic block 228106927ata2: EH completed
Find the most importantOther parts:
-
DRDY
,ERR
and optionallyUNC
in curly braces -
support error
status -
Unresolved read error
print message
How do I fix input output error in Linux?
boot from DVD / USB Ubuntu Live in Try Ubuntu mode.Open an airport terminal window by pressing Ctrl + Alt + T.Enter sudo fdisk -l.Determine the device name / dev / sdXX for your company’s Linux filesystem.Enter sudo fsck -f / dev / sdXX to replace sdXX with the previously found owner number.Try running fsck again, you may have encountered errors.
If you look and find it in the news (at least once), it will show that you usually face a physical hard drive failure.
If yes, don’t leave
dd
, press Ctrl + C to stop NOW; Turn off your system and system, and bring your hard drive – the data recovery storage you trust.-
If someone hasn’t found the worst messages mentioned above and / or has encountered these types of kernel messages repeatedly:
ata2: Exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozenata2: irq_stat 0x00000040, report status changedata2: SError: CommWake DevExchata2: link for hard resetata2: link falls back to slow response, wait (done = 0)
How do you fix input output error?
What is an I / O device failure? I / O device memory is fairly common.Reboot your computer.Check your cables and connections.Try a different USB port.Run CHKDSK and SFC.Update the device driver.Change the drive letter.Use Speccy to check the status of the disk.
Key elements:
-
Hard reset link
-
Link is too slow to respond
Then your business is more likely to face an obstacle to underSATA disconnections (for example, bad wiring): Press Ctrl + C to shutdown, in the vicinity of your system, repair the cables and reconnect the hard drive and try again.
-
Additional Notes
And I ran a Smartctl test to make sure the problem disk is being used. And he endured a mistake in his judgment.
Make sure some hard drives recognize a clear deception in their S.M.A.R.T status (I’m looking inside you Toshiba); my previous empty laptop hard drive hung on read errors and always said “no good” in the status registers.
If your forum is important, you should reconsider using a RAID-based configuration.
-
What is an input output error?
I / O error is a general idea of an error that constantly occurs in different situations. This indicates a problem with the file system, in particular, the operating system cannot access a certain part of the file disk (or virtual disk).
1 Short story: my roommate didn’t respond to this warning and the filesystem still runs a check on his desktop. I didn’t have to wait for me to check it until it finally boots up. When I had the opportunity to test this, hard drive corruption was already common (500 GB hard drive barely (I read Kbps at snail speed and so there wasn’t a significant constant readable area even after a few days).
On another little finger, in another case with the same condition, the owner of the car heeded my warning and also left it on until I could test it. Of course it was a hard drive failure. After half a definite GNU DDRescue session and another hard drive, he got some good headlines stating that his system and hard drive were restored to 100% locked, meaning all files were intact and ready to be reused without any changes.
How do I fix input output error on external hard drive Linux?
Before fixing the problematic disk I / O error, it is recommended to modify the computer and access the physical hard disk again. Sometimes, restarting your computer can help fix some hard drive errors. If the error persists when you want to transfer and write files to your hard drive, don’t worry.