public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Stephen Ecker <stephenecker240@gmail.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: expand-on-first-boot broken with btrfs subvolume
Date: Thu, 23 Jan 2025 10:38:17 +0300	[thread overview]
Message-ID: <510274b28f1ae5fc4f4d61a269f7441befdcc116.camel@ilbers.de> (raw)
In-Reply-To: <3652dfef-495c-431c-b91b-9ff1e6735157n@googlegroups.com>

On Wed, 2025-01-22 at 18:21 -0800, Stephen Ecker wrote:
> I have an initramfs script that moves the root filesystem to btrfs
> subvolume on first boot.  This breaks the expand-last-partition.sh
> script for the oddest reason:
> 
> line 4:  findmnt / -o source -n
> 
> normally this line outputs something like: /dev/name,
> but when on a btrfs subvolume, it outputs: /dev/name[@subvol] 
> 
> This leads to the error: "Boot device equals root device - no
> partitioning found"
> not exactly sure why, as I didn't dissect every line. I found that
> changing the command in line 4 to: findmnt / -o sources -n 
> fixed the problem... I tried this after I noticed running findmnt / -
> -output-all, the device name alone was listed under SOURCES, where
> SOURCE had the subvol appended.
> 
> I don't really like this solution, partly because 1) an ubuntu
> installation I have doesn't even have the sources output (though it
> was added 3 years ago,
> see: https://github.com/util-linux/util-linux/blame/master/misc-utils
> /findmnt.c#L135 )... but mainly because I don't know exactly what
> this will look like for other device / filesystem types.
> 
> maybe we could add a sed expression to trim past the device name? 
> i.e.  
> 
> findmnt / -o source -n | sed 's, [\[.*]*,,' 
> 
> thoughts?

It doesn't look like something to be changed in Isar.

But you could simply have custom expand script in you layer that does
things you need.

| meta-your-layer/recipes-support/expand-on-first-boot/expand-on-first-
boot_%.bbappend:
| 
| ```
| FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
| ```
| meta-your-layer/recipes-support/expand-on-first-boot/files/expand-
last-partition.sh

So, bitbake will take the script from your layer while other files of
the recipe will be taken from isar's `meta` layer.

> thanks,
>    Stephen
> -- 
> You received this message because you are subscribed to the Google
> Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to isar-users+unsubscribe@googlegroups.com.
> To view this discussion visit
> https://groups.google.com/d/msgid/isar-users/3652dfef-495c-431c-b91b-9ff1e6735157n%40googlegroups.com
> .

-- 
Best regards,
Uladzimir.



-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/510274b28f1ae5fc4f4d61a269f7441befdcc116.camel%40ilbers.de.

  reply	other threads:[~2025-01-23  7:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23  2:21 Stephen Ecker
2025-01-23  7:38 ` Uladzimir Bely [this message]
2025-01-23  7:50   ` Stephen Ecker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=510274b28f1ae5fc4f4d61a269f7441befdcc116.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=stephenecker240@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox