> So my questions are:
> • Is this just an unlucky flash problem or could there be something
> more sinister?
Your logs seem to show flash issues:
--
kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen
kernel: ata1: irq_stat 0x0040, PHY RDY changed
kernel: ata1: S
As per here:
https://doc.astlinux-project.org/userdoc:board_pcengines_apu2
The /mnt/kd/sensors.conf file must exist (for lmsensors to start) and #'s are
comments.
My APU2's /mnt/kd/sensors.conf is:
--
# libsensors configuration file
# -
# PC Engines APU2
# k10temp CP
Thanks Michael. It does look that way.
Hmm thanks for pointing out the error.
I realise that I am now confused about sensors.conf for the Jetway NF9HG-2930 &
Qotom Q190G4N-S07 & Qotom Q530G6.
Is the file empty with just comments or does the # mean something?
# libsensors configuration file
# ---
> Am 17.08.2019 um 05:16 schrieb Michael Knill
> :
>
> Hi Group
>
> I have an APU2 installed running version 1.3.6. Due to a UPS battery change,
> they powered down the APU but had problems with the system on powerup.
> Symptoms were that you could not web or SSH into box. Attended site and
Hi Group
I have an APU2 installed running version 1.3.6. Due to a UPS battery change,
they powered down the APU but had problems with the system on powerup.
Symptoms were that you could not web or SSH into box. Attended site and plugged
in a serial cable and found that the flash could not be rea
Hi Group
I have an APU2 installed running version 1.3.6. Due to a UPS battery change,
they powered down the APU but had problems with the system on powerup.
Symptoms were that you could not web or SSH into box. Attended site and plugged
in a serial cable and found that the flash could not be rea
