/etc/fstab file in Parrot OS rescue mode by booting from a Live USB, identifying your Western Digital drive with lsblk, mounting the root partition to /mnt, and using nano /mnt/etc/fstab to edit entries. This process allows you to correct UUID mismatches or add missing mount points for unformatted secondary drives without reinstalling the operating system.
Booting into the Rescue Environment
To access the underlying filesystem of a broken Parrot OS installation, you must first bypass the standard boot sequence. Insert a Parrot OS Live USB or any Debian-based live media into your machine. Restart the computer and enter the BIOS/UEFI settings, typically by pressing F2, Del, or Esc during startup. Change the boot order to prioritize the USB device. When the GRUB menu appears, select the option to boot from the USB. Once the desktop environment loads, open a terminal. You do not need to install anything on the hard drive yet; the live environment provides all necessary tools for system repair. This approach is similar to the methods described in our guide on How to Safely Change /etc/fstab in ParrotOS (Debian) on a Live USB with a Second Internal SSD, which covers general live USB editing procedures.Identifying the Western Digital Drive and Partitions
Before touching configuration files, you must know exactly which device node corresponds to your Western Digital hard drive. In the terminal, run the commandlsblk -f. This command lists all block devices along with their filesystem types, labels, and UUIDs. Look for the disk that matches the size and manufacturer of your WD drive. It will likely appear as sda, sdb, or vda depending on your hardware controller. Note the partition identifiers, such as sda1 for the EFI partition, sda2 for the root partition, and sda3 for swap or home. If you have an unformatted second drive, it may show up as sdb with no filesystem type listed. Do not guess the device names; using the wrong identifier can lead to data loss. For more context on handling storage devices in Debian environments, refer to our article on Installing Debian on a 115GB Hard Drive.
Mounting the System Root
The/etc/fstab file resides within the root partition of your installed OS, which is not mounted by default in the live environment. You need to manually mount this partition to a temporary directory. Create the mount point if it does not exist by running sudo mkdir -p /mnt. Then, mount your root partition. Assuming your root partition is sda2, execute sudo mount /dev/sda2 /mnt. If your system uses separate partitions for /boot or /home, you should mount those as well, though they are not strictly required for editing fstab. Verify the mount was successful by checking the contents of /mnt with ls /mnt. You should see directories like bin, etc, usr, and var. If these are present, you are ready to edit the configuration file.
Editing the /etc/fstab File
Navigate to the etc directory within your mounted system and open the fstab file using a text editor. Runsudo nano /mnt/etc/fstab. The file contains lines that define how disk partitions, swap space, and other storage devices are mounted into the filesystem tree. Each line has six columns: device, mount point, filesystem type, options, dump frequency, and pass number. Common issues include incorrect UUIDs, missing mount points for new drives, or incorrect filesystem types. To fix a UUID mismatch, find the current UUID of your drive using blkid /dev/sdaX and replace the old UUID in the fstab file. If you want to add your unformatted Western Digital drive, you must first format it with a tool like mkfs.ext4 or mkfs.ntfs, then add a corresponding entry to fstab. Be careful not to delete existing critical entries for / or /boot/efi. Save the file by pressing Ctrl+O, Enter, and exit with Ctrl+X.
Verifying and Unmounting
After saving changes, it is prudent to verify the syntax of the fstab file before rebooting. You can use the commandsudo chroot /mnt followed by mount -a to simulate the mounting process. If there are errors, the system will report them, allowing you to fix them while still in the live environment. Once satisfied, exit the chroot environment by typing exit. Now, unmount the partitions in reverse order of mounting to ensure data integrity. Run sudo umount /mnt. If you mounted other partitions, unmount them as well. Finally, remove the Live USB and reboot your computer. Your Parrot OS should now boot correctly with the updated fstab entries. Remember that improper fstab configurations can prevent booting, so always back up the original file before making changes. For related troubleshooting on external drive mounting issues, see our guide on Mounting External Drives with mount command in fstab not working: A Troubleshooting Guide.
Frequently Asked Questions
What happens if I enter the wrong UUID in /etc/fstab?
If the UUID is incorrect, the system will fail to mount the corresponding partition during boot. This often results in a drop to a emergency shell or a "Give root password for maintenance" prompt. You will need to boot from a live USB again to correct the typo.
Can I edit /etc/fstab while booted into my installed Parrot OS?
No, you cannot edit the active /etc/fstab while the system is running because the kernel has already read it to mount partitions. Changes only take effect after a reboot. Always use a live environment or recovery mode to make structural changes.
How do I find the UUID of my Western Digital drive?
Open a terminal and run blkid /dev/sdX, replacing sdX with your specific drive letter. The output will display a string starting with UUID=. Copy this value exactly, including the hyphens, when editing fstab.
Do I need to format the drive before adding it to fstab?
Yes, you must format the drive with a filesystem like ext4 or NTFS before it can be mounted. An unformatted drive has no filesystem type, so fstab cannot mount it. Use sudo mkfs.ext4 /dev/sdX to create a Linux-compatible filesystem.
Why does my system drop to a rescue shell after editing fstab?
This usually indicates a syntax error or a missing mount point in the fstab file. Check for typos in device names, mount paths, or filesystem types. Ensure that every non-comment line has the correct number of fields separated by spaces or tabs.