How to install a secondary drive + partitions

Thanks for the information but, we really need to take a look at the contents of “/etc/fstab” to see “what’s being mounted where”.

The contents of the “root” directory “/” (which, by the way, ** isn’t ** the ‘home’ directory of the user “root” – that’s usually the directory “/root/” on the system disk (partition)) are indicating that:

  • Apart from the system directories, you have only one user directory.
  • Whether or not the system directories with variable content ("/tmp/" and “/var/”) have their own partitions is not clear from the information provided so far.

/dev/sda has partitions as follows: 126 G Linux; 30 G Linux swap; 755 G Microsoft.
/dev/sdb has partitions as follows: 2 G Linux swap; 40 G Linux; 920 G Linux; 901 G Linux.
/dev/sdc has partitions as follows: 930 G Linux.
/dev/sdd has partitions as follows: 31 G Microsoft.
/dev/sdi has partitions as follows: 500 G Microsoft.

We really need the contents of “/etc/fstab” to be able to see where the partitions are being mounted.

And, because the fstab nowadays uses mostly UUIDs to identify the devices, we also need the links between UUIDs and partitions:

ls -l /dev/disk/by-uuid/

BTW
Instead of typing things like:

Result for “fdisk --list” :

it is easier (in any case for us, but I assume also for you) to simply post the line above the output (where the command is) together with the output. Best to copy/paste the line with the prompt and command, then the output that follows and including the line with the new prompt. All can see then what is your working directory, if your are root or end-user, what you typed and that it is complete. In other words, we then see what you saw and that is what this is all about.

/etc/fstab = permission denied.

Knowing its a konsole started with root rights (or at last Ive needed to login then the first part is red).

Result for "ls -l /dev/disk/by-uuid/ "

ls -l /dev/disk/by-uuid/ 
total 0
lrwxrwxrwx 1 root root 10 31 janv. 14:06 1e843072-3676-4a07-9591-bba2c991a61c -> **../../sdb4**
lrwxrwxrwx 1 root root  9 31 janv. 14:07 428179480037036A -> **../../sr0**
lrwxrwxrwx 1 root root 10 31 janv. 14:06 4e3e1359-cb9d-4971-b933-25b50e456c10 -> **../../sdb2**
lrwxrwxrwx 1 root root 10 31 janv. 14:06 895c5b18-748a-485d-8d8b-27f4bdf57e06 -> **../../sdc1**
lrwxrwxrwx 1 root root 10 31 janv. 14:07 b03efe3c-475c-498f-87b0-a08ec84e8aa4 -> **../../sda1**
lrwxrwxrwx 1 root root 10 31 janv. 14:06 e2728a66-fad8-4c32-ae0d-9e48bee97e78 -> **../../sda2**
lrwxrwxrwx 1 root root 10 31 janv. 14:06 E422C6F222C6C92E -> **../../sda3**
lrwxrwxrwx 1 root root 10 31 janv. 14:06 e9e43288-02ca-426b-b29b-b6bab2f1a7df -> **../../sdb1**
lrwxrwxrwx 1 root root 10 31 janv. 14:06 eab89bf6-286e-4939-ab98-71cd267e9c7c -> **../../sdb3**
lrwxrwxrwx 1 root root 10 31 janv. 14:06 F0E9-334E -> **../../sdd1**

/etc/fstab” is ‘normally’ owned by the user “root” with the group “root”, with “owner” ‘rw’ permission and “group” and “other” (“world”) ‘r’ permission.

Given the number of disks being considered here, for readability I would recommend “/dev/disk/by-id/” over the UUID. This also has the advantage that, the mount point name doesn’t change if the partition is reformatted: formatting changes the UUID of the partition.

On the other hand, if you’re using YaST to manage the partitions with UUID preferred, YaST will automatically update the “fstab” UUID entry if the partition is reformatted by means of YaST. <https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.advdisk.html>.

BTW, this openSUSE SDB entry is possibly useful for the Microsoft (Redmond) partitions: <https://en.opensuse.org/SDB:NTFS>.

Yes, and the first action one does when getting such an error message is of course looking at what ownership and permissions are!

ls -l /etc/fstab

I lost counting a bit, but this is I think the third time that I see something rotten in this system. IMO as long as that is not addressed surprises will be forthcoming.

****, took me some time to figure it, fstab = file, not folder.
In any case, here is the content of that file from ‘/etc/’


UUID=e2728a66-fad8-4c32-ae0d-9e48bee97e78 swap swap pri=2 0 0
UUID=e9e43288-02ca-426b-b29b-b6bab2f1a7df swap swap pri=1 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 / btrfs defaults 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /opt btrfs subvol=@/opt 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /srv btrfs subvol=@/srv 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /tmp btrfs subvol=@/tmp 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /usr/local btrfs subvol=@/usr/local 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/cache btrfs subvol=@/var/cache 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/crash btrfs subvol=@/var/crash 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/lib/libvirt/images btrfs subvol=@/var/lib/libvirt/images 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/lib/machines btrfs subvol=@/var/lib/machines 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/lib/mailman btrfs subvol=@/var/lib/mailman 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/lib/mariadb btrfs subvol=@/var/lib/mariadb 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/lib/mysql btrfs subvol=@/var/lib/mysql 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/lib/named btrfs subvol=@/var/lib/named 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/lib/pgsql btrfs subvol=@/var/lib/pgsql 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/log btrfs subvol=@/var/log 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/opt btrfs subvol=@/var/opt 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/spool btrfs subvol=@/var/spool 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/tmp btrfs subvol=@/var/tmp 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /.snapshots btrfs subvol=@/.snapshots 0 0
UUID=b03efe3c-475c-498f-87b0-a08ec84e8aa4 /boot                ext3       acl,user_xattr        1 2
UUID=eab89bf6-286e-4939-ab98-71cd267e9c7c /home                xfs        defaults              1 2

As to the content of /dev/disk/by-id/ :


