1. Your Parrot information
- OS version: run
cat /etc/*release
DISTRIB_ID=Parrot DISTRIB_RELEASE=4.10 DISTRIB_CODENAME=rolling DISTRIB_DESCRIPTION="Parrot 4.10" PRETTY_NAME="Parrot GNU/Linux 4.10" NAME="Parrot GNU/Linux" ID=parrot ID_LIKE=debian VERSION="4.10" VERSION_ID="4.10" HOME_URL="https://www.parrotsec.org/" SUPPORT_URL="https://community.parrotsec.org/" BUG_REPORT_URL="https://community.parrotsec.org/
- Kernel version: run
uname -a
```
Linux parrot 5.7.0-2parrot2-amd64 #1 SMP Debian 5.7.10-1parrot2 (2020-07-31) x86_64
GNU/Linux
```
Or if you can’t do it, please tell us ISO version you downloaded.
** ISO information **
Version: 4.9
Desktop Environment: Mate
Edition: Security
2. If you have this problem after fresh installation:
-
How did you create USB bootable?
- Software was used to make USB
- Steps of making USB bootable
Installed Parrot OS like many months ago from bootable USB > Desktop install icon and follow the prompts
- How did you install OS?
- Debian installer
3. If your hardware doesn’t work: wifi doesn’t show, graphic issue:
Hardware information
- Your device name or output of `lspci`
```
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 515 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08)
00:05.0 Multimedia controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Imaging Unit (rev 01)
00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:14.3 Multimedia controller: Intel Corporation CSI-2 Host Controller (rev 01)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.2 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #2 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:16.3 Serial controller: Intel Corporation Sunrise Point-LP Active Management Technology - SOL (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1e.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO UART Controller #0 (rev 21)
00:1e.6 SD Host controller: Intel Corporation Sunrise Point-LP Secure Digital IO Controller (rev 21)
00:1f.0 ISA bridge: Intel Corporation LPC/eSPI Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
3a:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
3b:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
```
- Did you try searching info about this issue on search engine? Please write **No** or any URL to this issue bellow
Yes
4. How did you get this error? Are there any steps to procedure it?
1. I installed this
2. I ran this new software
3. It shows me this or that
Removed my SSD and replaced it with a Windows 10 SSD so I can update my bios, after updating the bios, I reconnected the parrot SSD. It does not boot to GRUB loader anymore.
nvme0n1p1 is my efi system partition, type is vFAT. nvme0n1p2 contains root and everything else, type is BTRFS.
I tried to mount p1 to /boot , /boot/efi, /mnt/boot/efi on different occasions.
I tried to mount p2 to /mnt.
Whenever I try to mount or bind, p1 and p2 will automatically be mounted to /mnt/@ and /mnt/@home.
i tried to do a grub-install command (after chrooting) with --target x86_x64-efi, with all combinations of --efi-directory and --root-directory, it would often come up asking if /boot has been mounted, it cant find an efi system (even though it is mapped as is.)
Every time I tried to chroot to /mnt, it would say it is not added to /bin/bash. chroot /mnt /bin/bash would not work too. I have to chroot /mnt/@ then i would be able to access as root.
5. Error log or screenshot
┌─[user@parrot]─[~]
└──╼ $sudo fdisk -l
Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 970 EVO Plus 1TB
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: gpt
Disk identifier: CD3DDF53-AE93-2644-90A5-A83A13E83973
Device Start End Sectors Size Type
/dev/nvme0n1p1 4096 618495 614400 300M EFI System
/dev/nvme0n1p2 618496 1953520064 1952901569 931.2G Linux filesystem
Disk /dev/sda: 28.65 GiB, 30765219840 bytes, 60088320 sectors
Disk model: SanDisk 3.2Gen1
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: 0x114c4603
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 64 8424107 8424044 4G 17 Hidden HPFS/NTFS
/dev/sda2 8424108 8425579 1472 736K 1 FAT12
Disk /dev/loop0: 3.75 GiB, 4024725504 bytes, 7860792 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
┌─[user@parrot]─[~]
└──╼ $lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 3.7G 1 loop /usr/lib/live/mount/rootfs/filesystem.squashfs
sda 8:0 1 28.7G 0 disk
├─sda1 8:1 1 4G 0 part /usr/lib/live/mount/medium
└─sda2 8:2 1 736K 0 part
nvme0n1 259:0 0 931.5G 0 disk
├─nvme0n1p1 259:1 0 300M 0 part /boot
└─nvme0n1p2 259:2 0 931.2G 0 part /mnt
┌─[user@parrot]─[~]
└──╼ $cat /mnt/@/etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=B39A-1643 /boot/efi vfat defaults,noatime 0 2
UUID=f5fc61d9-b013-4534-8d1b-96ed74d4e382 / btrfs subvol=@,defaults,noatime,nodiratime,nodatacow,space_cache,autodefrag 0 1
UUID=f5fc61d9-b013-4534-8d1b-96ed74d4e382 /home btrfs subvol=@home,defaults,noatime,nodiratime,nodatacow,space_cache,autodefrag 0 2
6. If you have any idea or suggestion about this issue please tell us
** Your information **
Tried to follow the below guide and a few others but they arent specific enough as I am dealing with a x86_64 image and a SSD.
https://community.parrotsec.org/t/restoring-grub-efi/1914
I even tried to post on unix stackexchange but it is not fruitful yet. There are a lot of posts about other linux distros and different scenarios, none of them works in my context.
If you are having suggestion for our OS, please write it bellow
1. Current Parrot version and Parrot version you want it has
2. Its section and how it affects our system
- Pentesting / Forensic / Malware hunting / Privacy protection / …
- It is: AppArmor profile / software / system service / kernel module…
- when user runs this / start that, it can do…