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 <codecomplete@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.