ix2 Lenovo Buster boot issues

Hi Everyone,
I have a problem to solve. I have a bunch of Lenovo 1x2-ng's and have been able to get them to boot Debian-Bullseye with this guide (specifically using his "raw images" and his installer script)
https://minaret.biz/tips/ix2/index.html

However the program I want to run OpenMediaVault, does not install properly, after looking into it, it seems to be an issue with OMV 6, across the board.

So I want to install Buster on my ix2-ng to see if it works with OMV 5(tied to BUSTER) (much more stable).

But following Bohdi's instructions for debian buster:

Quote
Updated 25 Aug 2019: Basic Debian buster Kirkwood rootfs for most Kirwood plugs: - tarball size: 209M - install size: 536M - The init system used in this rootfs is sysvinit . To boot with systemd, see note 2 below. - Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, sysvinit-utils, u-boot-tools, and mtd-utils. - see LED controls in /etc/rc.local, and /etc/init.d/halt - see some useful aliases in /root/.profile - root password: root Download at Dropbox: Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 md5: cd8ad170aa1a9fdc2a0a1c43ab1c0721 sha256: 8ccbbced367b4c2bf3728262e882f8232aff0fecd1c0c767219a0cab49a0b9bf And remember to check the hash of what you download, as always. Installation: Installation can be done on any Linux box, with a fresh USB drive (SD card or HDD would work fine too). Note: all steps below must be done while logging in as root user (not sudo). If you are not the root user then don't continue, because the rootfs will not work. 1. Format a new USB drive with a single Ext3 partition, and label it rootfs. 2. Mount the drive on a Linux box. cd to top level directory and extract it. It is assuming the USB drive is mounted at /media/sdb1 cd /media/sdb1 tar -xjf Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 3. Adjust fstab (optional). Edit /media/sdb1/etc/fstab entry for root device to match the rootfstype of your rootfstype if you use Ext4 or Ext2. However, you can keep it as is without problem in booting since the kernel will figure out which file system the rootfs was formatted. LABEL=rootfs / ext3 noatime,errors=remount-ro 0 1 4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Do not do this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time). Please replace kirkwood-goflexnet.dtb below with the correct DTB name for your box (see the folder /media/sdb1/boot/dts for the exact spelling of your Kirkwood box name). Generate the uImage with DTB embedded inside: cd /media/sdb1/boot cp -a zImage-5.2.9-kirkwood-tld-1 zImage.fdt cat dts/kirkwood-goflexnet.dtb >> zImage.fdt mv uImage uImage.orig mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.2.9-kirkwood-tld-1 -d zImage.fdt uImage sync If your Linux box does not have mkimage, then install it apt-get install u-boot-tools 5. Done. Take this USB rootfs to your plug and cold start. After booted into Debian, see Note1 and Note2 below. It is very important that you do Note1 steps to secure your box. If you are booting this rootfs with stock u-boot, please see [url]https://forum.doozan.com/read.php?2,102054,105374#msg-105374[/url] for how to set up the envs in serial console. Note1: After logging in this rootf the first time, remember to generate new SSH key to make it your own unique rootfs. And also update your rootfs to get the latest Debian package security updates: rm /etc/ssh/ssh_host* ssh-keygen -A apt-get update apt-get upgrade Warning: Watch the apt-get upgrade progress. If the apt-get upgrade results in a new initramfs, the log would shows this message: update-initramfs: Generating /boot/initrd.img-5.2.9-kirkwood-tld-1 Then you need to regenerate the uInitrd boot file: cd /boot mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.2.9-kirkwood-tld-1 -d initrd.img-5.2.9-kirkwood-tld-1 uInitrd Note2: To boot with systemd, add parameter init=/bin/systemd to your u-boot env bootargs (beware that in later Debian distribution, the location of systemd binary might have changed). - For example, fw_setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts init=/bin/systemd' - Or, if you are booting with my latest u-boot images you can also use the uEnv.txt capability to do this. In the default envs, custom_params is a variable that allows you to add extra bootargs. So add the following line to uEnv.txt: custom_params=init=/bin/systemd If that's still not possible to run systemd, you might want to install it again: apt-get install systemd

I get the "bad magic number" error:

Quote
__ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** ix2-spi ** ** uboot_ver:0.0.8 ** ** MARVELL BOARD: DB-88F6282A-BP LE U-Boot 1.1.4 (Oct 28 2011 - 15:18:22) Marvell version: 3.6.1 - EMC U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CD5A0 Soc: 88F6282 A1 CPU running @ 1600Mhz L2 running @ 533Mhz SysClock = 533Mhz , TClock = 200Mhz DRAM (DDR3) CAS Latency = 7 tRP = 7 tRAS = 20 tRCD=7 DRAM CS[0] base 0x00000000 size 256MB DRAM Total size 256MB 16bit width Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done Found ADT7473, program PWM1 ... OK [1024kB@f8000000] Flash: 1 MB Marvell Serial ATA Adapter Integrated Sata device found CPU : Marvell Feroceon (Rev 1) Streaming disabled Write allocate disabled USB 0: host mode PEX 0: interface detected no Link. PEX 1: interface detected no Link. Net: egiga0 [PRIME] Hit any key to stop autoboot: 0 *Try USB* (Re)start USB... USB: scanning bus for devices... 2 USB Device(s) found Waiting for storage device(s) to settle before scanning... 1 Storage Device(s) found USB read: device 0 block # 2048, count 16384 ... ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... 16384 blocks read: OK USB read: device 0 block # 34816, count 24576 ... ......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................[Warning: Maximal number of characters per line exceeded! Check the line break settings in Terminal > Settings > Text or increase the limit in Terminal > Settings > Advanced.] 24576 blocks read: OK ## Booting image at 01000000 ... Bad Magic Number *Try IDE* Reset IDE: Marvell Serial ATA Adapter Integrated Sata device found IDE device not available *Try IDE1* IDE device 1: not available IDE device not available

I'm at a bit of a loss...

Thanks for any help

ix2USER,

Boot again. This time interrupt serial console and get the listing of the envs.

printenv

And then continue to boot like you did before.

Capture this entire serial console log and post here.

Your log above did not have any line breaks so it is quite difficult to read. If you are using a Linux terminal, just highlight the text in the terminal and then copy and paste it to the post here. Or you can use pastebin, too.

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