View Full Version : No Bootable device issue after Installing Kali Linux - Acer Aspire ES1-533
Hi,
I have purchased 3 Acer Aspire ES1-533 Laptos , I just tried to install Kali linux , created bootable disk using Rufus , and it was a GPT/UEFI compatible USB drive. But after my installation the system shows no bootable device found. Please help me to fix this.
In bios there is no option for changing UEFI boot type.
I have tried many options which are available in the internet.
Contacted Acer customer support
they simply neglected , by saying we are not supporting Linux
Tried many ways, dome morethan 10 times installation
some technicians told me to update BIOS from 1.08 to another version
But updating BIOS will affect the performance of PC
Friends I have no life without Kali...
Thanks in advance
B Hari
Boot into kali live and show the output of fdisk -l
This is the output of fdisk -l
root@kali:~# fdisk -l
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: gpt
Disk identifier: A1C297BA-E121-4924-9C40-517ECC72BC58
Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 1945495551 1944444928 927.2G Linux filesystem
/dev/sda3 1945495552 1953523711 8028160 3.8G Linux swap
Disk /dev/sdb: 7.5 GiB, 8004304896 bytes, 15633408 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: 0x8312dfc0
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 64 5636095 5636032 2.7G 17 Hidden HPFS/NTFS
/dev/sdb2 5636096 5637503 1408 704K 1 FAT12
Disk /dev/loop0: 2.5 GiB, 2646646784 bytes, 5169232 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:~#
It looks like the entry of grub was not created in the NVRAM while installation.
Anyway, you can reinstall grub.
Boot into kali live USB and follow the instructions:
mount /dev/sda5 /mnt
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount --bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars
mkdir /mnt/boot/efi
mount /dev/sda4 /mnt/boot/efi
mount -o remount,rw /dev/sda4 /mnt/boot/efi
mkdir /mnt/hostrun
mount --bind /run /mnt/hostrun
chroot /mnt
mkdir /run/lvm
mount --bind /hostrun/lvm /run/lvm
grub-install /dev/sda
update-grub
exit
umount /mnt/dev
umount /mnt/proc
umount /mnt/sys
umount /mnt/sys/firmware/efi/efivars
umount /mnt/boot/efi
umount /mnt/hostrun
umount /mnt/run/lvm
umount /mnt
REBOOT
The above method is not necessary if you know how to add entry of bootloaders in Boot menu options from your UEFI settings. There are plenty of features to explore in UEFI. In my hp PC i fix this issue using an option called Boot From EFI, once i boot kali i run sudo update-grub && sudo grub-install /dev/sda. This option is available in UEFI settings in other vendors like DELL with similar names like Add/Delete Boot devices.
root@kali:~# mount /dev/sda* /mnt
Usage:
mount [-lhV]
mount -a [options]
mount [options] [--source] <source> | [--target] <directory>
mount [options] <source> <directory>
mount <operation> <mountpoint> [<target>]
Mount a filesystem.
Options:
-a, --all mount all filesystems mentioned in fstab
-c, --no-canonicalize don't canonicalize paths
-f, --fake dry run; skip the mount(2) syscall
-F, --fork fork off for each device (use with -a)
-T, --fstab <path> alternative file to /etc/fstab
-i, --internal-only don't call the mount.<type> helpers
-l, --show-labels show also filesystem labels
-n, --no-mtab don't write to /etc/mtab
-o, --options <list> comma-separated list of mount options
-O, --test-opts <list> limit the set of filesystems (use with -a)
-r, --read-only mount the filesystem read-only (same as -o ro)
-t, --types <list> limit the set of filesystem types
--source <src> explicitly specifies source (path, label, uuid)
--target <target> explicitly specifies mountpoint
-v, --verbose say what is being done
-w, --rw, --read-write mount the filesystem read-write (default)
-h, --help display this help and exit
-V, --version output version information and exit
Source:
-L, --label <label> synonym for LABEL=<label>
-U, --uuid <uuid> synonym for UUID=<uuid>
LABEL=<label> specifies device by filesystem label
UUID=<uuid> specifies device by filesystem UUID
PARTLABEL=<label> specifies device by partition label
PARTUUID=<uuid> specifies device by partition UUID
<device> specifies device by path
<directory> mountpoint for bind mounts (see --bind/rbind)
<file> regular file for loopdev setup
Operations:
-B, --bind mount a subtree somewhere else (same as -o bind)
-M, --move move a subtree to some other place
-R, --rbind mount a subtree and all submounts somewhere else
--make-shared mark a subtree as shared
--make-slave mark a subtree as slave
--make-private mark a subtree as private
--make-unbindable mark a subtree as unbindable
--make-rshared recursively mark a whole subtree as shared
--make-rslave recursively mark a whole subtree as slave
--make-rprivate recursively mark a whole subtree as private
--make-runbindable recursively mark a whole subtree as unbindable
For more details see mount(8).
root@kali:~# mount --bind /dev /mnt/dev
mount: /mnt/dev: mount point does not exist.
This is the error message showing,
I just Gone to BIOS but the UEFI mode not changeable, Im not an expert in this area, please help me
I edited it. Do it again.
root@kali:~# fdisk -l
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: gpt
Disk identifier: 82579936-BA37-47E7-8351-0A934116964F
Device Start End Sectors Size Type
/dev/sda1 2048 488284159 488282112 232.9G Microsoft basic data
/dev/sda2 488284160 976566271 488282112 232.9G Microsoft basic data
/dev/sda3 976566272 1367191551 390625280 186.3G Microsoft basic data
/dev/sda4 1367191552 1386723327 19531776 9.3G Linux filesystem
/dev/sda5 1386723328 1484380159 97656832 46.6G Linux filesystem
/dev/sda6 1484380160 1894537215 410157056 195.6G Linux filesystem
/dev/sda7 1894537216 1933598719 39061504 18.6G Linux swap
Disk /dev/sdb: 7.5 GiB, 8004304896 bytes, 15633408 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: 0x8312dfc0
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 64 5636095 5636032 2.7G 17 Hidden HPFS/NTFS
/dev/sdb2 5636096 5637503 1408 704K 1 FAT12
Disk /dev/loop0: 2.5 GiB, 2646646784 bytes, 5169232 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:~#
I have again installed the LINUX , with different partition.
Now this is the output of fdisk -l can I use the above code without any change ?
From /dev/sda4 and /dev/sda5 which one is your /root partition, write that name in the first line. Earlier when i edited, it was /dev/sda2. Those commands works if you know which one is your /root linux filesystem. What was the point of reinstallation anyway?
The system stuck after processing the steps, now unable to do anything
when I try this step (mount --bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars ) it return mount point not found, so I tried different way and got stuck
the screenshot attached here in this URL (https://ibb.co/dGBEV6)
There is two screens u can see, 1 is showing my disk status and the other is my operations to install grub
You are not entering all the commands. You left some of them. Don't skip those commands. The code is written above. Just copy paste them.
Followed, but the terminal stuck there, this laptop came with Linpus Linux,
Brother please help me with a step by step process, In that screenshoot u can see my filesystem . please
please help me with a step by step process, In that screenshoot u can see my filesystem . please
I already posted every step in my earlier post.
mount /dev/sda5 /mnt
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount --bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars
mkdir /mnt/boot/efi
mount /dev/sda4 /mnt/boot/efi
mount -o remount,rw /dev/sda4 /mnt/boot/efi
mkdir /mnt/hostrun
mount --bind /run /mnt/hostrun
chroot /mnt
mkdir /run/lvm
mount --bind /hostrun/lvm /run/lvm
grub-install /dev/sda
update-grub
exit
umount /mnt/dev
umount /mnt/proc
umount /mnt/sys
umount /mnt/sys/firmware/efi/efivars
umount /mnt/boot/efi
umount /mnt/hostrun
umount /mnt/run/lvm
umount /mnt
REBOOT
For how long does it hold there? Can you again post a screenshot of doing it again along with the output of fdisk -l?
root@kali:~# fdisk -l
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: gpt
Disk identifier: 82579936-BA37-47E7-8351-0A934116964F
Device Start End Sectors Size Type
/dev/sda1 2048 488284159 488282112 232.9G Microsoft basic data
/dev/sda2 488284160 976566271 488282112 232.9G Microsoft basic data
/dev/sda3 976566272 1367191551 390625280 186.3G Microsoft basic data
/dev/sda4 1367191552 1368242175 1050624 513M EFI System
/dev/sda5 1368242176 1945495551 577253376 275.3G Linux filesystem
/dev/sda6 1945495552 1953523711 8028160 3.8G Linux swap
Disk /dev/sdb: 7.5 GiB, 8004304896 bytes, 15633408 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: 0x8312dfc0
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 64 5636095 5636032 2.7G 17 Hidden HPFS/NTFS
/dev/sdb2 5636096 5637503 1408 704K 1 FAT12
Disk /dev/loop0: 2.5 GiB, 2646646784 bytes, 5169232 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:~#
This is the latest output of fdisk -l
at this point grub-install /dev/sda the terminal got hang and entire system not responding please see this screenshoot https://ibb.co/faDsJR
what is the actual issue here ?
This PC has a pre installed linux that I was removed Linpus linux
Can't spot the error but if it hangs you can terminate the grub-install command by Ctrl+C. Then you can again enter that command. Which iso version is this? I never had this error. You can try with kali 2017.3 image.
Also show the output of dmesg. You should also see in /var/log/messages if there is a grub installation error.
No Key are working, Im using Kali 2017.3, I will restart the PC and show you the output of dmesg
No Key are working, Im using Kali 2017.3, I will restart the PC and show you the output of dmesg
There is no point of posting dmesg after the restart. I wanted to see the output after freeze.
After freeze the system not working any key or anything, last night full I have keep the PC in that state and wait for any chnages but nothing happend and to day I have restarted, now also done the same. please advice me how to take dmesg output while freeze the PC
I have to test if that problem is with 2017.3. You can try with kali weekly images: https://cdimage.kali.org/kali-images/kali-weekly/
I have few doubts
1. While the installation kali ask me that Force UEFI.... what option should I choose? Yes or No ?
2. Kali also aking for use Network Miroor I'm always give "Yes" is that affect badly ?
3. Finally some time kali ask to write Grub , what option should I choose here ?
One more thing
Which software is good to create bootable USB ? I have RUFUS and Win32 diskimage and which method is good ?
Now the Weekly Image is downloading, after that I will start Installation... thank you
1)YES
2)YES OR NO doesn't matter. I choose NO(not required)
3)YES
4)RUFUS
5)Don't install again. To save time live boot this weekly image and follow the above steps.
Booted from USB with weekly version of Kalilinux, and followed the steps given by you, again the same issue, the system stoped working.. :(
really very unluck...
You can reinstall but i'm feeling that this time you will get an error of grub-dummy failed to install in last step. If the grub was installed in your earlier installation of kali, then you can manually add the entry of grub in Boot menu options from your UEFI settings. I've told this earlier.
You will find it where you see Windows OS Manager written.
This PC has no windows, it came with LInux, (Linpus Linux) , then I just used live boot and formated entire hardist, then repatitioned, then installed , I have many times re installed this but not loading, I just want to use Kali linux only, no other OS required in my PC....
You can still find that option in your UEFI settings in boot priority tab.
Where is that option ?
in BIOS there is no option for UEFI settings, its BIOS 1.08
The BIOS 1.08 is actually BIOS. BIOS are now obsolete and were replaced by UEFI. Your PC has UEFI firmware. Explore its settings. You will find that option soon or post a screenshot if you don't find it.
Does your hard drive have any data? How about if you completely format it and delete all partitions? Then kali installer will do rest of the thing. Atleast this is the closest alternative for new users.
I have Deleted all partions , then changed partion table to GPT, Then made 3 partions for NTFS and keppt 300GB freespace to install kali linux then installed kali ,and followed many steps, including your steps.
please check this screenshoots of my BIOS
https://ibb.co/hNmKF6
https://ibb.co/c5dYa6
https://ibb.co/cEu6v6
https://ibb.co/g69H2m
https://ibb.co/hQrVNm
these above links show all screens of BIOS
So now you have again installed kali and your PC is still showing No bootable device found? Is grub installed this time during the installation?
system not asked me for grubinstall
It doesn't ask. It proceeds to install grub automatically. You might have didn't notice it. It's the 2nd last step of the installation. Installing grub is also written there.
Anyway, I noticed your firmware is developed by Insyde. It has a different key to go to boot menu options. The key may be F11 or something else. Try it. There you will find an option Boot From EFI. Select it and show the screenshot.
I want to see if grub was actually installed. Boot into kali live and enter this command:
First check what is the partition name of your EFI partition(/dev/sda<number>) using fdisk -l
mount /dev/sda+ /mnt
ls /mnt
Then show its output.
Disk /dev/sdb: 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: gpt
Disk identifier: 82579936-BA37-47E7-8351-0A934116964F
Device Start End Sectors Size Type
/dev/sdb1 2048 488284159 488282112 232.9G Microsoft basic data
/dev/sdb2 488284160 976566271 488282112 232.9G Microsoft basic data
/dev/sdb3 976566272 1367191551 390625280 186.3G Microsoft basic data
/dev/sdb4 1367191552 1368242175 1050624 513M EFI System
/dev/sdb5 1368242176 1945495551 577253376 275.3G Linux filesystem
/dev/sdb6 1945495552 1953523711 8028160 3.8G Linux swap
Disk /dev/loop0: 2.5 GiB, 2651066368 bytes, 5177864 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:~# mount /dev/sda+ /mnt
mount: /mnt: special device /dev/sda+ does not exist.
root@kali:~# ls /mnt
root@kali:~# ls
Desktop Documents Downloads Music Pictures Public Templates Videos
root@kali:~# ls
Desktop Documents Downloads Music Pictures Public Templates Videos
root@kali:~# ls /mnt
root@kali:~# mount /dev/sdb4 /mnt
root@kali:~# ls /mnt
EFI
root@kali:~#
Go inside that directory. ls /mnt/EFI
Have you found Boot menu options?
root@kali:~# ls /mnt/EFI
kali
root@kali:~# ls /mnt/EFI/kali
grubx64.efi
root@kali:~#
See grubx64.efi is installed. Now go to boot menu options i told you earlier. You can boot kali from Boot from EFI.
There is no bootmenu option, only there is a BIOS , that I have launch by pressing F2,
the screenshoots I have shared
Try other function keys. There is one. F8,F9,F19,F10,F11,F12,Esc are more common.
I got a boot Manager window while clicking F12 , But it shows pendrive Only see this screenshot https://ibb.co/hLkSk6
If your partition's name starts from /dev/sdb then why you were writing grub-install /dev/sda? /dev/sda is the name of your hard disk. In fdisk -l if it shows /dev/sdb then the command should be grub-install /dev/sdb. I think you need to re-run those commands with correct names. Always use fdisk -l to see the names.
If your system freezes again. Then again run those commands but this time skip grub-install command and jump to update-grub.
In some reboots , the HDD name will shows sda and some rare time it shows sdb i was noticed that.... :) will try update-grub
Output of update gub , please check
root@kali:~# fdisk -l
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: gpt
Disk identifier: 82579936-BA37-47E7-8351-0A934116964F
Device Start End Sectors Size Type
/dev/sda1 2048 488284159 488282112 232.9G Microsoft basic data
/dev/sda2 488284160 976566271 488282112 232.9G Microsoft basic data
/dev/sda3 976566272 1367191551 390625280 186.3G Microsoft basic data
/dev/sda4 1367191552 1368242175 1050624 513M EFI System
/dev/sda5 1368242176 1945495551 577253376 275.3G Linux filesystem
/dev/sda6 1945495552 1953523711 8028160 3.8G Linux swap
Disk /dev/sdb: 7.5 GiB, 8004304896 bytes, 15633408 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: 0x36f39ff0
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 64 5646719 5646656 2.7G 17 Hidden HPFS/NTFS
/dev/sdb2 5646720 5648127 1408 704K 1 FAT12
Disk /dev/loop0: 2.5 GiB, 2651066368 bytes, 5177864 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:~# mount /dev/sda5 /mnt
root@kali:~#
root@kali:~# mount --bind /dev /mnt/dev
root@kali:~# mount --bind /proc /mnt/proc
root@kali:~# mount --bind /sys /mnt/sys
root@kali:~#
root@kali:~# mount --bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars
root@kali:~# mount /dev/sda4 /mnt/boot/efi
root@kali:~# mount -o remount,rw /dev/sda4 /mnt/boot/efi
root@kali:~# mount --bind /run /mnt/hostrun
root@kali:~# chroot /mnt
root@kali:/# mount --bind /hostrun/lvm /run/lvm
root@kali:/# update-grub
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.13.0-kali1-amd64
Found initrd image: /boot/initrd.img-4.13.0-kali1-amd64
WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sda3 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sda4 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sda5 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sda6 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 10000000 microseconds.
Adding boot menu entry for EFI firmware configuration
done
root@kali:/# fdisk -l
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: gpt
Disk identifier: 82579936-BA37-47E7-8351-0A934116964F
Device Start End Sectors Size Type
/dev/sda1 2048 488284159 488282112 232.9G Microsoft basic data
/dev/sda2 488284160 976566271 488282112 232.9G Microsoft basic data
/dev/sda3 976566272 1367191551 390625280 186.3G Microsoft basic data
/dev/sda4 1367191552 1368242175 1050624 513M EFI System
/dev/sda5 1368242176 1945495551 577253376 275.3G Linux filesystem
/dev/sda6 1945495552 1953523711 8028160 3.8G Linux swap
Disk /dev/sdb: 7.5 GiB, 8004304896 bytes, 15633408 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: 0x36f39ff0
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 64 5646719 5646656 2.7G 17 Hidden HPFS/NTFS
/dev/sdb2 5646720 5648127 1408 704K 1 FAT12
Disk /dev/loop0: 2.5 GiB, 2651066368 bytes, 5177864 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:/#
It is done. But you didn't umount them. Is it working now?
It is not working, I'm waiting for your help
It might have not worked because you didn't complete it. You were supposed to umount them. Sometimes changes are not written to the disk. They are saved in RAM and once you umount them, they are written to the disk.
root@kali:~# fdisk -l
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: gpt
Disk identifier: 82579936-BA37-47E7-8351-0A934116964F
Device Start End Sectors Size Type
/dev/sda1 2048 488284159 488282112 232.9G Microsoft basic data
/dev/sda2 488284160 976566271 488282112 232.9G Microsoft basic data
/dev/sda3 976566272 1367191551 390625280 186.3G Microsoft basic data
/dev/sda4 1367191552 1368242175 1050624 513M EFI System
/dev/sda5 1368242176 1945495551 577253376 275.3G Linux filesystem
/dev/sda6 1945495552 1953523711 8028160 3.8G Linux swap
Disk /dev/sdb: 7.5 GiB, 8004304896 bytes, 15633408 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: 0x36f39ff0
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 64 5646719 5646656 2.7G 17 Hidden HPFS/NTFS
/dev/sdb2 5646720 5648127 1408 704K 1 FAT12
Disk /dev/loop0: 2.5 GiB, 2651066368 bytes, 5177864 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:~# mount /dev/sda5 /mnt
root@kali:~# mount --bind /dev /mnt/dev
root@kali:~#
root@kali:~# mount --bind /proc /mnt/proc
root@kali:~# mount --bind /sys /mnt/sys
root@kali:~# mount --bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars
root@kali:~#
root@kali:~# mount /dev/sda4 /mnt/boot/efi
root@kali:~# mount -o remount,rw /dev/sda4 /mnt/boot/efi
root@kali:~#
root@kali:~# mount --bind /run /mnt/hostrun
root@kali:~# chroot /mnt
root@kali:/#
root@kali:/# mount --bind /hostrun/lvm /run/lvm
root@kali:/#
root@kali:/# update-grub
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.13.0-kali1-amd64
Found initrd image: /boot/initrd.img-4.13.0-kali1-amd64
WARNING: Device /dev/loop0 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sda1 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sda2 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sda3 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sda4 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sda5 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sda6 not initialized in udev database even after waiting 10000000 microseconds.
WARNING: Device /dev/sdb1 not initialized in udev database even after waiting 10000000 microseconds.
Adding boot menu entry for EFI firmware configuration
done
root@kali:/# exit
exit
root@kali:~# umount /mnt/dev
root@kali:~# umount /mnt/proc
root@kali:~# umount /mnt/sys
umount: /mnt/sys: target is busy.
root@kali:~# umount /mnt/sys/firmware/efi/efivars
root@kali:~# umount /mnt/boot/efi
root@kali:~# umount /mnt/hostrun
root@kali:~# umount /mnt/run/lvm
root@kali:~# umount /mnt
umount: /mnt: target is busy.
root@kali:~# umount /mnt/sys
root@kali:~# umount /mnt
root@kali:~#
This is the complete out put... and Im going to reboot the PC
Again same NO BOOTABLE DEVICE
Is there any true solution for this issue?
Kali linux officials are not saying anything.... and Acer team also denied to Help.....
I advice People dont buy Acer if u need to use Kali linux
That was a true solution. Delete your all partitions and allow kali to use entire disk. You can create your reserved partitions later.
I will do it now...
after install Kali in full disk can I make another NTFS partition for storing data seperatly?
Im thinking that, if we use full disk for kali , in every time kali load 1TB HDD in startupp and get slow, right ??
I will do it now...
after install Kali in full disk can I make another NTFS partition for storing data seperatly?
Yes you can create a partition later once you install kali.
I'm thinking that, if we use full disk for kali , in every time kali load 1TB HDD in startup and get slow, right ??
No, it doesn't. Don't believe in such things wherever you read from.
And update your BIOS.
Reinstaled with full HDD, but no hop..... everything as same before.... I think Kali linux is not supporting Acer.....
This is the problem with your non-updated UEFI firmware then. Kali installer always installs grub in the EFI partition of HDD and creates a entry of bootloader in the NVRAM. UEFI is responsible for keeping that entry in its NVRAM. The current version of Insyde UEFI firmware is F.22 and I just updated the firmware yesterday.
What if you try to install ubuntu and windows 10? Will they going to end up like this? The more you experiment, the more you learn. I highly recommend updating your firmware. There were some known vulnerabilities in Intel firmware which were fixed in later version. Those vulnerabilities allow attackers to inject bootkit in your firmware.