Package: grub Version: 0.97-27 I don't know if its the kernel installation scripts fault or some grub scripts, so please forgive me if I'm wrong with my suggestion to blame grub.
After the last update/upgrade to a new kernel the system didn't want to boot because after the upgrade the menu.lst wasn't updated the right way. the old entry was: --- title Debian GNU/Linux, kernel 2.6.18-4-686 root (hd0,0) kernel /vmlinuz-2.6.18-4-686 root=/dev/mapper/c533-root ro initrd /initrd.img-2.6.18-4-686 --- the new one was updated to: --- title Debian GNU/Linux, kernel 2.6.18-5-686 root (hd1,0) kernel /vmlinuz-2.6.18-5-686 root=/dev/mapper/c533-root ro initrd /initrd.img-2.6.18-5-686 --- after changing the root device to (hd0,0) everything works now. I've installed debian 4.0 onto a scsi harddisk /dev/sda and used the debian installer to automatically make and format all partitions with encryption. this results in: /dev/sda1 to be a 250MB ext3 boot partition (/boot) /dev/sda2 to be a ~8GB extended partition /dev/sda5 to be a ~8GB encrypted luks lvm partition (dm-0) holding root (dm-1) and swap (dm-2) additionally there is an unused ide drive (2GB, /dev/hda) with two partitions (swap (hda1) and some old debian installation in one partition (hda2)) The bios is configured to boot the SCSI harddisk. After boot up /dev/hda is suspended via hdparm (-Y). I don't know why it's updated to the wrong root device but I think it's because the SCSI hdd is detected as second HDD now where it was detected correctly as the first one while installation... #cat /boot/grub/device.map (hd0) /dev/hda (hd1) /dev/sda no hardware changes since installation... best regards Michael Heide -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
