bug-grub
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #50280] legacy_initrd should have only one filename


From: Andy Smith
Subject: [bug #50280] legacy_initrd should have only one filename
Date: Sat, 11 Feb 2017 16:16:27 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0

URL:
  <http://savannah.gnu.org/bugs/?50280>

                 Summary: legacy_initrd should have only one filename
                 Project: GNU GRUB
            Submitted by: grifferz
            Submitted on: Sat 11 Feb 2017 09:16:26 PM UTC
                Category: Booting
                Severity: Major
                Priority: 5 - Normal
              Item Group: Software Error
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: Git master
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

When attempting to boot a Xen guest using legacy_configfile
/boot/grub/menu.lst the following config is generated:


set root='(hd0,1)'; set legacy_hdbias='0'                                     
                                         
legacy_kernel   '/boot/vmlinuz-3.16.0-4-amd64' '/boot/vmlinuz-3.16.0-4-amd64' 
                                         
'root=UUID=38420e46-6123-477d-ba23-baeba8ac0d59' 'ro'                         
                                         
legacy_initrd '/boot/initrd.img-3.16.0-4-amd64'
'/boot/initrd.img-3.16.0-4-amd64'


That comes from the following menu.lst:


default         0                                                             
                                         
timeout         5                                                             
                                         
color cyan/blue white/blue                                                    
                                         
title           Debian GNU/Linux, kernel 3.16.0-4-amd64                       
                                         
root            (hd0,0)                                                       
                                         
kernel          /boot/vmlinuz-3.16.0-4-amd64
root=UUID=38420e46-6123-477d-ba23-baeba8ac0d59 ro                          
initrd          /boot/initrd.img-3.16.0-4-amd64


The guest fails to boot with the following output:


[    1.470403] Freeing unused kernel memory: 216K (ffff8800017ca000 -
ffff880001800000)                                 
[    1.471934] Failed to execute /init (error -8)                             
                                         
[    1.472673] Starting init: /sbin/init exists but couldn't execute it (error
-8)                                      
[    1.473359] Starting init: /bin/sh exists but couldn't execute it (error
-8)                                         
[    1.473365] Kernel panic - not syncing: No working init found.  Try passing
init= option to kernel. See              
Linux Documentation/init.txt for guidance.                                    
                                         
[    1.473369] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.16.0-4-amd64 #1
Debian 3.16.39-1                             
[    1.473372]  0000000000000000 ffffffff81514c11 ffffffff81705310
ffff88003e23bf40                                     
[    1.473377]  ffffffff8151195e ffffffff00000008 ffff88003e23bf50
ffff88003e23bef0                                     
[    1.473380]  ffff88003e23bef8 0000000000000000 0000000000000495
0000000000000495                                     
[    1.473384] Call Trace:


The problem seems to be the repeated file name on the "legacy_initrd" line.
Editing the generated config and removing that second file name allows for a
normal boot.

This has been discussed on grub-devel in this thread
<http://lists.gnu.org/archive/html/grub-devel/2017-02/msg00053.html>




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?50280>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]