file:///dev/disk/by-id/ata-Hitachi_HDS721010CLA332_JP2940HQ2T50UH
file:///dev/disk/by-id/ata-Hitachi_HDS721010CLA332_JP2940HQ2T50UH-part1
file:///dev/disk/by-id/ata-Hitachi_HDS721010CLA332_JP2940HQ2T50UH-part2
file:///dev/disk/by-id/ata-Hitachi_HDS721010CLA332_JP2940HQ2T50UH-part3
file:///dev/disk/by-id/ata-ST1000DM010-2EP102_Z9ALY182
file:///dev/disk/by-id/ata-ST1000DM010-2EP102_Z9ALY182-part1
file:///dev/disk/by-id/ata-TSSTcorp_CDDVDW_SH-S223L_R1296GGZB00069
file:///dev/disk/by-id/ata-WDC_WD2003FYPS-27Y2B0_WD-WCAVY5450448
file:///dev/disk/by-id/ata-WDC_WD2003FYPS-27Y2B0_WD-WCAVY5450448-part1
file:///dev/disk/by-id/ata-WDC_WD2003FYPS-27Y2B0_WD-WCAVY5450448-part2
file:///dev/disk/by-id/ata-WDC_WD2003FYPS-27Y2B0_WD-WCAVY5450448-part3
file:///dev/disk/by-id/ata-WDC_WD2003FYPS-27Y2B0_WD-WCAVY5450448-part4
file:///dev/disk/by-id/scsi-0ATA_Hitachi_HDS72101_JP2940HQ2T50UH
file:///dev/disk/by-id/scsi-0ATA_Hitachi_HDS72101_JP2940HQ2T50UH-part1
file:///dev/disk/by-id/scsi-0ATA_Hitachi_HDS72101_JP2940HQ2T50UH-part2
file:///dev/disk/by-id/scsi-0ATA_Hitachi_HDS72101_JP2940HQ2T50UH-part3
file:///dev/disk/by-id/scsi-0ATA_ST1000DM010-2EP1_Z9ALY182
file:///dev/disk/by-id/scsi-0ATA_ST1000DM010-2EP1_Z9ALY182-part1
file:///dev/disk/by-id/scsi-0ATA_WDC_WD2003FYPS-2_WD-WCAVY5450448
file:///dev/disk/by-id/scsi-0ATA_WDC_WD2003FYPS-2_WD-WCAVY5450448-part1
file:///dev/disk/by-id/scsi-0ATA_WDC_WD2003FYPS-2_WD-WCAVY5450448-part2
file:///dev/disk/by-id/scsi-0ATA_WDC_WD2003FYPS-2_WD-WCAVY5450448-part3
file:///dev/disk/by-id/scsi-0ATA_WDC_WD2003FYPS-2_WD-WCAVY5450448-part4
file:///dev/disk/by-id/scsi-1ATA_Hitachi_HDS721010CLA332_JP2940HQ2T50UH
file:///dev/disk/by-id/scsi-1ATA_Hitachi_HDS721010CLA332_JP2940HQ2T50UH-part1
file:///dev/disk/by-id/scsi-1ATA_Hitachi_HDS721010CLA332_JP2940HQ2T50UH-part2
file:///dev/disk/by-id/scsi-1ATA_Hitachi_HDS721010CLA332_JP2940HQ2T50UH-part3
file:///dev/disk/by-id/scsi-1ATA_ST1000DM010-2EP102_Z9ALY182
file:///dev/disk/by-id/scsi-1ATA_ST1000DM010-2EP102_Z9ALY182-part1
file:///dev/disk/by-id/scsi-1ATA_WDC_WD2003FYPS-27Y2B0_WD-WCAVY5450448
file:///dev/disk/by-id/scsi-1ATA_WDC_WD2003FYPS-27Y2B0_WD-WCAVY5450448-part1
file:///dev/disk/by-id/scsi-1ATA_WDC_WD2003FYPS-27Y2B0_WD-WCAVY5450448-part2
file:///dev/disk/by-id/scsi-1ATA_WDC_WD2003FYPS-27Y2B0_WD-WCAVY5450448-part3
file:///dev/disk/by-id/scsi-1ATA_WDC_WD2003FYPS-27Y2B0_WD-WCAVY5450448-part4
file:///dev/disk/by-id/scsi-35000c500a56ff395
file:///dev/disk/by-id/scsi-35000c500a56ff395-part1
file:///dev/disk/by-id/scsi-35000cca35de72ac8
file:///dev/disk/by-id/scsi-35000cca35de72ac8-part1
file:///dev/disk/by-id/scsi-35000cca35de72ac8-part2
file:///dev/disk/by-id/scsi-35000cca35de72ac8-part3
file:///dev/disk/by-id/scsi-350014ee2afa145a0
file:///dev/disk/by-id/scsi-350014ee2afa145a0-part1
file:///dev/disk/by-id/scsi-350014ee2afa145a0-part2
file:///dev/disk/by-id/scsi-350014ee2afa145a0-part3
file:///dev/disk/by-id/scsi-350014ee2afa145a0-part4
file:///dev/disk/by-id/scsi-S__3
file:///dev/disk/by-id/scsi-S__Generic_Mass-Storage_1.09
file:///dev/disk/by-id/scsi-S__Generic_Mass-Storage_1.09-part1
file:///dev/disk/by-id/scsi-S__Generic_Mass-Storage_1.11
file:///dev/disk/by-id/scsi-S__Generic_Mass-Storage_1.11-part1
file:///dev/disk/by-id/scsi-SATA_Hitachi_HDS72101_JP2940HQ2T50UH
file:///dev/disk/by-id/scsi-SATA_Hitachi_HDS72101_JP2940HQ2T50UH-part1
file:///dev/disk/by-id/scsi-SATA_Hitachi_HDS72101_JP2940HQ2T50UH-part2
file:///dev/disk/by-id/scsi-SATA_Hitachi_HDS72101_JP2940HQ2T50UH-part3
file:///dev/disk/by-id/scsi-SATA_ST1000DM010-2EP1_Z9ALY182
file:///dev/disk/by-id/scsi-SATA_ST1000DM010-2EP1_Z9ALY182-part1
file:///dev/disk/by-id/scsi-SATA_WDC_WD2003FYPS-2_WD-WCAVY5450448
file:///dev/disk/by-id/scsi-SATA_WDC_WD2003FYPS-2_WD-WCAVY5450448-part1
file:///dev/disk/by-id/scsi-SATA_WDC_WD2003FYPS-2_WD-WCAVY5450448-part2
file:///dev/disk/by-id/scsi-SATA_WDC_WD2003FYPS-2_WD-WCAVY5450448-part3
file:///dev/disk/by-id/scsi-SATA_WDC_WD2003FYPS-2_WD-WCAVY5450448-part4
file:///dev/disk/by-id/usb-Generic-_Compact_Flash_058F63626476-0:1
file:///dev/disk/by-id/usb-Generic-_SD_MMC_058F63626476-0:0
file:///dev/disk/by-id/usb-Generic-_SM_xD-Picture_058F63626476-0:2
file:///dev/disk/by-id/wwn-0x5000c500a56ff395
file:///dev/disk/by-id/wwn-0x5000c500a56ff395-part1
file:///dev/disk/by-id/wwn-0x5000cca35de72ac8
file:///dev/disk/by-id/wwn-0x5000cca35de72ac8-part1
file:///dev/disk/by-id/wwn-0x5000cca35de72ac8-part2
file:///dev/disk/by-id/wwn-0x5000cca35de72ac8-part3
file:///dev/disk/by-id/wwn-0x50014ee2afa145a0
file:///dev/disk/by-id/wwn-0x50014ee2afa145a0-part1
file:///dev/disk/by-id/wwn-0x50014ee2afa145a0-part2
file:///dev/disk/by-id/wwn-0x50014ee2afa145a0-part3
file:///dev/disk/by-id/wwn-0x50014ee2afa145a0-part4

