headers
Stanislav Davydov | 11 May 17:24
Picon

Grub2 not recognise GPT when present hybrid MBR

Root issue:
 grub ignore protective GPT record if that record is not the first one in MBR.
Need to correct:
 If protective GPT record appears on any place in MBR - grub must consider system as GPT.

My system is Ubuntu and package I using is grub-pc  1.99-21ubuntu3.
I trust that my error is not distributive specific

I have hybrid GPT/MBR. Hybrid MBR contains protective record 0xEE but that  record is NOT first.
Here is output of gdisk (hybrid MBR):
Number  Boot  Start Sector   End Sector   Status      Code
   1                468992    101480447   primary     0x07
   2             234375168    234569727   primary     0xEF
   3      *      550782882    574927413   primary     0x83
   4                     1       468991   primary     0xEE

gdisk (GPT):
Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          206847   100.0 MiB   EF00  EFI system partition
   2          206848          468991   128.0 MiB   0C01  Microsoft reserved part
   3          468992       101480447   48.2 GiB    0700  win7
   4       101480448       138344447   17.6 GiB    AF00  other
   5       390625280       527343615   65.2 GiB    8301  copyfilesWIN7
   6       527343616       550780927   11.2 GiB    AF00  backupfile
   7       581042176       625141759   21.0 GiB    2700  Samsung_diag
   8       138344448       234375167   45.8 GiB    0700  DATA
  11       574927414       581042175   2.9 GiB     8200 
  12       234375168       234569727   95.0 MiB    EF02  grub
  13       550782882       574927413   11.5 GiB    0700  linux

After that it result in such errors:
root <at> helena:~# grub-install /dev/sda
/usr/sbin/grub-setup: warn: This msdos-style partition label has no post-MBR gap; embedding won't be possible!.
/usr/sbin/grub-setup: warn: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
/usr/sbin/grub-setup: error: will not proceed with blocklists.

invoking grub-mkconfig manually gives:
root <at> helena:~# grub-mkconfig  -o test.conf
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-24-generic
Found initrd image: /boot/initrd.img-3.2.0-24-generic
Found linux image: /boot/vmlinuz-3.0.0-19-generic
Found initrd image: /boot/initrd.img-3.0.0-19-generic
Found linux image: /boot/vmlinuz-2.6.38-14-generic
Found initrd image: /boot/initrd.img-2.6.38-14-generic
Found linux image: /boot/vmlinuz-2.6.38-8-generic
Found initrd image: /boot/initrd.img-2.6.38-8-generic
Found memtest86+ image: /boot/memtest86+.bin
grub-probe: error: cannot find a GRUB drive for /dev/sda4.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda5.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda6.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda7.  Check your device.map.
done

I have tried diferent approach - was  removed hybrid MBR (retained only protective record). After that grub-install succeed. After that I have created hybrid MBR (the same as above).
But after reboot I have got "grub rescue" prompt and error: no such partition.

--
--
   Stanislav Davydov <stas.davydov <at> gmail.com>

_______________________________________________
Bug-grub mailing list
Bug-grub <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-grub
Permalink | Reply | 1 comment |
headers
Wolfgang Schulze-Zachau | 10 May 15:22
Favicon
Gravatar

upgrade-from-grub-legacy failure

Hi all,

I was asked to report the failure of grup to be upgraded here. What
follows is the output of "/usr/sbin/grub-probe
--device-map=/boot/grub/device.map --target=fs -v /boot/grub":

build5:~# /usr/sbin/grub-probe --device-map=/boot/grub/device.map
--target=fs -v /boot/grub >/tmp/grub-failure.txt
/usr/sbin/grub-probe: info: Cannot stat
`/dev/disk/by-id/scsi-SATA_ST3300831AS_3NF0GST8', skipping.
/usr/sbin/grub-probe: info: Cannot stat
`/dev/disk/by-id/scsi-SATA_ST3300831AS_3NF0H7L9', skipping.
/usr/sbin/grub-probe: info: changing current directory to /dev.
/usr/sbin/grub-probe: info: changing current directory to dri.
/usr/sbin/grub-probe: info: changing current directory to snd.
/usr/sbin/grub-probe: info: changing current directory to net.
/usr/sbin/grub-probe: info: changing current directory to shm.
/usr/sbin/grub-probe: info: opening md0.
/usr/sbin/grub-probe: error: no such disk.

