Windows Diary

How Do I Fix The Debian Ls Reading Directory? I / O Error

Posted on by Brian Magallanes

 

Here are some simple methods that can help solve the problem of reading the Debian directory. I / O error.

Approved: Fortect

  • 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
    • Speed up your computer's performance now with this simple download.

     

     

    Only

    I wanted to share my experience: With FreeBSD 10.3 I have a USB hard drive with

    . established

      $ sudo ntfs-3g / dev / da0s1 / media

    I ran an absolute mkdir on my hard drive to create a directory and move some game files there from nusing the mv command. Finally, I often have the following command:

    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

    •   $ sudo sync

    debian ls reading directory . input/output error

    Then I used to mount the hard drive on a Linux machine with a shared kernel 4.4.0-78. Now, when I usually list the contents of the hard drive, the FreeBSD-generated site directory Jeff is displayed with the name: 

      $ ls -lhrtcils: Unable to start browsing 'Jeff': I / O errortotal 20K  ? D ????????? ? ! ? ? ? Jeff

    Also, when I try to delete the Jeff directory, I get the following error messages:

    debian ls reading directory . input/output error

      $ sudo rm -f -R Jeffrm: Failed to delete 'Jeff': I / O error

    I wouldn’t get rid of the Jeff directory on a Linux machine, so I used FreeBSD machines and remounted the hard drive to FreeBSD. But the ls , cd to rm commands in FreeBSD cause the same I / O error. There appears to be a credible bug in the FreeBSD package ntfs-3g .

    UPDATE

    I have moved all my data from my external hard drive to my Linux computer, of course the corrupted file Jeff could not be moved due to an E / S error. Then I reformatted the visible hard drive by zeroing the volume and checking the bad sector, for example: 

      $ sudo mkfs.ntfs / dev / sdb1

    debian ls reading directory . input/output error

    And then all of your backup data was moved to the outer volume. This way I lost the corrupted file referenced by Jeff , but there were no I / O errors on my external hard drive.

    The computer was working fine until this morning I learned that an I / O error occurred on the hard drive (two 4TB hard drives in RAID0 with mdadm ). 

      ls: display directory '.' : guilt

    And another dmseg related I / O check shows that accessing my MD127 CD is causing some warnings and errors: 

      [5789751.027967] EXT4-fs notification (device htree_dirblock_to_tree: 994: md127): inode # 184288528: lblock row: comm rg: error -5 while reading index block[5789751.027970] Ext4-fs warning (device md127): htree_dirblock_to_tree: 994: inode # 184288528: lblock 2: comm rg: error -5 Find directory block[5789751.027973] EXT4-fs (md127 device warning): htree_dirblock_to_tree: 994: Inode # 161822641: lblock 7: comm cp: Error -5 while reading directory block[5789751.027975]EXT4-fs warning (device htree_dirblock_to_tree: 994: md127): Inode # 184288528: lblock 2: comm rg: Error -5 while reading directory block[5789751.027976] EXT4-fs warning (device md127): htree_dirblock_to_tree: 994: Inode # 184288528: lblock 2: comm rg: Error -5 while reading directory site block[5789751.027979] EXT4-fs warning (device md127): htree_dirblock_to_tree: 994: Inode # 184288528: lblock 2: comm rg: Error suggestions when reading directory block[5789751.027982] EXT4-fs warning (device md127): htree_dirblock_to_tree: 994: Inode # 184288528: lblock 2: comm rg: error -5 read block[5789751 directory.027986] EXT4-fs warning (device md127): htree_dirblock_to_tree: 994: inode # 184288528: lblock two: comm rg: error Reading -5 website directory block[5789751.027987] EXT4-fs warning (device md127): htree_dirblock_to_tree: 994: Inode # 161822641: lblock 7: Communication error cp: -5 Display directory block[5789751.027989] EXT4-fs warning (device md127): htree_dirblock_to_tree: 994: Inode # 184288528: lblock 2: comm rg: -paar Error reading directory block

    After doing some research, I found several articles that talked about using fsck to fix this idea (I'm using Ubuntu 18.04).

    • Ext4 file system corrupted overnight
    • Ubuntu error EXT4-fs around 18.04.

    I also found a person who had a What a big problem with the RAID0 hard drive (but a long time ago, since it is actually kernel 4.0.0).

    My hard drive looks fine because using smartctl reads PASSED . And inode seems to work as there is so much left (only 7% used in inodes).

    What could be the cause of this spontaneous failure? I want to be sure because I want to know how to prevent this or be prepared for the next event.

    Right now I'm actually copying the undamaged files, but I can get by without restoring fsck .

     

     

    Speed up your computer's performance now with this simple download.

    In this situation, the first suggestion is to check / var / log / messages for disk-related warnings (you can see the key warnings). If you are having problems with your hard drive, try using Disk Utility to confirm. One possibility is to use smart tools. You need to enable smartool option to fix bad pads.

    What is an I / O device failure? I / O drive errors are quite common.Reboot your computer.Check your cables and connections.Try another useful USB port.Run CHKDSK and SFC.Update the device driver.Change the drive letter.Use Speccy to check the status of the disk.

    An I / O error is a generalized error message that occurs repeatedly in various situations. This indicates a problem with the file system, in particular, the operating system cannotaccess a specific portion of a specific disk (or virtual disk).

     

     

     

     

    Related Posts: