The "plain" option did the trick.
Another possibility is that it was an incomplete entry in crypttab (while the
other HDD wasn't configured... ), but I don't feel like checking at this
point.
So it was complicated, as usual, but it's solved at last.
Maybe I can try this:
https://sgros.blogspot.nl/2013/12/systemd-waiting-for-external-crypted.html
Here's the journalctl -xb log:
https://pastebin.com/bBJt2zEj
Some lines are supposed to be in black (don't seem like errors), some are in
red.
I remember one about the CPU thermal probe not working or something.
But what interest us is the repeating lines in the end, about cryptsetup, or
* I still can't access my drives without decrypting them and mounting them.
* one of the drives isn't even encrypted yet, and I can't mount it in
nautilus. All i did was to format it with one ext4 partition.
* I can see both drives though because I labeled them from /media in Gparted.
But
Thank you, now I'm in. Well, I couldn't mount /usr ("write-protected", then
"does not exist").
But I can access fstab anyway.
I don't know what to change though.
I 'll comment the new lines out for now, and see how it goes.
From the Live CD, install the package lvm2.
I don't know how to chroot.
Following this
guide(https://stephentanner.com/restoring-grub-for-an-encrypted-lvm.html),
vgscan is nowhere to be found on the LiveCD.
Also, I'm not even sure I'm unlocking the proper path.
After encrypting the HDD and enabling the keyfile,
I can't access the console anymore.
After booting and unlocking the main drive (SSD), it tries to unlock the
newly encrypted HDD with the keyfile, and...
I'm into emergency mode, and it says the root account is locked.
Of course it's locked,
After yet another install, I configured the drives to be mounted on
/media/folder1 and /media/folder2.
I was rewarded with systemd's cyclone eye. Great.
So Since I'm getting tired of all these bugs (not strictly Trisquel related),
I'll just encrypt them after the install with this
Nautilus sees and unlocks an encrypted external HDD amazingly well.
I'll try encryption again on the internal HDD and see how it goes. If it
works, I most likely did something wrong during the install.
Here's a possible reason why Nautilus doesn't see the internal HDD: The path
I told it to
OK, after the failed attempts above to unlock the drive as non-root:
* burn that computer
* uh, maybe try something else first. Like reformatting the drive with
Gparted.
I didn't succeed in opening gnome-disks as root.
G_IS_DBUS_CONNECTION failed
G_IS_DBUS_PROXY failed
Just a quick recap about this hacked install:
* encrypted internal HDD not recognized as root (same with different file
managers).
* I can input the passphrase as the normal user, but opening is
:/
It's complicated, it's an internal HDD, and the working machine is a laptop.
It might work with gnome-disks as sudo or gksudo, I didn't try yet.
No worries, the HDD is encrypted but empty for now. Thanks though, this might
work just fine.
Did you try with the other machine, the one that did work to open the disk
and change file permissions??
The hardest part is the installation.
But if I could do it I am sure you can.
I have encrypted drive with F2FS file system. Most things work perfectly.
You can watch a few videos on how to install arch and if you want something
special you can tell me maybe I can help you.
I've had less
Even PCmanFM as root doesn't display my drives (displayed as non-root).
It's kind of reassuring for Nautilus with gksudo (besides the odd looks).
Less regarding pkexec, but oh well.
It's less reassuring regarding unlocking my drives.
Well, I can reformat them with Gparted if I have to.
I'll try
I'm tempted. What about constant fixes and all that?
Is it really troublesome, or only something to check before updating?
This is the reason why I use parabola now.
I read somewhere that "stable" is usually not, as many bugs are fixed
constantly, and the quality of the GNU/Linux software is better everyday.
That convinced me and I am happy on parabola now :)
I would suggest you to try it. After all you use
I find in fstab the 3 logical volumes /root /home and /swap, and /boot.
The 2 other HDD which I can see in Nautilus (but can't in sudo nautilus) are
not there.
Anyway, I'm off the computer for a few days, but please keep the ideas
coming.
Even better: isn't there a file manager that just
What's the output of
cat /etc/fstab
https://help.ubuntu.com/community/Fstab
https://wiki.archlinux.org/index.php/Fstab
Right, I forgot.
Unfortunately, no luck with gksudo anyway.
As for pkexec,
I want to try again:
* On another machine with gnome shell, the command "pkexec env
DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY" is the only one that worked.
* it's odd as no files related to nautilus in the
Don't forget to reboot, sometimes it helps. Or power PC off and turning it on
OK, gksudo gave me the exact same result as sudo:
* odd display
* no access to the locked drive
I still have pkexec to fix hopefully (since it's the recommended way), and
through the command line (most likely like this:
But isn't gksudo deprecated? But I can install it and try, no problem.
I've never opened this one yet, but I do open external encrypted HDD on my
other PC but with gnome-disks, and with sudo.
Oh right, I forgot this option ^^"
Let me figure out how and I'll try.
Try gksudo nautilus it will look different because root has its own themes.
Don't worry. With Nautilus decrypt it and check permission.
You said you opened it as root before. Once I did that and after that my
normal user didn't have the permissions to use the disk :/
It was weird.
What happens when you decrypt and open with a terminal?
I donwloaded a policykit agent, and modified the path in .xinitrc to launch
it on startup and rebooted.
Now I have (authenticating as the normal user and inputting the sudo
passphrase when asked for):
polkit-agent-helper-1: error response to Policykit daemon: GDBus-Error:
pkexec nautilus (after installing nautilus-admin and restarting) gives me:
Error executing command as another user: not authorized.
additional info: sudo nautilus looks weird (not only the GTK), the disk isn't
displayed.
Thanks a lot albertoefg. I'll try from the CLI since sudo Nautilus doesn't
look right (even if I installed nautilus-admin).
Open it with robot.
Change file and directory permissions to proper user or group
This internal HDD is displayed in Nautilus,
and I am prompted to input the passphrase.
But it doesn't work.
It was encrypted during the install.
On another machine, I had to open gnome-disks as sudo,
then I could open the HDD.
Isn't it better (and possible) to just unlock from the normal user?
36 matches
Mail list logo
