Software problems after installing Kali in Windows 7 as dualboot

mischka7 · 12-29-2018, 07:45 PM

Hello,

couple of days ago I did partition of my HDD and install Kali-Linux at my HP-Laptop where was before "Windows 7 home premium", as Dualboot.
After installation I got huge problems. My Kali doesn't start from HDD and Windows 7 also not.
If choose after starting my machine in the selection Windows 7, it starts to boot and goes off. If I choose in the selection Kali-Linux, it brings an error message and doesn't start.

The error message looks like that:

Code:

"...No IRQ handler for vector. ...Idm_parse_tocblock(): Cannot find TOCBLOCK, database may be corrupt.
Gave up waiting for suspend/resume device.
mount: mounting /dev/sda5 on /root failed: No such device
mount: mounting /dev on /root/dev failed: No such file or directory ....
..............................................
run-init: current directory on the same filesystem as the root : error
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg."

My researches on the internet brong me to the result that it should have something to do with "Grub" and following commands should solve it, if I run Kali-Linux from USB-Disk and type into terminal:

Code:

fdisk -l
sudo mount /dev/sda5 /mnt
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
sudo chroot /mnt
grub-install /dev/sda
Press CTRL+D
sudo umount /mnt/dev
sudo umount /mnt/proc
sudo umount /mnt/sys
sudo umount /mnt

With

Code:

fdisk -l

I get following results:

Code:

root@kali:~# fdisk -l
Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 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: 0xc20c8307

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1              63      2047      1985 992.5K 42 SFS
/dev/sda2  *         2048    409599    407552   199M 42 SFS
/dev/sda3          409600 525092863 524683264 250.2G 42 SFS
/dev/sda4       525094910 625141759 100046850  47.7G  5 Extended
/dev/sda5       525094912 581734399  56639488    27G 83 Linux
/dev/sda6       581736448 625141759  43405312  20.7G 82 Linux swap / Solaris




Disk /dev/sdb: 114.6 GiB, 123010547712 bytes, 240254976 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: 0xdafb3ffb

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sdb1  *    120131584 240254974 120123391 57.3G  7 HPFS/NTFS/exFAT
/dev/sdb2            4096 120131583 120127488 57.3G  7 HPFS/NTFS/exFAT

Partition table entries are not in disk order.


Disk /dev/loop0: 2.7 GiB, 2876436480 bytes, 5618040 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
root@kali:~#

Then it comes to error messages again:

Code:

root@kali:~# sudo mount /dev/sda5 /mnt
root@kali:~# sudo mount --bind /dev /mnt/dev
mount: /mnt/dev: mount point does not exist.
root@kali:~#

What to do, how to solve the problem?
Thanks in advance for any help.

Brains · 12-31-2018, 03:23 AM

Did you shrink /dev/sda3 and create the extended partition and two logical Linux partitions during the installation of Kali-Linux?. If you did not shrink it with Windows disk management but rather shrunk it with Kali-Linux partition tool, you likely destroyed the dynamic disk database which may have given Windows 7 a headache trying to boot. See code below regarding Windows dynamic disks:

Quote:

Because each dynamic disk in a computer stores a replica of the dynamic disk database, for example, a corrupted dynamic disk database can repair one dynamic disk by using the database on another dynamic disk. The location of the database is determined by the partition style of the disk. On MBR partitions, the database is contained in the last 1 megabyte (MB) of the disk. On GPT partitions, the database is contained in a 1-MB reserved (hidden) partition.

According to the fdisk -l output you posted, the last Operating System you tried to boot before booting Kali live was Windows, which appears to have a boot partition on Drive 0 and the Operating System on Drive 1. This suggest the 47GB Linux is installed on Drive 0 did not contain the original Windows Operating System, rather the third dynamic disk was shrunk.

Quote:

Converting dynamic disks to basic disks. After you convert a basic disk into a dynamic disk, you cannot change the dynamic volumes back to partitions. Instead, you must move or back up your data, delete all dynamic volumes on the disk and then convert the disk.

Also, did you make a mistake in your first code?:

Code:

mount: mounting /dev/sda5 on /root failed: No such device
mount: mounting /dev on /root/dev failed: No such file or directory ....

/root is the administrator's home directory, the initrd.img will not reside in this directory, it will need to mount /
Anyway, if you did not convert Drive 0 back to a basic disk before changing partition scheme, this is likely where things went wrong.
Please clarify exactly what steps you took in creating the two Linux partitions.

berndbausch · 12-31-2018, 03:41 AM

Quote:

Originally Posted by mischka7

Hello,

couple of days ago I did partition of my HDD and install Kali-Linux at my HP-Laptop where was before "Windows 7 home premium", as Dualboot
....
it should have something to do with "Grub"
...

Code:

....
root@kali:~# sudo mount --bind /dev /mnt/dev
mount: /mnt/dev: mount point does not exist.

You probably didn't read https://www.linuxquestions.org/quest...ead-4175614092 about Kali.

When you install Kali, you should at least know what Grub is, and how to use a mount point. I suggest you first learn about Linux, then install Kali.

I would like to help you but don't know how messed up your boot configuration is. Therefore my suggestion:

Use your Windows rescue disk to repair Windows boot. Set up a virtual machine in Windows (Virtualbox is fine), install any Linux distro on it (perhaps Debian, since Kali derives from it, but even Kali if you must), find a beginner tutorial and learn. Your first assignment is to use the internet to understand the concepts of "mounting" and "Grub", and how to use them.