Can you show the output of ls when you are in rescue mode? Your external HDD must be plugged in before grub recognizes it.
Hello to everyone,
I have installed Win7 on my internal HD, and Kali Linux on second partition on my external HD. I placed Grub loader on my internal HD where Win7 is.
When computer boots, Grub loader goes directly in rescue mode with following errors: No such device, and file system error (or something like that). But when I manually enter into BIOS boot and pick to boot from internal HD everything works fine and Grub loader is raised with dual boot options.
In rescue mode with LS command I concluded that it can`t see the external drive, and I suppose that No such device error refer to this. But I`m confused - if it can`t see the external HD when computer automatically boots, how it can see it when I manually boot from Bios from my internal HD?
Can anyone help, it is really annoying to go into BIOS every time I boot or power on the computer?
Thank you
Can you show the output of ls when you are in rescue mode? Your external HDD must be plugged in before grub recognizes it.
0Yes, it is always plugged in. LS in rescue:
(hd0) (hd0,msdos1) (hd1) (hd1,msdos1)(hd1,msdos2)
When I Boot the system from BIOS and choose my internal HD, GRUB successfully boots. Here LS in command prompt adds additional: ..... (hd2) (hd2,msdos1) (hd2,msdos5) (hd2,msdos6)
Since I have one primary internal HD and one secondary HD with 2 partitions I assume that those disks are hd0 and hd1....and since my external HD has 3 partitions (Kali is on the last one) I assume that external disk is hd2. But rescue mod with LS command doesn`t see disk (hd2).
(hd0) is your internal HD and (hd1) is your external HD. I'm not sure what (hd2) is. Do you have UEFI firmware or BIOS?
Anyway once you boot kali, run [B]sudo grub-install /dev/sda[B] and sudo update-grub.
/dev/sda is the name of your hard disk. It can be /dev/sdb so check the name of your HD using fdisk -l in which grub will be installed. I think that'll fix the problem.
I have Bios. Since I have 2 internal drives second one must be hd1 or hd2.
I tried this but have error on the end:
So, sdb is definitely mi first internal HD where I have Win7 and where I placed Grub -256GB.root@kali:/home/mmajstor# fdisk -l
Disk /dev/sdb: 238.5 GiB, 256060514304 bytes, 500118192 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
Disklabel type: dos
Disk identifier: 0xbdefbed0
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 500115455 500113408 238.5G 7 HPFS/NTFS/exFAT
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x000837d6
Device Boot Start End Sectors Size Id Type
/dev/sda1 63 1953523119 1953523057 931.5G 42 SFS
Partition 1 does not start on physical sector boundary.
Disk /dev/sdd: 7.6 GiB, 8178892800 bytes, 15974400 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
Disklabel type: dos
Disk identifier: 0x9dcdecad
Device Boot Start End Sectors Size Id Type
/dev/sdd1 * 2048 8808447 8806400 4.2G b W95 FAT32
/dev/sdd2 8808448 15968255 7159808 3.4G 83 Linux
Disk /dev/sdc: 931.5 GiB, 1000194400256 bytes, 1953504688 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
Disklabel type: dos
Disk identifier: 0xe853fe39
Device Boot Start End Sectors Size Id Type
/dev/sdc1 64 903145535 903145472 430.7G 7 HPFS/NTFS/exFAT
/dev/sdc2 903158296 1953503999 1050345704 500.9G f W95 Ext'd (LBA)
/dev/sdc5 903158298 1928940614 1025782317 489.1G 7 HPFS/NTFS/exFAT
/dev/sdc6 * 1928940678 1953503999 24563322 11.7G 83 Linux
root@kali:/home/mmajstor# sudo grub-install /dev/sda
Installing for i386-pc platform.
error: invalid volume.
grub-install: warning: disk isn't LDM.
grub-install: error: embedding is not possible, but this is required for cross-disk install.
root@kali:/home/mmajstor# sudo grub-install /dev/sdb
Installing for i386-pc platform.
Installation finished. No error reported.
root@kali:/home/mmajstor# sudo update-grub
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.12.0-kali1-amd64
Found initrd image: /boot/initrd.img-4.12.0-kali1-amd64
error: invalid volume.
grub-probe: error: cannot find a GRUB drive for /dev/sda2. Check your device.map.
error: invalid volume.
grub-probe: error: cannot find a GRUB drive for /dev/sda3. Check your device.map.
Found Windows 7 on /dev/sdb1
Found Kali GNU/Linux Rolling (kali-rolling) on /dev/sdd2
done
sda should be my second internal HD which is not bootable and where I have two partitions (but he doesn`t see them) - 1TB.
sdd is my usb flash with two partitions where I have Linux installation - 8GB
sdc should be my external drive with 3 partitions, where is Kali installed (on the third one - sdc6) - 1TB
your command gives me error on sda2 and sda3 which should be partitions on my second internal drive.Why it check my second internal drive in the first place, when it is not bootable, and GRUB is on my first internal HD (sdb)?
But, when I recall the GRUB installation - when I needed to choose on which disk I want to install GRUB, I clicked by mistake second internal HD and after error I choose the correct first one...maybe this is causing this error?
Grub is installed. Can't you boot kali now? The Mast Boot Record which holds the bootloader is on /dev/sdb.