Update ZyXEL 326 from 6.6.2 to 6.7.5, failed to boot

Hi! I tried as I used to do:

su -
cd /boot
mkdir ./backup/2024-03-30/
cp -a uImage uInitrd ./backup/2024-03-30/
cp -a initrd.img-6.6.2-mvebu-tld-1 backup/2024-03-30/
cp -a System.map-6.6.2-mvebu-tld-1 backup/2024-03-30/
cp -a vmlinuz-6.6.2-mvebu-tld-1 backup/2024-03-30/
cp -a config-6.6.2-mvebu-tld-1 backup/2024-03-30/
cp -ra dts/ backup/2024-03-30/dts
wget https://bit.ly/3SI4bRv
mv 3SI4bRv linux-6.7.5-mvebu-tld-1-bodhi.tar.bz2
tar -vxjf linux-6.7.5-mvebu-tld-1-bodhi.tar.bz2
tar -xf  linux-dtb-6.7.5-mvebu-tld-1.tar
apt-get remove flash-kernel 
dpkg -i linux-image-6.7.5-mvebu-tld-1_1_armhf.deb
cp -a zImage-6.7.5-mvebu-tld-1 zImage.fdt
cat dts/armada-380-zyxel-nas326.dtb >> zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-6.7.5-mvebu-tld-1 -d zImage.fdt uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-6.7.5-mvebu-tld-1 -d initrd.img-6.7.5-mvebu-tld-1 uInitrd
sync 
sync
mount /dev/sdc1 /mnt/bootusb/
mkdir /mnt/bootusb/boot/backup/2024-03-30/
cp -a /mnt/bootusb/boot/uI* /mnt/bootusb/boot/backup/2024-03-30/
cp -a uImage uInitrd /mnt/bootusb/boot/
sync
sync
umount /mnt/bootusb
sync
shutdown -r now

It boots with a USB and continue with the rest on HD. But it never booted up. Wife want me out for dinner, so I did not have much time to check why. Then I read https://forum.doozan.com/read.php?2,32146 "Updated 16 Dec 2023: Rootfs Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2 has been uploaded. ". Is this something I need to do? Can I just overwrite what the rootfs I have now to keep all other settings? Or is it something else, if you can see it in your crystal ball? ;-)

raffe,

> It boots with a USB and continue with the rest on
> HD. But it never booted up. Wife want me out for
> dinner, so I did not have much time to check why.
> Then I read
> https://forum.doozan.com/read.php?2,32146 "Updated
> 16 Dec 2023: Rootfs
> Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2 has
> been uploaded. ". Is this something I need to do?

No, you don't need to use the new rootfs. You can install new kernel like you did. And whenever you feel like, you can upgrade the rootfs to bookworm.

> Can I just overwrite what the rootfs I have now to
> keep all other settings? Or is it something else,
> if you can see it in your crystal ball? ;-)

Most likely it got stuck in mounting the rootfs for some reason. If you have serial console, it will be easy to see. So connect serial console.

Because of this box quirk, you have to disconnect the TX and RX wire, power up, and then in 1..2 seconds, then reconnect it. It's a pain to have to do this each time you connect serial console, but it seems to be one of those "stupidest" hardware design and we have to live with it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Naturally it booted up just fine when I had it connected with serial console (and I do not need to disconnect wires to make it work). But I did find something strange: The device names for hard drives and USB-drives can switch between boots.

I make a new thread for that...

raffe,

> Naturally it booted up just fine when I had it
> connected with serial console (and I do not need
> to disconnect wires to make it work).

That's interesting. So the serial behavior on your box is different from what I recall on my box.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)