no reboot after updates

[oldgeek]

Re: no reboot after updates

More and more I'm coming to the conclusion that I cut off the kernel update process when I pressed reboot without checking to see if the update process was finished. That might be why grubby can't find the file. Or is the problem due to the fact that Kubuntu was installed using Wubi and grubby can't access a virtual partition? I'm more or less a novice with linux, but sometimes I make good guesses and have fixed a few problems, thanks to the community. I'm a bit frustrated with Kubuntu 9.10. I attempted to upgrade 9.04, but the upgrade crashed at 80% trying to upgrade flash, and I lost some important documents I had foolishly forgotten to back up. It took several downloads to get an error-free image disk. After Wubi installed it, I couldn't get an internet connection. It took 2 weeks to get that resolved, then this happened. I like the OS, but I'm losing my patience with it. Ubuntu, on the contrary, which I installed as the only OS on my laptop, works fine.

[lmilano]

Re: no reboot after updates

I did what you said and got: Error: file not found.

Mmm could you pls check if there is any /vmlinuz in "ls (hd0,5)/"

[lmilano]

Re: no reboot after updates

Ubuntu, on the contrary, which I installed as the only OS on my laptop, works fine.

I think your issue has to do more with real install vs virtual install (Wubi) than anything else ...

[oldgeek]

Re: no reboot after updates

I did what you said and got: Error: file not found.

Mmm could you pls check if there is any /vmlinuz in "ls (hd0,5)/"

No, there is not.

[lmilano]

Re: no reboot after updates

Sorry, I forgot to use the /.
ls (hd0,1)/ gives me a long list of titles which are from the windows partition.
ls (hd0,5)/ shows ubuntu and ubuntu backup, so that's obviously where kubuntu is.

Now all I have to do is just get there...
Thanks again for your interest and help.

Excellent, how about

root=(hd0,5)
linux /vmlinuz root=/dev/sda6
boot

Arggh, grub2 and grub1 use different numbering conventions, and there is a typo there, it should read:

root=(hd0,5)
linux /vmlinuz root=/dev/sda5
boot

[lmilano]

Re: no reboot after updates

I did what you said and got: Error: file not found.

Mmm could you pls check if there is any /vmlinuz in "ls (hd0,5)/"

No, there is not.

Ok, this is broken. Let's try this (just tried this in my mini-9, just for you ). Type:

ls (hd0,5)/boot

This will show you the contents of /boot. Now, one of the entries should be /vmlinuz-VERSION (where VERSION will be some linux version). Then, pls do this:

root=(hd0,5)
linux /boot/vmlinuz-VERSION root=/dev/sda5
boot

That should work. Make sure you replace VERSION by the output you got from ls.

Ok, so where is this Champagne? If this works, please back everything up and get a real install.

[oldgeek]

Re: no reboot after updates

I just tried the first ls (hd0,5)/boot command , and got: error: no file found.
I tried the same command on (hd0,1), with the same results.
Is there any other way of g4tting into my documents file?? The live cd?

[lmilano]

Re: no reboot after updates

