esdi
11th April 2010, 10:18 PM
Hello everyone,
I am trying to kickstart the F13 alpha from a usb drive.
The usb drive is labeled "disk" and is setup with extlinux and can boot fine.
My laptop has one hard drive (sda) and the only other drive is the usb (sdb)
The ISO is copied on the root of the usb disk
I extract the boot files from the F13 Alpha ISO and copy them on the disk also
cp /mnt/ISO/images/install.img /media/disk/images/install.img
cp /mnt/ISO/isolinux/vmlinuz /media/disk/boot/Fedora/.
cp /mnt/ISO/isolinux/initrd.img /media/disk/boot/Fedora/.
The problem is that when I boot the installation, anaconda has trouble locating some files
The kickstart file:
According to
http://fedoraproject.org/wiki/Anaconda/Options
I can supply the ks boot parameter like this
ks=hd:sda1:/ks.cfg
or
ks=hd:sdb1:/ks.cfg
I expect the usb disk to be sdb but to test i specified sda but neither found the ks file.
Ctrl-Alt-F2 at this point does not go to a shell so how can I find out what exists under /dev?
The label syntax works
ks=hd:LABEL=disk:/ks.cfg
So far I have a workaround but I an curious to know why it failed.
Unfortunately, later on, Anaconda cannot find the install.img file either.
In the text mode interface, I am asked to select a disk (the only option is /dev/sda)
and enter a path (default is / but I also tried /images/install.img)
I tried to boot with these options
ks=hd:LABEL=disk:/ks.cfg repo=hd:LABEL=disk:/ stage2=hd:LABEL=disk:/images/install.img
or
ks=hd:LABEL=disk:/ks.cfg repo=hd:LABEL=disk:/ stage2=hd:LABEL=disk:/
but it did not work either
As the message says, I press F2 to configure additional devices but the installations crashes and I am forced to reboot every time
Is it normal that I can't have a shell at this stage of the installation and how can I tell anaconda where to find the stage2 file on the usb drive
How can I extract the necessary information for filing a bug with this problem
Thanks
---------- Post added at 04:18 PM CDT ---------- Previous post was at 06:24 AM CDT ----------
I found the source of my problem
These parameters do work as expected
ks=hd:/dev/sdb1:/ks.cfg repo=hd:/dev/sdb1:/
They were not working before because of the way I told qemu to access the partition on the usb drive
Wrong
qemu-kvm -boot d -m 1024 -hda /home/sylvain/Desktop/VMGemeni.img -hdb /dev/sdb1 -cdrom /tmp/QemuBootChooser.ISO
Right
qemu-kvm -boot d -m 1024 -hda /home/sylvain/Desktop/VMGemeni.img -hdb /dev/sdb -cdrom /tmp/QemuBootChooser.ISO
Anaconda still can't find the stage2 image by itself with or without this parameter
stage2=hd:/dev/sdb1:/
fortunately, drive /dev/sdb1 is now proposed as a choice in the menu and I can proceed with the installation.
I am trying to kickstart the F13 alpha from a usb drive.
The usb drive is labeled "disk" and is setup with extlinux and can boot fine.
My laptop has one hard drive (sda) and the only other drive is the usb (sdb)
The ISO is copied on the root of the usb disk
I extract the boot files from the F13 Alpha ISO and copy them on the disk also
cp /mnt/ISO/images/install.img /media/disk/images/install.img
cp /mnt/ISO/isolinux/vmlinuz /media/disk/boot/Fedora/.
cp /mnt/ISO/isolinux/initrd.img /media/disk/boot/Fedora/.
The problem is that when I boot the installation, anaconda has trouble locating some files
The kickstart file:
According to
http://fedoraproject.org/wiki/Anaconda/Options
I can supply the ks boot parameter like this
ks=hd:sda1:/ks.cfg
or
ks=hd:sdb1:/ks.cfg
I expect the usb disk to be sdb but to test i specified sda but neither found the ks file.
Ctrl-Alt-F2 at this point does not go to a shell so how can I find out what exists under /dev?
The label syntax works
ks=hd:LABEL=disk:/ks.cfg
So far I have a workaround but I an curious to know why it failed.
Unfortunately, later on, Anaconda cannot find the install.img file either.
In the text mode interface, I am asked to select a disk (the only option is /dev/sda)
and enter a path (default is / but I also tried /images/install.img)
I tried to boot with these options
ks=hd:LABEL=disk:/ks.cfg repo=hd:LABEL=disk:/ stage2=hd:LABEL=disk:/images/install.img
or
ks=hd:LABEL=disk:/ks.cfg repo=hd:LABEL=disk:/ stage2=hd:LABEL=disk:/
but it did not work either
As the message says, I press F2 to configure additional devices but the installations crashes and I am forced to reboot every time
Is it normal that I can't have a shell at this stage of the installation and how can I tell anaconda where to find the stage2 file on the usb drive
How can I extract the necessary information for filing a bug with this problem
Thanks
---------- Post added at 04:18 PM CDT ---------- Previous post was at 06:24 AM CDT ----------
I found the source of my problem
These parameters do work as expected
ks=hd:/dev/sdb1:/ks.cfg repo=hd:/dev/sdb1:/
They were not working before because of the way I told qemu to access the partition on the usb drive
Wrong
qemu-kvm -boot d -m 1024 -hda /home/sylvain/Desktop/VMGemeni.img -hdb /dev/sdb1 -cdrom /tmp/QemuBootChooser.ISO
Right
qemu-kvm -boot d -m 1024 -hda /home/sylvain/Desktop/VMGemeni.img -hdb /dev/sdb -cdrom /tmp/QemuBootChooser.ISO
Anaconda still can't find the stage2 image by itself with or without this parameter
stage2=hd:/dev/sdb1:/
fortunately, drive /dev/sdb1 is now proposed as a choice in the menu and I can proceed with the installation.
