Opened 10 years ago
Closed 8 years ago
#15 closed defect (fixed)
AirBoot destroys logical partitions under certain conditions.
Reported by: | thobor | Owned by: | Ben Rietbroek |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | Boot Manager | Version: | 1.0 |
Keywords: | Cc: |
Description
AirBoot unable to show up when a USB harddisk (500gb) with more than one logical partition is attached at power up. Furthermore, if the disk has more than one logical partition, these partitions are destroyed after such an attempt to boot.
I have three usb harddisks at 500gb, set up with one, two, and three logical partitions respectively. When I power up my new machinery with one of those harddisks containing more than one logical partition attached right from the outset, the booting process stops before AirBoot shows up, displaying the message: "Too many partitions found, AIR-BOOT is supporting up to 45". However, my system contains only 14 partitions, so there is a long way to the 45. The booting process is halted at this point, and the machinery must be turned off and restarted without the usb-harddisk attached. When looking afterwards at the external usb-harddisk in DFSee, the partitions that are following the first logical partition on the disk, have vanished and have been turned into 'bad sectors'.
When the single partitioned HD is attached at boot-up, or when a harddisk that is partitioned into a primary and only one logical partition, is attached in the same way from the very first power-up, the booting process goes smoothly and the usb-disk is left unharmed. When any of the disks is attached during the booting process - at some point after the appearance of AirBoot - there is no halting of the process, and no harm done to the partitions.
Change History (2)
comment:1 by , 10 years ago
Owner: | set to |
---|---|
Status: | new → accepted |
comment:2 by , 8 years ago
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
* This issue is assumed to be fixed *
There is a new release of AiR-BOOT which should fix this issue.
It can be downloaded here: https://github.com/rousseaux/netlabs.air-boot/releases
If this specific issue is *not* fixed, then please create a *new* ticket
here, http://trac.netlabs.org/air-boot/newticket, describe the problem you
are experiencing and insert a *reference* to this issue if you think it is
related.
Happy booting,