being tired of the dracut selinux infinite loop, i've decided this morning to reinstall f18 from f18 x86 netinst disc. all attempts to boot with standard options failed with a kernel crash (maybe my video card is broken). i eventually managed to reach anaconda by booting in safe graphics mode. there, i've completed the steps required (what is the target device, what software, time zone) then pressed continue. then, i've been hit by this:
https://bugzilla.redhat.com/show_bug.cgi?id=857607 . I've seen this before on same system in the previous 5 (?) years so that was not a big surprise. a big surprise was that after i reboot, something messed my existing linux partitions (actually one of them is missing). what do i mean by 'messed'? well, first, grub2 fails to load a menu saying that "no such partition" and offers a grub shell. then, in f17 rescue mode, the system complains that i have no linux partitions. going to rescue mode's shell, the partitions are marked "Linux", but the last one (#7) is missing. then i booted system rescue cd. there, mount /dev/sdb{1,5,7} /mnt/mountpoint ended with something similar to "broken ntfs signature". adding -t ext3 in the mix didn't help, error was something like "bad superblock etc".
THIS is something i don't remember to have ever seen on fedora (alpha, beta or final).
from personal experience, i believe something is deeply wrong in the anaconda logic. and of course, the back and forth mess is also a problem. why not just continue to the next required step, with back being an option, and at the end present a summary of completed and incompleted steps, if any?
btw, on systems with many hard disks (at least 2), if linux/anaconda is unable to tell which is the first hard disk system will boot, why not install grub on all hard disk, just to be sure?
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
