Bug 5036 - Recent ISOs cause boot failure on HP6830s notebook
Summary: Recent ISOs cause boot failure on HP6830s notebook
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: release_blocker normal
Target Milestone: ---
Assignee: Anne Nicolas
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-21 00:02 CET by Martin Whitaker
Modified: 2012-05-02 22:47 CEST (History)
7 users (show)

See Also:
Source RPM: syslinux-4.04-2.mga2.src.rpm
CVE:
Status comment:


Attachments
Hardware description (2.10 KB, text/plain)
2012-03-21 00:03 CET, Martin Whitaker
Details

Description Martin Whitaker 2012-03-21 00:02:19 CET
Having successfully installed Mageia 2 beta 2 from the x86_64 DVD on two other machines, I tried to install it on my HP 6830s notebook. With the DVD in the drive, the machine hangs during boot device detection (before reaching the option of entering BIOS setup). It enters an infinite loop trying to access the DVD, which can only be interrupted by power off.

Further investigation shows that the same behaviour occurs with a USB stick (using the same ISO), and also with the x86_64 network install CD (boot.iso) on both a CD and on a USB stick.

More investigation shows that this behaviour starts with Mageia 2 alpha 3, so

Mageia 1          OK
Mageia 2 alpha 2  OK
Mageia 2 alpha 3  FAIL
Mageia 2 beta  1  FAIL
Mageia 2 beta  2  FAIL
Comment 1 Martin Whitaker 2012-03-21 00:03:57 CET
Created attachment 1808 [details]
Hardware description

I've attached a brief summary of the hardware in the affected machine. Let me know if there is any other information that would be useful.
Comment 2 Dave Hodgins 2012-03-21 00:45:20 CET
Try installing the package syslinux, and then running
isohybrid /path/to/iso/mageia-dvd-1-x86_64.iso

Then recopying the iso to a stick.

I noticed previously, that recent iso images have the start of the
first partition listed as sector 0, which is the mbr for the drive.

I didn't report it, as it works ok on my system.

Running the isohybrid command on with it's default settings will
change the starting sector of the partition from zero to 1.

CC: (none) => davidwhodgins

Thierry Vignaud 2012-03-21 18:06:51 CET

CC: (none) => pterjan, sysadmin-bugs, thierry.vignaud
Component: Installer => Release (media or process)

Comment 3 Martin Whitaker 2012-03-21 21:36:14 CET
Thanks Dave. It turns out that the default setting for isohybrid in the cauldron syslinux package is to start at sector zero (which is presumably why recent ISOs are like this). But after running

  isohybrid -o 1 Mageia-2-x86_64-beta2.iso

I now have a USB stick that boots on my HP laptop and is installing as I write.

A quick test shows this has also cured the problem I was seeing on another machine, where it couldn't boot from a USB stick created from the beta 2 ISO, although it could boot from a DVD created from the same ISO.

So the fix for this bug seems clear - revert to an offset of 1 when creating the ISOs. If I have two different machines (from different manufacturers) that are affected by this, chances are that there are many more out there.
Comment 4 Dave Hodgins 2012-03-22 00:09:12 CET
I was quite surprised when I first saw the start sector specified as zero.

In addition to the problem booting, it also causes additional messages
when bootloader-config is running, about a recursive partition tables,
which is what first got me to notice it.

It's clearly a buggy bios though.  The recursive partition should
only affect the boot if the partition type is x'05', extended.  A
bios that looks for a partition chain in any other partition type
is buggy.

I've updated the rpm field, and marked this bug as a release
blocker.

Priority: Normal => release_blocker
Source RPM: (none) => syslinux-4.04-2.mga2.src.rpm

Comment 5 Dave Hodgins 2012-03-22 00:12:09 CET
I should have added, that I think the correct fix is to change
the default offset in isohybrid (also in it's man page).
Comment 6 Dave Hodgins 2012-03-22 01:22:00 CET
s /man page/--help output/ :-)
Thierry Vignaud 2012-03-22 08:30:16 CET

CC: (none) => mageia

