Filesystem UUID cannot be used in kernel parameters

Discussion about U-Boot and the kernel.

Filesystem UUID cannot be used in kernel parameters

Postby vinibali » Sun May 14, 2023 10:17 am

Hello there!
I'm using the armv7 package with a Marvell Armada 380 (Zyxel 326).
This case I'm loading only the uImage and it seems, during the boot the kernel is unable to identify the root partition.
It's not working with label and UUID, only with PARTUUID.
Is this missing because of the lack of initrd?
$this->bbcode_second_pass_code('', '[ 2.800218] Waiting 10 sec before mounting root device...
[ 3.778601] scsi 2:0:0:0: Direct-Access SanDisk Ultra Fit 1.00 PQ: 0 ANSI: 6
[ 3.787185] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ 3.792958] sd 2:0:0:0: [sda] 120176640 512-byte logical blocks: (61.5 GB/57.3 GiB)
[ 3.801957] sd 2:0:0:0: [sda] Write Protect is off
[ 3.807461] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 3.826380] sda: sda1 sda2
[ 3.831619] sd 2:0:0:0: [sda] Attached SCSI removable disk
[ 4.592519] random: fast init done
[ 13.034069] F2FS-fs (sda2): Unrecognized mount option "rw" or missing value
[ 13.041150] List of all partitions:
[ 13.044714] 1f00 2048 mtdblock0
[ 13.044720] (driver?)
[ 13.051359] 1f01 2048 mtdblock1
[ 13.051364] (driver?)
[ 13.057979] 1f02 10240 mtdblock2
[ 13.057984] (driver?)
[ 13.064573] 1f03 15360 mtdblock3
[ 13.064577] (driver?)
[ 13.071168] 1f04 108544 mtdblock4
[ 13.071172] (driver?)
[ 13.077761] 1f05 15360 mtdblock5
[ 13.077765] (driver?)
[ 13.084344] 1f06 108544 mtdblock6
[ 13.084348] (driver?)
[ 13.090930] 0800 60088320 sda
[ 13.090934] driver: sd
[ 13.097075] 0801 524288 sda1 61deead2-01
[ 13.097079]
[ 13.103482] 0802 16777216 sda2 61deead2-02
[ 13.103487]
[ 13.109899] No filesystem could mount root, tried:
[ 13.109901] f2fs
[ 13.114810]
[ 13.118246] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2)
[ 13.126556] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.17.1-1-ARCH #1
[ 13.133121] Hardware name: Marvell Armada 380/385 (Device Tree)
[ 13.139076] unwind_backtrace from show_stack+0x10/0x14
[ 13.144342] show_stack from dump_stack_lvl+0x40/0x4c
[ 13.149427] dump_stack_lvl from panic+0xfc/0x30c
[ 13.154162] panic from mount_block_root+0x1d8/0x1e4
[ 13.159160] mount_block_root from prepare_namespace+0x150/0x18c
[ 13.165204] prepare_namespace from kernel_init_freeable+0x250/0x264
[ 13.171595] kernel_init_freeable from kernel_init+0x18/0x138
[ 13.177377] kernel_init from ret_from_fork+0x14/0x2c
[ 13.182460] Exception stack(0xc2859fb0 to 0xc2859ff8)
[ 13.187539] 9fa0: 00000000 00000000 00000000 00000000
[ 13.195761] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 13.203982] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 13.210638] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2) ]---')
vinibali
 
Posts: 14
Joined: Wed Oct 23, 2019 1:45 pm

Re: Filesystem UUID cannot be used in kernel parameters

Postby solskogen » Fri Jun 02, 2023 7:18 am

You might have some other error causing this.

Your log says:

$this->bbcode_second_pass_code('', '
F2FS-fs (sda2): Unrecognized mount option "rw" or missing value
')
solskogen
 
Posts: 160
Joined: Mon Nov 18, 2013 10:41 am

Re: Filesystem UUID cannot be used in kernel parameters

Postby summers » Fri Jun 02, 2023 7:12 pm

Think you have to use PARTUUID - there was a web page explaining why, trying to recall it ...

Ah - this is it https://github.com/torvalds/linux/blob/f49aa1de98363b6c5fba4637678d6b0ba3d18065/init/do_mounts.c#L191-L219
summers
 
Posts: 984
Joined: Sat Sep 06, 2014 12:56 pm


Return to U-Boot/Kernel

Who is online

Users browsing this forum: No registered users and 2 guests