Cubietruck hanging on boot after update [SOLVED]

This forum is for supported devices using an ARMv7 Allwinner SoC.

Cubietruck hanging on boot after update [SOLVED]

Postby Aitch » Fri Apr 06, 2018 12:35 pm

I've been running a sever on a Cubietruck from an attached SATA drive. It is kept very current with regular pacman updates.

Following the last update on 1st April (not funny) I could no longer ssh into it. Network and hardware issues are eliminated and I can boot and ssh into it from a SD card.

Watching the failing boot on screen it seems to load u_boot and recognise the SATA drive. It then moves to a new screen showing two Linux penquins at the top. Then it just hangs.

I've checked the pacman log and see the kernal was upgraded from linux-armv7 (4.15.8-1 -> 4.15.14-1), but without a completed boot I'm struggling to find error messages. Can anyone help me investigate further to avoid a complete re-install?
Last edited by Aitch on Mon Apr 30, 2018 1:57 pm, edited 1 time in total.
Aitch
 
Posts: 5
Joined: Tue Oct 07, 2014 8:20 pm

Re: Cubietruck hanging on boot after update

Postby blubb0r » Sun Apr 08, 2018 10:49 am

I've the same problem with my Cubietruck here.
I tried chrooting and running pacman update, but with no luck. Also downgrading to an older kernel was not successful.

Next thing I'll try is setting up another SD card with the latest ArchlinuxARM version. Let's see if this helps.

But actually I also prefer a solution not including a complete re-install.
blubb0r
 
Posts: 1
Joined: Sun Apr 08, 2018 10:44 am

Re: Cubietruck hanging on boot after update

Postby Aitch » Sun Apr 08, 2018 12:29 pm

I've tried with a new SD card image. No difference.
Aitch
 
Posts: 5
Joined: Tue Oct 07, 2014 8:20 pm

Re: Cubietruck hanging on boot after update

Postby Aitch » Wed Apr 11, 2018 10:07 am

As everything else blubb0r and I have tried is not finding the root cause, here's a record of all packages updated during the upgrade that is hanging booting from the SATA drive.

Can someone with some knowledge of the boot process please review and give us some hints?

