Bug#345931: grub 0.97 doesn't work on several machines
On Mon, Aug 28, 2006 at 03:37:10PM +0200, Robert Millan wrote: Why don't we move [/usr]/sbin/grub to /usr/lib ? Then we could even have a stub that echoes Use grub-install in /usr/sbin/grub. I have no idea; is this something I should have an opinion on? :) If you don't mean for the binary to be invoked directly by an admin, then of course /usr/lib is allowed/preferred under the FHS. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#345931: grub 0.97 doesn't work on several machines
Why don't we move [/usr]/sbin/grub to /usr/lib ? Then we could even have a stub that echoes Use grub-install in /usr/sbin/grub. -- Robert Millan My spam trap is [EMAIL PROTECTED] Note: this address is only intended for spam harvesters. Writing to it will get you added to my black list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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#345931: grub 0.97 doesn't work on several machines
retitle 345931 System fails to boot after updating boot sector from grub interactive shell thanks I have managed to reproduce this in vmware using the following procedure: - new Sarge install (has grub 0.95+cvs20040624-17) - change sources list to unstable and upgrade After grub is upgraded (to 0.97-4), but without re-installing its boot sector, the system reboots without problem. Now there are two methods to reinstall the grub boot sector to the new version. 1) Run the grub-install script # grub-install /dev/sda1 Installation finished. No error reported. This is the contents of the device map /boot/grub/device.map. Check if this is correct or not. If any of the lines is incorrect, fix it and re-run the script 'grub-install'. (hd0) /dev/sda # reboot = system reboots without any problems 2) Run the grub shell interactively as in the original report # grub grub find /boot/grub/menu.lst (hd0,0) grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) 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 Running embed /grub/e2fs_stage1_5 (hd0)... 16 sectors are embedded. succeeded Running install /grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/grub/stage2 /grub/menu..lst... succeeded Done. grub quit # reboot = Grub menu is not shown (screen remains blank); system fails to boot Conclusions: - grub-install does the right thing - the setup command in the grub interactive shell checks if the stage files exist, but apparently its setup command fails to check if they are compatible with the current version of grub I will keep the image I created this way in vmware for a while in case additional information is wanted. Cheers, Frans Pop -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345931: grub 0.97 doesn't work on several machines
close 345931 thanks Hi, grub-install copies the various stage* files into /boot/grub. grub shell does not. If you do not copy the stage* files then they will be incompatible with the boot sector that is installed. grub-install is the recommeneded method to install. On Mon, Feb 06, 2006 at 02:55:05PM +0100, Frans Pop wrote: retitle 345931 System fails to boot after updating boot sector from grub interactive shell thanks I have managed to reproduce this in vmware using the following procedure: - new Sarge install (has grub 0.95+cvs20040624-17) - change sources list to unstable and upgrade After grub is upgraded (to 0.97-4), but without re-installing its boot sector, the system reboots without problem. Now there are two methods to reinstall the grub boot sector to the new version. 1) Run the grub-install script # grub-install /dev/sda1 Installation finished. No error reported. This is the contents of the device map /boot/grub/device.map. Check if this is correct or not. If any of the lines is incorrect, fix it and re-run the script 'grub-install'. (hd0) /dev/sda # reboot = system reboots without any problems 2) Run the grub shell interactively as in the original report # grub grub find /boot/grub/menu.lst (hd0,0) grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) 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 Running embed /grub/e2fs_stage1_5 (hd0)... 16 sectors are embedded. succeeded Running install /grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/grub/stage2 /grub/menu..lst... succeeded Done. grub quit # reboot = Grub menu is not shown (screen remains blank); system fails to boot Conclusions: - grub-install does the right thing - the setup command in the grub interactive shell checks if the stage files exist, but apparently its setup command fails to check if they are compatible with the current version of grub I will keep the image I created this way in vmware for a while in case additional information is wanted. Cheers, Frans Pop ___ Pkg-grub-devel mailing list [EMAIL PROTECTED] http://lists.alioth.debian.org/mailman/listinfo/pkg-grub-devel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#345931: grub 0.97 doesn't work on several machines
Processing commands for [EMAIL PROTECTED]: close 345931 Bug#345931: System fails to boot after updating boot sector from grub interactive shell 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to John Hughes [EMAIL PROTECTED] thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345931: grub 0.97 doesn't work on several machines
reopen 345931 severity 345931 serious tags 345931 upstream thanks On Tue, Feb 07, 2006 at 09:01:01AM +1100, Jason Thomas wrote: close 345931 thanks grub-install copies the various stage* files into /boot/grub. grub shell does not. If you do not copy the stage* files then they will be incompatible with the boot sector that is installed. grub-install is the recommeneded method to install. Surely this is still a bug in the grub shell for failing to notice that it had rendered the system unbootable? I think this bug qualifies as serious; I think plenty of people are going to be upset when the grub shell toasts their system without warning. If you downgrade it, I'd appreciate if you would offer an explanation why you think this is an ok bug to release with given its non-obvious consequences; but please don't close it, as it does refer to a real bug. I've already talked with Otavio about getting 0.97 into testing in spite of this bug, since there are other bugs in testing that are at least as significant. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Processed: Re: Bug#345931: grub 0.97 doesn't work on several machines
Processing commands for [EMAIL PROTECTED]: reopen 345931 Bug#345931: System fails to boot after updating boot sector from grub interactive shell Bug reopened, originator not changed. severity 345931 serious Bug#345931: System fails to boot after updating boot sector from grub interactive shell Severity set to `serious'. tags 345931 upstream Bug#345931: System fails to boot after updating boot sector from grub interactive shell There were no tags set. Tags added: upstream thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345931: grub 0.97 doesn't work on several machines
Steve Langasek [EMAIL PROTECTED] writes: On Tue, Feb 07, 2006 at 09:01:01AM +1100, Jason Thomas wrote: close 345931 thanks grub-install copies the various stage* files into /boot/grub. grub shell does not. If you do not copy the stage* files then they will be incompatible with the boot sector that is installed. grub-install is the recommeneded method to install. Surely this is still a bug in the grub shell for failing to notice that it had rendered the system unbootable? I don't think so. If you're using grub's shell you need know what you're doing since it isn't indeed to be used for enduser. I think this bug qualifies as serious; I think plenty of people are going to be upset when the grub shell toasts their system without warning. If you downgrade it, I'd appreciate if you would offer an explanation why you think this is an ok bug to release with given its non-obvious consequences; but please don't close it, as it does refer to a real bug. This is a upstream issue and I doubt upstream will change it since it's currently in legacy mode and all effort in grub2. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - Microsoft gives you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345931: grub 0.97 doesn't work on several machines
On Mon, Feb 06, 2006 at 09:58:29PM -0200, Otavio Salvador wrote: Steve Langasek [EMAIL PROTECTED] writes: On Tue, Feb 07, 2006 at 09:01:01AM +1100, Jason Thomas wrote: close 345931 thanks grub-install copies the various stage* files into /boot/grub. grub shell does not. If you do not copy the stage* files then they will be incompatible with the boot sector that is installed. grub-install is the recommeneded method to install. Surely this is still a bug in the grub shell for failing to notice that it had rendered the system unbootable? I don't think so. If you're using grub's shell you need know what you're doing since it isn't indeed to be used for enduser. Er, but I do know what I'm doing; I'm telling grub to reinstall a boot block. What I *don't* know is that grub is going to silently fail to ascertain that the stage files on disk aren't compatible with the commands being run. Why does the grub shell even bother to look for the stage2 loader on disk, for instance, if it's not going to verify that it's usable? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#345931: grub 0.97 doesn't work on several machines
Jason Thomas wrote: Hi, Please check your menu.lst for a splashimage line. If one or more exists comment them out and try to boot again. No splashimage. (Onscreen garbage is text). How where the menu.lst files created? By normal grub install, linux-image install/update process. menu.lst attached to this message. You could also try pressing 'c' for the command line interface, when the random garbage is on the screen. But I've no idea if that will work. Doesn't work. I have seen this problem occurs when the splashimage directive points to a nonexistant file. On Wed, Jan 04, 2006 at 01:58:23PM +0100, John Hughes wrote: When the system random garbage gets printed on the screen. # menu.lst - See: grub(8), info grub, update-grub(8) #grub-install(8), grub-floppy(8), #grub-md5-crypt, /usr/share/doc/grub #and /usr/share/doc/grub-doc/. ## default num # Set the default entry to the entry number NUM. Numbering starts from 0, and # the entry number 0 is the default if the command is not used. # # You can specify 'saved' instead of a number. In this case, the default entry # is the entry saved with the command 'savedefault'. default 0 ## timeout sec # Set a timeout, in SEC seconds, before automatically booting the default entry # (normally the first entry defined). timeout 5 # Pretty colours color cyan/blue white/blue ## password ['--md5'] passwd # If used in the first section of a menu file, disable all interactive editing # control (menu entry editor and command-line) and entries protected by the # command 'lock' # e.g. password topsecret # password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/ # password topsecret # # examples # # title Windows 95/98/NT/2000 # root (hd0,0) # makeactive # chainloader +1 # # title Linux # root (hd0,1) # kernel/vmlinuz root=/dev/hda2 ro # # # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST ### BEGIN AUTOMAGIC KERNELS LIST ## lines between the AUTOMAGIC KERNELS LIST markers will be modified ## by the debian update-grub script except for the default options below ## DO NOT UNCOMMENT THEM, Just edit them to your needs ## ## Start Default Options ## ## default kernel options ## default kernel options for automagic boot options ## If you want special options for specifiv kernels use kopt_x_y_z ## where x.y.z is kernel version. Minor versions can be omitted. ## e.g. kopt=root=/dev/hda1 ro # kopt=root=/dev/hda2 ro ## default grub root device ## e.g. groot=(hd0,0) # groot=(hd0,0) ## should update-grub create alternative automagic boot options ## e.g. alternative=true ## alternative=false # alternative=true ## should update-grub lock alternative automagic boot options ## e.g. lockalternative=true ## lockalternative=false # lockalternative=false ## altoption boot targets option ## multiple altoptions lines are allowed ## e.g. altoptions=(extra menu suffix) extra boot options ## altoptions=(recovery mode) single # altoptions=(recovery mode) single ## controls how many kernels should be put into the menu.lst ## only counts the first occurence of a kernel, not the ## alternative kernel options ## e.g. howmany=all ## howmany=7 # howmany=all ## should update-grub create memtest86 boot option ## e.g. memtest86=true ## memtest86=false # memtest86=true ## ## End Default Options ## title Debian GNU/Linux, kernel 2.6.14-1-386 root(hd0,0) kernel /vmlinuz-2.6.14-1-386 root=/dev/hda2 ro initrd /initrd.img-2.6.14-1-386 savedefault boot title Debian GNU/Linux, kernel 2.6.14-1-386 (recovery mode) root(hd0,0) kernel /vmlinuz-2.6.14-1-386 root=/dev/hda2 ro single initrd /initrd.img-2.6.14-1-386 savedefault boot ### END DEBIAN AUTOMAGIC KERNELS LIST
Bug#345931: grub 0.97 doesn't work on several machines
Package: grub Version: 0.97-2 Severity: critical Justification: breaks the whole system After installing grub 0.97 and doing a simple setup the system is unbootable. The same behaviour was observed on an old Dell Dimension 4100 and a new Dell Optiplex GX270. This may be the same as bug 341535, but it's happening on machines other than a IBM thinkpad and using ext2 filesystems noy xfs. When the system random garbage gets printed on the screen. Here's a typescript of the grub setup: republic:~# grub Probing devices to guess BIOS drives. This may take a long time. GNU GRUB version 0.97 (640K lower / 3072K upper memory) Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename. ] grub find /grub/menu.lst (hd0,0) grub root (hd0,0) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) 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 Running embed /grub/e2fs_stage1_5 (hd0)... 16 sectors are embedded. succeeded Running install /grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/grub/stage2 /grub/menu ..lst... succeeded Done. grub quit republic:~# exit Script done on Wed 04 Jan 2006 01:49:59 PM CET -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-1-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages grub depends on: ii libc6 2.3.5-7GNU C Library: Shared libraries an ii libncurses5 5.5-1 Shared libraries for terminal hand grub recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345931: grub 0.97 doesn't work on several machines
Hi, Please check your menu.lst for a splashimage line. If one or more exists comment them out and try to boot again. How where the menu.lst files created? You could also try pressing 'c' for the command line interface, when the random garbage is on the screen. But I've no idea if that will work. I have seen this problem occurs when the splashimage directive points to a nonexistant file. On Wed, Jan 04, 2006 at 01:58:23PM +0100, John Hughes wrote: When the system random garbage gets printed on the screen. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
