The last line of the output is:
cat: /etc/mime.types: Input/output error
Do you think I should reinstall Centos and start from scratch? Thanks.
Well, one thing that came to mind is perhaps a hardware problem. Does dmesg | tail directly after such an error say anything about hardware issues with hard drives or something?
res 41/40:00:90:04:79/00:00:03:00:00/40 Emask 0x409 (media error)
[513790.794149] ata1.00: status: { DRDY ERR }
[513790.794149] ata1.00: error: { UNC }
[513790.795191] ata1.00: configured for UDMA/133
[513790.795200] sd 0:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
[513790.795201] sd 0:0:0:0: [sda] tag#3 Sense Key : Medium Error [current]
[513790.795202] sd 0:0:0:0: [sda] tag#3 Add. Sense: Unrecovered read error - auto reallocate failed
[513790.795204] sd 0:0:0:0: [sda] tag#3 CDB: Read(16) 88 00 00 00 00 00 03 79 04 90 00 00 00 08 00 00
[513790.795205] blk_update_request: I/O error, dev sda, sector 58262672 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[513790.795218] ata1: EH complete
I’d make a backup of every import file and directory if I were you! Doesn’t look good. That drive is having hardware errors, I wouldn’t trust it. What does SMART say?
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
I don’t know if I would trust that 
In any case, I’m convinced the OSError you’re getting from Python and even cat is the result of a hardware error and I would suggest to back everything up from the current drive and change the drive for a new one.
Thanks @Osiris,
I have another PC with the same hardware configuration. I will install Centos 8 on that one and let you know if there are any news.
At the same time, I will use the build-in diagnostics function to test the one which Python is not working on.
Cheers!
Hi Osiris, You are right - the hard drive didn’t pass the diagnostics test. 
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.