Re: EFI install (F15 beta rc2)
El dl 18 de 04 de 2011 a les 09:12 -0400, en/na James Laska va escriure: On Sun, 2011-04-17 at 12:41 +0200, Josep Puigdemont wrote: Hi, I followed the instructions for installing FC15-Beta (RC2) on an EFI system, and can confirm that the Testcase Boot Methods efidisk.img passed without problems, at least for x86_64. Can I put a check mark on that test [1], or should someone from the QA team do that? Please feel free to add your result. Thanks for testing! Done! Then I also want to report a couple of issues: The installation went smoothly, but when it finished and was about to reboot, the kernel panicked (didn't copy the stack trace sorry). I don't know if this is a known issue, I could file a bug report if you feel it's necessary. I'm not aware of any kernel panics on reboot. Unless we can get the stack trace, I don't think it's worth filing a bug at this point. I could also reproduce this issue with the final Beta released today, filed it here: https://bugzilla.redhat.com/show_bug.cgi?id=698004 Then I run into a problem when booting Fedora, as it just brings me to the grub prompt. I figured grub wasn't able to read the config file, but that doesn't seem to be the case. The grub.conf file in the EFI partition seems fine. Then I tried to manually type at the grub prompt the relevant commands I found in grub.conf: grub device (hd0) HD(...) grub root (hd0,1) Error 5: Partition table invalid or corrupt. That error seems a bit odd, as the partition table appears to be fine when I boot from a live CD disk (it's anaconda's default partition table). To test further, I did the EFI install of F14 and found the same issue. Could it just be a problem with my hardware, perhaps? Any pointers on how to debug the issue would be appreciated. Booting the installer with 'rescue' would be good. You can then have it locate your system partitions, and you can access installation log files. Those files will help ensure that the installer did everything right (/root/*log and /var/log/anaconda/*). Those files, along with 'parted' output, will help determine how your disk(s) are partitioned. I have access to all this information from the drive. I didn't see anything suspicious in the logs, but on the other hand I don't know what I should be looking for :) It's probably best that I file a bug. What component should that be, anaconda or grub? I guess the latter, but it doesn't hurt to ask. And what are the relevant log files I should attach, all of them? Do you recall where you directed the installer to write the bootloader? I just let the installed decide, but since there is only one HD, I suppose it used /dev/sda. If you have time, I might suggest doing a non-EFI install with the same partition selections, and compare results. If the problem only happens with EFI installs, that'll help narrow down the issue. Done. With a non-EFI install everything worked fine. I can boot without problems, so it seems to be only an issue with the EFI install. Thanks! /Josep -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: EFI install (F15 beta rc2)
On Sun, 2011-04-17 at 12:41 +0200, Josep Puigdemont wrote: Hi, I followed the instructions for installing FC15-Beta (RC2) on an EFI system, and can confirm that the Testcase Boot Methods efidisk.img passed without problems, at least for x86_64. Can I put a check mark on that test [1], or should someone from the QA team do that? Please feel free to add your result. Thanks for testing! Then I also want to report a couple of issues: The installation went smoothly, but when it finished and was about to reboot, the kernel panicked (didn't copy the stack trace sorry). I don't know if this is a known issue, I could file a bug report if you feel it's necessary. I'm not aware of any kernel panics on reboot. Unless we can get the stack trace, I don't think it's worth filing a bug at this point. Then I run into a problem when booting Fedora, as it just brings me to the grub prompt. I figured grub wasn't able to read the config file, but that doesn't seem to be the case. The grub.conf file in the EFI partition seems fine. Then I tried to manually type at the grub prompt the relevant commands I found in grub.conf: grub device (hd0) HD(...) grub root (hd0,1) Error 5: Partition table invalid or corrupt. That error seems a bit odd, as the partition table appears to be fine when I boot from a live CD disk (it's anaconda's default partition table). To test further, I did the EFI install of F14 and found the same issue. Could it just be a problem with my hardware, perhaps? Any pointers on how to debug the issue would be appreciated. Booting the installer with 'rescue' would be good. You can then have it locate your system partitions, and you can access installation log files. Those files will help ensure that the installer did everything right (/root/*log and /var/log/anaconda/*). Those files, along with 'parted' output, will help determine how your disk(s) are partitioned. Do you recall where you directed the installer to write the bootloader? If you have time, I might suggest doing a non-EFI install with the same partition selections, and compare results. If the problem only happens with EFI installs, that'll help narrow down the issue. Thanks, James signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
EFI install (F15 beta rc2)
Hi, I followed the instructions for installing FC15-Beta (RC2) on an EFI system, and can confirm that the Testcase Boot Methods efidisk.img passed without problems, at least for x86_64. Can I put a check mark on that test [1], or should someone from the QA team do that? Then I also want to report a couple of issues: The installation went smoothly, but when it finished and was about to reboot, the kernel panicked (didn't copy the stack trace sorry). I don't know if this is a known issue, I could file a bug report if you feel it's necessary. Then I run into a problem when booting Fedora, as it just brings me to the grub prompt. I figured grub wasn't able to read the config file, but that doesn't seem to be the case. The grub.conf file in the EFI partition seems fine. Then I tried to manually type at the grub prompt the relevant commands I found in grub.conf: grub device (hd0) HD(...) grub root (hd0,1) Error 5: Partition table invalid or corrupt. That error seems a bit odd, as the partition table appears to be fine when I boot from a live CD disk (it's anaconda's default partition table). To test further, I did the EFI install of F14 and found the same issue. Could it just be a problem with my hardware, perhaps? Any pointers on how to debug the issue would be appreciated. Thanks, /Josep [1] https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test#General_Tests -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: EFI install (F15 beta rc2)
Partition table invalid or corrupt. I saw this message from GRUB when I re-used a disk that had been part of a software RAID array for a Fedora installation. I do not recall now whether fdisk or the Fedora installer wrote a new partition table, but there were vestiges of the RAID format left on the disk that confused GRUB, even though fdisk displayed the expected partition table. I used parted to explore, and it reported the inconsistency. Ultimately, I zeroed the beginning of the disk, wrote my desired partition table, and installation of Fedora then succeeded. If you do not have a similar disk history, my experience may not explain why you have this problem. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: EFI install (F15 beta rc2)
El dg 17 de 04 de 2011 a les 09:30 -0400, en/na Richard Ryniker va escriure: Partition table invalid or corrupt. I saw this message from GRUB when I re-used a disk that had been part of a software RAID array for a Fedora installation. I do not recall now whether fdisk or the Fedora installer wrote a new partition table, but there were vestiges of the RAID format left on the disk that confused GRUB, even though fdisk displayed the expected partition table. I used parted to explore, and it reported the inconsistency. Ultimately, I zeroed the beginning of the disk, wrote my desired partition table, and installation of Fedora then succeeded. If you do not have a similar disk history, my experience may not explain why you have this problem. Thanks for the reply, Richard. The disk did had a previous partition layout, although it was not part of a RAID array. I checked with parted and gdisk, but neither complained about the partition table, and both agreed on this layout: Number Start End Size File system Name Flags 1 1049kB 211MB 210MB fat16 boot 2 211MB 735MB 524MB ext4 3 735MB 1000GB 999GB lvm When booting the Live CD, it actually activates the swap partition that anaconda created in the LVM partition. It is also possible to manually mount the different partitions in the disk, so I guess the partition table is healthy. regards, /Josep -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
