Bug#345931: grub 0.97 doesn't work on several machines
The first installation report states that /grub/stage1 exists. Is that indeed true? Checking if /boot/grub/stage1 exists... no Checking if /grub/stage1 exists... yes Checking if /grub/stage2 exists... yes Checking if /grub/e2fs_stage1_5 exists... yes
Bug#352207: grub-update does not work since update to 0.97-3
Hi again It doesn't fail on my machine, so either it is caused by the amd64 architecture or the raid device. It seems to fail around the command readlink -f /dev/sda1 Can you send the output of readlink -f /dev/sda1 and readlink -f /dev/sda1 ; echo $? Kristian On 2/12/06, Didrik Pinte [EMAIL PROTECTED] wrote: Le samedi 11 février 2006 à 10:19 +0100, Kristian Edlund a écrit : Can you reproduce the error when you run update-grub with sh update-grub? Can you send supply your menu.lst file, and try to run update-grub with sh -x update-grub and send the output of that file as well. Kristian The output of sh -x /sbin/update-grub is the following (showing no errors) : -- serveurmeteo:/home/did# sh -x /sbin/update-grub + set -e + grub_dirs='/boot/grub /boot/boot/grub' ++ find_grub_dir ++ echo -n 'Searching for GRUB installation directory ... ' Searching for GRUB installation directory ... ++ for d in '$grub_dirs' ++ '[' -d /boot/grub ']' ++ grub_dir=/boot/grub ++ break ++ '[' -z /boot/grub ']' ++ echo 'found: /boot/grub' found: /boot/grub ++ echo /boot/grub + grub_dir=/boot/grub + menu_file=/boot/grub/menu.lst ++ find_root_device +++ find_device / +++ mount_point=/ +++ device= +++ '[' -f /etc/fstab ']' +++ read DEV MNT FOO grep -q '^#' echo '#' +++ continue +++ read DEV MNT FOO echo '#' grep -q '^#' +++ continue +++ read DEV MNT FOO echo '#' grep -q '^#' +++ continue +++ read DEV MNT FOO echo proc grep -q '^#' +++ '[' /proc = / ']' +++ read DEV MNT FOO echo /dev/sda1 grep -q '^#' +++ '[' / = / ']' +++ device=/dev/sda1 +++ read DEV MNT FOO echo /dev/sda5 grep -q '^#' +++ '[' none = / ']' +++ read DEV MNT FOO echo /dev/hda grep -q '^#' +++ '[' /media/cdrom0 = / ']' +++ read DEV MNT FOO echo /dev/fd0 grep -q '^#' +++ '[' /media/floppy0 = / ']' +++ read DEV MNT FOO echo '' grep -q '^#' +++ '[' '' = / ']' +++ read DEV MNT FOO +++ '[' -n /dev/sda1 ']' +++ case $device in readlink -f /dev/sda1 +++ device= ++ device= + root_device= -- It seems it did not find any root_device ... I've attached the menu.lst file to the mail Didrik -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBD7ySo9Rlh4Zs4yBMRAnoNAKCkEVrOfB5aGERYiLarBlPxjSOQawCfaO/s toYG31UKDRjYhsLEoLsD8os= =R0nC -END PGP SIGNATURE- ___ Pkg-grub-devel mailing list [EMAIL PROTECTED] http://lists.alioth.debian.org/mailman/listinfo/pkg-grub-devel
Bug#352207: grub-update does not work since update to 0.97-3
Well that defininatly explains why update-grub stops. It gets 1 as return value and therefore exits. It seems that the file /dev/sda1 does not exist or something goes wrong in readlink. Can you try ls -la /dev/sda1 in order to see what /dev/sda1 points to? Kristian On 2/12/06, Didrik Pinte [EMAIL PROTECTED] wrote: Le dimanche 12 février 2006 à 19:22 +0100, Kristian Edlund a écrit : Hi again It doesn't fail on my machine, so either it is caused by the amd64 architecture or the raid device. It seems to fail around the command readlink -f /dev/sda1 Can you send the output of readlink -f /dev/sda1 and readlink -f /dev/sda1 ; echo $? Kristian Here you are ;-) --- serveurmeteo:/home/did# readlink -f /dev/sda1 serveurmeteo:/home/did# readlink -f /dev/sda1 ; echo $? 1 serveurmeteo:/home/did# --- Didrik -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBD735Z9Rlh4Zs4yBMRArq3AJ0ScNiD5Tei3tjRZW1RQEPP3vRjQgCeONC5 naJ0iqUgOEP212TJY23dxK4= =LuLN -END PGP SIGNATURE- ___ Pkg-grub-devel mailing list [EMAIL PROTECTED] http://lists.alioth.debian.org/mailman/listinfo/pkg-grub-devel
Bug#352207: grub-update does not work since update to 0.97-3
Can you reproduce the error when you run update-grub with sh update-grub? Can you send supply your menu.lst file, and try to run update-grub with sh -x update-grub and send the output of that file as well. Kristian
Bug#344767: This bug is fixed
Yes I believe that he bug is fixed in the 0.97-3 release. I just tried to install kernel 2.4.17-2-k7 and remove it again, and there was no problems with the scripts running. After that I purged the configuration, which also went without problems. I have tested with 2.6.15 as well, which also runs without problems. So I doubt that #349291, is related to this bug. When you try to purge your kernel, what command are you using and what happens? -- Best Regards Kristian Edlund GPG ID: 7DD7559F -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]