Red Hat Bugzilla – Bug 80571
Created boot Floppy disk incorrect
Last modified: 2007-04-18 12:49:20 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
Description of problem:
I've got XP Pro on /dev/hda and already had to repair it once because of grub,
so I decieded to to use a boot floppy to start this installaion. Only the boot
disk loads vmlinuz fist and then initrd which is backwards so the root
installation on /dev/hdb2 never runs/loads.
I've tried editing the syslinux.cfg file on the boot disk to no avail.
Version-Release number of selected component (if applicable):
Did some more investigation by downlaoding the latest version and version 1.65
of syslinux and creating bootdisk for each version. It didn't work. So
syslinux must handle initrd transparently in version 2.00. The last line in the
boot up process is:
RAMDISK: Compressed image found at block 0
and there she hangs. So it must be the image. I think.... I've tried giving
it the root param on the command line and it didn't help. At this point I'm at
a loss. This behavior is with both versions of syslinux.
Is your floppy full?
Not quite, 512 bytes free.
Done some more work on this little thing.
In a dos box in XP with the flopy disk in drive a: and the CD1 mounted I went
rdev a:\vmlinuz 3 67
This was done from the dosutils directory and used the parameters for that
partion since my root partion for Linux is /dev/hdb3.
On booting it worked until the point where it is trying to mount the root
filesystem. It becomes apparent that it's trying to use resierfs instead of
ext3 for the filesystem driver.
I thought that the Redhat default filesystem was to format as ext3. So why
does the floppy have the resierfs filesystem driver compiled in? Could someone
at RedHat create a bootdisk that has the ext3 filesystem driver compiled in?
don't use rdev on your boot disk.
lots of this changed lately - try everything again in the next beta