Opened 8 years ago
Closed 7 years ago
#26 closed defect (fixed)
AirBoot displays wrong LVM-drive info when booted with usb-stick inserted
| Reported by: | Ben Rietbroek | Owned by: | Ben Rietbroek |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Boot Manager | Version: | 1.0 |
| Keywords: | lvm | Cc: |
Description
Situation:
Multiple OS/2 installations on same drive-letter.
One of them is a PRI partition.
Without stick inserted the drive-letters display OK.
With stick inserted, bogus drive-letter displayed or wrong LVM-hidden status.
Looks like something goes wrong with getting info from Master LVM-record.
Change History (3)
comment:1 Changed 8 years ago by
| Owner: | set to Ben Rietbroek |
|---|---|
| Status: | new → accepted |
comment:2 Changed 8 years ago by
comment:3 Changed 7 years ago by
| 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,
Ben.
[BIOS geometry of an USB-stick]
The geometry of an USB-stick is determined by the BIOS.
Many BIOSses do *not* use the geometry exposed by the USB-stick, but do some
BIOS-specific translation. So, when an USB-stick CHS is queried using INT13,
these values differ from BIOS to BIOS!
Much of the CHS-code in AirBoot? assumed the BIOS CHS-values were usable, which
is kinda true for regular harddisks, which almost always expose 255/63 geometry.
But for USB-sticks the BIOS CHS-values are *not* usable because of the mentioned
BIOS-specific translation, that does *not* reflect the USB-exposed geometry.
(And even the USB-exposed geometry is often *not* the one used when partitioning)