My apologies, and thank you.
*I will make a new thread for this one.
Jon-Lars
My apologies, and thank you.
*I will make a new thread for this one.
Jon-Lars
I did the upgrade from 1.7 to 1.8 through the GUI last night and got the same kernel panic message as the original poster (see below). I've tried re-booting the machine, but still get the same message. The cursor sits blinking on an empty line after the message, but I'm not able to type any commands*, even just hitting enter does nothing... I reviewed the link that Andrew posted and did some google searching as well and I think if I could just get to a point where I could type a command line, I could get it working...
*
Also, I inserted an old 1.6 ISO disc just to see what would happen, and it looks like it'll let me install it, but just wondering if there is anything that can be done so I don't have to re-install the OS again (upgrades don't seem to like me very much...). Any help is much appreciated!
*
Kernel panic – not syncing: VFS: Unable to mount root fs on unknown-block (0,0)
Pid: 1, comm: swapper Not Tainted 2.6.35.11-83.fc14.i686.PAE #1
Usually you can press esc during boot and get the grub boot screen. This should allow you to boot an old kernel.
Andrew,
Yes, I just had the wife do this for me and there are 3 different kernels, so I still have hope!* Here are the 3 kernels:
*
Fedora (2.6.35.11-83.fc14.i686.PAE)
Fedora (2.6.35.10-74.fc14.i686.PAE)
Fedora (2.6.35.9-99.fc14.i686.PAE)
*
The first one is giving me the kernel panic error. I had my wife select the 2nd kernel which gives the following error message:
*
/dev/mapper/volGroup-lv_root: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY. (i.e. without -a or -p options)
************************************************** ************************* [FAILED]
*
***An error occurred during the file system check.
***Dropping you to a shell; the system will reboot
***when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
*
If you type Control-D to continue, you get a similar kernel panic error.... I haven't tried providing the password for maintenance or running fsck manually (I'm not sure what that is). I also haven't tried running the last kernel on the list. When I get home tonight, I am going to try booting from the last kernel; if that doesn't work, I was going to try giving the root password for maintenance on the 2nd kernel. Before I move ahead, what do you think the best suggestion is at this point?
I wouldn't bother with the third kernel - it's an old one. First try with the maintenance mode and run fsck on /dev/mapper/VolGroup-lv_root and /dev/mapper/VolGroup-lv_storage devices. If this fails you can try the same with a Fedora Live CD.
Avalx,
What's the downside to running the unit off of the old kernel? Also, what happens to my data if I run the fsck command, is there a possibility of data loss?
Running old kernel is usually OK, but in your case it looks like the problem is with the disk corruption so I guess even the old kernel will have the same problems (of course you can try it anyway). When there is need to run fsck it means that there might be something wrong with the disk so there is no 100% guarantee that there will be no data loss. But without that you are not able to access the disk. The best way would be for you to boot Fedora Live CD and try to copy your data to some other (USB) disk. And then go with the fsck. Of course this will not be possible it the storage disk is damaged. In short there is no way to know if there will be any data loss, but let's be optimistic.
Okay, so none of the kernels would load. I was able to load the Fedora 14 Live cd and get my information though, so I'm good there. I do get an error message that states the drive has many (45 I think) bad sectors and that the drive should be replaced. I ran some diagnostic tests this morning before I left for work, we'll see what happens. Is there any chance that the errors experienced in the upgrade are causing it to think some of the sectors are bad? I'm wondering if I should load the VB 1.8 ISO, or just go ahead and swap out the hard drive first...
Brandon, try to load the 1.8 OS. I have a 1TB here that you can have if you end up needing it....
sonorejr
http://www.sonore.us*
I agree with sonorejr to go with the new ISO, reinstalling will also probably fix disk problems.
On the other hand if you would like to play some more with current situation, you can try some of these: http://www.howtogeek.com/howto.....u-live-cd/ . I had some good experience with the Testdisk utility on Ubuntu.
Posting Permissions
Reply With Quote
Bookmarks