weird dual boot problem

[Not_Rich]

Hi when I want to try a Linux distro on my machine I firstly unplug my widows10 drive and my storage so I dont accidentally make changes to these.

I use the computers boot manager to select my linux.

Kali installs fine and reboots fine if its the only drive connected.

But when I connect the other two drives and select kali i get a black screen with the following

mounting /dev on /root/dev failed: No such file or directory
run init: opening console no such file or directory
target filesystem does not have sbin/init

motherboard is a msi h61m-p31/w8

[mmusket33]

MTeams has never installed a dual boot with Windows ten. We have installed to XP and Windows 7 many many times.

Suggest the following approach:

1. Restore your Management Boot Record in Windows, so Windows Ten boots on startup.

2. Delete the partitions using Linux so you have unallocated space. We suggest you do this by booting up kali-linux live and use gparted.

3. Install Kali Linux to the unallocated space thru graphical install choice. Kali setup gives you the options to install to the unallocated space.

However before doing any of this, study the install problems outlined in this forum reference Window 10 dual boot install of kali-Linux.

This being said _default has come up with some good solutions in these matters and may assist you with a quicker command line solution.





Musket Teams

[_defalt]

I've kali dual boot with windows 10. I don't call it dual boot if both of them are on different disk. In which disk your grub bootloader is installed?

[Not_Rich]

I've kali dual boot with windows 10. I don't call it dual boot if both of them are on different disk. In which disk your grub bootloader is installed?

Grub is on the kali hard drive

[Not_Rich]

This post fixed it.

although I replaced sda3 with sda1 my boot partition

From there, you'll have to use the terminal for the following commands:

mount /dev/sda3 /mnt
mount --bind /dev /mnt/dev
mount --bind /dev/pts /mnt/dev/pts
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt
grub-install /dev/sda
update-grub
exit
umount /mnt/dev/pts
umount /mnt/dev
umount /mnt/proc
umount /mnt/sys
umount /mnt

[_defalt]

This post fixed it.

although I replaced sda3 with sda1 my boot partition

What kind of partition is your /dev/sda1? Is it your EFI partition?

[Not_Rich]

What kind of partition is your /dev/sda1? Is it your EFI partition?

How do I find this out?

[_defalt]

How do I find this out?

Show the output of fdisk -l. I'll find out.

[Not_Rich]

Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 2048 178685951 178683904 85.2G 83 Linux
/dev/sdc2 178687998 195371007 16683010 8G 5 Extended
/dev/sdc5 178688000 195371007 16683008 8G 82 Linux swap / Solaris

With only one hard drive connected it was /dev/sda1 with the others connected in working state its now /dev/sdc1

[duxim]

On normal Bios, not UEFI, with two HDD installation goes like this.
Both hdd should be connected to the system
install Linux on the second hdd (where you want) with Grub
restart machine. Windows will boot now. Examine is everything ok with Windows
restart once again, go to BIOS, select second hdd, where is Linux installed, to be first for booting
When Linux start and you logon on it, just do " sudo update-grub" and watch if grab added windows loader to grub.cfg
After that you should have dual/multi boot Windows/Linux on separate hdd.

Problems could be with uefi, ssd, Windows 10 power options

[_defalt]

Is your kali-linux installed in /dev/sda1? The output is confusing. The reason why I was asking this because the solution that fixed your problem may not work with UEFI. So I need to know which partition one is supposed to mount to reinstall grub in UEFI. Do you have BIOS or UEFI?

[Not_Rich]

When I first installed Kali I only had one hard drive connected and this was /dev/sda1 and I ran the fix
"mount /dev/sda1 /mnt
mount --bind /dev /mnt/dev etc....."

With the other 2 drives connected the output from fdisk shows it as /dev/sdc1 maybe because it has detected the other two drives and changed this.

The motherboard uses BIOS