I am confused. So, ls (hd0,5)/ shows you /boot, but then ls (hd0,5)/boot fails? It seems unlikely, unless you had a typo when you tried ... (or unless there is something special about that WUbi special partition, etc.

Oh well, this might help though:
https://wiki.ubuntu.com/WubiGuide#Ho...rom%20Windows?

[rick001]

Re: no reboot after updates

Greetings,

I was just doing some updates on my laptop and I saw a thing that caused me to hunt down this thread. What had occurred, looked familiar.

During the first set of updates, I saw the restart icon hit my task bar. I looked at KPackageKit and it was busy... doing something, whatever it is after the updates have been applied. The little blue cylon "Hey I'm working here!" indicator was busy going back and forth.

I continued to play a Solitaire game on my Linux PC. After a few more minutes, nothing had changed on the laptop, status was as it was after the updates were applied. I looked at the "Refresh" button, on the KPackageKit window, and decided to hit it with my mouse. That seemed to have jiggled KPackageKit back into doing something a bit more productive and it ended.

I had seen that the Notification icon was telling me there were more updates to be had, during the updates already being worked on. Ok, before I do those, I will reboot the laptop. The boot process was nothing like I had ever seen before, except maybe with Windoze. I lost count of the number of different screens I saw flash before my eyes. I decided to get back to Solitaire and let the laptop do its thing.

It finally finished booting and got to what appeared to be a usable desktop environment. Every popup tooltip would leave artifacts of themselves behind. I didn't like that. I rebooted the laptop and went back to Solitaire.

The laptop booted no problem this time. I started KPackageKit and had it do its update thingy. It did its thing without a problem this time. I got the restart icon again and clicked it after KPK was gone. The laptop rebooted without any problems.

The moral of this story is: One cannot be hasty when it comes to OS updates / upgrades. One needs to be very observant of what is happening, or not happening, on the screen. Think before one clicks a button in haste: "What will happen if I click on this?" Above all else, one needs to be patient.

Thank you all for your time.

Snowbound in the Mid-West, U.S.A.

Rick

[oldgeek]

Re: no reboot after updates

I am confused. So, ls (hd0,5)/ shows you /boot, but then ls (hd0,5)/boot fails? It seems unlikely, unless you had a typo when you tried ... (or unless there is something special about that WUbi special partition, etc.

Oh well, this might help though:
https://wiki.ubuntu.com/WubiGuide#Ho...rom%20Windows?

Really, I appreciate all the effort and responses I've had on this problem, but in the end I ditched Wubi, gave up the files for lost, and ended up doing a real install job, which it is in the process of doing right now. The boot file on hd0,5 turned out to $boot, and when I used the ls command, it just gave a list of the contents. The problem seems to be with Wubi's virtual disk, from what I've been reading, or something got lost during the update process when I killed it prematurely. I can't call this problem 'solved', but I am resolving it. Once again, I appreciate all the help and wish I really could have broken out the champagne. Oh well...

[lmilano]

Re: no reboot after updates

You know what they say, In victory, you deserve Champagne, in defeat, you need it. Thank you for you kind words though. I still have the warm feeling that we tried, and this is what Free(dom) Software is all about, helping each other. Happy Holidays!

[aiiee]

Re: no reboot after updates

I am confused. So, ls (hd0,5)/ shows you /boot, but then ls (hd0,5)/boot fails? It seems unlikely, unless you had a typo when you tried ... (or unless there is something special about that WUbi special partition, etc.

Oh well, this might help though:
https://wiki.ubuntu.com/WubiGuide#Ho...rom%20Windows?

Really, I appreciate all the effort and responses I've had on this problem, but in the end I ditched Wubi, gave up the files for lost, and ended up doing a real install job, which it is in the process of doing right now. The boot file on hd0,5 turned out to $boot, and when I used the ls command, it just gave a list of the contents. The problem seems to be with Wubi's virtual disk, from what I've been reading, or something got lost during the update process when I killed it prematurely. I can't call this problem 'solved', but I am resolving it. Once again, I appreciate all the help and wish I really could have broken out the champagne. Oh well...

funny no one told you this is a known bug of Grub 2 and the solution is here, entry #160

https://bugs.launchpad.net/ubuntu/+s...in/+bug/477169

There's not much Wubi experience here. Not a slam, just truth. You're better off at the Ubuntu forum for Wubi issues. Good luck!

[oldgeek]

Re: no reboot after updates

Thanks for the tip. I went to the link, found the fix, and didn't really understand what it was trying to do. But as I have uninstalled wubi and reinstalled Kubuntu from the iso image disk, with real partitions and not windows-friendly virtual partitions. So far it's working fine, and starts up much quicker than 9.04 did (wubi-installed), which seem to take forever on the swap disk part of the process. I've been using Kubuntu from 8.04 on, and have made two successful upgrades without reinstalling from scratch. I have not had the same success with 9.10. First of all, the process got stuck at 80% when it hit the flash program. I ended up having to install it using wubi, but then I couldn't get the internet connection to work. After much consultation and trial and error, it's working. Then the update crash and the grub2 problem. Now that I know a little more about Kubuntu, I realize that linux systems can be as problematic as other systems, but at least there are a lot of generous, dedicated people out there trying to fix things as quickly as possible and a whole community of users willing to help dabblers like myself without asking anything in return. So thanks to all of you, and I'll let you know if I have another problem. Case closed.