I came across some issues here when upgrading my server from Jaunty to Karmic. The current problem is that Ubuntu Live CD does not detect my Hard Drives. Therefore I can neigher fix the faulty Karmic I installed on the disk earlier(upgraded from a working Januty), nor install a fresh Karmic from scrach.
Here is a brief history of how I got to this point.
Everything started when I tried to upgrade ubuntu from Jaunty to Karmic.
The upgrade finished with no error prompted, but when reboot, problems emerged. The first issue was
1) Boot failed with error message "One or more of the mounts listed in /etc/fstab cannot yet be mounted", it stopped at one hard disk that contain /home. After patiently waiting , it reached the recovery shell, pressing ctrl +D ended up the same. Apparently one hard disk that contain /home did not mount. Then I tried solutions from :http://creativeinstantia.blogspot.co...buntu-910.html, and
change UUID in fstab and dpkg --configure -a did not work , I then commented out mount /home disk and tried to skip it, I created another user in /temphome, rebooted, get the same error, but this time stopped at swap disk.
2) Checked fstab again, It did not use UUID for SWAP, so I thought I might tweak it to UUID instead
Then I tried https://bugs.launchpad.net/ubuntu/+s...sh/+bug/474720
3)1) get the uuid of your swap partition
/dev/sda1: UUID="d4c3f800-f968-4445-bc32-3151051b1064" TYPE="swap"
2) edit initramfs:
sudo gedit /etc/initramfs-tools/conf.d/resume
*** without " " ****
save and exit.
3) sudo update-initramfs -k all -u
3) However, after rebooting I got another error "udevadm trigger is not permitted while udev is unconfigured", perhaps the SWAP cannot be loaded at all.
What does this imply? I have no idea.udevadm trigger is not permitted while udev is unconfigured.1
udevadm settle is not permitted while udev is unconfigured.
svgalib: Cannot open /dev/mem.
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/byuuid/a46dd7c7-2caa-4fce-8941-95892956b121 does not exist. Dropping to a shell!
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) built-in shell (ash)
Enter 'help' for a list of built-in commands.
4) Googled an entry at https://bugs.launchpad.net/ubuntu/+s...er/+bug/358654 , attempted to try the solution
5) However, after downloading and burning a Karmic live cd, it firstly failed to boot and halt with keyboard indicators flashing, changed another keyboard, successfully logged in. not sure why though, the original keyboards worked with normal boot, but not live cd.The solution is to use a live-CD to mount the system (or boot from a completely separate installation), mount the failed OS partition(s), and complete the update process: e.g.
# create a target mount point
# mount root
mount /dev/sda8 /mnt/target
# mount boot
mount /dev/sda9 /mnt/target/boot
# into Jaunty
dpkg --configure -a
6) After I logged in to Ubuntu from Live CD, I cannot see the harddisk at all.
sudo fdisk -l returns nothing.
well, I am stuck again. Is there any other solution to 3)? What does it mean? I cannot find one on the net except 4).
Wondering if anyone has similar issues, and how did you solve them? Everything was perfect for upgrade of previous versions on this machine, from fiesty to jaunty, but not this time.
Anyway, please help if you have any thoughts and experience.