$this->bbcode_second_pass_code('', '[2018-04-01 11:31] [ALPM] upgraded filesystem (2017.10-2 -> 2018.1-2)
[2018-04-01 11:31] [ALPM] upgraded tzdata (2018c-1 -> 2018d-1)
[2018-04-01 11:31] [ALPM] upgraded gcc-libs (7.2.1+20180116-1 -> 7.3.1+20180312-2)
[2018-04-01 11:31] [ALPM] upgraded icu (60.2-1 -> 61.1-1)
[2018-04-01 11:31] [ALPM] upgraded libxml2 (2.9.8-1 -> 2.9.8-2)
[2018-04-01 11:31] [ALPM] upgraded libutil-linux (2.31.1-1 -> 2.32-2)
[2018-04-01 11:31] [ALPM] upgraded e2fsprogs (1.43.9-1 -> 1.44.1-1)
[2018-04-01 11:32] [ALPM] upgraded openssl (1.1.0.g-1 -> 1.1.0.h-1)
[2018-04-01 11:32] [ALPM] upgraded bind-tools (9.12.0-1 -> 9.12.1-1)
[2018-04-01 11:32] [ALPM] upgraded ca-certificates-mozilla (3.35-1 -> 3.36-1)
[2018-04-01 11:32] [ALPM] upgraded libgpg-error (1.27-1 -> 1.28-1)
[2018-04-01 11:32] [ALPM] upgraded libsystemd (237.64-1 -> 238.51-1)
[2018-04-01 11:32] [ALPM] upgraded device-mapper (2.02.177-1 -> 2.02.177-5)
[2018-04-01 11:32] [ALPM] upgraded cryptsetup (2.0.1-1 -> 2.0.2-1)
[2018-04-01 11:32] [ALPM] upgraded libpsl (0.19.1-1 -> 0.20.1-2)
[2018-04-01 11:32] [ALPM] upgraded libnghttp2 (1.30.0-1 -> 1.31.0-1)
[2018-04-01 11:32] [ALPM] upgraded curl (7.58.0-1 -> 7.59.0-2)
[2018-04-01 11:32] [ALPM] upgraded libtirpc (1.0.2-3 -> 1.0.3-1)
[2018-04-01 11:32] [ALPM] upgraded dovecot (2.3.0.1-2 -> 2.3.1-2)
[2018-04-01 11:32] [ALPM] upgraded glib2 (2.54.3+2+g94b38beff-1 -> 2.56.0+7+g66948ae23-1)
[2018-04-01 11:32] [ALPM] upgraded graphite (1:1.3.10-1 -> 1:1.3.11-1)
[2018-04-01 11:32] [ALPM] upgraded harfbuzz (1.7.6-1 -> 1.7.6-2)
[2018-04-01 11:32] [ALPM] upgraded fontconfig (2.12.6+5+g665584a-1 -> 2.13.0+10+g58f5285-1)
[2018-04-01 11:32] [ALPM-SCRIPTLET] Rebuilding fontconfig cache... done.
[2018-04-01 11:32] [ALPM] upgraded gawk (4.2.0-3 -> 4.2.1-1)
[2018-04-01 11:32] [ALPM] upgraded libcap-ng (0.7.8-1 -> 0.7.9-1)
[2018-04-01 11:32] [ALPM] upgraded libcups (2.2.6-4 -> 2.2.7-1)
[2018-04-01 11:32] [ALPM] upgraded libdrm (2.4.91-1.1 -> 2.4.91-3)
[2018-04-01 11:32] [ALPM] upgraded libevdev (1.5.8-1 -> 1.5.9-1)
[2018-04-01 11:32] [ALPM] upgraded util-linux (2.31.1-1 -> 2.32-2)
[2018-04-01 11:32] [ALPM] upgraded systemd (237.64-1 -> 238.51-1)
[2018-04-01 11:32] [ALPM] upgraded libwacom (0.28-2 -> 0.29-1)
[2018-04-01 11:32] [ALPM] upgraded libinput (1.10.2-1 -> 1.10.3-1)
[2018-04-01 11:32] [ALPM] upgraded linux-firmware (20180119.2a713be-1 -> 20180314.4c0bf11-1)
[2018-04-01 11:33] [ALPM] upgraded linux-armv7 (4.15.8-1 -> 4.15.14-1)
[2018-04-01 11:33] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2018-04-01 11:33] [ALPM] upgraded llvm-libs (5.0.1-2 -> 6.0.0-4)
[2018-04-01 11:33] [ALPM] upgraded lvm2 (2.02.177-1 -> 2.02.177-5)
[2018-04-01 11:33] [ALPM] upgraded mesa (17.3.6-1 -> 17.3.7-1)
[2018-04-01 11:33] [ALPM] upgraded nano (2.9.3-1 -> 2.9.4-1)
[2018-04-01 11:33] [ALPM] upgraded netctl (1.15-1 -> 1.16-1)
[2018-04-01 11:33] [ALPM] upgraded nspr (4.18-1 -> 4.19-1)
[2018-04-01 11:33] [ALPM] upgraded nss (3.35-1 -> 3.36-1)
[2018-04-01 11:33] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2018-04-01 11:33] [ALPM] upgraded pacman-mirrorlist (20171201-1 -> 20180323-1)
[2018-04-01 11:33] [ALPM] upgraded postfix (3.3.0-1 -> 3.3.0-2)
[2018-04-01 11:33] [ALPM] upgraded python-setuptools (1:38.5.2-1 -> 1:39.0.1-1)
[2018-04-01 11:33] [ALPM] upgraded xorg-xset (1.2.3-1 -> 1.2.4-1)
[2018-04-01 11:33] [ALPM] upgraded xdg-utils (1.1.2-1 -> 1.1.2-2)
[2018-04-01 11:33] [ALPM] upgraded qt5-base (5.10.1-4 -> 5.10.1-7)
[2018-04-01 11:33] [ALPM] upgraded s-nail (14.9.7-1 -> 14.9.9-1)
[2018-04-01 11:33] [ALPM] upgraded systemd-sysvcompat (237.64-1 -> 238.51-1)
[2018-04-01 11:33] [ALPM] upgraded xfsprogs (4.14.0-1 -> 4.15.1-1)
')
Aitch
 
