[haiku-development] Re: Failing to mount anyboot boot image
- From: "Adrien Destugues" <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 02 Sep 2016 11:27:06 +0000
2 septembre 2016 12:58 "Jessica Hamilton" <jessica.l.hamilton@xxxxxxxxx> a
écrit:
Hi,
I'm running into a bizarre issue whilst bringing my UEFI branch up to
date (will merge this weekend, I promise!). I'm testing with the
anyboot image (I can't get plain ISO to work, and not moved onto HDD
support yet), but the vfs boot code can't mount the boot partition.
Tail of the syslog:
Identified boot partition by partition offset.
module: Search for file_systems/write_overlay/v1 failed.
PANIC: could not mount boot device!
I've attached the full syslog output for reference.
The BFS partitions were found, but the write_overlay is missing. It is required
to boot from CD or any read-only media.
In standard el-torrito booting, this would be part of the boot "floppy" so it
can be loaded from there. It is added to the boot floppy here:
http://cgit.haiku-os.org/haiku/tree/build/jam/images/FloppyBootImage#n37
I don't know if your UEFI branch boots with a floppy image or some other way,
in either case, for CD boot it will need the write overlay available to the
kernel, before it can mount the main filesystem (and after that it will also
need packagefs).
--
Adrien.
Other related posts:
