Posts by frederik

Hi Dunno,

thanks a lot for your help! Unfortunately I only get this output from lsblk:

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS

sda 8:0 0 5,5T 0 disk

└─md0 9:0 0 5,5T 0 raid1 /srv/dev-disk-by-uuid-6ca5189d-cb82-4a7e-bd8c-cfe09e026c36

sdb 8:16 0 5,5T 0 disk

└─md0 9:0 0 5,5T 0 raid1 /srv/dev-disk-by-uuid-6ca5189d-cb82-4a7e-bd8c-cfe09e026c36

nvme0n1 259:0 0 931,5G 0 disk

├─nvme0n1p1

│ 259:1 0 512M 0 part /boot/efi

├─nvme0n1p2

│ 259:2 0 930,1G 0 part /var/lib/containers/storage/overlay

│ /

└─nvme0n1p3

259:3 0 977M 0 part [SWAP]

When I unmount /srv/dev-disk-by-uuid-6ca5189d-cb82-4a7e-bd8c-cfe09e026c36 I still get the same error message afterwards.

Best regards!

Frederik

Quote from dunno

Hello, frederik,

as the message "Perhaps a running process, mounted filesystem or active volume group?" says, you probably just need to unmount all filesystems that are on your array and also stop all (if any) volume groups on it as well. Here's an example from my setup:

With lsblk (list block devices) you can see a hierarchy from the physical disks (sda and sdb) through the array md0 and the volume groups vg0-share and vg0-timemachine down to the mount points of the filesystems (/export/share and whatnot).

Code

root@nas:~# lsblk
sda                        8:0    0   1.8T  0 disk  
└─md0                      9:0    0   1.8T  0 raid1 
  ├─vg0-share            253:0    0   1.3T  0 lvm   /export/share
  │                                                 /srv/dev-disk-by-uuid-0a26880d-83b3-4696-bf23-e4cbd2cb08ed
  └─vg0-timemachine      253:1    0 558.9G  0 lvm   /export/timemachine
                                                    /srv/dev-disk-by-uuid-06036ad8-5698-43a7-96d4-516bb9d4a1c9
sdb                        8:16   0   1.8T  0 disk  
└─md0                      9:0    0   1.8T  0 raid1 
  ├─vg0-share            253:0    0   1.3T  0 lvm   /export/share
  │                                                 /srv/dev-disk-by-uuid-0a26880d-83b3-4696-bf23-e4cbd2cb08ed
  └─vg0-timemachine      253:1    0 558.9G  0 lvm   /export/timemachine
                                                    /srv/dev-disk-by-uuid-06036ad8-5698-43a7-96d4-516bb9d4a1c9

Display More

So, if I wanted to stop my array md0, I'd simply have to run

Code

root@nas:~# umount /export/share
root@nas:~# umount /export/timemachine
root@nas:~# umount /srv/dev-disk-by-uuid-0a26880d-83b3-4696-bf23-e4cbd2cb08ed
root@nas:~# umount /srv/dev-disk-by-uuid-06036ad8-5698-43a7-96d4-516bb9d4a1c9
root@nas:~# vgchange -an vg0
  0 logical volume(s) in volume group "vg0" now active
root@nas:~# mdadm --stop md0
mdadm: stopped md0

And now you can see that my disks aren't used in anything anymore

Code

root@nas:~# lsblk
NAME                     MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda                        8:0    0   1.8T  0 disk
sdb                        8:16   0   1.8T  0 disk

Hope this help.

Display More

Hi, but isn't that only a temporary solution, which will not survive the reboot?

Quote from rramalho32

Hi all,

Just to say that the correct (or at least the most elegant...) way to resolve this issue is to use dunno 's solution above.

It just works. The result is clean and you don't need to mess around with udev rules.

Code

root@labbackups:~# ls /dev/md*
/dev/md0


/dev/md:
0
root@labbackups:~# mdadm --monitor --scan --oneshot
root@labbackups:~#

Thank you dunno

Display More

Hi @ all,

thanks for the recipe to fix this problem. Unfortunately when I run "

mdadm --stop /dev/md0 

"

I get the error: "mdadm: Cannot get exclusive access to /dev/md0:Perhaps a running process, mounted filesystem or active volume group?". Can someone give me hint? I tried to kill the corresponding processes, but that didn't help.

Best regards!

Frederik

I‘ve exactly the same problem after the upgrade to OMV 8.

Quote from ryecoaaron

Why not use the plugin to decrypt?

Thanks a lot for the fast replies! Sorry, my question was a little bit misleading. I meant to permanently remove the encryption from the drive without wiping it.

Hi there, does anybody know if there is a way to decrypt a drive again without wiping it?

Quote from votdev

Run the command mentioned here

Post

RE: Error after depolying omv-env variable unset OMV_BTRFS_ERROR_CHECK_ENABLED under 7.0.3

[…]

The md related notification config is still not there. Run the following command again

(Code, 1 line)

votdev

Mar 18th 2024

Thanks a lot!! Worked!!

Dear all,

when I want to apply the new configuration after changes, I get the error message in the attachment. ErrorMsg.txt Does anybody know how to fix this?

Best regards!

Frederik

Thanks a lot for the quick reply and that you directly investigated the problem. I just tested it without forcing ssl for the web interface and then it works perfectly with the links! Thanks a lot!!

I have exactly the same problem as fr33bsd.