Page 5 of 6 FirstFirst ... 3456 LastLast
Results 41 to 50 of 52

Thread: No Bootable device issue after Installing Kali Linux - Acer Aspire ES1-533

  1. #41
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    810
    Did it work?

  2. #42
    Junior Member
    Join Date
    Nov 2017
    Posts
    27
    Output of update gub , please check
    Code:
    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:/#

  3. #43
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    810
    It is done. But you didn't umount them. Is it working now?

  4. #44
    Junior Member
    Join Date
    Nov 2017
    Posts
    27
    It is not working, I'm waiting for your help

  5. #45
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    810
    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.

  6. #46
    Junior Member
    Join Date
    Nov 2017
    Posts
    27
    Code:
    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

  7. #47
    Junior Member
    Join Date
    Nov 2017
    Posts
    27
    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

  8. #48
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    810
    That was a true solution. Delete your all partitions and allow kali to use entire disk. You can create your reserved partitions later.

  9. #49
    Junior Member
    Join Date
    Nov 2017
    Posts
    27
    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 ??

  10. #50
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    810
    Quote Originally Posted by bsmith View Post
    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.

    Quote Originally Posted by bsmith View Post
    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.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •