Disk I/O error while update in fedora 38beta

I’ve had both of these things happen - a drive failed with a crashed head, but SMART still reported it OK as of the last test it ran. I’ve also had a case where the drive was perfectly good, but for some reason a SATA cable that had been in place for years suddenly quit reliably working, presumably from all the heat cycles. Hopefully, it’s the latter and not the former, since SATA cables are dirt cheap.

1 Like

Our IT group made a lowest bid bulk purchase of PC’s that turned out to have very low-quality ATA cable connectors. The spring tension of the female connections declined with age so that every time you moved a system you to check that the cable hadn’t become disconnected. A big advantage of newer tech is cables with fewer wires so it becomes less profitable to skimp on quality.


I will check it can you suggest how to get rid of that.
Readonly mode so after i have change those cables and stuff i can actually run that dnf update and see if everything okay now

Btw i find no error when i install flatpak apps and move large files from one to another partition.

If you’ve reinstalled and everything else seems fine, there’s not much more to do but see if it happens again. If running dnf update causes it twice, then I think we’ve found a very interesting problem!

Yes it happend again after running dnf update it updated successfully now i am running new kernel but i can’t run dnf update anymore as it is now reporting i/o error.

And just to make sure I’m not confused[1] — the problem happened again on a completely re-installed system?

I do think it’s likely that DNF is stressing your system in a way that other things aren’t for some reason. Might be worth looking at memory corruption, too. (Memtest86+ | The Open-Source Memory Testing Tool)

  1. and, I’m in an airport traveling home after a busy week of meetings,it’s very possible I am! ↩︎


Might be useful to watch temperatures during IO intensive things (dnf, gaming). Excessive heat can eventually damage cables and cause all sorts of other havoc. The first Linux program I ever wrote was to monitor temperature on an old ThinkPad that was burning my legs.

You can monitor is from command line with sensors or a GUI program like gkrellm.

If you notice high temperatures, you’ll want to clear out any dusty vent and if that doesn’t fix it and your CPU is removable, re-applying thermal paste can help.

1 Like

This is okay but can i solve that error now

That error that it have.
I am thinking if i delete this one will it solve this error.

SQLite is robust against program crashes and loss of power, but not software bugs or hardware problems, so erasing the file is likely treating a symptom, not the underlying disease. Make sure you have backups of user data. Open up the case to check for signs of damaged components (including corrosion around connections, which shows as green or brown on shiny conductors) and dust buildup. Failed disks and memory chips rarely have externally visible defects, so extensive testing is needed. Once you have done due diligence for hardware problems (and have backups), you can try cleaning up corrupt files, reinstalling, etc.

I once had a mission-critical PC that seemed to work fine but failed to transfer the end-product data to an NFS server. The Ethernet card vendor’s diagnostics gave it a clean bill of health, but when I examined the card there were visibly burned components. Replacing the card solved the problem. I have also encountered PC’s that’s with erratic glitches that had failed electrolytic capacitors. These are small cylinders usually wrapped in plastic with visible metal tops imprinted with a cross. When they fail the top bulges. Modern manufacturing is very reproducible, so many failure modes will be specific to a manufacturer and model. Internet searches can help identify common issues with your make and model.

1 Like

i have deleted this and then so a update with dnf update and i saw there was 340mb update available after update i have not seen anything like that i/o error now i am assuming that there mightbe a error like bug in dnf or software, that fixed with update but i need more testing to confirm that if that issue again comee back.

It might also be a problem with your RAM. I have seen a similar issue lately (disk I/O errors) which corrupted something in my BTRFS filesystem. It probably was caused by me overclocking my PC without properly checking the RAM stability under high load scenarios.