I take it all back...

[impp]

Ubuntu 9.10 was OK for a while but now it sucks.

The boot sector keeps corrupting....

First time the grub loader stopped working - no list of operating systems.

Now I get the Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3). It was working fine yesterday!!!

I'm getting fed up of reinstalling it. Good job I use dual boot or I would be really annoyed.

I know we have some true Linux techies here, anyone else had the Kernel Panic issue?

[Hamster_of_sorrow]

Im not sure if he had kernel panic issues, but overclock installed it and had to mess around in command line for 2 hours. he posted in our clan website forum, practically cussing every other word. so i assume he was not happy with it. you are not the only one.

[dip1stick]

there is a problem with 9.10, it seems it is still booting the 9.04 kernel, i would check grub and see what is being loaded, ubuntu forums have more info on this:cuac:

[Froste]

Now I get the Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3).

This means it can't mount the root filesystem, it's trying to load the wrong partition as /

This is the most common result for that message anyway, and it's caused by harddrives either moving position or changing names, either by you physically changing harddrives in your computer (maybe adding or removing one), or it might be a software change in a new kernel (did you update any new packages right before this started happening, in particular a new kernel?).

When grub starts up, highlight the kernel you want to load, and hit the "e" key, you get to edit the boot line then. Find the string root=, and try changing the hd value (hda, hdb, hdc, hde, hdd, hdf etc, or sda sdb sdc etc for sata/scsi drives), though leave the partition number intact.

If you know for sure that the partition it's trying to mount as / is absolutely correct, then it gets a little more complicated. Are you using a raid or lvm setup possibly? Or an encrypted root filesystem?

The filesystem itself might have gotten corrupted (maybe the harddrive is failing), you can test this by booting off a livecd (I assume the ubuntu installer cds would offer this as an option, or a rescue boot option or some such), and trying to mount the partition manually. If it really can't be mounted it could have been damaged in some way, and you'll have to repair it. Most such repairs can be done with minimal data loss.

[Brother-brian]

this is why im still sticking with 8.10, lol.... cause i dont want to lose anything.

[impp]

this is why im still sticking with 8.10, lol.... cause i dont want to lose anything.

Back on Vista for the time being.

From all the forums I've checked it's happening to a lot of people following a system update.

A lot of posts along the root suggestions most incomprehensible though, nearly fried the C: partition first time round, will try again tomorrow.

[Anpu]

My experience with 9.10 is also terrible, but I suggest using 9.04 for a while. If I recall right, its LTS, and very stable atm. No need to go on worse systems, like Vista :P

[kamax]

Ubuntu 9.10 use Grub 2, take care when you want to change something, you are not allowed to edit some files yourself like in the past with grub 1 and you must start one or two command that the files are correctly compiled.
Something like grub-updater and update-mkboot (don't remember well...)

[veluchami]

I too was tempted to update to 9.10, but my instincts (and some other work) saved me from doin it.. hoorah !!! And yes, I heard a lotta complaints about kernel issues on the koala too...

[Vythica]

The 2.6.31 kernel is the best I've seen (added support for a lot of new hardware). 0 problems.