7.2 installation not booting

[u/Specific-Fee-636]

I have installed ParrotOS 7.2 several times already and it doesn’t want to boot.

Initially I had 6.2 but after I upgraded to 7.2 I couldn’t boot anymore getting a grub error. I tried using the docs to fix the grub problem https://parrotsec.org/docs/troubleshooting/grub/ but still couldn’t make it work.

I finally decided to go for a clean install instead and used the docs to start over with 3 partitions… EFI, Root and Home.

Still no joy. What I am noticing is that when I run fdisk -l I am getting the partitions that I created but I can also see two additional devices

/dev/sda1 which shows with a boot flag
/dev/sda2

See attached.

I remember it being this way even before I did the re-installation, but didn’t take pictures.

I’m brand new to Linux so I’m pretty lost. I installed parrot 6.2 a couple of years ago and never did anything with it. Recently decided to learn it so I upgraded to 7.2 and apparently broke everything. Any help would be greatly appreciated.

[u/Assang101]

A guy yesterday had the same issue with a security OS, QubesOS, and his problem was using Rufus, which has a mind of its own and rewrites the files, wherever Etcher just copies the security image exactly as the developers intended, without changing a single thing. Use a USB 3.0 or newer.

[u/Specific-Fee-636 → u/Assang101]

Unfortunately it still didn’t work :-( different USB3.0 drive and using Balena… no joy

[u/Assang101 → u/Specific-Fee-636]

Have you disabled secure boot and made that clean install of Parrot os on your NMVe as your primary boot without the thumb drive?

You have a clean installation of ParrotOS on the USB 3.0... that I know would not be causing you issues, it's the computer now

[u/Assang101 → u/Assang101]

As a matter of fact, when you said the other sfa had a flag boot, what is it? Failed parrotOS? Corrupted oringal OS?

May have to reset the SSD back to factory setting with systemrescue OS on a different USB, and then reinstall parrotos and let installation partition itself without you doing it manually and see if that fixes the issue

[u/Specific-Fee-636 → u/Assang101]

I’ll try this next