Jump to content
  • 0

tinkerboard S's bricked after 5.70 upgrade


AdamD
 Share

Question

Hi all,

 

first post here so please forgive me if I've get any bits wrong.  Thanks for all the work put into supporting this project, and thanks in advance for any and all considerations extended in helping me step through my issue here. 

 

so i've had an 8 node kubernetes cluster running fairly smoothly on my tb's for nearly a full year now, so far I have not had any major issues with armbian updates until this weekends...  I did a round of updates to my cluster and, after rebooting all 3 of my model S tinkerboards seem bricked (redlight only, no output to HDMI)..  The remaining five orig TB models with Samsung EVO SD's all came up without issue...  since my k8s cluster master is one of the S models i'm really hoping there is someway somebody knows to quickly back out and salvage these machines without a full cluster rebuild...  I was thinking there might be an option because I can connect the boards via usb to pc and I am able to view the drive contents... just not sure where to look to fix a u-boot issue or if it's even possible this way.    I've just ordered a UART->usb adapter as it looks like I'm going to need one now,  but it won't be here until mid-week.    Im not sure what other information you might need or that i can get from the boards for you, but I've also attached the last console log of the machines at time of final reboot, HTH..

 

I'm guessing my questions at this point are:

  

1) Any known issues or anyone else having issues with S models after the last update to 5.70 ? 

2) Any other ideas on how I can debug or recover these machines before I receive a UART adapter?

3) Any other references to point me at to further debug this issue properly?

 

best regards,

-ad

 

 

Spoiler

Welcome to ARMBIAN 5.60 stable Debian GNU/Linux 9 (stretch) 4.14.70-rockchip
System load:   0.53 0.68 0.70   Up time:       36 days
Memory usage:  59 % of 2006MB   IP:            xxx.xxx.xxx.xxx
CPU temp:      35°C
Usage of /:    37% of 15G

