update yesterday == no boot today?

[sithlord48]

i did the normal updates yesterday (not really sure what packages but quite a few), any way i restarted my machine and not the kernel just freezes up when booting ,after it mounts my drives if i unplug my network cable i can see messages from it not being able to mount nfs shares (in my fstab) then after the last share the machine just stops doing things, (how ever if i hit crtl+alt+del twice i get a term message then it reboots.) i have no idea why its doing this , that is nothing i have done my self should cause this as i have not done any system changes except for normal updates. thanks in advance

[rb0171610]

Re: update yesterday == no boot today?

A few questions:
Which version of Kubuntu are you using? Are you using a beta version?
If so, this might be expected behavior. Sometimes things are broken, so test software at your own risk. Try restoring your installation from the last known good backup. If you do not make backups, then you should get in the habit of doing so.

[sithlord48]

Re: update yesterday == no boot today?

kubuntu 9.10, and yes it is a beta.although i don't expect much from beta software, and update should never make the machine useable, so i have just formated my root and started over (this is a machine for beta testing so there is nothing really on it.)

i wonder if anyone else had that problem, i got no errors, from it just non bootable machine (even to recovery mode...)

[bossa]

Re: update yesterday == no boot today?

kubuntu 9.10, and yes it is a beta.although i don't expect much from beta software, and update should never make the machine useable, so i have just formated my root and started over (this is a machine for beta testing so there is nothing really on it.)

i wonder if anyone else had that problem, i got no errors, from it just non bootable machine (even to recovery mode...)

Hi
Had the same problem bit scared of updating because I don't want have to keep re-installing. Did a fresh install having my home partition from the previous .Updated and all was well but I notice another update today with some kernel headers and I'm in two minds whether to update...might chance it later

[kevinc]

Re: update yesterday == no boot today?

I'm dual booting Kubuntu Jaunty and Karmic and updating usually daily. There have been lots of udates most days for Karmic but I haven't had any problems booting. As you noted it seems to be linked with mounting nfs shares.

You could try booting with the least number of connections, (such as no network) then add things one at a time and try rebooting to see where the problem is. Often the next lot of updates fix any problems, but if you can't boot, then it's difficult to get the latest updates.

As a matter of interest, are you updating using apt-get, kpackagekit or something else?

[bossa]

Re: update yesterday == no boot today?

Just updated using Kpackagekit (normally Synaptic ) and all went well after reboot

[dibl]

Re: update yesterday == no boot today?

No problems here, except for new kernels required re-installation of video drivers.

If the errors relate to mounting nfs shares, I would open /etc/fstab and comment out the nfs mount lines and try it again. Possibly there is some change handling nfs.

[sithlord48]

Re: update yesterday == no boot today?

the updates were applyed via the kpackagekit auto notify pop up..
what ever the updates changed it broke both the old kernel and the new (at that time) kernel , i had no problems w/ nfs mounting if i had my cable pluged in, when shutting off quiet (in grubs boot options) i could see the last thing it did was to mount my nfs shares then it would lock up.

i did a reinstall of 9.04 on this machine and am currently using it currently, nothing is to broke ne more as /home part was not harmed at all. the only program that complined about opening after a reinstall of 9.04 was amarok (unstandable because i was using v 2.2.0 on 9.10).

[heu]

Re: update yesterday == no boot today?

Notice I am pasting for my post on Ubuntu forum.

I upgraded from a working kubuntu 9.04 to kubuntu 9.10 beta on october the 6th. The Upgrade program downloaded everything and seemed to be going fine until it broke python (at least the error messages were python issues) which prevented the installer to proceed any further, leaving me with a broken system (it wasnt booting anymore, not the old kernel nor the new not completely installed 2.6.31.12). I downloaded the live kubuntu cd, booted from it, mounted the original kubuntu partition and chrooted to it

example:
running kubuntu live open a terminal
then
sudo mkdir /media/kv
sudo mount -t ext3 /dev/sda5 (or whatever your ubuntu partiton is) /media/kv
sudo chroot /media/kv su


now you can try apt-get upgrade (you can try dpkg --configure -a before to aid the recovery just in case there was some packet left unconfigured)

