#357 closed bug (invalid)
Recent boot changes broke booting
Reported by: | johndrinkwater | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | System/Kernel | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
boot_loader shows "PANIC: could not mount boot device!"
serial output attached
Attachments (3)
Change History (10)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
Status: | new → closed |
---|
comment:3 by , 19 years ago
Yup, 16917 fixed it :) If you'd still like some additional output (would probably be useful for reference?), i'd be happy to help.
thanks
comment:4 by , 19 years ago
Resolution: | → worksforme |
---|
comment:5 by , 19 years ago
You could turn on tracing in the src/system/boot/platform/bios_ia32/devices.cpp (by defining TRACE_DEVICES), as well as either dumping the device via KDiskDevice::Dump() or printing out its size via KDiskDevice::Size() in src/system/kernel/fs/vfs_boot.cpp:is_boot_device(). Just for reference, and thanks :-)
comment:6 by , 19 years ago
You didn't make the change to src/system/kernel/fs/vfs_boot.cpp - only having one side of the story isn't that helpful in this case, though.
by , 19 years ago
Attachment: | faultyboottracediff added |
---|
serial output with trace on; diffed to the previous
comment:7 by , 19 years ago
attachments.isobsolete: | 0 → 1 |
---|
The log didn't tell me that much, though. Could you try again with hrev16917? I've made the boot device recognition less strict, maybe this fixes it already.
If not, could you add some more debug output to the boot loader and kernel if I tell you where?