Page 1 of 6 123 ... LastLast
Results 1 to 10 of 52

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

  1. #1
    Junior Member
    Join Date
    Nov 2017
    Posts
    27

    Unhappy 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
    Last edited by maiki; 2017-11-23 at 09:57 AM. Reason: Removed Link in Signature

  2. #2
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    813
    Boot into kali live and show the output of fdisk -l

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

  4. #4
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    813
    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:
    Code:
    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.
    Last edited by _defalt; 2017-11-26 at 07:49 AM.

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

  6. #6
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    813
    I edited it. Do it again.

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

  8. #8
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    813
    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?

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

  10. #10
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    813
    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.
    Last edited by _defalt; 2017-11-26 at 07:47 AM.

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
  •