Comment 7 Anne Nicolas 2012-03-27 10:56:15 CEST
I will check this. The point is build machine is still using Mandriva 2010.2 so syslinux 3.x.

CC: (none) => ennael1
Assignee: bugsquad => ennael1

Comment 8 Thierry Vignaud 2012-03-27 11:49:36 CEST
Ouch.
Shouldn't it be done in a mgaX chroot when generating the mgaX ISO then?
Comment 9 Anne Nicolas 2012-03-27 11:50:53 CEST
No need for that. But for sure it would be better to have Mageia instead. Anyway build server should moved just after release
Comment 10 Anne Nicolas 2012-03-30 07:21:19 CEST
A test iso (DVD 32) has been provided using new isohybrid options. Boot was successfull and installer launched. bcd has been modified accordingly.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 11 Dave Hodgins 2012-04-07 00:18:09 CEST
The live cd pre-release versions have this problem ...

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           0     1533951      766976   17  Hidden HPFS/NTFS

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 12 Martin Whitaker 2012-04-07 00:35:25 CEST
Also the current boot.iso:

   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1   *           0       34815       17408   17  Hidden HPFS/NTFS
Comment 13 Pascal Terjan 2012-04-07 00:43:15 CEST
They should all have started at 0 since Mageia exists...
I am surprised that some did not.
Comment 14 Martin Whitaker 2012-04-07 01:00:17 CEST
If that is true, there must be some other change that is causing the strange behaviour on my laptop. I've installed many Mandriva and Mageia releases on it from DVD, and it only with Mageia 2 that this problem has appeared.
Comment 15 Pascal Terjan 2012-04-07 01:04:30 CEST
I have checked and it starts at 1 for Mageia 1, but I don't know why.
It used to start at 0 on Mandriva too.
Comment 16 Dave Hodgins 2012-04-07 03:44:38 CEST
If it has a start sector of zero, some machines with a buggy bios will
go into a hard loop, looking for a partition chain, if a drive (hard
or usb) is connected to the computer.

It has to be set to one, or those systems cannot boot.

In addition, it'll cause boot-loader-config to generate messages
about the looping partition chain, if the device is connected
while it's running.
Comment 17 Pascal Terjan 2012-04-07 03:55:48 CEST
I understand, but that does not explain why it was not the case for Mageia 1 iso.

I noticed http://svnweb.mageia.org/soft/build_system/bcd/trunk/BCD/Genisoimage.pm?r1=3225&r2=3224&pathrev=3225

Maybe iso from Mageia 1 were manually hybridified?