For now, its mainly 'Backup & Restoration" who is the worry, as music & video are stored there and cant be played (music is ok using Clementine that said).

Then, Ill see to move these folder to a standard location, which should solve that worry.
As that drive is used as to store backup data and since Ive more than enough space its alright I guess.

Still, What could be reason for the partition being set as root only (“solved” by using Dolphin in SuperUser mode).

@seden:
Good! Now we can begin with the translation from UUID (your “/etc/fstab” is perfectly correct – no need to convert from UUID to “by-dev-id” !!! ):

  1. With the user “root”, execute from a terminal CLI: “lsblk -f”
    You should see something like this (the UUID is translated to a mount-point) – and, this example is for a “not so new” system with UEFI:

 # lsblk -f
NAME   FSTYPE LABEL UUID                                 MOUNTPOINT
sda                                                      
├─sda1 vfat         85FD-C13A                            /boot/efi
├─sda2 swap         c0a219eb-5ea7-470b-9297-3e0d70964554 [SWAP]
├─sda3 btrfs        fa6a0367-a191-447e-8298-35761792b861 /
└─sda4 xfs          31ee5d31-773e-4a8f-8862-876413323c28 /home
sr0                                                      
 # 

  1. Further, with the user “root” you can then, with “blkid -U” and “partx --show”, investigate further as to what is going on – for example:

 # blkid -U 85FD-C13A
/dev/sda1
 # partx --show /dev/sda1
NR START    END SECTORS SIZE NAME    UUID
 1  2048 321535  319488 156M primary 432f0931-2e5c-4274-955b-92239c264ee4
 # 

**
linux-i70q:~ #** lsblk -f
NAME   FSTYPE LABEL                UUID                                 MOUNTPOINT
sda                                                                      
├─sda1 ext3                        b03efe3c-475c-498f-87b0-a08ec84e8aa4 /boot
├─sda2 swap   Swap-Disc1           e2728a66-fad8-4c32-ae0d-9e48bee97e78 [SWAP]
└─sda3 ntfs   Backup & Restoration E422C6F222C6C92E                     /run/media/root/Backup & Restoration
sdb                                                                      
├─sdb1 swap   Swap-Disc2           e9e43288-02ca-426b-b29b-b6bab2f1a7df [SWAP]
├─sdb2 btrfs                       4e3e1359-cb9d-4971-b933-25b50e456c10 /
├─sdb3 xfs    Home                 eab89bf6-286e-4939-ab98-71cd267e9c7c /home
└─sdb4 xfs    Documents            1e843072-3676-4a07-9591-bba2c991a61c  
sdc                                                                      
└─sdc1 btrfs  Jeux                 895c5b18-748a-485d-8d8b-27f4bdf57e06 /run/media/root/Jeux
sdh                                                                      
└─sdh1 vfat                        F0E9-334E                             
sdi                                                                      
└─sdi1                                                                   
sr0    udf    Skyrim               428179480037036A                      
**linux-i70q:~ #**

For “blkid -U” :
b03efe3c-475c-498f-87b0-a08ec84e8aa4 = /dev/sda1
e2728a66-fad8-4c32-ae0d-9e48bee97e78 = /dev/sda2
eab89bf6-286e-4939-ab98-71cd267e9c7c = /dev/sdb3
E422C6F222C6C92E = /dev/sda3
e9e43288-02ca-426b-b29b-b6bab2f1a7df = /dev/sdb1
4e3e1359-cb9d-4971-b933-25b50e456c10 = /dev/sdb2
eab89bf6-286e-4939-ab98-71cd267e9c7c = /dev/sdb3
1e843072-3676-4a07-9591-bba2c991a61c = /dev/sdb4
895c5b18-748a-485d-8d8b-27f4bdf57e06 = /dev/sdc1
F0E9-334E = /dev/sdh1

Last one = dvd, so no interest.

To be noted, the blkid command did not give as much information :

