Fedora 11: Boot freezes at setting hostname
 

Hi all,

A few hours ago I was doing some heavy IO between two hdd's on my system and, from what I can tell, the screensaver tried to come on and X locked up. I ssh'd in from another computer and rebooted the system. But dring the boot process when Fedora starts starting service, after setting the hostname it outputs the previous output again and then freezes (see picture below).
I have never seen anything like this and don't even know where to begin to try and fix it. Any help is awesome especially since, as it stands, this computer is essentially useless.
I'm running an encrypted, updated Fedora 11 64bit.

http://i.imgur.com/prmOh.jpg

Anyone? Problem still persists.
A few more details are available on my thread at the Fedora Forums.
http://forums.fedoraforum.org/showth...53760&posted=1

I'm running an encrypted, updated Fedora 11 64bit.
-------------------
on an encrypted disk the easiest way might be to restore from a good back up .

what were you doing ( that is what were you moving from one disk to the other )
from the fedora forum

were you running an update when you rebooted ?
if so that might be very bad .

According to the yum logs, the only packages that were updated yesterday (the day the problem started) were the X-screensaver packages although I do not believe the update process was running when I rebooted. Would screensaver packages even be able to prevent the system from booting? I mean, if they are associated with X, how could they cause the boot to fail at such an early stage even when X has not yet been started?

I recently bought a larger hdd to keep my home directory on so I was copying my home directory to the new drive. But the thing is, my current home directory is on another drive than where / is. So there was no more IO going on with the drive / is on than usual.

There is nothing in the boot log, the kernel log, or the yum log to go off of. :confused:

Well it turns out that my / filesystem is severely corrupted despite fsck reporting it is clean. I still have no idea how this happened but it seems like a good time to do a clean install and upgrade to Fedora 12.