Opened 7 years ago

Last modified 4 years ago

#8104 new bug

Installer installs bootman automatically when it should not, corrupting install.

Reported by: agildehaus Owned by: korli
Priority: high Milestone: R1
Component: Applications/Installer Version: R1/Development
Keywords: Cc: jwlhc172@…
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

DriveSetup has the capability of creating a Haiku volume without using an Intel partition map. You can make the entire drive a Haiku volume.

In fact, I was not aware it could. I thought when selecting the drive and using the menus Partition > Initialize > Be File System that I was creating an Intel partition map on that drive with the first partition taking up the entire space. Unsure if this is a usability issue or just me, but I digress.

Should you wind up creating a Haiku volume spanning the entire drive with no partition map, Haiku will happily install to it. This is fine. What's not fine is that Installer will happily install the boot manager to the drive, automatically, at the end of the file copy procedure. This corrupts the volume.

Rebooting I am presented with a boot manager that sees no Haiku volumes.

Change History (3)

comment:1 Changed 7 years ago by axeld

Priority: normalhigh

IIRC there were already some other people having issues using DriveSetup as intended in this regard. I might even have been one of them at some point, if only I could remember 8-)

In any case, that's a rather stupid bug, thanks for investigating it!

comment:2 Changed 4 years ago by jwlh172

Cc: jwlhc172@… added

comment:3 Changed 4 years ago by pulkomandy

Installer does not install BootMan anymore unless requested. DriveSetup handles adding a boot sector when creating an intel partition map, and Installer makes the partition bootable.

Anything left to do here?

Note: See TracTickets for help on using tickets.