Re: Gutsy Upgrade problem

On 03/18/2008 06:55 PM, Rick Knight wrote:
NoOp wrote:
On 03/18/2008 01:09 PM, Rick Knight wrote:

NoOp wrote:

Should be:

sudo update-initramfs -u (or -c -k to create a new one). See man
update-initramfs.

EXAMPLES
Update the initramfs of the newest kernel:

update-initramfs -u

Create the initramfs for a specific kernel:

update-initramfs -c -k 2.6.18-1-686

So in your case:

sudo update-initramfs -c -k 2.6.22-14-generic




NoOp,

My mistake. I did this last night and was going from memory. My history
shows i entered...

sudo update-initramfs -u 2.6.22-14-generic

I also checked /boot/initrd.img-2.6.22-14-generic at the time to make
sure it updated, it did.

Anything else you can suggest?

Thanks,
Rick





It _should_ have taken, but I think that you need the '-k' when
specifying the kernel version.




NoOp,

I ran the command as you suggested, update-initramfs -k
2.6.22-a4-generic -u, and checked the time and date of
/boot/initrd.img-2.6.22-14-generic and it looks like the command took. I
rebooted and still go the BusyBox prompt and my hard drive are not
present. My USB mass storage device is OK and my ZipDrive is visible,
just no hard drives ( have 2, linux is on /dev/hdb). Anything else you
can suggest?

Thanks,
Rick


I presume you mean:

sudo update-initramfs -c -k 2.6.22-14-generic

I've used blkid to verify the uuid is correct. I've edited
/boot/grub/menu.lst and /etc/fstab to use drive path (/dev/hdb5 &
/dev/sdb5) instead of uuid.

You might want to relook at your fstab - they should be sdb vs hdb. Here
is a copy of mine:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=<myuuid> / ext3 defaults,errors=remount-ro 0 1
# /dev/sda5
<myuuid> none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/scd1 /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
# /dev/sdb1
/dev/sdb1 /media/windows ntfs iocharset=utf8,umask=000 0 0

Note: sdb1 is a dual boot drive for windows. No UUID works, but
eventually I'll get around to putting a UUID there.

If all else fails, you can try substituting the UUID temporarily and use
/dev/sda1 & /dev/sda5 to see if you can boot.

My grub menu.lst on this machine looks like this:

title Ubuntu 7.10, kernel 2.6.22-14-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-14-generic root=<myuuid> ro quiet splash
initrd /boot/initrd.img-2.6.22-14-generic

I'd also try using the alternate CD and select "rescue a broken system"
+ options.

Other than that, you'll need Nils...



--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Relevant Pages

  • Re: Gutsy Upgrade problem
    ... NoOp wrote: ... update-initramfs. ... Create the initramfs for a specific kernel: ...
    (Ubuntu)
  • Re: Gutsy Upgrade problem
    ... NoOp wrote: ... update-initramfs. ... Create the initramfs for a specific kernel: ...
    (Ubuntu)
  • Re: Gutsy Upgrade problem
    ... NoOp wrote: ... update-initramfs. ... Create the initramfs for a specific kernel: ...
    (Ubuntu)
  • Re (3): Re^n: Grub vs. linux-image-2.6.32 conundrum
    ... "if it ain't broke, don't fix it" ... But it is broke! ... currently the kernel update fails when update-initramfs ... Fix the update-initramfs script so that it works with lilo. ...
    (Debian-User)
  • Re: "Waiting for root file system ..."
    ... for that earlier 2.6.18 kernel (i don't want to touch the working ... already posted once that there is a problem with the update-initramfs ro ... system (which modules would be included in the initrd disk). ... and last but not least it's pretty tricky to boot broken initram but not too ...
    (Debian-User)