There's lots of these in your logs -- they indicate failure communicating with the hard drive. This could be failing hard drive, bad cables, bad power supply, bad motherboard, etc.
I suggest making backups if you don't already have some -- do not overwrite old backups, you may need those. Then troubleshoot or replace etc.
Hello, note the following lines from your dmesg:
[ 3.791052] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 00:00:00/ 00:00:00: 00:00/e0 tag 0 dma 4096 in
res 51/04:08: 00:00:00/ 00:00:00: 00:00/e0 Emask 0x1 (device error) 00:00:00/ 00:00:00: 00:00/e0 tag 0 dma 4096 in
res 51/04:08: 00:00:00/ 00:00:00: 00:00/e0 Emask 0x1 (device error)
[ 3.791095] ata3.00: BMDMA stat 0x65
[ 3.791116] ata3.00: failed command: READ DMA
[ 3.791137] ata3.00: cmd c8/00:08:
[ 3.791202] ata3.00: status: { DRDY ERR }
[ 3.791222] ata3.00: error: { ABRT }
[ 3.793984] ata3.00: configured for UDMA/133
[ 3.794009] ata3: EH complete
[ 3.806999] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 3.807047] ata3.00: BMDMA stat 0x65
[ 3.807068] ata3.00: failed command: READ DMA
[ 3.807089] ata3.00: cmd c8/00:08:
[ 3.807154] ata3.00: status: { DRDY ERR }
[ 3.807174] ata3.00: error: { ABRT }
[ 3.809935] ata3.00: configured for UDMA/133
[ 3.809961] ata3: EH complete
There's lots of these in your logs -- they indicate failure communicating with the hard drive. This could be failing hard drive, bad cables, bad power supply, bad motherboard, etc.
I suggest making backups if you don't already have some -- do not overwrite old backups, you may need those. Then troubleshoot or replace etc.
Thanks