**linux-i70q:~ #** blkid -U b03efe3c-475c-498f-87b0-a08ec84e8aa4
/dev/sda1

As to the third command, how to use it ?

@sedan:
OK, now to unravel what’s going on:

  • There’s an ‘ext3’ boot partition on the ‘sda’ drive with the UUID “b03efe3c-475c-498f-87b0-a08ec84e8aa4”.

This partition seems to be correctly mounted;

UUID=b03efe3c-475c-498f-87b0-a08ec84e8aa4 /boot                ext3       acl,user_xattr        1 2
  • The ‘sdb’ drive contains a Btrfs system partition with the UUID “4e3e1359-cb9d-4971-b933-25b50e456c10” which also seems to be correctly mounted in “/etc/fstab”.
  • The ‘sdb’ drive also contains a user “/home” partition with the UUID “eab89bf6-286e-4939-ab98-71cd267e9c7c” which also seems to be correctly mounted:
UUID=eab89bf6-286e-4939-ab98-71cd267e9c7c /home                xfs        defaults              1 2
  • There are 2 swap partitions defined in “/etc/fstab”.

The swap partition on the drive ‘sda’ with the UUID “e2728a66-fad8-4c32-ae0d-9e48bee97e78” is correctly mounted with priority ‘2’:

UUID=e2728a66-fad8-4c32-ae0d-9e48bee97e78 swap swap pri=2 0 0

The swap partition on the drive ‘sdb’ with the UUID “e9e43288-02ca-426b-b29b-b6bab2f1a7df” is correctly mounted with priority ‘1’:

UUID=e9e43288-02ca-426b-b29b-b6bab2f1a7df swap swap pri=1 0 0

An explanation of multiple swap partitions on Linux is here: https://unix.stackexchange.com/questions/84453/what-is-the-purpose-of-multiple-swap-files.
An openSUSE explanation of swap is available in the Reference Guide: https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/index.html section 5 “Advanced Disk Setup”: https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.advdisk.html subsection “5.1.6.1 Using swap”. There’s a useful hint for swap usage there:

 > cat /proc/swaps
Filename                                Type            Size    Used    Priority
/dev/sda2                               partition       2098172 0       -1
 >  


  • The other partitions in the system are not (yet) mentioned in “/etc/fstab”.
  • There is a Microsoft NTFS partition present on the system with the UUID “E422C6F222C6C92E” which seems to be dynamically mounted via ‘Fuse’.

Possibly, the first thing to do is, get the XFS “Documents” permanently mounted – in “/etc/fstab” add the line:

UUID=1e843072-3676-4a07-9591-bba2c991a61c /documents                xfs        defaults              1 2

The Btrfs partition on the ‘sdc’ drive which is currently mounted via ‘Fuse’ could be permanently mounted with the following line added to “/etc/fstab”:

UUID=895c5b18-748a-485d-8d8b-27f4bdf57e06 /jeux btrfs defaults 0 0

The ‘sdh’ drive seems to be a USB device, with a FAT partition which is VFAT capable and has the UUID “F0E9-334E”.

  • My suggestion is, to mount this device on a per-user basis by means of ‘Fuse’.

The ‘sr0’ drive is a CD/DVD device with a UDF partition which has the UUID “428179480037036A”.

  • My suggestion is, to also mount this device on a per-user basis by means of ‘Fuse’.

Did as instructed, resuts are mixed.

Wine cannot open the files anymore (.sh on jeux).
Otherwise, quite some folders are locked, guess that one should be easy to change (but how ?).

Otherwise, there is still something strange, from a file from the download folder toward the jeux drive, its not possible to copy/move, must still be done using dolphin with super user rights.

This said, what should I have do as to have it correct (not locked behing root login) ?

Please check the all of the directory and file ownerships on the drive you’ve newly added to ‘/etc/fstab’.

  • It seems that, the directories and files on that drive are setup with User and Group ownerships which do not match to the values in the system’s ‘/etc/passwd’ and ‘/etc/group’ files.
