OK I'd better admit first that I'm only understanding about 50% of what
you say, so...
Best fit I can find from google is this:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/31126
except that it doesn't appear that I ran out of disk space on the
gutsy's / partition. I can get as far as figuring out which partition it
is, mounting it, and viewing folders. I have no idea if I have another
kernel I can boot from - how would I find out, and then how would I do
that? Presumably by creating a new entry in grub - but where might a
kernel be?
[EMAIL PROTECTED] mount /dev/sda2 ./tmp/sda2
[EMAIL PROTECTED] mount
/dev/sda3 on / type ext3 (rw,noatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
proc on /proc type proc (rw)
/sys on /sys type sysfs (rw)
varrun on /var/run type tmpfs (rw)
varlock on /var/lock type tmpfs (rw)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
devshm on /dev/shm type tmpfs (rw)
lrm on /lib/modules/2.6.15-27-desktop64-smp/volatile type tmpfs (rw)
/dev/sda5 on /home type ext3 (rw,noatime)
/dev/sdb1 on /media/photos type ext3 (rw,nosuid,nodev)
/dev/sdb2 on /media/music type ext3 (rw,nosuid,nodev)
/dev/sdb3 on /media/software type ext3 (rw,nosuid,nodev)
/dev/sdb5 on /media/backup type ext3 (rw,nosuid,nodev)
/dev/sdb6 on /media/vmware type ext3 (rw,nosuid,nodev)
/dev/sda2 on /home/roger/tmp/sda2 type ext3 (rw)
[EMAIL PROTECTED] ls -tal ./tmp/sda2/boot/
total 23832
-rw-r--r-- 1 root root 5521408 2008-02-14 11:24 initrd.img-2.6.22-14-generic
drwxr-xr-x 3 root root 4096 2008-02-14 11:23 .
drwxr-xr-x 3 root root 4096 2008-02-14 11:23 grub
-rw-r--r-- 1 root root 417807 2008-02-12 17:30 abi-2.6.22-14-generic
-rw-r--r-- 1 root root 67666 2008-02-12 17:30 config-2.6.22-14-generic
-rw-r--r-- 1 root root 1052627 2008-02-12 17:30 System.map-2.6.22-14-generic
-rw-r--r-- 1 root root 1743752 2008-02-12 17:30 vmlinuz-2.6.22-14-generic
-rw-r--r-- 1 root root 7704940 2008-02-11 19:57
initrd.img-2.6.22-14-generic.dpkg-bak
-rw-r--r-- 1 root root 7704741 2008-02-09 00:30
initrd.img-2.6.22-14-generic.bak
drwxr-xr-x 23 root root 4096 2007-12-27 09:52 ..
-rw-r--r-- 1 root root 103204 2007-09-28 23:03 memtest86+.bin
This is as far as I've been able to get, at this point I have no idea
how to proceed.
Roger
(having previously used fdisk to figure out that /dev/sda2 wasn't
mounted and is the gutsy / )
[EMAIL PROTECTED] fdisk -l
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 30159 30401 1951897+ 82 Linux swap / Solaris
/dev/sda2 * 27727 30158 19535040 83 Linux
/dev/sda3 25295 27726 19535040 83 Linux
/dev/sda4 1 25294 203174023+ 5 Extended
/dev/sda5 1 25294 203173992 83 Linux
Partition table entries are not in disk order
Disk /dev/sdb: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 7783 62516916 83 Linux
/dev/sdb2 7784 15566 62516947+ 83 Linux
/dev/sdb3 15567 23271 61890412+ 83 Linux
/dev/sdb4 23272 38913 125644365 5 Extended
/dev/sdb5 23272 31092 62822151 83 Linux
/dev/sdb6 31093 38913 62822151 83 Linux
Steve Holdoway wrote:
Sounds like your initrd image is hosed. Do you have more than one (gutsy)
kernel installed, and can you boot off one of the others? If so, then
mkinitramfs will let you rebuild the affected file ( which is actually a cpio
archive of all the driver, etc files you need to bootstrap the kernel )
One of the reasons I don't like SuSE is the way it cleans up after itself and
*doesn't* give you that option... unless things have changed of course!
Steve
On Thu, 14 Feb 2008 19:37:13 +1300
Roger Searle <[EMAIL PROTECTED]> wrote:
Hi, the following occurred out of the blue today, though may be the
second time it has happened. While using the machine as normal, the
video cut out, and needed a hard reset. The previous time it may have
occurred was about 3 or 4 days ago (where it re-booted fine), and that
pre-dated running the Adept Updater yesterday. One of the updates
yesterday was a kernel upgrade to (from memory) 2.6.22-something. So I
can't be sure that the following is related to the update:
On reboot, I get the following:
RAMDISK: ran out of compressed data
invalid compressed format (err=1)
Kernel panic - not syncing: VFS: unable to mount root fs on
unknown-block (0,0)
I have absolutely no idea what this is about, I'm googling but looking
for any experience from the list about how to proceed.
This email is being composed booted into Mepis - the previous
installation to the above Gutsy problem. So the hardware is
functional. df isn't showing me any full partitions.
Any pointers gratefully received!
Roger
