Description of problem: Newly install FC6T3 system on x86-64 doesn't boot successfully. It boots and immediately automatically reboots. Suspected Kernel/File system (file system misdetection) issue. Version-Release number of selected component (if applicable): FC6T3, 2.6.17-1.2630.fc6 How reproducible: Always. (3 times proven) Steps to Reproduce: 1. Install 2. Boot 3. Observe it to reboot during the bootup sequence Actual results: Automatically reboots. Expected results: To bootup successfully. Additional info: Refer to serial console captured kernel logs. It'd seem ext3 file system is being accessed as ext2, as confirmed by EXT2-fs & SELinux messages. A few times, during the installation procedure, I've confirmed that the file system selection was indeed ext3 & also subsequently, by switching to a virtual console, confirmed that the choosen file system was indeed mounted as ext3 by consulting kernel logs (ie, EXT3-fs & SELinux messages of the installation kernel).
Created attachment 136989 [details] FC6T3 kernel dmesg
I too experienced this. I used the x86-64 DVD. I have an Asus M2V, with a VIA K8T890 chipset. I was able to use the i386 DVD to get a working system. Initially I couldn't get the x86-64 DVD install to work. I checked bugzilla and found someone with a similar problem, and the resource asked if them if there were any ReiserFS partitions. They replied yes, so I deleted my ReiserFS partition and then the install worked. I formatted the partition as an ext3 partion. However, once the install completed, the automatic reboots occurred. I had four primary partitions: Windows XP 64 NTFS (1), Swap (2), ext3 (4), and a Fat32 (3).
Could it be because it lacks an initrd image? (there's no initrd file on x86-64 installation, while there's one on x86) Thanks
Creating initrd image manually solved the problem. (1. Bbooted on rescue mode [using the DVD] 2. Located the right FC6T3 system, & had it mounted by the rescue program 3. Chrooted to that system 4. Created an initrd image 5. Added a ref to it in the grub boot loader 6. Booted the system successfully :-)) It'd be a good idea for FC6 installer to create the initrd image & a ref for it in the boot loader. Thanks
The lack of an initrd was an anaconda bug in test3 that should now be fixed.