dualbooting with f16beta

Adam Williamson awilliam at redhat.com
Thu Oct 13 18:15:20 UTC 2011


On Thu, 2011-10-13 at 11:18 +0200, Moritz Baumann wrote:
> >> disk setup (all sata2/3)
> >>
> >> p1: 120GB gpt windows7 64bit (EFI)
> >> p2: 3TB gpt
> >> ( p3: 3TB (truecrypt volume) )
> >> p4: DVD
> 
> ups its
> p1: 3TB GPT (where 600GB linux and a win data part. should end)
> (p2: 3TB GPT (truecrypt vol))
> p3: 120G GPT window7 EFI
> 
> >> I installed win7 via efi first (with other disks unplugged)
> >>
> >> Now I tried several things (with all disks but p2 unplugged):
> > 
> > It would probably be best to install Fedora via EFI with the Windows
> > disk still plugged in. Just ensure it's not selected as a target disk
> > for installation.
> 
> anaconda throws a
> 
> "you have not created a bootloader stage1 target device"
> 
> as described in
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=739389
> 
> So can I create this partition with parted on disk (p1) (or do I have to
> shrink and move windows partition on (p3)).
> 
> I select /dev/sdc1 as /boot/efi
> 
> parted /dev/sdc print shows:
> 
> Model: ATA Corsair CSSD-F12 (scsi)
> Disk /dev/sdc: 120GB
> Sector size (logical/physical): 512B/512B
> Partition Table: gpt
> 
> Number  Start   End    Size   File system  Name
>  Flags
>  1      1049kB  106MB  105MB  fat32        EFI system partition
>  boot
>  2      106MB   240MB  134MB               Microsoft reserved partition
>  msftres
>  3      240MB   120GB  120GB  ntfs         Basic data partition
> 
> parted /dev/sda print shows:
> 
> Model: ATA WDC WD30EZRX-00M (scsi)
> Disk /dev/sda: 3001GB
> Sector size (logical/physical): 512B/4096B
> Partition Table: gpt
> 
> Number  Start   End     Size    File system  Name  Flags
>  1      1049kB  3146kB  2098kB                     bios_grub
> 
> 
> The bios grub partition is not formated in any way.
> Still the error shows up.

There's reasons other than the existence or otherwise of a BIOS boot
partition that anaconda's 'is this a valid bootloader stage1 target'
test can fail. storage.log should show exactly which sub-tests are
failing for which devices.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net



More information about the test mailing list