I should probably mention that there was a problem during the upgrade.
This machine runs entirely on a software RAID1 (no boot partition, and
root is mounted on /dev/md0). During the upgrade to squeeze, mdadm found
that the device ID for md0 had changed. I updated the
/etc/mdadm/mdadm.conf file, but forgot to run update-initramfs, and then
subsequent boots failed until I booted into rescue mode and ran the
command from the rescue shell.
The system now boots, using the chainloader. However, during the boot
process I also get error messages that some information could not be
read from the drives.

Detailed log files are available if needed.

--

-- 
best regards

Wolfgang

Amino | Mob: +44 7554 457 455 | Desk: +44 1954 234 190 | skype: wszachauamino
Permalink | Reply | 1 comment |
headers
Mads Kiilerich | 10 May 12:09
Picon

[bug #36446] wrong fonts for starfield theme

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

                 Summary: wrong fonts for starfield theme
                 Project: GNU GRUB
            Submitted by: kiilerix
            Submitted on: Thu 10 May 2012 10:09:03 GMT
                Category: None
                Severity: Major
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: Bazaar - trunk
         Reproducibility: None
         Planned Release: None

    _______________________________________________________

Details:

The build system will create dejavu.pf2 with no special mkfont options and it
will thus be 16 point only. The starfield theme do however use other fonts.

As a work around I used something like

rm dejavu.pf2
grub-mkfont -o DejaVuSans-10.pf2      -s 10
/usr/share/fonts/dejavu/DejaVuSans.ttf # "DejaVu Sans Regular 10"
grub-mkfont -o DejaVuSans-12.pf2      -s 12
/usr/share/fonts/dejavu/DejaVuSans.ttf # "DejaVu Sans Regular 12"
grub-mkfont -o DejaVuSans-Bold-14.pf2 -s 14
/usr/share/fonts/dejavu/DejaVuSans-Bold.ttf # "DejaVu Sans Bold 14"

- but the theme installation is very hardcoded in the build system.

Slightly related:
It would be nice if mkfont showed exactly which "font name" it created.
It would be nice if mkfont didn't create empty pf2 files when no font source
is specified.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
Permalink | Reply | 0 comments |
headers
Jordan Uggla | 8 May 10:43
Picon

[bug #36433] Leading spaces after '\' line continuation cause syntax error

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

                 Summary: Leading spaces after '\' line continuation cause
syntax error
                 Project: GNU GRUB
            Submitted by: jordanu
            Submitted on: Tue 08 May 2012 08:43:50 AM GMT
                Category: None
                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: Bazaar - trunk
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

The following code causes a syntax error in grub but is completely valid and
causes no problems in bash:

echo \
 test

Note the space before "test". With a file test.cfg containing the above two
lines I can run "bash test.cfg" and it will simply print "test\n" as expected
but when I run "grub-script-check test.cfg" I get the following output:

error: out of memory.
error: syntax error.
Syntax error at line 2

I ran into this bug while trying to get bvk's autoiso.cfg working for Super
GRUB2 Disk.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
Permalink | Reply | 1 comment |
headers
Chris Trenkamp | 5 May 03:49
Picon

[bug #36404] Colons in environment variable identifiers are unreadable

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

                 Summary: Colons in environment variable identifiers are
unreadable
                 Project: GNU GRUB
            Submitted by: christrenkamp
            Submitted on: Sat 05 May 2012 01:49:54 AM GMT
                Category: Terminal
                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: Bazaar - trunk
         Reproducibility: Every Time
         Planned Release: None

    _______________________________________________________

Details:

If an environment variable has a colon in its identifier, it will be
inaccessible when attempting to read it.

For example, after the user runs 'net_bootp', the environment variable
'net_pxe:dhcp_boot_file' will be set.  If the user attempts to read it with
echo '${net_pxe:dhcp_boot_file}', the command will return these errors:
error: $.
error: syntax error.
error: Incorrect command.
error: syntax error.

I've tried various ways to read these variable, but can't find one that works.
 I know these variables were meant to be read-only, which is probably why
there's a colon in the identifier, but it would be extremely useful to be able
to read them.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
Permalink | Reply | 1 comment |
headers
Jose Manuel Ferrer Mosteiro | 4 May 12:26
Picon

grub-install doesn't work

Hi

I tryed to install grub but i get this error message:

---

root <at> morgul:~# grub-install /dev/sdg
/usr/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem of /dev/md1 failed.
Please report this together with the output of "/usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub" to <bug-grub <at> gnu.org>
root <at> morgul:~# /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub
/usr/sbin/grub-probe: info: Cannot stat `/dev/disk/by-id/ata-WDC_WD3200AAJS-00B4A0_WD-WMAT15012811', skipping.
/usr/sbin/grub-probe: info: Cannot stat `/dev/disk/by-id/ata-WDC_WD3200AAJS-00B4A0_WD-WMAT15009217', skipping.
/usr/sbin/grub-probe: info: changing current directory to /dev.
/usr/sbin/grub-probe: info: changing current directory to space.
/usr/sbin/grub-probe: info: changing current directory to dri.
/usr/sbin/grub-probe: info: changing current directory to snd.
/usr/sbin/grub-probe: info: changing current directory to net.
/usr/sbin/grub-probe: info: changing current directory to shm.
/usr/sbin/grub-probe: info: changing current directory to mapper.
/usr/sbin/grub-probe: info: opening md/1.
/usr/sbin/grub-probe: error: no such disk.
root <at> morgul:~#

---

The operating system is a Debian Squeeze.

Have a nice day.

-- Jose Manuel Ferrer Mosteiro Administrador de Sistemas / System Administrator http://www.andago.com Phone: +34 637 74 11 26 / +34 916 011 373 / +34 946 416 066 Fax: +34 916 011 372 / +34 944 318 286 C/Alcalde Ángel Arroyo 10, 1ª Planta 28904 Getafe, Madrid C/Kanala Bidea, Edif. 103, 1ª Izda.Parque Tecnológico 48170 Zamudio, Bizkaia Cuide el medio ambiente, no imprima este correo si no es necesario. ************************************* AVISO LEGAL **************************************** ANDAGO CONSULTING, SL / ANDAGO INGENIERÍA, SL le informa que los datos facilitados por Ud. y utilizados para el envío de esta comunicación serán objeto de tratamiento automatizado o no en nuestros ficheros, con la finalidad de gestionar la agenda de contactos de nuestra empresa y para el envío de comunicaciones profesionales por cualquier medio electrónico o no. Vd. podrá en cualquier momento ejercer el derecho de acceso, rectificación, cancelación y oposición en los términos establecidos en la Ley Orgánica 15/1999. El responsable del tratamiento es ANDAGO CONSULTING SL / ANDAGO INGENIERIA SL, con domicilio en C/ ALCALDE ANGEL ARROYO, 10, 28904, Getafe (Madrid). El contenido de esta comunicación, así como el de toda la documentación anexa, es confidencial y va dirigido únicamente al destinatario del mismo. En el supuesto de que usted no fuera el destinatario, le solicitamos que nos lo indique y no comunique su contenido a terceros, procediendo a su destrucción. Please do not print this message to preserve environment. ************************************ DISCLAIMER ***************************************** The content of this communication and any attached information is confidential and exclusively for the use of the addressee. If you are not the addressee, we ask you to notify to the sender and do not pass its content to another person, and please be sure you destroy it. 
_______________________________________________
Bug-grub mailing list
Bug-grub <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-grub
Permalink | Reply | 0 comments |
headers
mkaiser-bb | 30 Apr 09:49
Picon
Favicon

grub with ubuntu 11.10

hi there ,

 

maybe you can help me - updated ubuntu to 11.10 version , have installed xp too , bootloader does not

 

find xp - in other words , its not in listed in boot menue anymore

 

what can i do to resolve ?

 

regards

 

martin k, böblingen

_______________________________________________
Bug-grub mailing list
Bug-grub <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-grub
Permalink | Reply | 0 comments |
headers
Mads Kiilerich | 30 Apr 00:49
Picon

[bug #36340] 'make html' fails

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

                 Summary: 'make html' fails
                 Project: GNU GRUB
            Submitted by: kiilerix
            Submitted on: Sun 29 Apr 2012 10:49:36 PM GMT
                Category: Installation
                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: Bazaar - trunk
         Reproducibility: None
         Planned Release: None

    _______________________________________________________

Details:

'make html' fails with
grub-dev.texi:1692: @image file `font_char_metrics..png' (for HTML) not
readable: No such file or directory.
on the line
@image{font_char_metrics,,,,.png}

Removing the . from png makes it work ... apparently contrary to what makeinfo
documentation says. Leaving the extension out works for html - but might break
for other formats.

(Depending on how this is fixed, the next issues might be that other images
are completely missing and that 'make install-html' doesn't install the
images.)

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
Permalink | Reply | 2 comments |
headers
Midnight Matt | 29 Apr 05:51
Picon
Favicon

Grub bootloader installation bug report

To whom it may concern:

I have tried and failed to manually install a grub bootloader onto an external hard drive. So here is the
output from the `/usr/sbin/grub-probe --device-map="/media/EHD/boot/grub/device.map"
--target=fs -v /media/EHD/boot/grub` command as requested:

Auto-detection of a filesystem of /dev/sdb1 failed.
/usr/sbin/grub-probe: info: cannot open `/media/EHD/boot/grub/device.map'.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: scanning hd0 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: no LVM signature found
.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: scanning hd1 for LVM.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: no LVM signature found
.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: scanning hd0 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: no LVM signature found
.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: scanning hd0,msdos5 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: no LVM signature found
.
/usr/sbin/grub-probe: info: scanning hd0,msdos1 for LVM.
/usr/sbin/grub-probe: info: the size of hd0 is 117304992.
/usr/sbin/grub-probe: info: no LVM signature found
.
/usr/sbin/grub-probe: info: scanning hd1 for LVM.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: no LVM signature found
.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: scanning hd1,msdos1 for LVM.
/usr/sbin/grub-probe: info: the size of hd1 is 155907768.
/usr/sbin/grub-probe: info: no LVM signature found
.
/usr/sbin/grub-probe: info: changing current directory to /dev.
/usr/sbin/grub-probe: info: /dev/sdb1 starts from 2048.
/usr/sbin/grub-probe: info: opening the device /dev/sdb.
/usr/sbin/grub-probe: info: the size of /dev/sdb is 155907768.
/usr/sbin/grub-probe: info: Partition 0 starts from 256.
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.

I hope this is of use in resolving this situation.

Sincerely,
-matthew dodt
<randygaffer <at> yahoo.com>
Permalink | Reply | 1 comment |
headers
Mark Preston | 28 Apr 19:41
Picon
Favicon

GRUB recovery mode has blank screen in Ubuntu Linux

After my video card failed, I used the on-board video on the
motherboard. That changed caused the GRUB boot-time to not output a
readable signal by the monitor. (blank screen) Using the app Startup
Manager I set the advanced options for 800x600. That returned me to a
viewable selection of kernels, memory tests and boot windows options,
but not GRUB Recovery mode(s). After a week the vid card maker sent me a
replacement video card. I installed it, and switched the BIOS from
video-internal to pci-e (it's an EVGA 9500GT a pci-e device). 

On boot if I select Recovery mode, the screen still blanks and after a
moment a message flashes by (VGA=769 is deprecated) and a bunch of words
that go by way too quickly to read. I tried to take a photo, but it's
way too fast. Is there a way to edit grub.config to slow that down or
find the logfile with that error message?

After that VGA= message, the screen blanks. However, I can push the
Enter (CR) key, and that starts the "Resume Normal Boot" function. So,
presumably pressing the up or down cursor keys would take me somewhere
in the GRUB recover options. Which I don't do, without being able to see
what I am selecting. I have tried the one I know from memory: Resume
Normal Boot. 

I have manually updated the GRUB with sudo update-grub. All went well at
the terminal.

Anybody know how to return my system to normal????

I continue to have this problem in Precise Pangolin 12.04. I first
posted this message at Ubuntuforums.org in Nov. 2009.
Permalink | Reply | 0 comments |
headers
Goh Lip | 20 Apr 17:44
Picon

[bug #36258] error grub-install v2.00 beta4

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

                 Summary: error grub-install v2.00 beta4
                 Project: GNU GRUB
            Submitted by: gohlip
            Submitted on: Fri 20 Apr 2012 03:44:49 PM GMT
                Category: None
                Severity: Major
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: gohlip
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 
                 Release: Bazaar - experimental branch
         Reproducibility: None
         Planned Release: None

    _______________________________________________________

Details:

Downloaded and make install grub v2.00 beta4.
Confirmed installation complete withour error with "grub-install -v" which
gives "grub-install (GRUB) 2.00~beta4"

However when I "sudo grub-install /dev/sda", the following error message
appears...
"/usr/local/sbin/grub-bios-setup: error: cannot write to `/dev/sda': Bad file
descriptor."

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/
Permalink | Reply | 4 comments |

Gmane