Kubuntu reboots at startup

[Uber Nooblett]

Hey, I just had a small issue with Kubuntu where my net went a bit funny, so, as I usually do when the PC stops responding with the router, I rebooted.

Unfortunately, for some reason, it now wont boot into KDE and instead simply reboots not too long after I hear the pop of my soundcard being activated. I tried loading into the recovery for that Kernel, but it just does the same thing, shortly afterr it shows a message of "recovering journal" or something like that with a bit of text afterwards.

The same prob happened with my Gutsy install which is why I don't currently use it. I'm in Windoze at the moment

Any ideas? help much appreciated

JJ

[opie]

Re: Kubuntu reboots at startup

I don't have an answer but recovering journal suggests a hard drive problem or some corruption. It is very important to know what that "little bit of text" is and whether it is actually ending at that point or whether the journal check is completing.

It looks as if you have a cutting edge system with a huge amount of ram and a raid array, which comlicates things.

You say the same happened with gutsy. If these are recent problems I would first make sure you backup important data, in case you have a hardware problem or an impending failure.

I'm curious as to whether you are using power management settings that are putting the system in a reduced state at some point and it might not be properly recovering from this state.

Also have you ruled out possible heat issues with your hard drives?

[Uber Nooblett]

Re: Kubuntu reboots at startup

Hey, thanks for your response. I believe U have found the offending piece of hardware, though unfortunately this meant I had to resize a partition and create a new boot.

What seems to have happened is that the sata drive onto which I installed Gutsy beta is having some issues. Being as Gutsy beta was installed after my feisty install, it seemed to take ownership of GRUB as root install, therefore, when that drive failed on accessing or mounting, the system rebooted.

I therefore unplugged the drive and decided the best option was to do a fresh install on a 100gb partition on another SATA instead. Naturally, this made the Feisty install completely inaccessible to boot due to file system changes, but should I wish to resolve that it shouldn't be too much trouble.

I just spent the whole of Friday tweaking and customizing the new install and its running smoother than ever before without a hitch. Think I'll be throwing that other SATA in the bin :P

[img width=400 height=160]http://img105.imageshack.us/img105/4637/snapshot1smallfd2.jpg[/img]

[img width=400 height=160]http://img105.imageshack.us/img105/1333/snapshot2smallhz3.jpg[/img]

[img width=400 height=160]http://img267.imageshack.us/img267/7903/snapshot3smalllk7.jpg[/img]