Thanks Fabien85 and gm10 for your help. I have to say that my initial problem is solved, and then I had a second problem that could have been adressed in another thread. I think now I am done with both problem, thanks to your advice and help and some experiments. I agree a "short thread" and clear title are important. I can stop here. Here is the present situation :
1. I had this "login loop" preventing me from logging in my own session. It happened after a crash for low power reason. I was not able to figure out what was the problem. I commented my fstab file with no effect. The Fabien's idea to make chroot from a live USB let me update my system "from the inner side". After that I could boot again. I don't know the file or folder involved in this first problem.
2. But my initial fstab file was still not supported. This was my second problem. The system booted only with a "one line" fstab. Then I experiment to build again my fstab file by adding one by one the initial lines. It was OK for swap, /efi/boot, even /Documents, but crashed again with my "bind mounts" that are made to "automount" all my Documents folders (movies, pictures, downloads, documents, Music). I changed some options until it worked again. So now, all seems to be OK. The login is OK, even with my full fstab file.
For information :
- I don't know if the bind mount is better than symlink. But it is automatically mounted during the boot and works rather well (except during these last days !). Bind mount is made to access part of a mount on another mount point. It's what I need, but symlink can be as efficient as it is. Do you think symlink is better on some aspects ? I don't know the key differences if any.
- Here is my fstab file. What made it to work again was to add "0 0" at the end of the lines for my bind mounts. I don't know why before this crash my fstab worked without them, and they are needed now. But it is normal to have these "0 0" at the end of the lines in the fstab file. I also changed "auto" in "none" as gm10 suggested but I believe this didn't change anything.
Code: Select all
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=39591c06-37af-4ad1-b8a1-7b0fe10aa0ae / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=70D6-1701 /boot/efi vfat umask=0077 0 1
# swap was on /dev/sda4 during installation
UUID=8381e749-9e32-49ce-8bad-2ee3c17d872b none swap sw 0 0
#Shared documents partition
LABEL=Documents /mnt/Documents hfsplus nofail,rw,user,noauto,x-systemd.automount,relatime,nls=utf8 0 0
#last fstab line, 2018/08
#LABEL="Documents" /mnt/Documents hfsplus force,rw,user,uid=501,umask=022 0 0
#mtab line for inspiration
#LABEL=Documents /media/Joe/Documents hfsplus rw,relatime,umask=22,uid=0,gid=0,nls=utf8 0 0
#Bind mounts for shared documents
/mnt/Documents/Users/Joe/Documents /home/Joe/Documents none bind,x-systemd.requires=/mnt/Documents 0 0
/mnt/Documents/Users/Joe/Music /home/Joe/Musique none bind,x-systemd.requires=/mnt/Documents 0 0
/mnt/Documents/Users/Joe/Pictures /home/Joe/Images none bind,x-systemd.requires=/mnt/Documents 0 0
/mnt/Documents/Users/Joe/Movies /home/Joe/Vidéos none bind,x-systemd.requires=/mnt/Documents 0 0
/mnt/Documents/Users/Joe/Downloads /home/Joe/Téléchargements none bind,x-systemd.requires=/mnt/Documents 0 0
#Partition systeme MacOS
UUID=f07169e0-e9ab-3d4c-ba5e-4ad629623c0f /mnt/SystemeMacOS auto nosuid,nodev,nofail,noauto 0 0
- As told by gm10, x-systemd.requires let the systemd process to mount the partition (or piece of a partition when it is a bind mount like in my case) only after and if another device is mounted, preventing some errors. It can be used to mount online partition too, only if the network is available for instance.
- I changed since the install my uid in 501. To log in, one's has to modify a few files about "MIN_UID" parameters, which are default to 1001 and one's needs to set it at 501 in order one's user does appear on the login screen. This allows to use the same hfsplus partition in MacOS and Linux Mint without having to change anything on permissions, since the owner is the same (501 in both OS). You have to make the same changes for the group and gid.