When i powered on my linux machine it goes starting all the processes and what not and it said it failed on some drive mountings I had remember hearing that problem was a known issue with FC6 and the maching proceeded to boot and load just fine.

I than started to download a program for linux i saved it on the desktop, i came back to check on the download and the box saying there are some updates for linux available i accidently clicked update instead of cancel so it started doing its thing, the computer started to run really slow after that, then the program i was downloading came up saying that the folder it was saving to was write protected, it was about 90% done. I was getting these weird blank popup boxes after i tried to change the save location of the file without any luck. The computer ran even slower, so i went restart the system, then it went to the loggoff screen and just sat there with the HD light on and parts of the screen would flicker and it distorted some of the graphics.

I just pressed the reset button now every time it boots i get the Kernel panic error as you can see in my screen shot link.

http://www.kamby.net/IMG_1270.jpg

So is my drive bad, do i need to reinstall FC6?

Any info would be helpful

Thanks

Jason

Hi, I'd guess that your drive is OK, but your root partition has a problem : invalid inode block. IMO there surely is a way to repair it (start out by checking gparted, or knoppix; both liveCDs that have filesystem tools). Never came across this problem personally, so take this only as advice, not a solution.

PS : As last option, I'd suggest formatting the root partition, thus re-installing fedora, but really only as last option.

Or, try booting your install DVD using the "linux rescue" option. Then run fsck on your /boot partition (which, if you've used the Fedora defaults, is the device with partition type 83 when you do a fdisk -l as "root").

Warning: Never run fsck on a logical volume (partition type 8e). Instead, run it on /dev/mapper/... which is where the LV contents are "visible" to tools like fsck.

Here the results of the suggestions i hope i did them right.


Loaded the cd did the linux rescue command, chose language layout. it loaded anaconda, asked to start ethernet said no. Started to find linux installation, pressed continue, searched and said you do not have any linux partitions, system will reboot when you exit shell.

While in shell i did the fsck /boot command on got this same result for /dev/mapper/


Sh-3.1#
fsck 1.39 (29-May-2006)
Warning Couldn't open /etc/fstab No such file or directory
e2fsck 1.39 (29-May-2006) No such file or directory while trying to open /boot

The superblock could not be read or does not describe a correct ext2 filesystem. If the device is vaild and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with alternat superblock
e2fsck -b 8193 <device>

Any ideas i know it installed just fine cause i was able to use fedora for about a week, then this happend. Bad sector maybe?


This computer has been sitting for about a year i decided to fire it up and run linux on it for another Local NAS/FTP server. It originally had xp, it loaded xp just fine when it had been sitting, then i shut it off that night and went to download fedore core 6(i chose fedore cause i have been using reh hat products in the past with good luck)anyway i downloaded the dvd ver went to boot up the machine so i can stick the dvd in and it said my C:\windows\system32 folder was corrupt. So did a format and installed linux worked fine for a few days till i had this problem

Ok, here is what i got when i typed in fdisk -l


Disk /dev/hda: 41.1gb, 41110142976 bytes
255 heads, 63 sectors/tracks, 4998 cylinders
units= cylinder of 16065 * 512 = 8225280 bytes


Device Boot Start End Blocks ID Sytem
/dev/hda * 1 13 104391 83 Linux
/dev/hda 14 4998 400420124 8E Linux LVM

ok i have the same problem, only this time the problem started right after i installed FC5X86_64 on a sata2 drive. I have some fat partitions on the drive and it seams they are ok i can read and write on them(if i boot from an ata hdd i keep just to have backup OS when hell brake loos on my pc). So can somebody help us or is this a FC bug that cannot be fixed like the nvidia radeon problem?
Anyway my fc5 says something like this

Decompressing Linux...done.
Booting the kernel.
RedHat nash version 5.0.32 starting
Unable to access resume device(LABEL=SWAP-nvidia_dde)
mount could not find filesystem"/dev/root"
setuproot: moving /dev failed:no such file or directory
setuproot:error mounting /proc:No such file or directory
setuproot:error mounting:sys: No such file or directory
switchroot: mount failed: No such file or directory
Kernel panic- not syncing: Attempted to kill init!


Thenx
P.S. and just for fun a question :"how in GOD's name can a kernel panic??????"

Problem solved.

After reinstalling FC5 i came to understand that either ext2 or RAID on SATA2 hdd's creates this problem.

Solution (i hope )

Avoid using ext2 partitions and especially deactivate RAID if you want to install FC5 on a SATA2 hdd.

Warning: the solution is not confirmed yet. It seems to be working for now for me, hope it lasts

Regards.

I dont have a sata drive, i have the suse live cd downloaded, im trying to avoid dl too many distros as i am runnning low on dvd's, I havent had the chance to try the knoppix or gparted, which i may try with suse.

The harddrive is a 40gb maxtor IDE drive. Going to try and run the maxtor util to make sure its not a drive failure. When it had xp on it told me the system32 folder was corrupted after the computer had sat for a year or so.

It has an Athlon XP Proc 1.5ghz
512mb ram (memtest86 came back with no problems)
Maxtor 40gb hd
Iomega DVD (i think)
and some MSI motherboard

ok, sorry to say but i just had an maxtor 40 Gb ide drive in one of the computeres i had to repair this week, and i was amaized to see that no mater the Linux distro or the Windows thath i tried to instal after a few restarts it crashed, MBR crashed and a lot of the first clusters got overmagnetised, looked it up and it seames that Maxtor hdds with the capacity of 30-60 may have this problem from the day they where ,,born". so u may be losing important data every time you reboot. (Hope that is not the case)
if that is not the problem, then you need to reset the mount points or so, sorry to say but i don't know how to do that, but maby someone will pop in thei thred and explain how that is done. Anyway search the forum for how to reset mounting points. But i recomend that you try to run a hdd maintenance program on your first 10240 clusters. You can use an FC5 rescue disk and run badblocks, for the exact way of usage try to se an online manual.
Sorry i can't help more.
Hope this advice may help solve your problems......

Windows ran fine on my maxtor drive, it just freaked out with the linux partitions. Unfortunatly and to no surprise the maxtor software doesnt work on linux partitions to check for bad sectors. I was in the proccess of checking out suse 10.2 unfortunalty the power cut out at exactly 100% formated and partitioned on the last partition created during install. Oh well if it still acts up i think i still have some 10gb drive somewhere i'll just throw a couple in there.