On 02/02/2015 06:32 PM, Rich Emberson wrote:
Tried:
# wipefs -a /dev/md127
which did not word, so I next tried:
# wipefs -f -a /dev/md127
/dev/md127: 6 bytes were erased at offset 0x (crypto_LUKS): 4c
55 4b 53 ba be
and then
# mdadm -S /dev/md127
mdadm: Cannot get exclusive access
Also, you probably want to check crypttab to make sure this device
entry is removed, and also from fstab to make sure whatever file
system was on it isn't going to be automounted anymore. Otherwise good
chance you'll get a failed boot while a non-existent fs is being
looked for (and it'll take a wh
On Mon, Feb 2, 2015 at 5:25 PM, Rich Emberson wrote:
> # cryptsetup status luks-ab8911f9-b3a4-4f33-8b10-7e52c7217ae9
> /dev/mapper/luks-ab8911f9-b3a4-4f33-8b10-7e52c7217ae9 is active.
That's the problem. First use df or mount to see if this device has a
mounted filesystem, and if so unmount it. T
Tried:
# wipefs -a /dev/md127
which did not word, so I next tried:
# wipefs -f -a /dev/md127
/dev/md127: 6 bytes were erased at offset 0x (crypto_LUKS): 4c 55
4b 53 ba be
and then
# mdadm -S /dev/md127
mdadm: Cannot get exclusive access to /dev/md127:Perhaps a running process,
mounte
Thanks - wipefs fails see below
# dmsetup ls
luks-ab8911f9-b3a4-4f33-8b10-7e52c7217ae9 (253:9)
luks-35719a97-5898-4420-9a56-1576ffdc6db3 (253:1)
luks-c80d9988-30f6-42cf-a9b7-89ee3408eccb (253:6)
luks-03c06df8-f9b9-4f0d-847e-79a7ed527888 (253:0)
luks-a2ebb2b0-527d-47f3-83ef-
What do you get for:
dmsetup ls
cryptsetup status
I see this:
> /dev/mapper/luks-ab8911f9-b3a4-4f33-8b10-7e52c7217ae9 /raid1
This suggests an encrypted device mapper device created from the raid1
device, and it's active. So that has to be closed, or wipefs before
you can stop the raid and then
