Bug#602071: /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
Package: grub-pc Version: 1.98+20100804-7 Severity: grave Justification: renders package unusable currently i'm boot from a 250GB sata disk (/dev/sdc). I have debootstrapped a 32bit system to /mnt. /dev/sda1 == /boot of new system /dev/sda2 == dm-crypt and / for new system /dev/sdb == data disk /dev/sdc currently running (old) system /dev/sd[ab] are disks from a hw-raid controller. but now i can't install grub into sda. # grub-install --root-directory=/mnt /dev/sda /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map. Auto-detection of a filesystem module failed. Please specify the module with the option `--modules' explicitly. some additional informations: # fdisk -lu Disk /dev/sdc: 250.0 GB, 2500 bytes 255 heads, 63 sectors/track, 30394 cylinders, total 488281250 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x5b6cfb68 Device Boot Start End Blocks Id System /dev/sdc12048 19531161597654784 83 Linux /dev/sdc2 195311616 39062527997656832 83 Linux Note: sector size is 4096 (not 512) Disk /dev/sda: 107.4 GB, 107374182400 bytes 255 heads, 63 sectors/track, 1631 cylinders, total 26214400 sectors Units = sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x3c7af5b2 Device Boot Start End Blocks Id System /dev/sda1 256 51455 204800 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 5145626214399 104651776 83 Linux Partition 2 does not end on cylinder boundary. Note: sector size is 4096 (not 512) Disk /dev/sdb: 3855.8 GB, 3855806889984 bytes 255 heads, 63 sectors/track, 58596 cylinders, total 941359104 sectors Units = sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x0804 Disk /dev/sdb doesn't contain a valid partition table Note: sector size is 4096 (not 512) Disk /dev/dm-0: 107.2 GB, 107161845760 bytes 255 heads, 63 sectors/track, 1628 cylinders, total 26162560 sectors Units = sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x Disk /dev/dm-0 doesn't contain a valid partition table # cat /proc/mounts rootfs / rootfs rw 0 0 none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 none /proc proc rw,nosuid,nodev,noexec,relatime 0 0 none /dev devtmpfs rw,relatime,size=1954524k,nr_inodes=488631,mode=755 0 0 none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 /dev/disk/by-uuid/e674b4d5-7530-4e6a-9c7e-18ed8e649c24 / ext4 rw,relatime,barrier=1,data=ordered 0 0 tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0 /dev/mapper/cryptroot /mnt ext4 rw,relatime,barrier=1,stripe=256,data=ordered 0 0 /dev/sda1 /mnt/boot ext3 rw,relatime,errors=continue,barrier=0,data=ordered 0 0 proc /mnt/proc proc rw,nosuid,nodev,noexec,relatime 0 0 sysfs /mnt/sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 none /mnt/dev devtmpfs rw,relatime,size=1954524k,nr_inodes=488631,mode=755 0 0 # cat /mnt/boot/grub/device.map (hd0) /dev/disk/by-id/scsi-222ca000155f3122f (hd1) /dev/disk/by-id/scsi-222b7000155f06178 (hd2) /dev/disk/by-id/ata-SAMSUNG_SP2504C_S0WRJ1RP459526 # grub-probe -t device /mnt/boot/ /dev/sda1 # grub-probe -t fs /mnt/boot/ grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map. r...@niassan:~# grub-probe -v -t fs /mnt/boot/ grub-probe: info: the size of hd0 is 209715200. grub-probe: info: the size of hd0 is 209715200. grub-probe: info: the size of hd0 is 209715200. grub-probe: info: the size of hd0 is 209715200. grub-probe: info: the size of hd1 is 7530872832. grub-probe: info: the size of hd1 is 7530872832. grub-probe: info: the size of hd2 is 488281250. grub-probe: info: the size of hd2 is 488281250. grub-probe: info: the size of hd2 is 488281250. grub-probe: info: the size of hd2 is 488281250. grub-probe: info: the size of hd0 is 209715200. grub-probe: info: the size of hd0 is 209715200. grub-probe: info: the size of hd0 is 209715200. grub-probe: info: the size of hd0 is 209715200. grub-probe: info: the size of hd1 is 7530872832. grub-probe: info: the size of hd1 is 7530872832. grub-probe: info: the size of hd2 is 488281250. grub-probe: info: the size of hd2 is 488281250. grub-probe: info: the size of hd2 is 488281250. grub-probe: info: the size of hd2 is 488281250. grub-probe: info: changing current directory to /dev. grub-probe: info: changing current directory to snd. grub-probe: info: changing current directory to cpu. grub-probe: info: changing current
Bug#602071: /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
grub-probe: info: /dev/sda1 starts from 2048.
grub-probe: info: opening the device hd0.
grub-probe: info: the size of hd0 is 209715200.
grub-probe: info: Partition 0 starts from 256.
grub-probe: info: Partition 1 starts from 51456.
grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your
device.map.
This looks like a 4K sector disk. We already have a bugreport for those.
I tried to fix them but abandoned when I've seen that no BIOS I had
around me even exposes such disks which means that making GRUB support
such is pointless.
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/disk/by-uuid/e674b4d5-7530-4e6a-9c7e-18ed8e649c24 / ext4
rw,relatime,barrier=1,data=ordered 0 0
/dev/mapper/cryptroot /mnt ext4 rw,relatime,barrier=1,stripe=256,data=ordered
0 0
/dev/sda1 /mnt/boot ext3 rw,relatime,errors=continue,barrier=0,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/scsi-222ca000155f3122f
(hd1) /dev/disk/by-id/scsi-222b7000155f06178
(hd2) /dev/disk/by-id/ata-SAMSUNG_SP2504C_S0WRJ1RP459526
*** 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='(hd0,msdos1)'
search --no-floppy --fs-uuid --set e674b4d5-7530-4e6a-9c7e-18ed8e649c24
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set e674b4d5-7530-4e6a-9c7e-18ed8e649c24
set locale_dir=($root)/boot/grub/locale
set lang=de
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.36.nias' --class debian --class
gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set e674b4d5-7530-4e6a-9c7e-18ed8e649c24
echo'Loading Linux 2.6.36.nias ...'
linux /boot/vmlinuz-2.6.36.nias
root=UUID=e674b4d5-7530-4e6a-9c7e-18ed8e649c24 ro quiet
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.36.nias
}
menuentry 'Debian GNU/Linux, with Linux 2.6.36.nias (recovery mode)' --class
debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set e674b4d5-7530-4e6a-9c7e-18ed8e649c24
echo'Loading Linux 2.6.36.nias ...'
linux /boot/vmlinuz-2.6.36.nias
root=UUID=e674b4d5-7530-4e6a-9c7e-18ed8e649c24 ro single
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.36.nias
}
menuentry 'Debian GNU/Linux, with Linux 2.6.36-trunk-amd64' --class debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set e674b4d5-7530-4e6a-9c7e-18ed8e649c24
echo'Loading Linux 2.6.36-trunk-amd64 ...'
linux /boot/vmlinuz-2.6.36-trunk-amd64
root=UUID=e674b4d5-7530-4e6a-9c7e-18ed8e649c24 ro quiet
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.36-trunk-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.36-trunk-amd64 (recovery mode)'
--class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set e674b4d5-7530-4e6a-9c7e-18ed8e649c24
echo'Loading Linux 2.6.36-trunk-amd64 ...'
linux /boot/vmlinuz-2.6.36-trunk-amd64
root=UUID=e674b4d5-7530-4e6a-9c7e-18ed8e649c24 ro single
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.36-trunk-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to
Bug#602071: /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
Am Montag, 1. November 2010 schrieben Sie: grub-probe: info: /dev/sda1 starts from 2048. grub-probe: info: opening the device hd0. grub-probe: info: the size of hd0 is 209715200. grub-probe: info: Partition 0 starts from 256. grub-probe: info: Partition 1 starts from 51456. grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map. This looks like a 4K sector disk. We already have a bugreport for those. I tried to fix them but abandoned when I've seen that no BIOS I had around me even exposes such disks which means that making GRUB support such is pointless. yes, i have configured the hw-raid controller to expose the raid array as 4k disks (Promise Supertrak EX4650). i think all modern raid controller support 4k disks and you can expose your raid array as 4k disk.(no need for 64bit LBA adresses for large dm- crypt disks). would you fix this bug or not? are there any workarounds which i can use? msc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#602071: /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
Am Montag, 1. November 2010 schrieb Vladimir 'φ-coder/phcoder' Serbinenko: The main problem is the BIOS. I was unable to find any BIOS able to boot from 4k disk. Even if you manage to install GRUB I see no way to boot it. Supporting 4k disks is somewhat difficult because of brain damaged way the msdos partition work with such disks. GPT should be functional from GRUB side. But you still BIOS with the support of 4k-sector disks. ok thanks. then i would drop my raid-array and recreate them with 512byte sector size. can be closed. msc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
