Emergency mode boot in deployment 0 after secondary drive formatting
Please forgive any stupidity on display, as this is my first Linux experience
Yesterday night, after biting the bullet and formatting my storage HDD to btrfs with mount point /var/mnt/media, a reboot sent me into the emergency mode this morning. Deployment 1 works fine, so I went to work troubleshooting there. After changing the mount point, because "maybe the word "media" is causing some conflicts idk", I rebooted into 0 to find the mount point unchanged and still broken. So, is deployment 0 dead to me now? How do I set 1 as my main, or fix 0?
Yesterday night, after biting the bullet and formatting my storage HDD to btrfs with mount point /var/mnt/media, a reboot sent me into the emergency mode this morning. Deployment 1 works fine, so I went to work troubleshooting there. After changing the mount point, because "maybe the word "media" is causing some conflicts idk", I rebooted into 0 to find the mount point unchanged and still broken. So, is deployment 0 dead to me now? How do I set 1 as my main, or fix 0?
Solution
UPD:
Following this guide (https://www.youtube.com/watch?v=-2wca_0CpXY), resetting the mount point and the perms of the drive solved the issue
Following this guide (https://www.youtube.com/watch?v=-2wca_0CpXY), resetting the mount point and the perms of the drive solved the issue
YouTubeMike's Tech Tips
In this video we'll look at the scenarios that get Linux into emergency mode and the process of fixing your fstab file to get it out of emergency mode
timestamps
00:00 Introduction
00:31 Scenarios that cause Linux to go into emergency mode
00:54 The current issue
01:12 Summary of the solution
01:35 Getting into Grub
02:13 Editing Grub at boot t...
timestamps
00:00 Introduction
00:31 Scenarios that cause Linux to go into emergency mode
00:54 The current issue
01:12 Summary of the solution
01:35 Getting into Grub
02:13 Editing Grub at boot t...
