Why does the hard drive go into Read-Only mode after a while?

Question

Hard disks

Hello to all!
There was a strange problem with the hdd.
Namely:
After some time (after about 30 minutes), the hard disk becomes Read-Only, to fix this, you have to restart the computer and run fsck -y, and after that it is Read-Write again, but not for long ...
Mb someone did you face this problem?

Answer 1

First things first - backup.
> I/O error, dev sdb, sector 3905173186 Is the
sector always the same?
If the sectors are different - change the interface cable. If the same - unreadable block. But the disk itself does not remap it.
Try to overwrite this block (MHDD, victoria, at least dd), it is likely that the disk will remap it.
And do a test of the entire surface, it may be better to replace the disk.

Answer 2

Jun  2 10:55:16 fibro-desktop kernel: [ 2045.454910] ata3: lost interrupt (Status 0x50)
Jun  2 10:55:16 fibro-desktop kernel: [ 2045.454926] ata3: exception Emask 0x50 SAct 0x0 SErr 0x40d0802 action 0xf
Jun  2 10:55:16 fibro-desktop kernel: [ 2045.454930] ata3: SError: { RecovComm HostInt PHYRdyChg CommWake 10B8B DevExch }
Jun  2 10:55:16 fibro-desktop kernel: [ 2045.454937] ata3: hard resetting link
Jun  2 10:55:17 fibro-desktop kernel: [ 2046.363650] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jun  2 10:55:17 fibro-desktop kernel: [ 2046.403886] ata3.00: configured for UDMA/133
Jun  2 10:55:17 fibro-desktop kernel: [ 2046.403899] ata3: EH complete
Jun  2 10:55:17 fibro-desktop kernel: [ 2046.504492] end_request: I/O error, dev sdb, sector 3905173186
Jun  2 10:55:17 fibro-desktop kernel: [ 2046.504568] Aborting journal on device sdb1-8.
Jun  2 10:55:17 fibro-desktop kernel: [ 2046.504881] EXT4-fs (sdb1): delayed block allocation failed for inode 160956702 at logical offset 0 with max blocks 2048 with error -30
Jun  2 10:55:17 fibro-desktop kernel: [ 2046.504885] This should not happen!!  Data will be lost
Jun  2 10:55:17 fibro-desktop kernel: [ 2046.504977] EXT4-fs error (device sdb1) in ext4_reserve_inode_write: Journal has aborted
Jun  2 10:55:17 fibro-desktop kernel: [ 2046.505728] EXT4-fs error (device sdb1) in ext4_da_writepages: Journal has aborted
Jun  2 10:55:17 fibro-desktop kernel: [ 2046.522587] EXT4-fs error (device sdb1): ext4_journal_start_sb: Detected aborted journal
Jun  2 10:55:17 fibro-desktop kernel: [ 2046.522591] EXT4-fs (sdb1): Remounting filesystem read-only
Jun  2 10:55:17 fibro-desktop kernel: [ 2046.581630] EXT4-fs (sdb1): ext4_da_writepages: jbd2_start: 7355 pages, ino 160956702; err -30

Here is the error log of what is happening at this moment.

Answer 3

this always happens when a drive dies or a bad sata cable.