[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: sata_nv OK in f10?



> I found this gibberish in /var/log/message (no clue what it
> might mean :-)
> 
> Dec  9 16:55:21 zooty kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x3980000 action 0x6 frozen
> Dec  9 16:55:21 zooty kernel: ata1: SError: { 10B8B Dispar LinkSeq TrStaTrns UnrecFIS }

That looks like you for some reason got bits scrambled on the SATA cable.
That can happen very occasionally with SATA and isn't fatal (it's
checksummed and caught as part of the design)

> Dec  9 16:55:21 zooty kernel: ata1.00: cmd 35/00:40:95:d3:42/00:02:1f:00:00/e0 tag 0 dma 294912 out
> Dec  9 16:55:21 zooty kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> Dec  9 16:55:21 zooty kernel: ata1.00: status: { DRDY }
> Dec  9 16:55:21 zooty kernel: ata1: hard resetting link
> Dec  9 16:55:22 zooty kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> Dec  9 16:55:22 zooty kernel: ata1.00: configured for UDMA/133
> Dec  9 16:55:22 zooty kernel: ata1: EH complete

And we then come back. Generally speaking smartutils will tell you if you
have a drive problem and can ask the drive about that. If you only get
these very very rarely I wouldn't be too worried. If they keep popping up
it may be worth further investigation, cable checking etc.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]