Struggle to mount storage partition (system call failed: No such file or directory)

Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
User avatar
SprinterDriver
Level 4
Level 4
Posts: 260
Joined: Sun Jan 25, 2015 3:35 pm
Location: Norway

Struggle to mount storage partition (system call failed: No such file or directory)

Post by SprinterDriver »

Hi.

I have had this work many times before, and I cannot understand why it doesn't work this time.

It is the same computer as discussed in this thread, the Dell Optiplex 780 with SSD + HDD, now I have activated the third storage device.

This happens when trying to mount

Code: Select all

sprinterdriver@OptiPlex-780:~$ sudo mount -a
[sudo] password for sprinterdriver:          
mount: /terralager: mount(2) system call failed: No such file or directory.
lsblk

Code: Select all

sudo lsblk --fs
NAME   FSTYPE LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                          
├─sda1 ext4              37f68ebe-1ea5-4cdd-ac94-a44d321f8d22  720,1M    21% /boot
├─sda2 btrfs  Håom       4d3c5932-453b-4eb2-9a71-3c017b230cd7   43,3G    11% /home
├─sda3 btrfs  lager1     879e6a15-206b-46c2-881f-197d79808eda   59,4G    72% /lager1
└─sda4 ext4              45c07f2f-eca6-4948-aaed-2471610b22d4   26,2G     3% /var
sdb                                                                          
└─sdb1 btrfs  terralager d77d3850-667c-43d8-a806-779286baa711                
sdc                                                                          
├─sdc1 swap              4cb64699-ed99-4431-9e28-37c50244d887                [SWAP]
└─sdc2 btrfs             746dc818-52db-4720-ba39-c26494ee3007   64,8G     8% /
sr0
/etc/fstab

Code: Select all

sudo cat /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>
# / was on /dev/sdb2 during installation
UUID=746dc818-52db-4720-ba39-c26494ee3007 /               btrfs   defaults,subvol=@ 0       1
# /boot was on /dev/sda1 during installation
UUID=37f68ebe-1ea5-4cdd-ac94-a44d321f8d22 /boot           ext4    defaults        0       2
# /home was on /dev/sda2 during installation
UUID=4d3c5932-453b-4eb2-9a71-3c017b230cd7 /home           btrfs   defaults,subvol=@home 0       2
# /lager1 was on /dev/sda3 during installation
UUID=879e6a15-206b-46c2-881f-197d79808eda /lager1         btrfs   defaults        0       2
# /var was on /dev/sda4 during installation
UUID=45c07f2f-eca6-4948-aaed-2471610b22d4 /var            ext4    defaults        0       2
# swap was on /dev/sdb1 during installation
UUID=4cb64699-ed99-4431-9e28-37c50244d887 none            swap    sw              0       0
#
# Terralager internal hdd extra storage space
UUID=d77d3850-667c-43d8-a806-779286baa711 /terralager     btrfs   defaults,subvol=@ 0     1
Content of top directory

Code: Select all

root@OptiPlex-780:/# ls -l
total 48
lrwxrwxrwx    1 root           root              7 Jan 16 23:42 bin -> usr/bin
drwxr-xr-x    4 root           root           4096 Jan 17 00:10 boot
drwxr-xr-x    1 root           root              0 Jan 16 23:45 cdrom
drwxr-xr-x   20 root           root           4560 Jan 17 00:46 dev
drwxr-xr-x    1 root           root           4248 Jan 17 00:30 etc
drwxr-xr-x    1 root           root              8 Apr 15  2020 home
drwxrwxr-x.   1 sprinterdriver sprinterdriver  138 Aug 19 13:37 lager1
lrwxrwxrwx    1 root           root              7 Jan 16 23:42 lib -> usr/lib
lrwxrwxrwx    1 root           root              9 Jan 16 23:42 lib32 -> usr/lib32
lrwxrwxrwx    1 root           root              9 Jan 16 23:42 lib64 -> usr/lib64
lrwxrwxrwx    1 root           root             10 Jan 16 23:42 libx32 -> usr/libx32
drwxr-xr-x    1 root           root              0 Jan  4 15:14 media
drwxr-xr-x    1 root           root              0 Jan  4 15:14 mnt
drwxr-xr-x    1 root           root              0 Jan  4 15:14 opt
dr-xr-xr-x  303 root           root              0 Jan 17 00:46 proc
drwx------    1 root           root            122 Jan 17 00:21 root
drwxr-xr-x   34 root           root            900 Jan 17 00:46 run
lrwxrwxrwx    1 root           root              8 Jan 16 23:42 sbin -> usr/sbin
drwxr-xr-x    1 root           root              0 Jan  4 15:14 srv
dr-xr-xr-x   13 root           root              0 Jan 17 00:46 sys
drwxr-xr-x    1 root           root              0 Jan 17 00:33 terralager
drwxrwxrwt    1 root           root           1256 Jan 17 00:57 tmp
drwxr-xr-x    1 root           root            116 Jan  4 15:14 usr
drwxr-xr-x   12 root           root           4096 Jan  4 15:48 var

[edit]

Sorry, this starting to be a bad habit of me, starting posts in forums and then figure out the solution before anyone get time to involve in discussion. This is no exception.

While reading through my own post just after submitting, I realized that the other storage partition /lager1 , that was already there when install (I added the mount point during Mint installation) did not had the subvol option for btrfs in fstab. So I tried to remove that, and now it work.

The new line in /etc/fstab is just changed to

Code: Select all

UUID=d77d3850-667c-43d8-a806-779286baa711 /terralager     btrfs   defaults   0     1

The only thing I don't like about this is that the solution was just a strike of luck. If I haven't seen the line with /lager1 in /etc/fstab, I wouldn't have figured this out.

So therefore I have a follow up question : How can I list up subvolumes in btrfs volumes (a web search reveals how to create, but cannot find any way to differentiate between subvolume and ordinary folders on the root folder of the volume) ?

Also, how does subvol=@ differs from not having that mount option at all ?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
So I got this bright idea. But when I tried to grab the light bulb, I did not hurt my hands as expected from a warm bulb, because it turned out to be one of those LED bulbs.
Locked

Return to “Storage”