Hi Giles, It really looks like the version of uboot you're using only understands ext2 (and fat, most likely, but I'm not sure that helps you in this situation)
Try dropping back to ext2 for anything that needs to be accessed by uboot. Enjoy! Rick On Thu, Jun 9, 2022, at 6:26 AM, Gilles wrote: > Forgot to write that I tried this line manually: > > Marvell>> setenv bootcmd_usb 'usb start; ext4load usb 0:1 0x00800000 > /uImage; ext4load usb 0:1 0x01100000 /uInitrd' > > > Marvell>> print > baudrate=115200 > bootargs=console=ttyS0,115200 > bootargs_console=console=ttyS0,115200 > bootcmd=setenv bootargs $(bootargs_console); run bootcmd_usb; bootm > 0x00800000 0x01100000 > bootcmd_usb=usb start; ext4load usb 0:1 0x00800000 /uImage; ext4load usb > 0:1 0x01100000 /uInitrd > bootdelay=3 > ethact=egiga0 > ethaddr=02:50:43:e7:5c:e1 > ipaddr=192.168.0.10 > serverip=192.168.0.12 > stderr=serial > stdin=serial > stdout=serial > x_bootargs=console=ttyS0,115200 > mtdparts=orion_nand:512k(uboot),4m@1m(kernel),507m@5m(rootfs) rw > x_bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs > x_bootcmd_kernel=nand read 0x6400000 0x100000 0x400000 > x_bootcmd_sata=ide reset; > x_bootcmd_usb=usb start; > Environment size: 706/131068 bytes > > Marvell>> run bootcmd > > (Re)start USB... > USB: Register 10011 NbrPorts 1 > USB EHCI 1.00 > scanning bus for devices... 2 USB Device(s) found > scanning bus for storage devices... 1 Storage Device(s) found > Unknown command 'ext4load' - try 'help' > Unknown command 'ext4load' - try 'help' > ## Booting kernel from Legacy Image at 00800000 ... > Image Name: kernel 4.9.0-18-marvell > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 2080634 Bytes = 2 MiB > Load Address: 00008000 > Entry Point: 00008000 > Verifying Checksum ... Bad Data CRC > ERROR: can't get kernel image! > Marvell>> > > On 09/06/2022 15:14, Gilles wrote: >> I used another USB stick, with the root+boot formated in ext4, the >> install completed, but… Uboot fails loading: >> >> ========= >> U-Boot 2011.12 (Mar 11 2012 - 18:59:46) >> Marvell-Sheevaplug - eSATA - SD/MMC >> >> SoC: Kirkwood 88F6281_A0 >> DRAM: 512 MiB >> WARNING: Caches not enabled >> NAND: 512 MiB >> In: serial >> Out: serial >> Err: serial >> Net: egiga0 >> 88E1116 Initialized on egiga0 >> Hit any key to stop autoboot: 0 >> (Re)start USB... >> USB: Register 10011 NbrPorts 1 >> USB EHCI 1.00 >> scanning bus for devices... 2 USB Device(s) found >> scanning bus for storage devices... 1 Storage Device(s) found >> Loading file "/uImage" from usb device 0:1 (usbda1) >> Failed to mount ext2 filesystem... >> ** Bad ext2 partition or disk - usb 0:1 ** >> Loading file "/uInitrd" from usb device 0:1 (usbda1) >> Failed to mount ext2 filesystem... >> ** Bad ext2 partition or disk - usb 0:1 ** >> ## Booting kernel from Legacy Image at 00800000 ... >> Image Name: kernel 4.9.0-18-marvell >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 2080634 Bytes = 2 MiB >> Load Address: 00008000 >> Entry Point: 00008000 >> Verifying Checksum ... Bad Data CRC >> ERROR: can't get kernel image! >> Marvell>> >> ========= >> >> That was with the original settings: >> setenv bootargs_console console=ttyS0,115200 >> setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x00800000 /uImage; >> ext2load usb 0:1 0x01100000 /uInitrd' >> setenv bootcmd 'setenv bootargs $(bootargs_console); run bootcmd_usb; >> bootm 0x00800000 0x01100000' >> >> => Does Uboot support ext4, or just ext2? Or is the 2011.12 release >> too old, and I should either upgrade or go back to ext2 instead? >> >> On 08/06/2022 15:36, Philip Hands wrote: >>> Gilles <codecompl...@free.fr> writes: >>> >>>> On 08/06/2022 00:54, Rick Thomas wrote: >>>>> On Tue, Jun 7, 2022, at 6:32 AM, Gilles wrote: >>>>>> It ends with a single error : "partman: mkswap: can't open >>>>>> '/dev/sda5': >>>>>> No such file or directory": >>>>>> >>>>>> https://pastebin.com/raw/h0beZWnP >>>>> It looks like /dev/sd5 doesn't actually exist. This is probably >>>>> because the USB stick has an MBR partition table which by default >>>>> only provides partitions 1-4. You may need to pre-partition it >>>>> with a GUID partition table. >>>>> >>>>> Rick >>>> Good call. After using Windows' diskpart*, I removed the MBR and >>>> converted to GPT. The installer went one step further… and failed: >>>> >>>> https://postimg.cc/ns5XMQL7 >>>> >>>> Here's the log: >>>> >>>> https://pastebin.com/raw/htYCmhS3 >>> The ``bad block bitmap checksum'' relating to /dev/sda2, followed by >>> ``Remounting filesystem read-only'' seems to be the source of your >>> problem. >>> >>> After that point nothing's going to work because your new root >>> filesystem (/target/) is faulty, and is now read-only, so there's no way >>> to create the /target/boot directory, so the mount of the boot partition >>> fails. >>> >>> My guess would be an underlying hardware fault on whatever /dev/sda2 is. >>> >>> I don't suppose there's any chance it's a fake USB stick - see: >>> >>> http://oss.digirati.com.br/f3/ (packaged for Debian as ``f3'') >>> >>> Cheers, Phil. >> >>