It had been done starting at 0 years ago at Mandriva when starting doing hybrid isos so that you can mount the first partition of the usb key, but maybe it was changed since.
Comment 18 Martin Whitaker 2012-04-07 10:56:12 CEST
Checking my DVD collection, it looks like the last version of Mandriva I installed from DVD was 2010.0. This has a start sector of 1. So if the change to hybrid ISOs and a start sector of 0 happened after 2010.0 was released, and Mageia 1 reverted to a start sector of 1 (for reasons yet unknown), that would explain why I have not seen this problem before.
Comment 19 Dave Hodgins 2012-04-07 22:00:14 CEST
(In reply to comment #15)
> I have checked and it starts at 1 for Mageia 1, but I don't know why.
> It used to start at 0 on Mandriva too.

I don't remember it ever starting at 0 prior to Mageia 2.  If you think
about it, how can a partition start at sector 0?  Sector zero is
reserved for the mbr.

If you look at the iso in hexedit, it has the mbr in sector zero,
followed by 63 sectors worth of hex zeros, with the livecd data
starting at offset x8000.  That's the equivalent of sector 64.

Most hard drives have 63 sectors per track.  The iso image is
set to 32 sectors per track.  Obviously syslinux is ignoring
the start sector, so it should be any value other than zero.

May as well go with 1, as that works for Mageia 1.
Comment 20 Pascal Terjan 2012-04-07 22:16:06 CEST
The first partition contains the full iso, the partition table is inside the iso (yes this is a hack but it allows it to work both on a CD/DVD and an USB drive).

It seems I actually added a patch to isohybrid in Mandriva in 2009 to start at 1 but I didn't remember.

I had even blogged about it http://fasmz.org/~pterjan/blog/?date=20090410 :)
Comment 21 Thomas Backlund 2012-04-08 00:10:41 CEST
boot.iso fixed as of drakx-installer-images-1.71-1.mga2

draklive fixed in svn, so next livecds will be ok

Status: REOPENED => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED

Comment 22 Dave Hodgins 2012-04-17 02:27:56 CEST
This bug applies to the current beta 3 pre-release dvd iso image.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 23 Martin Whitaker 2012-04-19 09:05:33 CEST
And also applies to the final beta 3 x86_64 DVD ISO image.
Comment 24 Pascal Terjan 2012-04-25 22:39:14 CEST
Mageia-2-beta3-dual-CD/Mageia-2-beta3-dual-CD.iso1   *           1     1421311      710655+  17  Hidden HPFS/NTFS
Mageia-2-beta3-i586-DVD/Mageia-2-beta3-i586-DVD.iso1   *           0     7051263     3525632   17  Hidden HPFS/NTFS
Mageia-2-beta3-i586/Mageia-2-beta3-i586-DVD.iso1   *           0     7049215     3524608   17  Hidden HPFS/NTFS
Mageia-2-beta3-LiveCD-GNOME-Africa-India-i586-CD/Mageia-2-beta3-LiveCD-GNOME-Af  *           1     1359871      679935+  17  Hidden HPFS/NTFS
Mageia-2-beta3-LiveCD-GNOME-Asia-Noindia-i586-CD/Mageia-2-beta3-LiveCD-GNOME-As  *           1     1357823      678911+  17  Hidden HPFS/NTFS
Mageia-2-beta3-LiveCD-GNOME-Europe1-Americas-i586-CD/Mageia-2-beta3-LiveCD-GNOM  *           1     1398783      699391+  17  Hidden HPFS/NTFS
Mageia-2-beta3-LiveCD-GNOME-Europe1-Americas-x86_64-CD/Mageia-2-beta3-LiveCD-GN  *           1     1431551      715775+  17  Hidden HPFS/NTFS
Mageia-2-beta3-LiveCD-GNOME-Europe2-i586-CD/Mageia-2-beta3-LiveCD-GNOME-Europe2  *           1     1423359      711679+  17  Hidden HPFS/NTFS
Mageia-2-beta3-LiveCD-KDE4-Africa-India-i586-CD/Mageia-2-beta3-LiveCD-KDE4-Afri  *           1     1335295      667647+  17  Hidden HPFS/NTFS
Mageia-2-beta3-LiveCD-KDE4-Asia-Noindia-i586-CD/Mageia-2-beta3-LiveCD-KDE4-Asia  *           1     1435647      717823+  17  Hidden HPFS/NTFS
Mageia-2-beta3-LiveCD-KDE4-Europe1-Americas-i586-CD/Mageia-2-beta3-LiveCD-KDE4-  *           1     1392639      696319+  17  Hidden HPFS/NTFS
Mageia-2-beta3-LiveCD-KDE4-Europe1-Americas-x86_64-CD/Mageia-2-beta3-LiveCD-KDE  *           1     1433599      716799+  17  Hidden HPFS/NTFS
Mageia-2-beta3-LiveCD-KDE4-Europe2-i586-CD/Mageia-2-beta3-LiveCD-KDE4-Europe2-i  *           1     1472511      736255+  17  Hidden HPFS/NTFS
Mageia-2-beta3-x86_64-DVD/Mageia-2-beta3-x86_64-DVD.iso1   *           0     7157759     3578880   17  Hidden HPFS/NTFS
Mageia-2-beta3-x86_64/Mageia-2-beta3-x86_64-DVD.iso1   *           0     7155711     3577856   17  Hidden HPFS/NTFS


It seems LiveCD are OK, dual too but not DVD
Comment 25 Anne Nicolas 2012-04-26 07:53:21 CEST
strange I will check this, thanks
Comment 26 Anne Nicolas 2012-05-02 22:47:35 CEST
bcd bug. Fixed now and tested

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.