Hi,
[…]
I was quite happy to find that this is possible out of the box. I'd suggest elaborating on "inspection" in the documentation as this may be confusing for new users!
I am glad you could help yourself but I am afraid you merely found the pragmatic workaround for utilizing multiple block devices as that use-case is not yet properly addressed with the current Sculpt. Since this not “officially” supported and diverting the inspection functionality is a happy little accident we refrain from documenting this behaviour.
That being said, you can make it work by managing the NVMe device manually. That involves starting an appropriately configured 'part_block' as well as an 'ext2_fs' instance. You can use the pkgs published in my depot (see 'cnuke → Tools (Extra)) as they are not available in the genodelabs depot. The following examplary launcher reference those pkgs since configuring the block session, i.e. setting the label for the partition, is not possible via the GUI:
# nvme-part_block <launcher pkg="cnuke/pkg/part_block/2024-04-11" priority="-1"> <route> <service name="Block"> <child name="nvme" label="1"/> </service> <service name="Report" label="partitions"> <parent/> </service> </route> </launcher>
# nvme-part_2_fs <launcher pkg="cnuke/pkg/ext2_fs/2024-04-11" priority="-1"> <route> <service name="Block"> <child name="nvme-part_block" label="2"/> </service> <service name="RM"> <parent/> </service> </route> </launcher>
You can store the launcher on your USB stick (config/24.04/launcher) and start them manually or add them to your persistent deply config (so that they get started when you 'Use' the USB stick). Afterwards you just point the other components to 'nvme-part_2_fs'.
Regards Josef