IO error

Meet8939 · March 5, 2019

I have installed linux (Ubuntu 18.04.2) on my PC. I have been having error where I have to run command 'fsck' in it initframs to make it boot, but then it becomes laggy. While I was researching about it I found a thread on net which encouraged to run command 'systemctl' which I did and then it showed me that there is error in some sector of my HDD ( basically sector 2055, and my drive starts at 2048). I was now not even able to reinstall ubuntu, so I thought that I should exclude that portion of storage and install it after almost 1GB if space and it installed fine and was running buttery smooth, but now it has started again. When I ran the 'systemctl' command it also showed the command that is jammed in that sector, it was 'Read DMA' and something related to it afterwards.

Some guy on the thread I mentioned suggested the guy to input zeros in the sector, i tried it but was unsuccessful. Can anyone help resolve it!

unijab · March 5, 2019

did you clone a HDD to an SSD?

Falconevo · March 6, 2019

6 hours ago, Meet8939 said:

I have installed linux (Ubuntu 18.04.2) on my PC. I have been having error where I have to run command 'fsck' in it initframs to make it boot, but then it becomes laggy. While I was researching about it I found a thread on net which encouraged to run command 'systemctl' which I did and then it showed me that there is error in some sector of my HDD ( basically sector 2055, and my drive starts at 2048). I was now not even able to reinstall ubuntu, so I thought that I should exclude that portion of storage and install it after almost 1GB if space and it installed fine and was running buttery smooth, but now it has started again. When I ran the 'systemctl' command it also showed the command that is jammed in that sector, it was 'Read DMA' and something related to it afterwards.

Some guy on the thread I mentioned suggested the guy to input zeros in the sector, i tried it but was unsuccessful. Can anyone help resolve it!

Start with checking the health of the disks, Linux engineers always go around fucking with their OS to fix a problem with the underlying hardware that they are usually too ignorant to check.

Start with this first, run HDSentinel and check to see what the status of the disk health is. This is SMART data for people who can't interpret it themselves.

https://www.hdsentinel.com/hard_disk_sentinel_linux.php

If the health of the drive comes back perfect, then you start looking at the OS. To me, this sounds like a hardware issue with the drive.