described here OMG i've been LMGTFY :D boot into single mode. enable all the services one by one and check if they come up or hang, you should find the guilty one then. Or boot into runlevel 2 (single + network) and do a yum update, this might fix things as well. First i tried this one: > su > init...

And how exactly do I boot in any of those modes?

when I do: and then reboot, it just stops at the line before:
and visually it hangs on the fedora logo again.

Isn't that what is being show in the first screenshot?

Hey, After spending some time on the #Fedora and #Amahi (with cpg and bigfoot65) IRC I still haven't been able to fix my current problem. I have a Fedora 12 computer for an Amahi media server (NAS). Recently I updated it, but not quite sure if i've rebooted since then. Anyway I rebooted today and wa...

* BUMP *

You mean like this one:
That one gave me the same problems

[root@NAS Data1]# umount /dev/sdb2 umount: /dev/sdb2: niet aangekoppeld [root@NAS Data1]# umount /mnt/Data2 umount: /mnt/Data2: niet aangekoppeld where "niet aangekoppeld" means "not mounted" [root@NAS Data1]# mount -t ufs -o ufstype=ufs2,rw /dev/sdb2 /mnt/Data2 mount: onjuiste ...

I tried a couple of things, but these didn't work, so I must be doing something wrong :-) mount -t ufs -o ufstype=ufs2,rw /dev/sdb2 /mnt/Data2 mount -t ufs -o ufstype=ufs2,ro -rw /dev/sdb2 /mnt/Data2 mount -t ufs -o rw ufstype=ufs2,ro /dev/sdb2 /mnt/Data2 mount -t ufs -o ufstype=ufs2,w /dev/sdb2 /mn...

[root@NAS ~]# cd /mnt/Data1; touch test.txttouch: kan tijdsstempels van ‘test.txt’ niet wijzigen: Bestandssysteem is alleen-lezen In english it would be something like: "cannot change timestamps of text.txt: Filesystem is read-only" So apparently the whole thing is read-only, with folders...