Restoring file system

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


/dev/nvme0n1p1: UUID="3332-4A96" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="1474c318-785a-480d-8531-b49a255c82a1"
/dev/nvme0n1p2: UUID="ed9304b3-56ab-4fd9-8834-ad4a80bb4734" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c507a792-ad28-4d21-80a9-09ff799d1061"
/dev/sda1: BLOCK_SIZE="512" UUID="74887B8F06B25C1C" TYPE="ntfs" PARTUUID="27b8abf7-01"
/dev/sdb1: LABEL="Games" UUID="cb609a3b-fe9a-4d56-82b9-94b133e6c0b1" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="00c02aae-01"
/dev/sdc1: LABEL="ZM-CM-!loha I" BLOCK_SIZE="512" UUID="A8F4FEE6F4FEB622" TYPE="ntfs" PARTUUID="0005f519-01"
/dev/sdd1: UUID="1102fe71-ef5c-4037-838d-7c82ae39ef87" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="27edd0df-af64-4cc8-b0eb-a320dd5c8c0a"
/dev/sde2: LABEL="ZM-CM-!loha III" BLOCK_SIZE="512" UUID="4214F02314F01C1B" TYPE="ntfs" PARTUUID="9acec1b2-02"

The missing one:


The system registers it (same goes to the GParted) but the Dolphin and other applications are blind to it.
Any help?

What did you do to solve this yourself?

What have you researched?

What have you found?

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

The disk is not missing, only the mount point.

I searched for answers this forum and the Manjaro wiki and on the Internet found only solutions for Ubuntu from 2009

Alright thanks.
How can I restore it? Is there any automatic backup for mount points? And I don’t think using the IBM solution is a good idea…

Thank you
And if I understand correctly I have to add these lines to the fstab file:

UUID=74887B8F06B25C1C /run/media/oracle911/74887B8F06B25C1C/
ntfs-3g  auto,nofail,uid=1000,gid=1000,utf8,umask=022,defaults   0   0
UUID=4214F02314F01C1B /run/media/oracle911/Záloha III ntfs-3g  auto,nofail,uid=1000,gid=1000,utf8,umask=022,defaults   0   0
UUID=A8F4FEE6F4FEB622 ntfs-3g  /run/oracle911/Záloha I auto,nofail,uid=1000,gid=1000,utf8,umask=022,defaults   0   0
UUID=cb609a3b-fe9a-4d56-82b9-94b133e6c0b1 /run/media/oracle911/Games

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 tried this solution. It failed miserably

Now what?

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. :slightly_frowning_face:

Actually I did tell you above and I did NOT try the Ubuntu solution:

/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.

1 Like

OK, what is your suggestion?
And is there any automatically created backup for fstab (not sure if the crontab is active)?

Read the tutorials again. Make sure you understand what is being said. :man_shrugging:

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.

1 Like
/dev/sda1: BLOCK_SIZE="512" UUID="74887B8F06B25C1C" TYPE="ntfs"

The device is Windows proprietary filesystem - don’t try to fix it on Linux.

Boot Windows and use the Disk Manager to correct the errors.

It is legacy disk and I do NOT have windows…
Edit: And also it explains why a certain folder appears to be empty in the Dolphin manager…

You can use

Use ventoy to create a bootabel USB

sudo pacman -Syu ventoy

Is that a live CD?

It is a Windows PE tool ISO

  • completely legit for the use case
  • you could call it live
  • but you cannot install the system
  • so it is more like a rescue, tools and utility system
1 Like

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.

I did not edited the fstab and I commented the failed fix and rebooted afterwards (and later deleted them).

How can I fix it, is there tutorial o thread?