Hello
After a power outage my file system got messed up and one of the internal disk went missing. Saying this because when I use the command in the terminal
It’s important to keep in mind that the community volunteers are not paid professionals and the forum is not a commercial support service.
– Effectively using the forum to get support
I have problem with this: UUID="1102fe71-ef5c-4037-838d-7c82ae39ef87" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="27edd0df-af64-4cc8-b0eb-a320dd5c8c0a"
I don’t know where to put it. This is why I am asking you kindly how to restore the fstab to its previous state automatically because I have little trust in my capabilities…
Bottom line I found this but I don’t think it will work for Manjaro:
I don’t know which “solution” you think I gave you, but all I posted were two tutorials, and the fact that you are now running into a problem suggests that you did not do everything as you were supposed to do — whichever that was, because you’re not telling us.
/run is a tmpfs — its contents only exist in virtual memory. Therefore, they make a poor choice for setting up a static mountpoint, given that the mountpoint will cease to exist once you power down the computer.
/run/media is only used when relying on auto-mounted filesystems, and auto-mounting should only be used on removable media.
Read the tutorials again. Make sure you understand what is being said.
Only if your editor is set to create backups of the file being edited. There is no other backup. And of course, you’re supposed to back up your system anyway.
If you have a timeshift backup, then you can restore that, or — if you know what you’re doing — dig up the /etc/fstab file from one of the recent backups and copy it back. The actual files are always located under /run/timeshift/snapshots/<date-and-time-here>/localhost.
You may refer to bookmarks in Dolphin. These can be volatile and you might have simply picked the folder /run/media/… when you created them.
If your current problem is to undo your failed fix, simply login at the system prompt emergency shell (or by adding rescue to the kernel line), comment out the respective fstab line you added (failed fix) and reboot. This way the system won’t touch it, but you can use the system to do whatever outside said borked ntfs partition mount. You can also use it to post your fstab and the output of mount after the reboot. It is unlikely the fstab is corrupt, unless you were editing just before the power outage occurred.
