On Sat, 25 Sep 2010 12:28:00 -0400 (EDT) Stephen Powell <zlinux...@wowway.com> wrote:
> On Sat, 25 Sep 2010 03:40:04 -0400 (EDT), bri...@aracnet.com wrote: > I'm also going to need > to see the output of the following commands: > > ls -Al /dev/disk/by-id/ lrwxrwxrwx 1 root root 9 Sep 26 18:12 ata-WDC_WD2500YS-01SHB0_WD-WCANY2148692 -> ../../sda lrwxrwxrwx 1 root root 10 Sep 26 18:12 ata-WDC_WD2500YS-01SHB0_WD-WCANY2148692-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 26 18:12 ata-WDC_WD2500YS-01SHB0_WD-WCANY2148692-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Sep 26 18:12 ata-WDC_WD2500YS-01SHB0_WD-WCANY2148692-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Sep 26 18:12 ata-WDC_WD2500YS-01SHB0_WD-WCANY2148692-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Sep 26 18:12 scsi-SATA_WDC_WD2500YS-01_WD-WCANY2148692 -> ../../sda lrwxrwxrwx 1 root root 10 Sep 26 18:12 scsi-SATA_WDC_WD2500YS-01_WD-WCANY2148692-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 26 18:12 scsi-SATA_WDC_WD2500YS-01_WD-WCANY2148692-part2 -> ../../sda2 lrwxrwxrwx 1 root root 10 Sep 26 18:12 scsi-SATA_WDC_WD2500YS-01_WD-WCANY2148692-part3 -> ../../sda3 lrwxrwxrwx 1 root root 10 Sep 26 18:12 scsi-SATA_WDC_WD2500YS-01_WD-WCANY2148692-part4 -> ../../sda4 lrwxrwxrwx 1 root root 9 Sep 26 18:12 usb-SanDisk_CF_SDDR-189_2008102301130-0:3 -> ../../sde lrwxrwxrwx 1 root root 9 Sep 26 18:12 usb-SanDisk_mSD_SDDR-189_2008102301130-0:0 -> ../../sdb lrwxrwxrwx 1 root root 9 Sep 26 18:12 usb-SanDisk_MSxDSDDR-189_2008102301130-0:2 -> ../../sdd lrwxrwxrwx 1 root root 9 Sep 26 18:12 usb-SanDisk_SD_SDDR-189_2008102301130-0:1 -> ../../sdc > ls -Al /dev/disk/by-uuid/ > > lrwxrwxrwx 1 root root 10 Sep 26 18:12 4b764501-da53-4323-a751-3da37d7e2a91 -> ../../sda3 lrwxrwxrwx 1 root root 10 Sep 26 18:12 558d7790-5914-494d-938f-3387296eed45 -> ../../sda4 lrwxrwxrwx 1 root root 10 Sep 26 18:12 9EFC3C45FC3C1A4B -> ../../sda1 lrwxrwxrwx 1 root root 10 Sep 26 18:12 a948d6b6-8395-49a1-9f0f-21a10ceee9c2 -> ../../sda2 So there's something going on with the swap partition (/dev/sda4). I must have had an aborted resume from hibernate mode or something (don't remember doing it). either way, not good. > > It seems like I have two different problems. I have a lilo entry > > that doesn't work at all and another one which dumps me into this > > resume nonsense. > > ERROR! No initial RAM disk specified! Add: > > initrd=/boot/initrd.img > ok. > ERROR! No initial RAM disk image. Add: > > initrd=/boot/initrd.img.old ok. > >> /etc/kernel-img.conf > > > > Where is it? I need to see the contents of that file. > It's very important. > # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = no relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = yes postinst_hook = lilo-update postrm_hook = lilo-update I haven't gone through the rest of the changes yet. Working on that right now. Brian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100926191429.2ede9...@windy.deldotd.com
