I have a separate data partition on the same SSD as my root partition.
After booting, the data partition is not automatically mounted. You have to click on the partition in dolphin and enter your root/user password (which is the same in my case) to authorise it.
So I added this to the fstab (with the correct UUID of the data partition, of course)
After modifying the fstab and rebooting, the Manjaro OS boot screen is displayed, but the OS does not actually boot all the way through.
There may be a simple solution to have the root password added automatically on boot, perhaps similar to what is done with the root partition.
I have searched some of the topics in this forum but have not found a clear answer to my problem.
Put this to the autostart and it will mount it at login. That is exactly what Dolphin does when you click to mount.
1./run is a tmpfs and fstab needs an existing mountpoint, otherwise it will fail. Add X-mount.mkdir and it should create it when mounting.
2. Don’t use ""
Does this command mean that it will automatically be put to autostart and it mounts at login than, or do I need to do something else?
Can I use this command exactly as it is, or do I need to replace “UUID” in this command with the UUID of the data partition?
What exactly does “unique” mean and why is it wrong?
I created this partition using the KDE partition manager and simply entered the partition name “data”. The partition manager automatically created this mountpoint
With KDE you can add removable devices by mount on login. Yes, I am aware of this feature, but it did not work with /run/media/user/data, but by setting a new mount point like /disks/data it works now.
I would still like to understand how to use the command:
udisksctl mount -b /dev/disk/by-uuid/UUID
I have attached a screenshot of the startup screen. Do I need to add a login script (“Anmeldungs-Skript hinzufügen”)? Do I need to create a bootdevice.sh file or what kind of text file do I need to add to make the command work? And is it exactly this command or do I have to replace the UUID with the real UUID of the disk partition?
I have attached a screenshot of autostart mask. Do I have to add a login script '? Do I have to create a boot.sh file or what kind of text file has to be added for making the command work? And is it exactly this command or has the UUID replaced with the real UUID of disk-partition?
When it is finally clear what the solution is, I will write a summary for other searchers. Maybe as a tutorial with reference to your two answers.
For several years I have been struggling with this simple problem of booting properly, because I never got a really clear answer. I could find the solution by combining your answer and Nachlese’s - at least for the non encrypted, no hibernation version.
MeanwhiIe I have tried out some installations for the data partition not using
/run/media/user/data
but
/disks/data
by creating an on own mouting point with KDE partition manager. It works fine.
But if you want to mount this way an encrypted partition it does not work at all. Even the entry in /etc/fstab is correctly created by KDE partition manager.
It is probably because it asks at boot for the password but it is not provided. Thus it stops booting.
I believe a password file has to be connected in /etc/fstab
UUID=<this is a placeholder> /disks/data btrfs defaults,credentials=/home/user/.datacredentials 0 0
In the self created file /home/user/.datacredentials probably simple this content has to added
password=yourpasswordforencrypteddevice
How do you think?
Even this works. I am also not happy because the password is just not protected written in a file on the PC in home directory.
first:
I have absolutely zero experience with and only very little understanding of how BTRFS works.
I’ll simply not use it until that changes - it is too different from what I know.
As far as encrypted partitions are involved:
that is where /etc/crypttab comes in
