Page 1 of 1

disk failure - cable problem?

Posted: Mon Feb 10, 2020 12:16 am
by parsifal9
Hi Forum,
I had a disk failure on a fitpc3. The machine would not boot at all and I got errors like
"ata1.00 device reported invalid CHS sector 0"
when I got into rescue mode.

I replaced the disk and installed an operating system. However, I am still getting error messages. I have looked around on some message
boards and they suggest this sort of thing might be the SATA cable. The fix is to re-seat it at both ends or preferably replace it. However, on a fitpc3, I don't see how to do that. Here are some of the error messages I have been getting. What do you think? Can I fix this?

from /var/log/syslog
ata1.00: exception Emask 0x10 SAct 0x30 SErr 0x0 action 0x6 frozen
ata1.00: irq_stat 0x08000000, interface fatal error
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/10:20:00:e0:b7/00:00:03:00:00/40 tag 4 ncq dma 8192 out
res 40/00:20:00:e0:b7/00:00:03:00:00/40 Emask 0x10 (ATA bus error)
ata1.00: status: { DRDY }

and in dmesg (edited a lot to cut it down)

3.360481] ata1: SATA max UDMA/133 abar m1024@0xc124c000 port 0xc124c100 irq 19
[ 3.832144] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3.832495] ata1.00: supports DRM functions and may not be fully accessible
[ 3.833447] ata1.00: ATA-11: Samsung SSD 860 EVO 250GB, RVT01B6Q, max UDMA/133
[ 3.833451] ata1.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
[ 3.835861] ata1.00: supports DRM functions and may not be fully accessible
[ 3.838740] ata1.00: configured for UDMA/133
[ 3.842518] ata1.00: Enabling discard_zeroes_data
[ 7.184922] ata1: log page 10h reported inactive tag 26
[ 7.184939] ata1.00: exception Emask 0x1 SAct 0x38000000 SErr 0x0 action 0x0
[ 7.184944] ata1.00: irq_stat 0x40000008
[ 7.184964] ata1.00: cmd 60/08:d8:f8:11:80/00:00:11:00:00/40 tag 27 ncq dma 4096 in
[ 7.184970] ata1.00: status: { DRDY }
[ 7.184975] ata1.00: failed command: READ FPDMA QUEUED
[ 7.184986] ata1.00: cmd 60/08:e0:00:12:80/00:00:11:00:00/40 tag 28 ncq dma 4096 in
[ 7.191730] ata1: EH complete
[ 7.191890] ata1.00: Enabling discard_zeroes_data
[ 14.152845] ata1.00: exception Emask 0x0 SAct 0x40000001 SErr 0x0 action 0x6
[ 14.152917] ata1.00: status: { DRDY ERR }
[ 14.152925] ata1.00: error: { ICRC ABRT }
[ 14.152942] ata1: hard resetting link

Re: disk failure - cable problem?

Posted: Mon Feb 10, 2020 2:49 pm
by tamir
There's a small PCB connected to the board that provides the SATA socket
you may see that the HDD connects to when you slide the service door. if there's anything to check beside the HDD I would guess it could be it or the SBC. Unfortunately either way this requires replacement parts or lab tests of the board to know which is the faulty HW - that is only if you really eliminate any possible SW issue.

As last SW issue elimination step, I'd suggest to install Linux mint that is known to work from our fit-pc WiKi page: ... _Mint_19.2

If the above doesn't work, then unfortunately the machine would require repair service via RMA procedure documented at the below link:

Re: disk failure - cable problem?

Posted: Tue Feb 11, 2020 7:12 am
by parsifal9
Hi Tamir,

thanks for that. I think that this repair is not something I can do.

I bought the machine in another country at least 8 years ago. So sending it back to the supplier is not really on the cards.

The Displayport output has also failed (a while ago) so I am using the hdmi.
I use the machine a lot and it is on all the time. I am using it now with no problem. However, rather than wait for something to fail I have put in an order for a barebones fitpc4. I will just move the memory and SSD card over,
and find another use for this machine.

I am looking forward to the new machine.
Thanks for you help.

Re: disk failure - cable problem?

Posted: Tue Feb 11, 2020 11:06 am
by tamir
Sorry that your fit-pc3 couldn't serve you more reliably for longer time.
I hope the your fit-pc4 will work well and reliably at least as well as the fit-pc3 did.