bugGNU GRUB - Bugs: bug #32030, Missing low level installer (or...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #32030: Missing low level installer (or documentation)

Submitter:  Hadmut Danisch <hadmut>
Submitted:  Sun 02 Jan 2011 11:00:12 PM UTC
   
 
Category:  Installation Severity:  Major
Priority:  5 - Normal Item Group:  Feature Request
Status:  Fixed Privacy:  Public
Assigned to:  None Originator Name:  Hadmut
Open/Closed:  Closed Release:  1.98
Release:  Reproducibility:  Every Time
Planned Release:  None

Tue 04 Jan 2011 01:33:42 PM UTC, comment #2: 
Vladimir Serbinenko <phcoder>
Group administrator
Tue 04 Jan 2011 01:12:32 PM UTC, comment #1: 

Just add
(hd0)  /dev/mapper/raid-vmtest
to device.map

Vladimir Serbinenko <phcoder>
Group administrator
Sun 02 Jan 2011 11:00:12 PM UTC, original submission:  

Hi,

I am becoming more and more desperate about grub. It lacks a simple and plain low level install program.

Grub always tries to be more smart and clever than the admin, and unfortunately this does not always work.

Grub tries to hide as much as possible behind black magic like grub-install, but does not tell what is really going on there.

This works only as long as there is the standard situation of installing linux the regular way.

However, I was not able to figure out how to install grub the way it works with other boot loaders like lilo or syslinux, i.e. tell grub to just

- install itself on a given block device without trying to be magic or smart
- use the grub files from a given directory
- boot the first bios drive

and that's it.

I am trying to install a boot loader on a virtual disk (i.e. an lvm device) used as the boot disk for a virtual machine.

When installing the boot code, the virtual disk is seen from the host system like /dev/mapper/raid-vmtest with partitions. When starting the virtual machine, the same device now looks like /dev/hda or /dev/sda, or the first physical disk from the BIOS view.

Unfortunately, it is not possible (or at least I did not find a way due to the poor documentation) to install grub successfully on such a virtual disk. Grub always tries to find something about this device /dev/mapper/raid-vmtest through opaque black magic, and cannot accept that the disk appears with a differnt name and at a different place when booting. This is horrible, a nightmare.

There should be some low level installation program, which does not use any magic or autoconfiguration at all, which just installs grub with parameters given on the command line (or some documentation telling how to achieve that), e.g. for

- preparing virtual disks
- preparing real external disks with a USB adapter for later
  use as a boot disk
- repairing boot disks while booting from a USB-Stick


I've already wasted so much time with unsuccessfully trying to install grub the way I need it (and not the way grub believes it should be), especially because grub always prepares the disk to boot it as if it appeared at the same place it is while installing grub.

Please improve.




Hadmut Danisch <hadmut>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by phcoder (Posted a comment)
  • -email is unavailable- added by hadmut (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2011-01-04 phcoder StatusNone Fixed
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code