pgibson
July 24th, 2009, 09:17 PM
Long post trying to provide all the details ... (Moderator, please move this if it would be better located elsewhere).
The problem thus far:
The short version is that something went amiss during huge the-computer-has-been-off-for-months upgrade, which included a kernel upgrade from 2.6.28-11 to 2.6.28-13.
The system in question is running Ubuntu 9.04 with an XFCE desktop, on our old Micron PIII.
Grub comes up, the new kernel is listed there, choose it and ...
The Jaunty-Cylon-eye splash screen comes on and then disappears and drops into a shell after 5 or ten seconds. The resulting text, (which I've transcribed by hand, as I cannot figure out how to copy it or print it or what-have-you) says:
Boot from (hd0,2) ext3 a21c4ab7-e6ee-44c3-8afe-44bef9723ee6
Starting up ...
[ 4.050772] IO APIC resources could not be allocated.
Loading, please wait ...
udevadm trigger is not permitted while udev is unconfigured.
Gave up waiting for root device. Common problems:
-Boot args (cat /proc/modules; ls /dev)
-Check rootdelay= (did the system wait for the right device?)
-Missing modules (cat /proc/modules; ls /dev?)
ALERT! /dev/disk/by-uuid a21c4ab7-e6ee-44c3-8afe-44bef9723ee6 does not exist, Dropping to shell.
Busybox v1.10.2 (Ubuntu 1:10.2-2 ubuntu 7) built-in shell (ash)
Enter 'help' for a list of built in commands.
(initramfs)
My (valiant and failed) efforts to fix this, thus far:
I typed "help," read the resulting list of commands, but really didn't see anything that I recognized as helpful (but, I didn't recognize much).
I followed some prompts and fsck stuff, and (being naive and trusting and lucky) I have managed to boot the prior kernel 2.6.28-11. The resulting desktop was mostly functional, though couldn't connect to the internet. And this was only to see what was there. I may have made things worse, I don't know.
However, poking around I found files in the /home directory I don't remember seeing before, such as vmlinuz.new vmlinuz.old ... ah HA! I don't really know if it's significant but ah HA! all the same.
A few other (possibly useful) facts and details:
/dev/sda1 is winXP
/dev/sda2 is /home ext3
/dev/sda3 is / ext3
I think the technical term is "borked." I've borked the downstairs desktop computer, because I was rushing to do other things, the warning of which I didn't pay close enough attention to now remember. Oops.
The pop-up told me there was some sort of problem asked if I wanted to quit, so I clicked that then clicked to close Synaptic, which subsequently hung, for like a minute or two. I was rushing and simply clicked the "leave" button, and chose "shut-down." Boop. No problem ... Until I went to start it back up.
My deepest appreciation in advance,
:)
The problem thus far:
The short version is that something went amiss during huge the-computer-has-been-off-for-months upgrade, which included a kernel upgrade from 2.6.28-11 to 2.6.28-13.
The system in question is running Ubuntu 9.04 with an XFCE desktop, on our old Micron PIII.
Grub comes up, the new kernel is listed there, choose it and ...
The Jaunty-Cylon-eye splash screen comes on and then disappears and drops into a shell after 5 or ten seconds. The resulting text, (which I've transcribed by hand, as I cannot figure out how to copy it or print it or what-have-you) says:
Boot from (hd0,2) ext3 a21c4ab7-e6ee-44c3-8afe-44bef9723ee6
Starting up ...
[ 4.050772] IO APIC resources could not be allocated.
Loading, please wait ...
udevadm trigger is not permitted while udev is unconfigured.
Gave up waiting for root device. Common problems:
-Boot args (cat /proc/modules; ls /dev)
-Check rootdelay= (did the system wait for the right device?)
-Missing modules (cat /proc/modules; ls /dev?)
ALERT! /dev/disk/by-uuid a21c4ab7-e6ee-44c3-8afe-44bef9723ee6 does not exist, Dropping to shell.
Busybox v1.10.2 (Ubuntu 1:10.2-2 ubuntu 7) built-in shell (ash)
Enter 'help' for a list of built in commands.
(initramfs)
My (valiant and failed) efforts to fix this, thus far:
I typed "help," read the resulting list of commands, but really didn't see anything that I recognized as helpful (but, I didn't recognize much).
I followed some prompts and fsck stuff, and (being naive and trusting and lucky) I have managed to boot the prior kernel 2.6.28-11. The resulting desktop was mostly functional, though couldn't connect to the internet. And this was only to see what was there. I may have made things worse, I don't know.
However, poking around I found files in the /home directory I don't remember seeing before, such as vmlinuz.new vmlinuz.old ... ah HA! I don't really know if it's significant but ah HA! all the same.
A few other (possibly useful) facts and details:
/dev/sda1 is winXP
/dev/sda2 is /home ext3
/dev/sda3 is / ext3
I think the technical term is "borked." I've borked the downstairs desktop computer, because I was rushing to do other things, the warning of which I didn't pay close enough attention to now remember. Oops.
The pop-up told me there was some sort of problem asked if I wanted to quit, so I clicked that then clicked to close Synaptic, which subsequently hung, for like a minute or two. I was rushing and simply clicked the "leave" button, and chose "shut-down." Boop. No problem ... Until I went to start it back up.
My deepest appreciation in advance,
:)