NSA 325 LUKS-RAID device problems !!!

This forum is for topics dealing with problems with software specifically in the ARMv5 repo.

NSA 325 LUKS-RAID device problems !!!

Postby jama » Sun Oct 18, 2015 2:37 am

Hello,

Today I updated my NSA 325 box with 'pacman -Suy' as usual.

Now, the RAID -partition is not detected any more during the boot.

However, I can start it manually with 'mdadm --run md4', as 'mdadm.conf' has the correct entry.

The second, and the more severe problem is that I've encrypted the corresponding partition with 'cryptsetup', and now the 'cryptsetup' simply hangs up after the correct password is entered.

The data itself is intact; I can pull out the disks and attach those to my desktop computer. So, otherwise everything is fine.

What could be wrong?

$this->bbcode_second_pass_code('', '
[root@alarm ~]# uname -a
Linux alarm 4.2.3-1-ARCH #1 PREEMPT Mon Oct 5 03:10:32 MDT 2015 armv5tel GNU/Linux
[root@alarm ~]# cat /proc/version
Linux version 4.2.3-1-ARCH (builduser@leming) (gcc version 5.2.0 (GCC) ) #1 PREEMPT Mon Oct 5 03:10:32 MDT 2015
')

$this->bbcode_second_pass_code('', '
# cryptsetup 1.6.7 processing "cryptsetup --verbose --debug luksOpen /dev/md4 md4_c"
# Running command open.
# Locking memory.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
# Allocating crypt device /dev/md4 context.
# Trying to open and read device /dev/md4 with direct-io.
# Initialising device-mapper backend library.
# Trying to load LUKS1 crypt type from device /dev/md4.
# Crypto backend (gcrypt 1.6.4) initialized.
# Detected kernel Linux 4.2.3-1-ARCH armv5tel.
# Reading LUKS header of size 1024 from device /dev/md4
# Key length 32, device size 1942162048 sectors, header size 2050 sectors.
# Timeout set to 0 miliseconds.
# Password retry count set to 3.
# Password verification disabled.
# Iteration time set to 1000 miliseconds.
# Activating volume md4_c [keyslot -1] using [none] passphrase.
# dm version OF [16384] (*1)
# dm versions OF [16384] (*1)
# Device-mapper backend running with UDEV support enabled.
# dm status md4_c OF [16384] (*1)
# Interactive passphrase entry requested.
Enter passphrase for /dev/md4:
# Trying to open key slot 0 [ACTIVE_LAST].
# Reading key slot 0 area.
# Using userspace crypto wrapper to access keyslot area.
Key slot 0 unlocked.
# Calculated device size is 1942157947 sectors (RW), offset 4101.
# dm versions OF [16384] (*1)
# Device-mapper backend running with UDEV support enabled.
# DM-UUID is CRYPT-LUKS1-c65101fae0ed475d88eca41167f26921-md4_c
# Udev cookie 0xd4dd70c (semid 0) created
# Udev cookie 0xd4dd70c (semid 0) incremented to 1
# Udev cookie 0xd4dd70c (semid 0) incremented to 2
# Udev cookie 0xd4dd70c (semid 0) assigned to CREATE task(0) with flags (0x0)
# dm versions OF [16384] (*1)
# Device-mapper backend running with UDEV support enabled.
# dm create md4_c CRYPT-LUKS1-c65101fae0ed475d88eca41167f26921-md4_c OF [16384] (*1)
# dm reload md4_c OF [16384] (*1)
# dm resume md4_c OF [16384] (*1)
# md4_c: Stacking NODE_ADD (253,0) 0:0 0600 [verify_udev]
# md4_c: Stacking NODE_READ_AHEAD 256 (flags=1)
# Udev cookie 0xd4dd70c (semid 0) decremented to 1
# Udev cookie 0xd4dd70c (semid 0) waiting for zero
')
jama
 
Posts: 7
Joined: Thu Nov 06, 2014 8:47 am

Return to ARMv5

Who is online

Users browsing this forum: No registered users and 8 guests