Posts: 5
Joined: Tue Oct 07, 2014 8:20 pm

Re: Cubietruck hanging on boot after update [SOLVED]

Postby Aitch » Mon Apr 30, 2018 2:05 pm

I revisited this issue after some days working on other systems.

I booted from a new sd card and noticed an error message in dmesg log when the sda1 disk was mounted. I ran e2fsck on sda1 disk as suggested and there were a lot of issues needing fixing - disk corrupted during the 1st April update???

Anyway all working as before and IMAP mail server back up and running again :o))

If it's of interest to anyone here's the output from e2fsck:
$this->bbcode_second_pass_quote('', '[')root@alarm /]# e2fsck -v /dev/sda1
e2fsck 1.43.9 (8-Feb-2018)
/dev/sda1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes

Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 6553717: 26247724--26247726
Multiply-claimed block(s) in inode 6553903: 26247724--26247726
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1D: Reconciling multiply-claimed blocks
(There are 2 inodes containing multiply-claimed blocks.)

File /var/cache/pacman/pkg/dbus-1.12.6-1-armv7h.pkg.tar.xz (inode #6553717, mod time Thu Feb 22 00:48:32 2018)
has 3 multiply-claimed block(s), shared with 1 file(s):
/var/lib/pacman/local/harfbuzz-1.7.6-2/mtree (inode #6553903, mod time Fri Mar 30 00:45:02 2018)
Clone multiply-claimed blocks<y>? yes
File /var/lib/pacman/local/harfbuzz-1.7.6-2/mtree (inode #6553903, mod time Fri Mar 30 00:45:02 2018)
has 3 multiply-claimed block(s), shared with 1 file(s):
/var/cache/pacman/pkg/dbus-1.12.6-1-armv7h.pkg.tar.xz (inode #6553717, mod time Thu Feb 22 00:48:32 2018)
Multiply-claimed blocks already reassigned or cloned.

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(172233--172941) -(8552463--8552557) -(8552562--8552564) -8552573 -(8552615--8552645) -(8552651--8552697) -(8552700--8552707) -(8552709--8552734) -(8552739--8552809) -(8552817--8552959) -(8580327--8580329) -8580389 -8580397 -8580428 -(26250418--26250480) -26259609 -(26259630--26259633) -(26259673--26259677)
Fix<y>? yes
Free blocks count wrong for group #0 (3016, counted=3013).
Fix<y>? yes
Free blocks count wrong for group #5 (2326, counted=3035).
Fix<y>? yes
Free blocks count wrong for group #261 (32115, counted=32542).
Fix<y>? yes
Free blocks count wrong for group #801 (24694, counted=24767).
Fix<y>? yes
Free blocks count wrong (27075784, counted=27076990).
Fix<y>? yes

/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****

83062 inodes used (1.13%, out of 7331840)
536 non-contiguous files (0.6%)
69 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 77361/104
2227960 blocks used (7.60%, out of 29304950)
0 bad blocks
1 large file

72134 regular files
4970 directories
0 character device files
0 block device files
0 fifos
1683 links
5925 symbolic links (5565 fast symbolic links)
24 sockets
------------
84736 files
Aitch
 
Posts: 5
Joined: Tue Oct 07, 2014 8:20 pm


Return to Allwinner

Who is online

Users browsing this forum: No registered users and 3 guests

cron