mount problem LUKS after upgrade

MarcS · 3. Dezember 2021

I get this error message after an upgrade, reboot and trying to unlock one of my LUKS drives:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; mount -v --source '/dev/disk/by-uuid/b6c87626-ea4b-4661-abbd-d3b5a2137ea9' 2>&1' with exit code '1': mount: /dev/disk/by-uuid/b6c87626-ea4b-4661-abbd-d3b5a2137ea9: can't find mount source /dev/disk/by-uuid/b6c87626-ea4b-4661-abbd-d3b5a2137ea9 in /etc/fstab.

This is my folder /dev/disk/by-uuid

Code

drwxr-xr-x 2 root root 320 Dec  3 12:27 .
drwxr-xr-x 7 root root 140 Dec  3 12:21 ..
lrwxrwxrwx 1 root root   9 Dec  3 12:21 21d2fc7f-9624-412c-85c8-9ea04fbe7523 -> ../../sdg
lrwxrwxrwx 1 root root   9 Dec  3 12:27 25e4e11c-4d8d-44d4-8d21-2cc826382777 -> ../../sdd
lrwxrwxrwx 1 root root  15 Dec  3 12:21 45e99191-771b-4e12-a526-0779148892cb -> ../../mmcblk0p2
lrwxrwxrwx 1 root root  15 Dec  3 12:21 4BBD-D3E7 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root   9 Dec  3 12:21 5b435f64-7776-4aea-8ab7-b67fa5dda010 -> ../../sde
lrwxrwxrwx 1 root root   9 Dec  3 12:27 5e8dfae8-c632-4b7d-b5d6-ba061b4e2b8f -> ../../sdc
lrwxrwxrwx 1 root root   9 Dec  3 12:27 9a41e37c-2ee1-431e-9109-17a4c51598dc -> ../../sdf
lrwxrwxrwx 1 root root  10 Dec  3 12:27 9a47ccda-02e9-49ab-b561-ab7c189dde1b -> ../../dm-1
lrwxrwxrwx 1 root root  10 Dec  3 12:27 b6c87626-ea4b-4661-abbd-d3b5a2137ea9 -> ../../dm-3
lrwxrwxrwx 1 root root   9 Dec  3 12:27 c231a12a-7cd6-422c-bb3e-710c791543b8 -> ../../sdb
lrwxrwxrwx 1 root root  10 Dec  3 12:27 c63661cf-07ae-4c90-99cd-54cf2808f226 -> ../../dm-0
lrwxrwxrwx 1 root root   9 Dec  3 12:21 de9b0bd9-740f-4451-877a-0f8df847d0d4 -> ../../sda
lrwxrwxrwx 1 root root  10 Dec  3 12:21 e3f54227-f3de-4f4f-bba6-ba24994fd1b1 -> ../../sdh1
lrwxrwxrwx 1 root root  10 Dec  3 12:27 f1bf31f3-3b27-4fe7-bb69-a023bb75fbf7 -> ../../dm-2

Alles anzeigen

MarcS · 3. Dezember 2021

I did some more digging and found that the disk UUIDs for 2 HDs are somehow mixed up.

In "/dev/disk/by-uuid" is defined

sdg --> ....523

sdf --> .....8ds

In "LUKS GUI screen" is defined

sdg --> ....8ds

sdf --> .....523

and I can unlock all disk, just mounting of sdg doesn't work and throws the error message above.

Soma · 3. Dezember 2021

Is this still related with this thread???

On the Pi???

upgrade errors - General - openmediavault

MarcS · 3. Dezember 2021

Yes its on the Pi. I dont know if it is related but after reboot the mounting doesnt work anymore. Kernel seems stable though.

Soma · 3. Dezember 2021

Zitat von MarcS

Yes its on the Pi. I dont know if it is related but after reboot the mounting doesnt work anymore. Kernel seems stable though.

So you DO have a special situation running on the Pi even after I asked you there if you did anything different!!!!

Sorry but it's difficult to provide proper solutions if the problem is not fully known.

And I did asked you on the other thread.

If you have crypto drives, that is why you have to redo the initramfs every time the kernel is updated.

Otherwise the modules aren't loaded before the mounting of the drives.

If it's done correctly (which I trust it is due to the initramfs errors on the other thread), it will all happen automatically.

But if you don't have space on the /boot drive (it's only 256MiB ) it will fail.

Did you make any of what I described here:

RE: upgrade errors

MarcS · 3. Dezember 2021

I wasn't aware that by "special situation" you meant LUKS drives.

Anyhow, I did not delete any of the old kernels but rebotted and then noticed the LUKS drive issue.

So in which order shall I proceed?

Soma · 3. Dezember 2021

Do you have any updates pending via OMV Gui to see it's output?

To see if you still having the same errors with the initramfs on the update?

Otherwise, just follow the #10 on the other thread (link above)

MarcS · 3. Dezember 2021

Yes. I suddenly have around 30 updates in the GUI list.

I am now on Kernel 5.10.63 v7l+ or ...v8 (depending on booting the Pi as 64 Bit or 32-bit) and OMV 5.6.21-1

Shall I run all those updates first?

Soma · 3. Dezember 2021

First, you really need to have a good working backup clone of your SD Card, before attempting anything.

I don't want you to blame me if your system goes kaput,

Zitat von MarcS

