UGH just upgraded to Hardy and having an issue!

[andyho]

I've waited quite some time before upgrading to Hardy.. heck, I barely had Gutsy running good after finally getting Feisty all worked out! But now I've got...

"init rc-default main process (5731) killed be SEGV signal"

after upgrading! I'm assuming it might have something to do with my nvidia drivers? I always seem to have problems with them. But just in case it's not the drivers, any other ideas? Thanks!!

[cmnorton]

What is your hardware configuration?

[stchman]

I've waited quite some time before upgrading to Hardy.. heck, I barely had Gutsy running good after finally getting Feisty all worked out! But now I've got...

"init rc-default main process (5731) killed be SEGV signal"

after upgrading! I'm assuming it might have something to do with my nvidia drivers? I always seem to have problems with them. But just in case it's not the drivers, any other ideas? Thanks!!

Did you go the upgrade route or did you do a clean install? I recommend a clean install as it is faster and less likely to give errors.

[andyho]

Did you go the upgrade route or did you do a clean install? I recommend a clean install as it is faster and less likely to give errors.

No, of course I went the upgrade route.. UGH! My own dumbness there...

[andyho]

Ok.. so here's EXACTLY what I get at bootup..

*Setting the system clock
Segmentation fault
*Loading kernel modules... [OK]
*Loading manual drivers... [OK]
*Setting kernel variables...
*Activating swap...
...done.
mount: you must specify the filesystem type
*Cannot check root file system because it is not mounted read-only
Segmentation fault
*Starting early crypto disks... [OK]
*Starting remaining crypto disks... [OK]
*Checking file systems...
1207
fsck 1.40.8 (13-Mar-2008)
[OK]
Segmentation fault
Segmentation faultfilesystems...
[OK]
*Activating swapfile swap... [OK}
*Checking minimum space in /tmp... [OK]
*Skipping firewall: ufw(not enabled)... [OK]
*Configuring Network interfaces... [OK]
init:rc-default main process (5254) killed by SEGV signal


So is it that I have a bad mount point??

CMNORTON: How can I get my hardware configuration to all show? I tried lshw, but I could only see part of it.

If I kill X-server I can log in.. so I'm hoping it's something that's still fixable!!

[andyho]

Even more info... I've tried booting into other kernel's but no such luck there. However, I did just get this to show up..

*Checking root file system...
1207
...fail!
*An automatic file system check (fsck) of the root filesystem failed. A manual fsck must be perfomed, then the system restarted.
The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode.
*The root filesystem is currently mounted in read-only mode.
A maintenance shell will now be started.
After performing system maintenance. press ctrl+d to terminate the maintenance shell and restart the system.
bash: no job control in the shell
bash: groups: command not found
bash: lesspipe: command not found
bash: Command: command not found
bash: The: command not found
bash: dircolors: command not found
bash: Command: command not found
bash: The: command not found

HTH some more... still trying to figure what's causing this...

[philinux]

when you hit the cli type

fsck -v

the -v switch is for verbose.

[andyho]

when you hit the cli type

fsck -v

the -v switch is for verbose.

Ok when I do that I get..

/dev/sda1 is mounted.

WARNING!!! Running e2fsk on a mounted filesystem may cause SEVERE filesystem damage.

Do you really want to continue(y/n)?

Do I?!? LOL!

[andyho]

Hmm I just noticed something weird.. one minute it had me as root for some reason, that's when it gave me what I last posted.. This time though it says...

andyho@andyho-ubuntu:~$ fsck -v
fsck 1.40.8 (13-Mar-2008)
fsck.ext3: Unable to resolve 'UUID=bfcf5100-02eb-4274-b599-72545d15005'

?!?!

[andyho]

anyone?!?