Discussion:
[fedora-arm] HD messages?
Robert Moskowitz
2018-09-12 21:25:52 UTC
Permalink
This is on a Cubieboard2

with Fedora-Xfce-armhfp-29-20180911.n.0-sda image on the HD and only
uboot on the uSD.

System booted up as expected.  GUI setup occured and Xfce started. Then
on console I started seeing HD related messages.  Are these drive
errors, and I need to get a new drive for testing or some other sort of
messages?

[  824.049554] ata1.00: failed command: READ FPDMA QUEUED
[  824.054798] ata1.00: cmd 60/20:60:10:ab:34/00:00:00:00:00/40 tag 12
ncq dma 16384 in
[  824.054798]          res 40/00:84:50:ab:34/00:00:00:00:00/40 Emask
0x10 (ATA bus error)
[  824.070574] ata1.00: status: { DRDY }
[  824.074287] ata1.00: failed command: READ FPDMA QUEUED
[  824.079495] ata1.00: cmd 60/08:68:00:ab:34/00:00:00:00:00/40 tag 13
ncq dma 4096 in
[  824.079495]          res 40/00:84:50:ab:34/00:00:00:00:00/40 Emask
0x10 (ATA bus error)
[  824.095220] ata1.00: status: { DRDY }
[  824.098928] ata1.00: failed command: READ FPDMA QUEUED
[  824.104134] ata1.00: cmd 60/10:70:e8:aa:34/00:00:00:00:00/40 tag 14
ncq dma 8192 in
[  824.104134]          res 40/00:84:50:ab:34/00:00:00:00:00/40 Emask
0x10 (ATA bus error)
[  824.119808] ata1.00: status: { DRDY }
[  824.123520] ata1.00: failed command: READ FPDMA QUEUED
[  824.128725] ata1.00: cmd 60/38:78:00:32:31/00:00:00:00:00/40 tag 15
ncq dma 28672 in
[  824.128725]          res 40/00:84:50:ab:34/00:00:00:00:00/40 Emask
0x10 (ATA bus error)
[  824.144503] ata1.00: status: { DRDY }
[  824.148234] ata1.00: failed command: READ FPDMA QUEUED
[  824.153440] ata1.00: cmd 60/48:80:50:ab:34/00:00:00:00:00/40 tag 16
ncq dma 36864 in
[  824.153440]          res 40/00:84:50:ab:34/00:00:00:00:00/40 Emask
0x10 (ATA bus error)
[  824.169219] ata1.00: status: { DRDY }
[  824.172947] ata1: hard resetting link
[  824.486151] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  824.539710] ata1.00: configured for UDMA/33
[  824.544114] ata1: EH complete
[  824.577421] ata1.00: exception Emask 0x10 SAct 0x2 SErr 0x280100
action 0x6 frozen
[  824.585177] ata1.00: irq_stat 0x08000000, interface fatal error
[  824.591239] ata1: SError: { UnrecovData 10B8B BadCRC }
[  824.596429] ata1.00: failed command: READ FPDMA QUEUED
[  824.601605] ata1.00: cmd 60/48:08:50:ab:34/00:00:00:00:00/40 tag 1
ncq dma 36864 in
[  824.601605]          res 40/00:2c:10:ab:34/00:00:00:00:00/40 Emask
0x10 (ATA bus error)
[  824.617259] ata1.00: status: { DRDY }
[  824.620962] ata1: hard resetting link
[  824.937794] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  824.994304] ata1.00: failed to set xfermode (err_mask=0x100)
[  830.196474] ata1: hard resetting link
[  830.509657] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[  830.560362] ata1.00: configured for UDMA/33
[  830.564657] ata1: EH complete

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/ar
Peter Robinson
2018-09-12 21:59:23 UTC
Permalink
Post by Robert Moskowitz
This is on a Cubieboard2
with Fedora-Xfce-armhfp-29-20180911.n.0-sda image on the HD and only
uboot on the uSD.
System booted up as expected. GUI setup occured and Xfce started. Then
on console I started seeing HD related messages. Are these drive
errors, and I need to get a new drive for testing or some other sort of
messages?
To be honest no idea, hard disk errors aren't ARM specific, nor likely
Fedora specific so you could probably shove any one of those strings
into google and get an answer!

The storage error reporting standard (part o ATA/SCSI standards) is
called SMART (Self-Monitoring, Analysis and Reporting Technology) and
there's linux tools called smartmontools, available in Fedora, maybe
try installing those and seeing what they have to say.
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/***@li
Robert Moskowitz
2018-09-12 22:13:53 UTC
Permalink
Post by Peter Robinson
Post by Robert Moskowitz
This is on a Cubieboard2
with Fedora-Xfce-armhfp-29-20180911.n.0-sda image on the HD and only
uboot on the uSD.
System booted up as expected. GUI setup occured and Xfce started. Then
on console I started seeing HD related messages. Are these drive
errors, and I need to get a new drive for testing or some other sort of
messages?
To be honest no idea, hard disk errors aren't ARM specific, nor likely
Fedora specific so you could probably shove any one of those strings
into google and get an answer!
The storage error reporting standard (part o ATA/SCSI standards) is
called SMART (Self-Monitoring, Analysis and Reporting Technology) and
there's linux tools called smartmontools, available in Fedora, maybe
try installing those and seeing what they have to say.
with all the interesting things done for arm i thought I would start
here.  I knew it was a stretch.

Running Xfce directly on the Cubie is slow.  The idea is to go to
multi-user mode and install tiger-vncserver, so most of the graphics
work is on my notebook.  That is for tomorrow.  I had it working for my
userid, so it is 'just a matter' of repeat.  Lots of errors setting up
vnc for root with Xfce; I have done this with Gnome...

Well time to google some.

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/***@lists.fedoraproj
Loading...