Brief history:
- Fresh install of 13.2 about 6 weeks ago - clean slate except kept existing windows7 install.
- Used Leap on USB to upgrade above
- Leap install tooks 6+ hours - lots www timeouts/retrys (China “internet”)
- Leap install DID request passphrase for encrypted home during install
…on rebooot enter passphrase, then get error “Logging in s888-lounge… Cannot enter home directory. Using /.”
The obvious things I can see:-
In terminal can see home IS already mounted and can access files OK.
Network is not loaded/active… there are log errors about that - seems like flow on effect of main issue.
cat /etc/crypttab
cr_home /dev/disk/by-id/ata-HGST_…-part7 none none
Erorrs in logs that seem relevant are:
systemd-fsck[878]: /dev/mapper/cr_home: Superblock last mount time is in the future
systemd-fsck[878]: /dev/mapper/cr_home: Superblock last write time is in the future
…
kdm[1363]: :0 '[1363] Cannot chdir to s888-lounge’s home /home/s888-lounge: No such file or directory"
So I have looked around to understand how the boot/encryption/mount process work and found a little bit of info (which helped get above info).
Also looked really hard at kernel log and journalctl.
This system is not critical - more of a secondary dev and test system - in fact was once again testing out BTRFS and encryption.
Really just trying to build experience recovering from BTRFS/encryption issues, as I have successfully done for both BTRFS and encryption in the past.
Also would like to avoid several days effort re-installing a LOT of dev apps Xilinx FPGA, gdb, openOCD, and a LOT more.
But I am at a loss as to where to look for hints, or what above info suggests I should do.
Any suggestions where to look/act?
I’ve also been testing out worst case scenarios on a separate disk as it’s the best way to understand BTRFS.
In response to the “Superblock last mount time is in the future” message.
You may have a time discrepancy between your local time setting in your hardware and the timezone setting that you’ve set in Yast. For example UTC+2, UTC+3 etc…
The problem is with the first time fsck running under initramfs with UTC. When leaving initramfs, the second fsck is running at an earlier time (i.e UTC+2) fooling fsck
into thinking that the root filesystem has had its superblock is written in the future.
Ensure that /etc/adjtime is included in initrd. You can check this by typing: lsinitrd
The fix:
Type: " su - " (without the quotes)
then
dracut --include /etc/adjtime /etc/adjtime --force
If this doesn’t resolve the problem, I would submit a bug report on e2fsprogs with Bugzilla.
Good Luck!
It is also possible that the hardware time is being changed in Windows. When dual booting all the OS’s must agree on the time zone that the hardware clock represents.
thanks to both responders above.
Yes I am aware of the dual o/s issue with windows … have been dual booting several systems for many years. This system has been dual booting for 2 months without issue.
Did try the dracut suggestion, but that has not fixed the major issue “Cannot enter home directory. Using /.”](https://forums.opensuse.org/showthread.php/511550-Leap-42-1-upgrade-of-13-2-(encrypted-BTRFS-home)-quot-Cannot-enter-home-directory-Using-quot)
Please have a look at this link: openSUSE Documentation
During the boot process fstab is also checked. Please post /etc/fstab.
@spanner888
I would highly recommend you subscribe to the openSUSE Factory ML.
We have a lot of devs and openSUSE members that can help you out.
**
FYI**
Do not encrypt the root partition using BTRFS unless the disk has a GPT disk label.
Grub2 will not be able to boot using, not MSDOS.