Bug 143983

Summary: mini-iso not bootable
Product: [openSUSE] SUSE Linux 10.1 Reporter: Karsten Keil <karsten.keil>
Component: InstallationAssignee: Steffen Winterfeldt <snwint>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Blocker    
Priority: P5 - None CC: ro, suse
Version: Beta 1   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: test iso

Description Karsten Keil 2006-01-18 23:24:58 UTC
No of the i386 mini-iso from preview4 or the (test) Beta1 mini iso boot on any of my systems. ISO/CD are verified and a test with the 10.0 RC4 mini-iso on the same (RW) CD boot without any problem, so I can rule out any CD writing problems.
Comment 1 Karsten Keil 2006-01-19 00:02:52 UTC
If I compare the ISO images I see following difference:
working 10.0 RC4 is 67137536 bytes  and isoinfo -d -i reports:
Logical block size is: 2048
Volume size is: 32782
El Torito VD version 1 found, boot catalog is in sector 46

The not working SLES-10-i386-Preview4.iso is only 38868992 bytes but reports:
Logical block size is: 2048
Volume size is: 2204449
El Torito VD version 1 found, boot catalog is in sector 458


Comment 2 Karsten Keil 2006-01-19 00:29:22 UTC
Sorry, forget comment #1, I take the wrong image (SLES-10-i386-Preview4.iso) for the isoinfo -d -i output, the isoinfo -d -i output of the not working looks OK.
Comment 3 Steffen Winterfeldt 2006-01-19 10:13:34 UTC
What do you mean? The BIOS doesn't see it as bootable? Or it starts and
gets stuck?
Comment 4 Steffen Winterfeldt 2006-01-19 10:22:27 UTC
I don't see any problems.
Comment 5 Karsten Keil 2006-01-19 11:02:57 UTC
It doesn't detect it as bootable. If I disable HDD boot on one of the affected machines, it display "DISK BOOT FAILURE,INSERT SYSTEM DISK AND PRESS ENTER".

I did some more tests and found out that here are machines which boot from this disk (eg. my laptop and a second P4 system), but 3 other machines does not, the affected machines are very different (AMD K6/400 with PATA CDROM, AMD Athlon with PATA DVD, Intel P4 with PATA DVD).
I verified that the DISK is readable without any error on all these systems, if I boot via a other boot source.



Comment 6 Steffen Winterfeldt 2006-01-19 11:13:44 UTC
> machines, it display "DISK BOOT FAILURE,INSERT SYSTEM DISK AND PRESS ENTER".

Does it display the very same message if you don't have any CD-ROM in the drive?
Comment 7 Karsten Keil 2006-01-19 11:24:50 UTC
Yes.
Comment 8 Steffen Winterfeldt 2006-01-19 11:32:26 UTC
Where did you get the iso from?

And you are *absolutely* sure it is not a broken CD?
Comment 9 Steffen Winterfeldt 2006-01-19 11:41:27 UTC
Created attachment 63971 [details]
test iso

Does the attached iso work?
Comment 10 Karsten Keil 2006-01-19 12:08:51 UTC
Yes this ISO works.
And yes I'm sure that the CDs are OK, I did a dd bs=2048 if=/dev/hdc of=verify
on the none booting machines and then compared verify with the original ISO.
Comment 11 Steffen Winterfeldt 2006-01-19 12:18:24 UTC
Ok, then you have a broken CD.
Comment 12 Karsten Keil 2006-01-19 12:27:40 UTC
Sorry, but what means broken CD ?
Comment 13 Steffen Winterfeldt 2006-01-19 13:17:23 UTC
You can run checkmedia to see if your iso is ok. If that's ok, I suspect
a badly burned CD.
Comment 22 Steffen Winterfeldt 2006-01-19 16:59:56 UTC
Ok, then the result of all this is: the boot catalog must not be
at sector 0x2f.
Comment 23 Steffen Winterfeldt 2006-01-23 15:37:28 UTC
*** Bug 144653 has been marked as a duplicate of this bug. ***