McKentin Posted January 18, 2018 Share Posted January 18, 2018 I did my search on google and did not found any clear awnser noir solution. Please help. Quote Jan 18 03:07:56 StorageBox kernel: ata11.00: disabling queued TRIM supportJan 18 03:07:56 StorageBox kernel: ata11.00: supports DRM functions and may not be fully accessibleJan 18 03:07:56 StorageBox kernel: ata11.00: disabling queued TRIM supportJan 18 03:07:56 StorageBox kernel: ata11.00: configured for UDMA/133Jan 18 03:07:56 StorageBox kernel: ata11: EH completeJan 18 05:29:55 StorageBox kernel: ata11.00: exception Emask 0x10 SAct 0xc000000 SErr 0x280100 action 0x6 frozenJan 18 05:29:55 StorageBox kernel: ata11.00: irq_stat 0x08000000, interface fatal errorJan 18 05:29:55 StorageBox kernel: ata11: SError: { UnrecovData 10B8B BadCRC }Jan 18 05:29:55 StorageBox kernel: ata11.00: failed command: READ FPDMA QUEUEDJan 18 05:29:55 StorageBox kernel: ata11.00: cmd 60/a0:d0:20:96:c4/06:00:07:00:00/40 tag 26 ncq dma 868352 inJan 18 05:29:55 StorageBox kernel: res 40/00:d0:20:96:c4/00:00:07:00:00/40 Emask 0x10 (ATA bus error)Jan 18 05:29:55 StorageBox kernel: ata11.00: status: { DRDY }Jan 18 05:29:55 StorageBox kernel: ata11.00: failed command: READ FPDMA QUEUEDJan 18 05:29:55 StorageBox kernel: ata11.00: cmd 60/60:d8:c0:9c:c4/09:00:07:00:00/40 tag 27 ncq dma 1228800 inJan 18 05:29:55 StorageBox kernel: res 40/00:d0:20:96:c4/00:00:07:00:00/40 Emask 0x10 (ATA bus error)Jan 18 05:29:55 StorageBox kernel: ata11.00: status: { DRDY }Jan 18 05:29:55 StorageBox kernel: ata11: hard resetting linkJan 18 05:29:56 StorageBox kernel: ata11: SATA link up 6.0 Gbps (SStatus 133 SControl 300)Jan 18 05:29:56 StorageBox kernel: ata11.00: supports DRM functions and may not be fully accessibleJan 18 05:29:56 StorageBox kernel: ata11.00: disabling queued TRIM supportJan 18 05:29:56 StorageBox kernel: ata11.00: supports DRM functions and may not be fully accessibleJan 18 05:29:56 StorageBox kernel: ata11.00: disabling queued TRIM supportJan 18 05:29:56 StorageBox kernel: ata11.00: configured for UDMA/133Jan 18 05:29:56 StorageBox kernel: ata11: EH completeJan 18 09:34:08 StorageBox kernel: pcieport 0000:00:02.0: AER: Corrected error received: id=0010Jan 18 09:34:08 StorageBox kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0010(Receiver ID)Jan 18 09:34:08 StorageBox kernel: pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000001/00002000Jan 18 09:34:08 StorageBox kernel: pcieport 0000:00:02.0: [ 0] Receiver Error (First)Jan 18 11:04:18 StorageBox kernel: pcieport 0000:00:02.0: AER: Corrected error received: id=0010Jan 18 11:04:18 StorageBox kernel: pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0010(Receiver ID)Jan 18 11:04:18 StorageBox kernel: pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000001/00002000Jan 18 11:04:18 StorageBox kernel: pcieport 0000:00:02.0: [ 0] Receiver Error (First) Quote Link to comment
JorgeB Posted January 18, 2018 Share Posted January 18, 2018 Please post your diagnostics: Tools -> Diagnostics Quote Link to comment
McKentin Posted January 18, 2018 Author Share Posted January 18, 2018 Sorry and thanks for the tip. Here it is storagebox-diagnostics-20180118-1235.zip Quote Link to comment
JorgeB Posted January 18, 2018 Share Posted January 18, 2018 Most likely a bad SATA cable on Cache2 SSD: 199 CRC_Error_Count -OSRCK 099 099 000 - 102 Once you replace it monitor this value, it won't reset but if all is well it will stop increasing. Quote Link to comment
McKentin Posted January 18, 2018 Author Share Posted January 18, 2018 Thanks i will order a few new cables today to test. Quote Link to comment
McKentin Posted January 18, 2018 Author Share Posted January 18, 2018 2 hours ago, johnnie.black said: Most likely a bad SATA cable on Cache2 SSD: 199 CRC_Error_Count -OSRCK 099 099 000 - 102 Once you replace it monitor this value, it won't reset but if all is well it will stop increasing. Both error have to do with sata cable ? Quote Link to comment
JorgeB Posted January 18, 2018 Share Posted January 18, 2018 The ATA errors yes, the PCIe errors no, those can sometimes be fixed by using the offending controller on a different slot, or with a bios update. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.