depending on booting the Pi as 64 Bit or 32-bit

I need you to explain me this???

Are you jumping from architecture on boot? (adding the arm64=1 to the config.txt)?

MarcS · 3. Dezember 2021

Yes. I usually run on 32-Bit but 12 months ago installed 64-Bit Kernel so it runs in both modes.

THe LUKS disks worked fine with either. Just after the recent Kernel update and reboot the LUKS/disk order is mixed up.

Soma · 3. Dezember 2021

Zitat von MarcS

Yes. I usually run on 32-Bit but 12 months ago installed 64-Bit Kernel so it runs in both modes

You either run it on arm64 or armhf, stick to one or the other.

uname -a will show what architecture is the kernel. That is the one to follow.

Just make a clone of the OS and then try the update.

Post the output here.

MarcS · 3. Dezember 2021

running on 32-Bit at the moment

I ran upgrades and still errors. PLease see attached files.

history.log.txt

term.log.txt

Soma · 3. Dezember 2021

Zitat von MarcS

running on 32-Bit at the moment

Why?

From the other thread you posted:

Zitat

I now rebooted and the current kernel shows as
Linux pi3 5.10.63-v8+ #1488 SMP PREEMPT Thu Nov 18 16:16:16 GMT 2021 aarch64 GNU/Linux

How do you jump from 32 to 64bit ?????

And you keep having the same errors (your /boot is FULL and the update can't regenerate the initramfs)

Code

ln: failed to create hard link '/boot/initrd.img-5.10.0-0.bpo.9-armmp.dpkg-bak' => '/boot/initrd.img-5.10.0-0.bpo.9-armmp': Operation not permitted
update-initramfs: Generating /boot/initrd.img-5.10.0-0.bpo.9-armmp
cryptsetup: ERROR: Couldn't resolve device /dev/root
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries 
    nor crypto modules. If that's on purpose, you may want to uninstall the 
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs 
    integration and avoid this warning.
W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
W: mdadm: failed to auto-generate temporary mdadm.conf file.
pigz: abort: write error on <stdout> (No space left on device)
E: mkinitramfs failure cpio 141 pigz 28
update-initramfs: failed for /boot/initrd.img-5.10.0-0.bpo.9-armmp with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
Log ended: 2021-12-03  15:00:42

Alles anzeigen

MarcS · 3. Dezember 2021

I switch 32-Bit to 64-Bit by changing 1 line in the config.txt.

I normally run on 32-Bit but because of all these errors I tried 64-Bit to see if it helps.

So I should remove old Kernels from the Boot folder?

MarcS · 3. Dezember 2021

right now I am on

Linux pi3 5.10.63-v7l+ #1488 SMP Thu Nov 18 16:15:28 GMT 2021 armv7l GNU/Linux

which is 32-Bit as I understand

MarcS · 3. Dezember 2021

I deleted the files.

Now there is 154M available on /boot

OMV GUI doesnt how any updates though.

Shall I run manually?

MarcS · 3. Dezember 2021

When I run apt update, it says all packages up to date

When I run omv-update, I get this error message

Code

Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up initramfs-tools (0.133+deb10u1) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.133+deb10u1) ...
ln: failed to create hard link '/boot/initrd.img-5.10.0-0.bpo.9-armmp.dpkg-bak' => '/boot/initrd.img-5.10.0-0.bpo.9-armmp': Operation not permitted
update-initramfs: Generating /boot/initrd.img-5.10.0-0.bpo.9-armmp
cryptsetup: ERROR: Couldn't resolve device /dev/root
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
W: mdadm: failed to auto-generate temporary mdadm.conf file.

Alles anzeigen

Soma · 3. Dezember 2021

Zitat von MarcS

I switch 32-Bit to 64-Bit by changing 1 line in the config.txt.

I know how to change it, what I don't understand is WHY you keep on doing it.

Reverting back and forth.

This is forcing your OS to have the repositories for both architectures, not only that and also doubling the space for the debs for both.

With all the conflicts that come with it, this isn't worth it, sorry to tell you.

Now, everytime you boot on a different kernel, you need a specific initramfs for it taking double the size needed on /boot (armhf and arm64)

All I can tell you is to free some of the old files (like I told you before) to at least, the update regenerate a new initramfs without problems.

The crypto errors will (might) be solved. If not, I can't help you since I don't use crypto (LUKS) drives.

But the errors for the lack of space on /boot will be solved.

Soma · 3. Dezember 2021

Zitat von MarcS

When I run apt update, it says all packages up to date

When I run omv-update, I get this error message

Code

Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up initramfs-tools (0.133+deb10u1) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.133+deb10u1) ...
ln: failed to create hard link '/boot/initrd.img-5.10.0-0.bpo.9-armmp.dpkg-bak' => '/boot/initrd.img-5.10.0-0.bpo.9-armmp': Operation not permitted
update-initramfs: Generating /boot/initrd.img-5.10.0-0.bpo.9-armmp
cryptsetup: ERROR: Couldn't resolve device /dev/root
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
W: mdadm: failed to auto-generate temporary mdadm.conf file.

Alles anzeigen

Because now, you're running arm64.

And the updates were on armhf.

Or vice-versa

i'm completely LOST

Understand know the paradox?!?

MarcS · 3. Dezember 2021

ok. ANy ideas how to solve this?

Jetzt mitmachen!