Harddrive случайным образом переходит в режим только для чтения, как мне его исправить?
У меня довольно новая машина с Ubuntu 16.04, где / находится на SSD, а / home - на жестком диске (Seagate Archive 8TB). Обычно после нескольких часов работы жесткий диск переходит в режим только для чтения со следующим dmesg:
[27339.722410] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[27339.722420] ata2.00: failed command: FLUSH CACHE EXT
[27339.722430] ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 17
res 40/00:ff:81:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
[27339.722436] ata2.00: status: { DRDY }
[27339.722442] ata2: hard resetting link
[27345.091967] ata2: link is slow to respond, please be patient (ready=0)
[27349.758981] ata2: COMRESET failed (errno=-16)
[27349.758992] ata2: hard resetting link
[27355.087317] ata2: link is slow to respond, please be patient (ready=0)
[27359.767613] ata2: COMRESET failed (errno=-16)
[27359.767625] ata2: hard resetting link
[27365.107960] ata2: link is slow to respond, please be patient (ready=0)
[27394.817890] ata2: COMRESET failed (errno=-16)
[27394.817901] ata2: limiting SATA link speed to 3.0 Gbps
[27394.817905] ata2: hard resetting link
[27399.874212] ata2: COMRESET failed (errno=-16)
[27399.874223] ata2: reset failed, giving up
[27399.874228] ata2.00: disabled
[27399.874244] ata2: EH complete
[27399.874274] sd 1:0:0:0: [sdb] tag#18 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27399.874281] sd 1:0:0:0: [sdb] tag#18 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00
[27399.874290] blk_update_request: I/O error, dev sdb, sector 11769753208
[27399.874340] Aborting journal on device sdb2-8.
[27399.874513] sd 1:0:0:0: [sdb] tag#19 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27399.874518] sd 1:0:0:0: [sdb] tag#26 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27399.874520] sd 1:0:0:0: [sdb] tag#19 CDB: Write(16) 8a 00 00 00 00 02 18 08 b3 00 00 00 00 28 00 00
[27399.874525] blk_update_request: I/O error, dev sdb, sector 8993157888
[27399.874532] EXT4-fs warning (device sdb2): ext4_end_bio:330: I/O error -5 writing to inode 33557225 (offset 0 size 20480 starting block 1124144741)
[27399.874537] Buffer I/O error on device sdb2, logical block 134271072
[27399.874540] sd 1:0:0:0: [sdb] tag#26 CDB: Write(16) 8a 00 00 00 00 02 bd 86 30 00 00 00 00 08 00 00
[27399.874545] blk_update_request: I/O error, dev sdb, sector 11769622528
[27399.874550] blk_update_request: I/O error, dev sdb, sector 11769622528
[27399.874554] Buffer I/O error on device sdb2, logical block 134271073
[27399.874556] Buffer I/O error on device sdb2, logical block 134271074
[27399.874559] Buffer I/O error on device sdb2, logical block 134271075
[27399.874561] Buffer I/O error on device sdb2, logical block 134271076
[27399.874567] Buffer I/O error on dev sdb2, logical block 481329152, lost sync page write
[27399.874591] sd 1:0:0:0: [sdb] tag#28 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27399.874593] sd 1:0:0:0: [sdb] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27399.874597] sd 1:0:0:0: [sdb] tag#20 CDB: Write(16) 8a 00 00 00 00 02 19 83 47 20 00 00 05 40 00 00
[27399.874601] blk_update_request: I/O error, dev sdb, sector 9017968416
[27399.874606] sd 1:0:0:0: [sdb] tag#28 CDB: Write(16) 8a 00 00 00 00 02 19 84 66 70 00 00 04 60 00 00
[27399.874610] blk_update_request: I/O error, dev sdb, sector 9018041968
[27399.874614] sd 1:0:0:0: [sdb] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27399.874617] JBD2: Error -5 detected when updating journal superblock for sdb2-8.
[27399.874623] EXT4-fs warning (device sdb2): ext4_end_bio:330: I/O error -5 writing to inode 33557798 (offset 0 size 2310144 starting block 1127255386)
[27399.874626] Buffer I/O error on device sdb2, logical block 137381670
[27399.874631] Buffer I/O error on device sdb2, logical block 137381671
[27399.874635] Buffer I/O error on device sdb2, logical block 137381672
[27399.874638] sd 1:0:0:0: [sdb] tag#21 CDB: Write(16) 8a 00 00 00 00 02 19 83 4c 60 00 00 02 c0 00 00
[27399.874641] blk_update_request: I/O error, dev sdb, sector 9017969760
[27399.874647] EXT4-fs warning (device sdb2): ext4_end_bio:330: I/O error -5 writing to inode 33557642 (offset 0 size 2310144 starting block 1127246308)
[27399.874648] Buffer I/O error on device sdb2, logical block 137381673
[27399.874651] Buffer I/O error on device sdb2, logical block 137381674
[27399.874712] sd 1:0:0:0: [sdb] tag#30 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27399.874717] sd 1:0:0:0: [sdb] tag#30 CDB: Write(16) 8a 00 00 00 00 02 19 85 11 c0 00 00 02 b8 00 00
[27399.874721] blk_update_request: I/O error, dev sdb, sector 9018085824
[27399.874734] sd 1:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27399.874738] sd 1:0:0:0: [sdb] tag#1 CDB: Write(16) 8a 00 00 00 00 02 19 85 19 b8 00 00 04 60 00 00
[27399.874741] blk_update_request: I/O error, dev sdb, sector 9018087864
[27399.874748] EXT4-fs warning (device sdb2): ext4_end_bio:330: I/O error -5 writing to inode 33557787 (offset 0 size 2310144 starting block 1127261123)
[27399.874812] sd 1:0:0:0: [sdb] tag#3 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27399.874816] sd 1:0:0:0: [sdb] tag#3 CDB: Write(16) 8a 00 00 00 00 02 29 f6 a2 78 00 00 00 40 00 00
[27399.874819] blk_update_request: I/O error, dev sdb, sector 9293963896
[27399.874823] EXT4-fs warning (device sdb2): ext4_end_bio:330: I/O error -5 writing to inode 33556520 (offset 0 size 0 starting block 1161745488)
[27399.874831] EXT4-fs warning (device sdb2): ext4_end_bio:330: I/O error -5 writing to inode 33556520 (offset 0 size 0 starting block 1161745492)
[27399.874839] EXT4-fs warning (device sdb2): ext4_end_bio:330: I/O error -5 writing to inode 33556520 (offset 0 size 0 starting block 1161745493)
[27399.874844] EXT4-fs warning (device sdb2): ext4_end_bio:330: I/O error -5 writing to inode 33556520 (offset 0 size 0 starting block 1161745495)
[27399.874855] sd 1:0:0:0: [sdb] tag#5 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27399.874860] sd 1:0:0:0: [sdb] tag#5 CDB: Write(16) 8a 00 00 00 00 02 2c 54 3b 80 00 00 00 88 00 00
[27399.874864] EXT4-fs warning (device sdb2): ext4_end_bio:330: I/O error -5 writing to inode 33556515 (offset 0 size 0 starting block 1166706553)
[27399.874878] EXT4-fs warning (device sdb2): ext4_end_bio:330: I/O error -5 writing to inode 33556515 (offset 0 size 0 starting block 1166706561)
[27399.876306] Buffer I/O error on dev sdb2, logical block 0, lost sync page write
[27399.876327] EXT4-fs error (device sdb2): ext4_journal_check_start:56: Detected aborted journal
[27399.876335] EXT4-fs (sdb2): Remounting filesystem read-only
[27399.876339] EXT4-fs (sdb2): previous I/O error to superblock detected
[27399.876354] Buffer I/O error on dev sdb2, logical block 0, lost sync page write
[27399.876456] JBD2: Detected IO errors while flushing file data on sdb2-8
[27629.975965] scsi_io_completion: 23 callbacks suppressed
[27629.975969] sd 1:0:0:0: [sdb] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[27629.975970] sd 1:0:0:0: [sdb] tag#20 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[28230.011238] sd 1:0:0:0: [sdb] tag#22 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[28230.011241] sd 1:0:0:0: [sdb] tag#22 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[28830.051754] sd 1:0:0:0: [sdb] tag#24 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[28830.051774] sd 1:0:0:0: [sdb] tag#24 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[29430.089893] sd 1:0:0:0: [sdb] tag#26 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[29430.089896] sd 1:0:0:0: [sdb] tag#26 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
[29462.293106] sd 1:0:0:0: [sdb] tag#28 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[29462.293108] sd 1:0:0:0: [sdb] tag#28 CDB: Read(16) 88 00 00 00 00 02 31 2a 85 68 00 00 00 18 00 00
[29462.293109] blk_update_request: 26 callbacks suppressed
[29462.293110] blk_update_request: I/O error, dev sdb, sector 9414804840
[29462.293145] sd 1:0:0:0: [sdb] tag#29 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[29462.293147] sd 1:0:0:0: [sdb] tag#29 CDB: Read(16) 88 00 00 00 00 02 31 2a 85 68 00 00 00 08 00 00
[29462.293148] blk_update_request: I/O error, dev sdb, sector 9414804840
Я уже пробовал следующее (предложения от поиска google):
«smartctl -l error / dev / sdb» и «smartctl -H / dev / sdb» не сообщают об ошибках, и тот же диск с той же материнской платой не создает проблем для Windows 10, поэтому я сомневаюсь, что это проблема с оборудованием. / sys / block / sdb / device / queue_depth установлено в 1 (было 31). Я установил pcie_aspm = off. Установлено ядро linux-generic-hwe-16.04. «fsck / dev / sdb2» (при запуске с живого диска) не обнаруживает ошибок.Я также нашел этот пост в блоге кого-то с аналогичной проблемой: http://dvblog.soabit.com/seagate-8tb-st8000as0002-vs-linux-aka-kernel-issues-you-might- face /
... Однако предлагаемый курс действий состоит в том, чтобы скомпилировать мое собственное ядро, что я не знаю, как это сделать. Есть ли еще более простой способ исправить это, что я упустил до сих пор?
0
задан Nico Schaumberger
6 October 2017 в 18:07
поделиться