Bug 262098 - [nanobsd] builds with s2 for /cfg, and can't boot?
Summary: [nanobsd] builds with s2 for /cfg, and can't boot?
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 12.3-RELEASE
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-21 16:34 UTC by peter.larsen
Modified: 2022-10-03 12:17 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description peter.larsen 2022-02-21 16:34:26 UTC 
There seems to have been many changes from 12.2 to 12.3 in /usr/src/tools/tools/nanobsd


for some reason I end up with a disk image with root on s1, /cfg on s2 and nothing on s3 


this have not been a problem on 12.2, but I assume its a problem due to I have 

"NANO_IMAGES=1" in my .conf file

expected behaviour:

s1 for root, s2 preserved as a blank, and s3 used for /cfg

actually getting:

s1 for root, s2 used for /cfg, s3 blank


result:
Image can't boot... it expect /cfg on s3
Comment 1 ovi 2022-10-03 12:17:17 UTC 
I have the same issue on FreeBSD 12.3, 13.0 and 13.1, on i386 architecture.

I've also tried the complete example from this page (using NANO_IMAGES=1):

https://docs.freebsd.org/en/articles/nanobsd/

More info from nanobsd log:

newfs -b 4096 -f 512 -i 8192 -U -Lnanobsds3 /dev/md0s3
newfs: /dev/md0s3: could not find special device
Running exit trap code