Bug#664718:

2014-12-01 Thread Moonwalker
I have the same issue when /boot is a separate ext2 partition. If I change it 
to ext4, grub-install will succeed.

Package: grub-pc
Architecture: amd64
Version: 1.99-27+deb7u2


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#664718:

2014-12-01 Thread Moonwalker
I have the same issue when /boot is a separate ext2 partition. If I change it 
to ext4, grub-install will succeed.

Package: grub-pc
Architecture: amd64
Version: 1.99-27+deb7u2


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#664718: grub-pc 1.99-18: grub-setup: error: cannot read `/grub/core.img' correctly

2012-04-17 Thread David Roguin
This is still happening with version 1.99-21 which recently hit testing.
After the upgrade the system can no longer boot and I'm unable to
install grub on the MBR.

-- 
David



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#664718: Info received (grub-pc 1.99-18: grub-setup: error: cannot read `/grub/core.img' correctly)

2012-04-05 Thread Colin Watson
On Wed, Apr 04, 2012 at 08:49:19AM +0200, Jakub Moc wrote:
> The above error about inability to read core.img got replaced with
> "error: non-sector-aligned data is found in the core file" somewhere
> between 1.99-19 and 1.99-20 (which got fixed 1.99-21 - #666992) so
> this I guess may be closed).

The fix in 1.99-21 was just to fix the regression in 1.99-19.  Did it
really fix this bug as well?  I wasn't expecting it to.

-- 
Colin Watson   [cjwat...@debian.org]



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#664718: Info received (grub-pc 1.99-18: grub-setup: error: cannot read `/grub/core.img' correctly)

2012-04-03 Thread Jakub Moc
The above error about inability to read core.img got replaced with
"error: non-sector-aligned data is found in the core file" somewhere
between 1.99-19 and 1.99-20 (which got fixed 1.99-21 - #666992) so
this I guess may be closed).

(For people hitting the same, I could work around it by reformatting
/boot to ext3 on *some* of the affected systems. NFC. Running
grub-setup with --debug showed that it really was unable to find the
file, would suggest some cryptic bug in ext2.mod. Systems with grub
installed to MBR were unaffected, however that is not really an option
for everyone, e.g. cannot be used on dual-boot boxes using
Bitlocker-encrypted Vista/W7 system partition.)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#664718: grub-pc 1.99-18: grub-setup: error: cannot read `/grub/core.img' correctly

2012-03-20 Thread Jakub Moc
Package: grub-pc
Version: 1.99-17
Severity: important

/usr/sbin/grub-setup: warn: Attempting to install GRUB to a partitionless disk
or to a partition.  This is a BAD idea..
/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: cannot read `/grub/core.img' correctly.

This renders the box unbootable. Fixed by downgrading to 1.99-17:

Nastavuji balík grub-common (1.99-17) …
Nastavuji balík grub2-common (1.99-17) …
Nastavuji balík grub-pc-bin (1.99-17) …
Nastavuji balík grub-pc (1.99-17) …
/usr/sbin/grub-setup: warn: Attempting to install GRUB to a partitionless disk
or to a partition.  This is a BAD idea..
/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..
Installation finished. No error reported.



-- Package-specific info:

*** WARNING grub-setup left core.img in filesystem

*** BEGIN /proc/mounts
/dev/mapper/root / btrfs 
rw,noatime,nodiratime,compress=lzo,space_cache,autodefrag 0 0
/dev/sda5 /boot ext2 rw,noatime,nodiratime,errors=remount-ro,user_xattr,acl 0 0
/dev/mapper/home /home ext4 
rw,noatime,nodiratime,errors=remount-ro,user_xattr,barrier=0,data=writeback 0 0
/dev/mapper/dpkg /var/lib/dpkg reiserfs rw,relatime,notail 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/device.map
(hd0)   /dev/disk/by-id/memstick-SA02G_0x22eaeeea
(hd1)   /dev/disk/by-id/ata-FUJITSU_MHY2160BH_K405T822HFRJ
*** END /boot/grub/device.map

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}

function load_video {
  insmod vbe
  insmod vga
  insmod video_bochs
  insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(hd1,msdos5)'
search --no-floppy --fs-uuid --set=root ad33bdb0-637d-4fe2-a7e8-031b71d4aae4
if loadfont /grub/unicode.pf2 ; then
  set gfxmode=1024x768
  load_video
  insmod gfxterm
  insmod part_msdos
  insmod ext2
  set root='(hd1,msdos5)'
  search --no-floppy --fs-uuid --set=root ad33bdb0-637d-4fe2-a7e8-031b71d4aae4
  set locale_dir=($root)/grub/locale
  set lang=cs_CZ
  insmod gettext
fi
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='(hd1,msdos5)'
search --no-floppy --fs-uuid --set=root ad33bdb0-637d-4fe2-a7e8-031b71d4aae4
insmod png
if background_image /grub/linuxmint.png; then
  true
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/06_mint_theme ###
insmod part_msdos
insmod ext2
set root='(hd1,msdos5)'
search --no-floppy --fs-uuid --set=root ad33bdb0-637d-4fe2-a7e8-031b71d4aae4
insmod png
if background_image /grub/linuxmint.png ; then
  set color_normal=white/black
  set color_highlight=white/light-gray
else
  set menu_color_normal=white/black
  set menu_color_highlight=white/light-gray
fi
### END /etc/grub.d/06_mint_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'LinuxMint GNU/Linux, with Linux 3.2.0-10.dmz.1-liquorix-amd64' 
--class linuxmint --class gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd1,msdos5)'
search --no-floppy --fs-uuid --set=root 
ad33bdb0-637d-4fe2-a7e8-031b71d4aae4
echo'Loading Linux 3.2.0-10.dmz.1-liquorix-amd64 ...'
linux   /vmlinuz-3.2.0-10.dmz.1-liquorix-amd64 root=/dev/mapper/root ro 
 quiet splash i915.modeset=1 video=1280x800-24@60 pcie_aspm=force 
acpi_osi=Linux acpi_apic_instance=2
echo'Loading initial ramdisk ...'
initrd  /initrd.img-3.2.0-10.dmz.1-liquorix-amd64
}
menuentry 'LinuxMint GNU/Linux, with Linux 3.2.0-10.dmz.1-liquorix-amd64 
(recovery mode)' --class linuxmint --class gnu-linux --class gnu --class os {
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd1,msdos5)'
search --no-floppy --fs-uuid --set=root 
ad33bdb0-637d-4fe2-a7e8-031b71d4aae4
echo'Loading Linux 3.2.0-10.dmz.1-liquorix-amd64 ...'
linux   /vmlinuz-3.2.0-10.dmz.1-liquorix-amd64 root=/dev/mapper/root ro 
single 
echo'Loading initial ramdisk ...'
initrd  /initrd.img-3.2.0-1