UUID=e2728a66-fad8-4c32-ae0d-9e48bee97e78 swap swap pri=2 0 0
UUID=e9e43288-02ca-426b-b29b-b6bab2f1a7df swap swap pri=1 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 / btrfs defaults 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /opt btrfs subvol=@/opt 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /srv btrfs subvol=@/srv 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /tmp btrfs subvol=@/tmp 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /usr/local btrfs subvol=@/usr/local 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/cache btrfs subvol=@/var/cache 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/crash btrfs subvol=@/var/crash 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/lib/libvirt/images btrfs subvol=@/var/lib/libvirt/images 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/lib/machines btrfs subvol=@/var/lib/machines 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/lib/mailman btrfs subvol=@/var/lib/mailman 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/lib/mariadb btrfs subvol=@/var/lib/mariadb 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/lib/mysql btrfs subvol=@/var/lib/mysql 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/lib/named btrfs subvol=@/var/lib/named 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/lib/pgsql btrfs subvol=@/var/lib/pgsql 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/log btrfs subvol=@/var/log 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/opt btrfs subvol=@/var/opt 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/spool btrfs subvol=@/var/spool 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /var/tmp btrfs subvol=@/var/tmp 0 0
UUID=4e3e1359-cb9d-4971-b933-25b50e456c10 /.snapshots btrfs subvol=@/.snapshots 0 0
UUID=b03efe3c-475c-498f-87b0-a08ec84e8aa4 /boot                ext3       acl,user_xattr        1 2
UUID=eab89bf6-286e-4939-ab98-71cd267e9c7c /home                xfs        defaults              1 2
UUID=1e843072-3676-4a07-9591-bba2c991a61c /documents                xfs        defaults              1 2
UUID=895c5b18-748a-485d-8d8b-27f4bdf57e06 /jeux                btrfs        defaults 0 0
UUID=E422C6F222C6C92E /run/media/eden.sb/Backup & Restoration/ ntfs defaults 0 0

  1. If so, how are handled these two files, passwd & group ? Aka reading then use (as to have all the file on these drives unlocked).

We’re using Linux and, with Linux, UNIX®, and anything else which looks or smells like UNIX® such as macOS or Android, there’s no such thing as a “locked disk”.
An openSUSE reference for managing disk partitions is here: <https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.advdisk.html>.

In your ‘fstab’, the fourth field of the mount point ‘/jeux’ contains “defaults” which means: “rw, suid, dev, exec, auto, nouser, and async” (‘man fstab’ and ‘man mount’).

The command ‘mount’ should be indicating for the mount point ‘/jeux’ the parameter value “rw”.

With the user “root” the command “chown” manages the User and Group ownerships of directories and files.
GUI File Managers such as the KDE Dolphin in super-user mode can alternatively be used to correct the directory and file ownership issues of the partition ‘/jeux’.

The system files ‘/etc/passwd’ and ‘/etc/group’ document, for the system, the User and Group ID (identification) numeric values.
The following Wikipedia articles explain User and Group ID values: <https://en.wikipedia.org/wiki/User_identifier>; <https://en.wikipedia.org/wiki/Group_identifier>.

Done as seen then on boot today, emergency mode (Failed to load kernel Modules) with this (after root password >journalctl -xb)
run-media-eden.sb-backup.mount loaded failed failed
audit.service failed failed
systemd- modules- load.service failed failed

I can’t see how, correcting the directory and file ownerships within the user partition of a non-system disk can suddenly cause an extreme system failure.

Have you somehow moved the boot partition and BIOS/EFI settings away from the original system disk?

Or, have you changed something else within the system partitions of the system disk?

No, the only change where did to the fstab file. I’ve opened the group and user but did not edit them at the time of the system reboot.

Given I’ve only access to command lines, is there a way to see what happened? (a log?).

Then, the issue is the Btrfs system partition and, not enough housekeeping:

  • From the systemd Emergency Mode, login with the password of the user ‘root’ and execute all the Btrfs housekeeping tasks in ‘/etc/cron.weekly/’ and ‘/etc/cron.monthly/’. When the Btrfs housekeeping has completed, reboot.

I forgot to mention that, the Btrfs housekeeping may take several hours (read, possibly only a few or maybe even 24 hours or more) to complete.

Add “nofail” to the mount options in fstab to prevent the boot failing if it cannot be mounted for some reason.

The “Failed to load kernel Modules” error is likely unrelated and shouldn’t cause entering emergency mode.

Btw, I suppose the problem are the spaces in your mount point:

UUID=E422C6F222C6C92E /run/media/eden.sb/Backup & Restoration/ ntfs defaults 0 0

You need to write \040 instead.
This should work:

UUID=E422C6F222C6C92E /run/media/eden.sb/Backup\040&\040Restoration/ ntfs defaults 0 0

From “man fstab”:

       **The second field** (fs_file).
              This field describes the mount point (target) for the filesys-
              tem.   For  swap partitions, this field should be specified as
              `none'. If the name of the mount point contains  spaces  these
              can be escaped as `\040'.