I have received this code on boot several times. It usually comes up after a major update. This time it didn’t go away after running a recovery mode with mint. I am usually able to get it to boot with generic boot. Everything works but now it when I boot up I have this error issue.
Linux Mint 22.1 Cinnamon, version 6,4,8. On a HP Pavilion, Intel Code i7
Any suggestions?
How old is the system, more specifically how old is the disk / sdd? You most likely a bad spot on your ssd / disk drive. The first thing I’d do would be to run badblocks against the disk. If the device is “/dev/sda” then run “sudo badblocks -vs /dev/sda”. Depending on the size of the device, and whether it’s an hdd or ssd, this process will take some time. I’m guessing that it will report a/some bad block(s).
Then I would back everything up, do a format of the disk / ssd, reinstall Mint and restore your data. Performing a format should map out bad block/sectors.
This is my OPINION, it may or may not work in your case.
I did a test run of badblocks on a 1TB ssd, it took between 49 and 50 minutes. I would expect an HDD to take 2-3 times as long, if not more.
root@mint:~# time badblocks -vs /dev/sda
Checking blocks 0 to 976762583
Checking for bad blocks (read-only test): done
Pass completed, 0 bad blocks found. (0/0/0 errors)
real 49m9.586s
user 0m6.521s
sys 5m18.785s
I had replaced the hard drive when I changed the Mint to the current version(22.1) this spring. It is a HP SSD 1gig hard drive. This issue developed last month and I was thinking it might be what you said. I just did the upgrade today to 22.2. I hope that it will maybe help in replacing this bad sector but not sure. The problem has not come back up so far. Its a wait and see at the moment.
Thanks for the info, I will see if I need to run that process. I hope not, redo on hard drives don’t always go you way. That’s why I chose replace it in the first place!
So you replaced the possibly faulty drive, or upgraded to mint 22.2 on the drive which may be faulty? Installing or upgrading an operating system may or may not map out bad blocks or sectors. I’d run the badblocks command on your ssd, just to have the data in hand.
When you did the 22.2 install/upgrade, did you by chance format the ssd, or install on top of what was there?
Is there a process that can eliminate bad blocks without erasing the disk and having to run endless backups?? I always thought there was a process that you can avoid use of those bad areas of a hard drive. Its a ssd hard drive. not sure of this but I vaguely remember at one time there was a way of doing this without having to redo the whole disk.
I’ve successfully used this product on a few different drives:
What SpinRite does
New Drive testing, Data Recovery & SSD Performance Recovery
The developer has an interesting history with software.
Ok its a software that you suggest. I was thinking there was fsdisk command sequence that I could follow that would tell the os not to use that damaged sector.
Yes, you
This way, SpinRite operates completely separate from your computer’s drive, so is able to access every sector on that computer’s drive.
I decided that the software’s effectiveness, at a reasonable price, was way more efficient/accurate than my trying to figure out the drive’s problems manually. PLUS, it performs remedial actions (e.g. trim) that I could never do myself.
Ok, this lovely little issue has been flogging me for weeks and I think I might have it solved. Ran the fsck at start up a couple times as the above error kept occurring. So then a error came from the after recovery mode reboot. That was: R_ERR response for host-to-device non data FIS, non-CRC.
Did a little research and loaded badlocks and ran it. It found nothing, so my SSD drive has S.M.A.R.T. built into it therefore I could run smartmontools using the sudo smartctl -H /dev/sda command. It showed that this error had reoccurred every time I had the issue.
As far as I can tell, this might be the wire connection to hard drive issue. Going to take the computer apart and see if there is an obvious issue. I do have a parts computer that I might take its wire and see if that remedies the issue.