Description of Problem: when the root partition is uncleanly unmounted (hard system reset), the rc.sysinit script somehow forces a fsck on the partition instead of allowing for journal reconstruction. Version-Release number of selected component (if applicable): How Reproducible: Every time. Steps to Reproduce: 1. reset running system with "/" as ext3 2. upon bootup, the message "Press Y within X seconds to force ...", do nothing 3. Actual Results: theorectically, the system should skip the fsck and mount the ext3 partition, allowing the ext3 journaling code to reconstruct the journal. This doesn't happen. Expected Results: Additional Information: This bug is corrected in the 7.3 initscripts. I even tried forcing the AUTOFSCK_OPT option to NULL, still ended up getting a fsck'y. Anyway, I've upgraded my laptop to 7.3 and the expected behavior is present. I tried diffing the .rpmsave version which I would assume is the one that was here before the upgade (although I won't swear to that). They are exactly the same. <shrug>
Odd. Did your 7.2 initrd have ext3 in it?
I don't recall. I did an upgrade from 6.2 to 7.2 and selected ext3 for my "/" partition when the installer promted me to convert to ext3. My filesystem was / == ext3 and /boot == ext2 on the 7.2 system. I do not know what was contained in my initrd for the 7.2 system, it would have been what ever was installed by the 7.2 upgrade process. I don't recall if I upgraded my kernel rpm or not. If I did upgrade it, then I didn't build a new initrd. Assuming I did upgrade my kernel rpm and didn't build a new initrd, would that have been able to cause this? The ext3 filesystem was operating as ext3 according to my boot logs, I remember watching that stuff.
*** Bug 105617 has been marked as a duplicate of this bug. ***
Closing bugs on older, no longer supported, releases. Apologies for any lack of response. If this persists on a current release, such as Fedora Core 4, please open a new bug.