Date: Mon, 13 Apr 2026 16:15:58 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 294480] do not boot with custom partition layout Message-ID: <bug-294480-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294480 Bug ID: 294480 Summary: do not boot with custom partition layout Product: Base System Version: 16.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: sergey@fidoman.ru Created attachment 269720 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=269720&action=edit patch Hello, I tried to install FreeBSD in VM with minimalistic disk layout: 1) only BSD disklabel (no DOS/GPT partition table) 2) reordered partitions - swap first, UFS second (to be able to expand UFS without touching swap). => 0 266338304 da0 BSD (127G) 0 2097152 1 freebsd-swap (1G) 2097152 33554432 2 freebsd-ufs (16G) 35651584 230686720 - free - (110G) After install system refused to boot - missing /boot/kernel/kernel message or something Manually sepcifying 0:ad(0,b)/boot/loader allowed to boot system. I examined boot2.c and found that it use only very first partition to boot (and even without initialization of part no.). So here is patch that makes boot2 to scan all partitions for valid loader. After applying, making and gpart bootcode -b with file from /user/obj system began to boot without manual intervention. (maybe patch -l is needed due to space/tab differences) -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-294480-227>