LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (http://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Can not boot to OS, how do I update? (http://www.linuxquestions.org/questions/linux-newbie-8/can-not-boot-to-os-how-do-i-update-753954/)

widget 09-09-2009 02:58 PM

Can not boot to OS, how do I update?
 
I have an install of Ubuntu 9.10 (alpha testing) that will not boot. I think that if it were updated it would work.

I need to do this with a liveCD or another OS on the drive.

It seems that I should be able to get control of the wayward bugger and update it. Something like this must be common usage fore servers but I have not got a clue.

Can some kind soul explain the procedure to me? Or tell me I am just full of male bovine excrement?

Thanks

yancek 09-09-2009 03:06 PM

Quote:

I have an install of Ubuntu 9.10 (alpha testing) that will not boot.
Just installed? Never booted? Booted one or more times and stopped? Only OS on the machine?

Quote:

I think that if it were updated it would work.
If what (it) was updated? The install? kernel?

Grub (I assume you are using Grub?) usually gives error messages, did you get any? If so, what were they? If your Ubuntu is not the only thing on the machine, it would help if you posted the output of sudo fdisk -l.

widget 09-09-2009 03:46 PM

Quote:

Originally Posted by yancek (Post 3676273)
Just installed? Never booted? Booted one or more times and stopped? Only OS on the machine?


If what (it) was updated? The install? kernel?

Grub (I assume you are using Grub?) usually gives error messages, did you get any? If so, what were they? If your Ubuntu is not the only thing on the machine, it would help if you posted the output of sudo fdisk -l.

It was booted and updated for several weeks. There is a problem with ATI cards and the kernal that are being worked out. There was an update a week ago that brought this kind of problem to all of the variations that I have on the drive. They would, with a little editing, boot to a CLI login and I could update them and eventually get them to work. This one seems more screwed than the rest.

I believe that if I run a full update, which will include a new kernal, that it will boot.

I have 11 OSs on that drive, 5 including the bad one, are 9.10A5 variations.

Grub2 is what I am usig to boot that drive. The message on this OS is "file not found".

The OS is there, I can get into it with nautilus and poke around.

yancek 09-09-2009 06:56 PM

Haven't used Grub 2 yet but, the file not found message usually means the Grub code in the mbr is pointing to the wrong partition or the files it is looking for are not where it expects.

I assume you are able to boot all/most of your other systems? What OS do you use to boot and on which partition? Do you keep the same Grub menu.lst and modify it with new installs? What method do you use to boot, kernel entries with /dev/sd?, UID, chainloader, configfile?

widget 09-10-2009 03:17 PM

Quote:

Originally Posted by yancek (Post 3676504)
Haven't used Grub 2 yet but, the file not found message usually means the Grub code in the mbr is pointing to the wrong partition or the files it is looking for are not where it expects.

I assume you are able to boot all/most of your other systems? What OS do you use to boot and on which partition? Do you keep the same Grub menu.lst and modify it with new installs? What method do you use to boot, kernel entries with /dev/sd?, UID, chainloader, configfile?

I am getting pretty good with grub2. It is a little rough still but with custom entries you can pretty much make it sit up and bark.

Grub2 does not have /boot/grub/menu.lst. What you see on the screen comes from /boot/grub/grub.cfg which is a read only file generated every time update-grub is run by scripts in /etc/grub.d. Grub.d is also where you can create your custom entries.

The neat part of this is that, assuming that /etc/grub.d/30_os-prober is working properly, is that every OS with grub2 is up to date with every OS on the drive. This is not real smooth yet we are on alpha 5.

The jist of this is that, yes, I am sure that my menu entry is fine.

One of the updates did away with some needed files. I do not know enough to know all of them. I figure to do a dist-upgrade, if I can get in control from a liveCD or the 9.04 install on that drive, and that should fix the problem.

On another note - if you want to find the uuid of any partition run the command "blkid". Maybe all of you know that, I'm a noob, I think it is really slick. You can add that output to the file you edit (hashed out) for easy checking.

widget 09-10-2009 06:12 PM

I realize now that what I need is instruction on chroot. Either from an installed OS or LiveCD.

All my searching comes up with is stuff that has nothig to do with what I am doing. Building distros from scratch on the same partition that you are working from and so on.

I just want to control another OS so that I can dist-upgrade the bugger.

linus72 09-10-2009 06:27 PM

You should be able to chroot into the installed OS and run apt-get update, etc

you got a ubuntu-910 livecd?

ok
boot it up, open a term, become root with sudo su
cd into your 910 partition and try this

Code:

mount -o bind /dev dev

mount -t proc /proc proc

chroot .

thats chroot space period

hit enter after typing in each one

once in, you can run apt-get update and apt-get upgrade, etc

OH, if you need a desktop, try using xnest
Code:

apt-get install xnest
or use the synaptic pkg manager in livecd, install xnest to livecd

once chrooted as above, start xnest

Code:

xnest -ac ":2" &
then to get your 910 desktop(gnome?)

Code:

env DISPLAY=":2" startgnome &
gnome should start within xnest window
some apps like opera, etc may cause xnest to crash:(

widget 09-13-2009 12:30 PM

Thanks a bunch. Sorry for the delay in answering, been (still am) sick as a dog.

I still can't boot the bugger but I don't get the "file not found" error and it does try to boot. I just need to feel up to poking around in there and it will probably boot (there seems to be an xorg.conf problem with ATI cards). I just need to fine the right combination.

I am quite pleased with this problem. I got into this testing to learn something and up until now it has been pretty tame and stable.

I read an interesting thing on the ubuntu forums earlier by a guy that runs jaunty but has upgraded his kernal as they come out. He had no trouble with 2.6.30 but is having these same problems with 2.6.31. This is interesting because I read the other day that .31 has been "declared" stable.


All times are GMT -5. The time now is 01:56 PM.