Bug 447323
Summary: | Snake renders F9 system unbootable (GRUB GRUB GRUB..) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Will Woods <wwoods> |
Component: | snake | Assignee: | James Laska <jlaska> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 9 | CC: | jturner, wwoods |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-06-21 14:59:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Will Woods
2008-05-19 14:57:41 UTC
Interestingly I've seen similar complaints from people using Hibernate for the first time after boot. Maybe there's a deeper problem with GRUB? Greetings Will. Can you note the version of snake used, the architecture you're seeing this on, and any cmdline arguments used? Any chance you have the {grub,yaboot,elilo}.conf before rebooting? Thanks! James I'm using the F9 default snake - snake-0:0.11-0.5.fc9. grub.conf exists (and looks normal) before reboot. Workaround is to boot media into rescue mode and run: chroot /mnt/sysimage grub-install /dev/sda Which doesn't change grub.conf. So it's kind of perplexing. Not able to reproduce on F-9 i386, x86_64 or ppc so far. Anything funky about the environment (e.g. kvm, qemu, bare metal, vmware)? Is there a non-default partitioning setup involved (e.g. grub on a partition instead of MBR)? Would you mind attaching the grub.conf and maybe /var/log/anaconda.log from the previous install? Thanks! Bare metal machine. The only thing of note about the partitioning is that there's no /boot partition - we've got / and swap and that's it. Happens on i386 and x86_64. Rats, no luck reproducing using the environment specified in comment#5. Any chance I can get access to the system you're seeing this on? |