[DragonFlyBSD - Bug #1407] (Resolved) disklabel64 boot problem

Thomas Nikolajsen via Redmine bugtracker-admin at leaf.dragonflybsd.org
Mon Oct 8 00:08:28 PDT 2012

Issue #1407 has been updated by Thomas Nikolajsen.

Status changed from New to Resolved
Assignee deleted (0)

(don't remember why I kept this one open)
Bug #1407: disklabel64 boot problem

Author: Thomas Nikolajsen
Status: Resolved
Priority: Normal
Target version: 

Booting DragonFly from disklabel64 slice has problems:
 - using HAMMER it almost works: one module can't be read
Reading /modules/acpi.ko fails; after booting (host can run without ACPI)
(i.e. by kernel) acpi.ko can be read and contents is correct.
(files on test HAMMER system are just cpdup'ed from a working system;
cmp verified acpi.ko is readable and has same contents)

Also doing ls command in loader on HAMMER file system can crash loader.
It seems like libstand/hammerread has an issue.

 - using UFS it doesn't work: I just see a spinning bar
It doesn't show any text, like BTX..

I had the impression that disklabel64 booting should be working
(since commits below); is this correct?


Is zeroing slice start before making bootable disklabel still needed?
If yes: is it enough to zero 16KB, like disklabel32.

I was going to update disklabel64.8 to include boot info again;
but will hold it back until this issue is resolved.

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

More information about the Bugs mailing list