FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Yesterday I had run Kstars for the first time.. seemed to be working fine for a while..then i was scrolling round and got a lockup... totally.. numlock didn't work or anything...
then after a few minutes it cleared itself up. but nothing was writable, or readable.. ie i couldn't browse either my /home or even smb:// locations.
so i ctrl + alt + f2'd into a prompt,
at this time, alot of error messages were scrolling up screen, but messages like this happened before so i just ignored it. i could just type round it.
so i logged into root, and issused /sbin/shutdown -h now and the pc turned off. (after absolutely every shitdown procedure failed)
so i powered it back up and get the following error:
Quote:
Red Hat nash version 4.1.18 starting
JBD: failed to read block at offset 4360
EXT3-fs: error loading journal
Update - Just tried fedora dvd, I can get into linux rescue ok.. didn't try mounting file systems. Thought i better see what i'm supposed to do before i make it worse
ok, somehow the HD boot is not working. there is a problem with the read/mount process in your linux partition.
with the cd you can check if the partition is detected and read. this kind of error comes from a bad umount process during shutdown. anyway sounds weird, considering how you made it. should not happen. i don't know fedora but i thinks there must be a possibility just to boot from the cd and get a prompt for your linux partition.
that is the advice.
More info if you want it... I booted off a Knoppix 3.6 cd to backup my data.
When i logged out i got the folllowing error:
Cloop read error at pos 11823235 in file /cdrom/knoppix/knoppix 19783 bytes lost.
cloop error -3 uncompressing block 1056 65536/0/19783/0 11323265-11843018
and that was scrolling up the screen mighty fast. only stopped with it INIT id "1" scrolling too fast or something so pausing for 5 mins... i just reset the pc.
newbie here also.
so, let's return to knoppix. you could back up your data with knoppix?
it means that there was no boot errors? can you insert the cd again and start the system once more.
after that at a shell prompt can you post the output of
Code:
dmesg | grep -i ext
dmesg | grep -i journ
i just want to check if there is something wrong mounting your root partition.
did you try to boot with your FC3 cd? do you get a prompt?
i am also a newbie. hope some guru can join us here.
Sorry haven't replied for a while.. i'm moving house tomorrow, just been packing up and stuff... will try and do the above today.
Not sure about my net situation for a while at the flat.... So i'm still around, just unplugged :P
Yesterday I had run Kstars for the first time.. seemed to be working fine for a while..then i was scrolling round and got a lockup... totally.. numlock didn't work or anything...
then after a few minutes it cleared itself up. but nothing was writable, or readable.. ie i couldn't browse either my /home or even smb:// locations.
so i ctrl + alt + f2'd into a prompt,
at this time, alot of error messages were scrolling up screen, but messages like this happened before so i just ignored it. i could just type round it.
so i logged into root, and issused /sbin/shutdown -h now and the pc turned off. (after absolutely every shitdown procedure failed)
so i powered it back up and get the following error:
and then it just hangs there.
How can i get this running again please?
I ran into the same thing today with Fedora Core 4. I wasn't running anything out of the ordinary...I did try the "eject" command about five minutes prior to my disk becoming completely READ ONLY! And I was running the initial instance of vmware server while the file system became read only. After rebooting I got the JBD: failed to read block # error. When fsck ran it encountered a lot of errors. Right now I'm in the middle of a big backup with Knoppix.
i ran into similar problem but on redhat 5 (RHEL). i figured out that i had just edited grub.conf where i had renamed the OS to windows xp from others. So, i logged into rescure mode, switched to root and then edited the grub.conf file back original as others from windowx xp. Rebooted the system n back in business - this is first time i have ran into this kind of a problem - earlier i played around with this config file without any issues..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.