xxxx@yyyy:~$ sudo apt update
[sudo] password for xxxx:
Get:1 http://security.debian.org stretch/updates InRelease [94.3 kB]
Ign:3 http://cdn-fastly.deb.debian.org/debian stretch InRelease
Get:5 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease [91.0 kB]
Get:6 https://download.docker.com/linux/debian stretch InRelease [44.8 kB]
Get:7 http://cdn-fastly.deb.debian.org/debian stretch-backports InRelease [91.8 kB]
Hit:8 http://cdn-fastly.deb.debian.org/debian stretch Release
Hit:2 https://packages.cloud.google.com/apt kubernetes-xenial InRelease
Get:4 https://apt.armbian.com stretch InRelease [19.0 kB]
Get:9 http://cdn-fastly.deb.debian.org/debian stretch-backports/main armhf Packages.diff/Index [27.8 kB]
Get:10 http://cdn-fastly.deb.debian.org/debian stretch-backports/main armhf Contents (deb).diff/Index [28.0 kB]
Get:11 http://cdn-fastly.deb.debian.org/debian stretch-backports/non-free armhf Packages.diff/Index [12.5 kB]
Get:12 http://cdn-fastly.deb.debian.org/debian stretch-backports/non-free armhf Contents (deb).diff/Index [9,592 B]
Get:13 http://cdn-fastly.deb.debian.org/debian stretch-backports/main armhf Packages 2019-01-13-0212.27.pdiff [293 B]
Get:15 http://cdn-fastly.deb.debian.org/debian stretch-backports/main armhf Packages 2019-01-13-0810.11.pdiff [215 B]
Get:15 http://cdn-fastly.deb.debian.org/debian stretch-backports/main armhf Packages 2019-01-13-0810.11.pdiff [215 B]
Get:16 http://cdn-fastly.deb.debian.org/debian stretch-backports/main armhf Contents (deb) 2019-01-13-0212.27.pdiff [304 B]
Get:16 http://cdn-fastly.deb.debian.org/debian stretch-backports/main armhf Contents (deb) 2019-01-13-0212.27.pdiff [304 B]
Get:17 http://cdn-fastly.deb.debian.org/debian stretch-backports/non-free armhf Packages 2019-01-12-2012.01.pdiff [227 B]
Get:17 http://cdn-fastly.deb.debian.org/debian stretch-backports/non-free armhf Packages 2019-01-12-2012.01.pdiff [227 B]
Get:18 http://cdn-fastly.deb.debian.org/debian stretch-backports/non-free armhf Contents (deb) 2019-01-12-2012.01.pdiff [271 B]
Get:18 http://cdn-fastly.deb.debian.org/debian stretch-backports/non-free armhf Contents (deb) 2019-01-12-2012.01.pdiff [271 B]
Get:19 https://apt.armbian.com stretch/main armhf Packages [322 kB]
Get:20 https://apt.armbian.com stretch/stretch-utils armhf Packages [4,893 B]
Fetched 747 kB in 7s (104 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
5 packages can be upgraded. Run 'apt list --upgradable' to see them.
xxxx@yyyy:~$ sudo apt upgrade -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  linux-dtb-next-rockchip linux-image-next-rockchip linux-libc-dev
  linux-stretch-root-next-tinkerboard linux-u-boot-tinkerboard-next
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 20.8 MB of archives.
After this operation, 26.9 MB of additional disk space will be used.
Get:1 https://apt.armbian.com stretch/main armhf linux-dtb-next-rockchip armhf 5.70 [84.5 kB]
Get:2 https://apt.armbian.com stretch/main armhf linux-image-next-rockchip armhf 5.70 [18.8 MB]
Get:3 https://apt.armbian.com stretch/main armhf linux-libc-dev armhf 5.70 [1,007 kB]
Get:4 https://apt.armbian.com stretch/main armhf linux-stretch-root-next-tinkerboard armhf 5.70 [425 kB]
Get:5 https://apt.armbian.com stretch/main armhf linux-u-boot-tinkerboard-next armhf 5.70 [489 kB]
Fetched 20.8 MB in 4s (4,641 kB/s)
(Reading database ... 31727 files and directories currently installed.)
Preparing to unpack .../linux-dtb-next-rockchip_5.70_armhf.deb ...
Unpacking linux-dtb-next-rockchip (5.70) over (5.60) ...
Preparing to unpack .../linux-image-next-rockchip_5.70_armhf.deb ...
update-initramfs: Deleting /boot/initrd.img-4.14.70-rockchip
Removing obsolete file uInitrd-4.14.70-rockchip
Unpacking linux-image-next-rockchip (5.70) over (5.60) ...
Preparing to unpack .../linux-libc-dev_5.70_armhf.deb ...
Unpacking linux-libc-dev (5.70) over (4.9.130-2) ...
Preparing to unpack .../linux-stretch-root-next-tinkerboard_5.70_armhf.deb ...
Leaving 'diversion of /etc/mpv/mpv.conf to /etc/mpv/mpv-dist.conf by linux-stretch-root-next-tinkerboard'
Unpacking linux-stretch-root-next-tinkerboard (5.70) over (5.60) ...
Preparing to unpack .../linux-u-boot-tinkerboard-next_5.70_armhf.deb ...
Unpacking linux-u-boot-tinkerboard-next (5.70) over (5.60) ...
Setting up linux-image-next-rockchip (5.70) ...
update-initramfs: Generating /boot/initrd.img-4.19.14-rockchip
update-initramfs: Converting to u-boot format
Setting up linux-u-boot-tinkerboard-next (5.70) ...
Setting up linux-libc-dev (5.70) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.19.14-rockchip
update-initramfs: Converting to u-boot format
Setting up linux-stretch-root-next-tinkerboard (5.70) ...
Setting up linux-dtb-next-rockchip (5.70) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.19.14-rockchip
update-initramfs: Converting to u-boot format
xxxx@yyyy:~$ sudo reboot

 

........
 

 

Link to comment
Share on other sites

Recommended Posts

  • 0

There was a change of default to mimick the vendor behavior, that was later partially reverted, I think this is part of that situation. I'll poke at it and provide a separate thread to discuss it and a solution.
@Martinayotte the vendor went from one uart to another between releases, most likely due to blocking a HAT's compatibility.

Sent from my Pixel using Tapatalk

Link to comment
Share on other sites

Search Before Posting!

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...