Briefly describe your issue below:
I’ve tried installing parrot os 4.6 through a USB on my Acer laptop but after it is complete I pull out my USB and after reboot it keeps giving me “No bootable device” how can I fix this?
What version of Parrot are you running? (include version (e.g. 4.6), edition(e.g. Home//KDE/OVA, etc.), and architecture (currently we only support amd64)
What method did you use to install Parrot? (Debian Standard / Debian GTK / parrot-experimental)
Configured to multiboot with other systems? (yes / no)
If there are any similar issues or solutions, link to them below:
If there are any error messages or relevant logs, post them below:
Hello! Sorry to here about the error. So frustrating when you get through the whole thing and then just crickets when you go to boot. Especially since the system doesn’t really explain what went south after a seemingly smooth install.
Anyways, let’s square away some details since the MIA bootloader can manifest from various scenarios. Lets start with your bootable USB. Even slight discrepencies in the creation of your install media can lead to an unsuccessful install. Couple questions to start and then we can go from there.
What method did you use to create your USB stick, and what OS were you using when you created it? Balena’s Etcher? dd? Something else? Also let us know if your thumb drive is USB 2 or 3 (either will work fine, but I’ve run into issues in scenarios like writing to a USB3 drive then inserting it into a USB2 port for the installation).
Tell us about your installation process and the drive you attempted to install to. Did you use the guided install for an entire disk, or something a little fancier that involved manual disk partitioning? Also add whatever information you can about the disk you were attempting to install to. Is it a new hard drive? Or maybe a used one that had some existing partitions lingering on it.
Are you attempting a duel boot?
Let’s shed some light on those points first so we can either rule out or triage corrupted installation media
One last question. Did you configure your computer’s BIOS to recognize the new installation? Both setting it to the first boot priority and ensuring Legacy/UEFI compatability.