That should finish the upgrade process but if you, just like me, are getting a nightmare of python dependencies or errors with files like __init__.py, CommandNotFound.py, etc (not even apt-get -f install was able to solve the dependencies..and yes I tried Aptitude as well)

what I did was, since the install sources had been downloaded, and apt-get would go through the downloading process finely every time, you can go to /var/cache/apt/archives and do

root@ubuntu:/# ls /var/cache/apt/archives

It will give you a list of .deb files that have failed to install (jn my case there were about 20 packages) . You can install them manually using dpkg -i xxxx.deb starting with python base files and paying attention to the dependency errors, going back to install those packages the one you just tried to install depends upon and so on.

Then you can try

dpkg --configure -a

and

apt-get upgrade (just to see if anything else is required) again, reboot, and you should be fine and have your system back and upgraded

[LinuxRocks]

Re: update yesterday == no boot today?

No problems here, except for new kernels required re-installation of video drivers.

Interesting thing I found today when I did my updates. I though I would have to reinstall the drivers too, because as I booted, I was met with a blank screen and no disc activity. However, when I did a ctrl+alt+del to reboot, all of the sudden, the x server started and I was greeted with a log in screen. Strange. This is repeatable and consistent.

Thoughts?

Joe

[dibl]

Re: update yesterday == no boot today?

I did observe one instance of a hung boot the other day, on my 9.10 system*. The new kernels are incorporating some new "fast boot" features and I have a feeling that sometimes things proceed just a tad too fast. You can use the Alt-SysRq RSEIUB routine to safely restart it.

The black screen thing is obviously related to video -- either it never got to the point of loading the driver, or else the driver misbehaved somehow. I personally am still manually installing the downloaded Nvidia driver -- among other considerations, I can run the Beta version that way. But, you need to settle upon one way or the other and stay with it -- you can't mix 'n match the Hardware Drivers method with the manual installation method, as there will be conflicting files laying around.

Also, I have observed a condition with the Nvidia driver, a few times over several years, when the video driver was "partially" broken. One would think it would either load and work, or not, but the sure sign of the problem is if glxgears won't run. If you think your Nvidia driver is working, but glxgears won't run, the first thing you need to do is reinstall the driver.

* My motherboard, PSU, and CPU hardware is 3+ years old and has been worked pretty hard (running a 17% overclock here ...) -- it is starting to make funny noises on cold boot. So ...

[LinuxRocks]

Re: update yesterday == no boot today?

I personally am still manually installing the downloaded Nvidia driver -- among other considerations, I can run the Beta version that way. But, you need to settle upon one way or the other and stay with it -- you can't mix 'n match the Hardware Drivers method with the manual installation method, as there will be conflicting files laying around.

So, to just recap... To manually install the nvidia driver, I just remove the driver I installed using the jockey utility, save the xorg.conf file, reboot , /etc/init.d/kdm stop, sudo install the driver.bin from nvidia, replace the xorg.conf file and reboot?

Is there any other files to mod like in previous versions of Kubuntu?

Thanks!!!

Joe

[dibl]

Re: update yesterday == no boot today?

To manually install the nvidia driver, I just remove the driver I installed using the jockey utility, save the xorg.conf file, reboot , /etc/init.d/kdm stop, sudo install the driver.bin from nvidia, replace the xorg.conf file and reboot?

That's basically it -- review this: http://kubuntuforums.net/forums/inde...4892#msg164892

Those first steps are necessary to rip out the nvidia-glx-* stuff installed by jockey.

The new command for KDM stopping is

sudo service kdm stop

and use "start" to start it. I guess I should write a new version of the instruction, as that one is getting a little gray-haired at this point. :P

The 190.36 Beta driver is running fine on my 9.10 system -- I can't find any fault with it.

[LinuxRocks]

Re: update yesterday == no boot today?

Ok, I got the 190.32 package installed (That was the latest that they had on the site) and so far all is well.

Did you install the 32bit compat drivers that it offered?

Thanks!!!

Joe

[dibl]

Re: update yesterday == no boot today?



Says 190.36 here: http://www.nvnews.net/vbulletin/showthread.php?t=122606

Right?

YES, I choose "yes" on the 32-bit compatibility. After I've got a good working xorg.conf, I choose "no" to have it overwrite it on a subsequent driver installation.