You are not logged in.
Pages: 1
Note: I did not try 'BIOS-type' install .
Today I removed Win10 from nvme, because of bug:
... in the Windows 10 May 2020 Update (Version 2004), the Windows Defragmenter has a bug that defragments SSDs too frequently, trims non-SSD drives, and forgets when it last optimized a drive each time it restarts.
So I decided to remove such unresponsible hardware-destroying OS, and put Devuan on nvme and get Steam there.
Installation with (not-LVM) Encrypted root partition with unencrypted /boot, EFI system partition, installed from desktop-live - does boot.
However, there are some errors You see immediately on booting, that, btw, do not prevent booting:
error: no such device: <UUID of decrypted root appears here>
error: file '/usr/share/desktop-base/grub-themes/cinnabar-grub/theme.txt' not found.
error: file '/usr/share/desktop-base/grub-themes/cinnabar-grub/unifont-regular-16.pf2 not found.
I assume first error is because GRUB can't see UUID of decrypted root_fs before decrypting.
This is correctable by editing grub.cfg lines 63, 65, 81, 83 and replacing that UUID with uuid of /boot partition,
But, it will revert on any grub-updating. I do not know how to make this change permanent on grub update.
Any help on this will be appreciated.
Second and third error is - grub themes are on root_fs which is in time of showing this message, stil encrypted,
so I copy/pasted themes on /boot/grub and corrected paths in 05_debian_theme and /etc/default grub ... and ...
... and after that noticed that is already discussed here
I can confirm after replacing cryptdisks-functions with fsmithred's file, system shutdown delay is one second!
Thanks again!
P.S.
Long Live Refracta Installer!
We did not fork cryptsetup
OK, thank You, this explains a lot.
Correct me if I am wrong, but doesn't fsmithred's patch applys only to the LVM FDE? I mean, will that work on non-LVM FDE system?
I will try with the debian installer (netinstall Iso) and report here after that.
Edit: by "non-LVME FDE" I mean simple luks encrypted system (root) not using LVME, having EFI and /boot unencrypted.
... if you don't need LVM don't use it...
I always search for (ultra rare) Distro that have "FDE without LVM" enabled throuhg installer.
So, today I was delighted with Refracta installer from latest Live.iso! One of the best installer out there.
Ofcourse I picked FDE, without LVM, separate /boot partition - to have LUKS v.2, separate swap partition, and everything else on / ;
installation (in VBox) was quick.
Again, I thought this time will be different ..
Then, after rebooting from installed system, there was a suspicious 40 sec
delay ... but no any visible messages. Next time I pressed shutdown instead of reboot, and, as I suspected :
Stopping remaining crypt disks...root_fs (busy)...root_fs (busy).....root_fs (busy).....root_fs (busy).....root_fs (busy).....root_fs (busy)......
Maybe this is impropriety comment, but no pun intended:
Recently, when Debian 10 was released, I tested it with (simple, not-LVM) Full Disk Encription, and it shutdown immediately; so, after all this years, they finally fixed this bug.
Maybe somebody who know how to do it, can see there how it is done.
I am just at user-level, so I can't do it myself.
About patch:
(I tested Beowulf because I thought "this time will be different" )
In Beowulf file name for patching is "cryptdisks-functions"
I am not using LVM.
Everything else I already noticed https://dev1galaxy.org/viewtopic.php?id=674 #12 :
"for i in 1; do" --- this does shorten shutdown/reboot time. (Beowulf included)
But, the question is: Does encrypted filesystem/partition/container in the end get proper unmount?
Because all those unmounting messages are ending with "failed".
am concerned that over time, some files may become corrupted without noticing.
Edit: This is beginning to be thread hijacking, so I'll not continue on here.
.. and there is no repeating message (?):
Stopping remaining crypt disks...sdX_crypt(busy)
I have it on Beowulf.
I see it on MX Linux 18. (There it appears for very short moment, but it DOES appear)
Probably this is an issue on ALL debian/devuan distros.
Also,
If Your installation is on UEFI based machine, and I see it is, You can put GRUB into retirement and use EFISTUB.
for i in 1; do
This really do the trick;
But, the question is: Does encrypted filesystem/partition/container in the end get proper unmount?
Because all those unmounting messages are ending with "failed".
My guess is "yes", because on reboot there are no messages about recovering journal or similar.
However, this is only a guessing.
I am concerned that over time, some files may become corrupted without noticing.
More light into this issue will be appreciated.
I wish Devuan installer will have option to use-and-NOT-FORMAT existing swap partitions.
Downloaded "devuan_ascii_2.0.0_amd64_desktop-live.iso" file from https://files.devuan.org/devuan_ascii/desktop-live/
has wrong sha256sum (bc7820d25f4af393cc375645922a1307dd6ff87356cbdd270b8e001c3378d072)
Then I downloaded same file from https://devuan.unetresgrossebite.com/de … ktop-live/ and it is OK
(76584ce7183993306af8b00edc8ffce3a1dc69b10f0a97e0a6302d49b0a63858)
... spotted right there:
https://files.devuan.org/devuan_ascii/
?
can't mount logical disk using PCManFM in ASCII RC, LXDE or OpenBox:
I had similar problem with mounting disks/partitions under ASCII;
Solved by creating file:
/etc/polkit-1/localauthority/50-local.d/whatewernameYouPick.pkla
[Storage Permissions]
Identity=unix-user:your_user_name
Action=org.freedesktop.udisks2.filesystem-mount;org.freedesktop.udisks2.filesystem-mount-system;org.freedesktop.udisks2.filesystem-mount-other-seat;org.freedesktop.udisks2.filesystem-unmount-others;org.freedesktop.udisks2.encrypted-unlock;org.freedesktop.udisks2.encrypted-unlock-system;org.freedesktop.udisks2.encrypted-unlock-other-seat;
ResultAny=yes
ResultInactive=yes
ResultActive=yes
Pages: 1