Luks with a 4 TB HDD (USB)

Installing and Using OpenWrt
1

I can format do cryptsetup/format my extern HDD. Then I can format it with any filesystem. When I mount it, after some copy tries of files, I get lots of errors, like this:

root@OpenWrt:~# dmesg 
[ 1243.923956] XFS (dm-0): Metadata corruption detected at 0x829425b0 [xfs@deae95aa+0xa13e0], xfs_inode block 0xecf29e90 xfs_inode_buf_verify
[ 1243.935136] XFS (dm-0): Unmount and run xfs_repair
[ 1243.942158] XFS (dm-0): First 128 bytes of corrupted metadata buffer:
[ 1243.949898] 00000000: ec 4f 81 de 2a cb de 5c e3 a1 c7 37 92 9f d4 9c  .O..*..\...7....
[ 1243.959908] 00000010: cd 22 ab 46 aa 01 96 38 1c 8d da 12 33 03 c7 37  .".F...8....3..7
[ 1243.968958] 00000020: 36 83 a6 12 d6 67 75 4d 87 ef 4c 92 97 09 1a 5a  6....guM..L....Z
[ 1243.981604] 00000030: aa df b0 0b 1c 18 4e a1 83 86 06 38 a3 a9 de 11  ......N....8....
[ 1243.988388] 00000040: 28 e8 ee b2 15 bb 87 ac 45 00 f9 53 90 06 f6 d6  (.......E..S....
[ 1243.998623] 00000050: 88 cf 2a f4 dc 7a 9c 65 cf 80 3a f7 65 8d b8 d5  ..*..z.e..:.e...
[ 1244.007670] 00000060: 8b 0d ce 94 4b ba 20 2e ed 0a 08 55 57 6c 27 e6  ....K. ....UWl'.
[ 1244.020349] 00000070: 78 5a 54 9b df 08 32 70 67 49 6b e6 3b f0 af 3c  xZT...2pgIk.;..<
[ 1244.027210] XFS: metadata IO error: 57 callbacks suppressed
[ 1244.027281] XFS (dm-0): metadata I/O error in "0x829426c8 [xfs@deae95aa+0xa13e0]" at daddr 0xecf29e90 len 32 error 135
[ 1244.127988] XFS (dm-0): xfs_do_force_shutdown(0x1) called from line 296 of file fs/xfs/xfs_trans_buf.c. Return address = 04de1dbf
[ 1244.138328] XFS (dm-0): I/O Error Detected. Shutting down filesystem
[ 1244.144579] XFS (dm-0): Please unmount the filesystem and rectify the problem(s)
[ 1258.048702] XFS (dm-0): Unmounting Filesystem
[ 1567.116934] XFS (dm-0): Mounting V5 Filesystem
[ 1567.609817] XFS (dm-0): Ending clean mount
[ 1567.650160] xfs filesystem being mounted at /home supports timestamps until 2038 (0x7fffffff)

With HDDs under 2 TB, the partitionstable is DOS and with this I have no problems to use luks. but when the partitionstable is GPT ( its recommend by HDDs, greater than 2TB ), I get the Problems. I have tried many OpenWRT versions, but allways run in to the errors.

Anybody now, why ans can help?

2

Its not an openwrt issue, try ext4 over usb3.0 only.

Before unmount the disk, run "sync".

3

That make no different. Here the full text, what I was doing ...

WARNING!
========
This will overwrite data on /dev/sda1 irrevocably.

Are you sure? (Type 'yes' in capital letters): YES
Enter passphrase for /dev/sda1: 
Verify passphrase: 
root@OpenWrt:~# cryptsetup open /dev/sda1 home
Enter passphrase for /dev/sda1: 
root@OpenWrt:~# mkfs.ext4 /dev/mapper/home 
mke2fs 1.46.5 (30-Dec-2021)
Creating filesystem with 976753664 4k blocks and 244195328 inodes
Filesystem UUID: b6d549e9-4978-4244-99a9-73c0eb6f4229
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
        102400000, 214990848, 512000000, 550731776, 644972544

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done       

root@OpenWrt:~# mount /dev/mapper/home /home
mount: mounting /dev/mapper/home on /home failed: No error information
root@OpenWrt:~#

By the way, I use USB 1.0

4

I used a 4TB USB 3.0 device with GPT and luks2 before, and had no issue. Currently I am running multiple 500GB HDDs with LVM on LUKS on MDRAID, no issue either. It is really hard to recommend anything to you, because the error was generic and contained no helpful information:

mount: mounting /dev/mapper/home on /home failed: No error information

Can you try to scan the HDD for badblocks? Or at least try to create the partition with offset more than 1MiB, let's say test it with 16MiB offset? IO errors are usually caused by damaged sectors.

[ 1244.138328] XFS (dm-0): I/O Error Detected. Shutting down filesystem

5

A bit test,

  • pendrive 16g
  • gpt label
  • cryptsetup with key file
  • ext4 fs
root@EA8500:~# gpg --decrypt /tmp/key.gpg | cryptsetup --key-size 512 --key-file - luksFormat /dev/sda1
gpg: AES256 encrypted data
Enter passphrase: 
gpg: encrypted with 1 passphrase

root@EA8500:~# gpg --decrypt /tmp/key.gpg | cryptsetup --key-file - luksOpen --allow-discards /dev/sda1 lukydisk
gpg: AES256 encrypted data
gpg: encrypted with 1 passphrase

root@EA8500:~# mkfs.ext4 -L pendrive /dev/mapper/lukydisk               mke2fs 1.45.6 (20-Mar-2020)
Creating filesystem with 752640 4k blocks and 188416 inodes
Filesystem UUID: b127c283-2b9c-49ac-aed8-8e1cb08c6199
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

root@EA8500:~# mount /dev/mapper/lukydisk /mnt/storage/
root@EA8500:~# dmesg | tail -n 1
[401893.933689] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
root@EA8500:~# date > /mnt/storage/file1
root@EA8500:~# sync ; echo $?
0
root@EA8500:~# df /mnt/storage/
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mapper/lukydisk   2888880        28   2721940   0% /mnt/storage

root@EA8500:~# cat /mnt/storage/file1
Sun Dec 18 13:00:00 -03 2022
root@EA8500:~# umount /mnt/storage/
root@EA8500:~# cryptsetup close lukydisk
6

But on a normal Debian PC, the HDD works well. I have copied over 2TB data to the HDD, without any errors. When I dont use luks on my openWrt Box, the HDD works well, too. I only get problems when I use luks with the 4TB HDD ( USB 1.1 ).

7

@ [powtrix]
I did the same, like you, for testing with an 32GB stick and gpt label. I get similar errors:

[ 5060.570925] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[ 5101.673252] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5101.690560] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5104.901511] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5104.918594] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5130.776041] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5130.794037] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5133.677246] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5133.694205] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5146.276419] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5146.293659] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5149.400233] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5149.417703] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5168.989556] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5169.006982] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5172.879276] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
[ 5172.896710] EXT4-fs error (device dm-0): ext4_readdir:204: inode #11: comm mc: path /mnt/lost+found: directory fails checksum at offset 8192
8

By the way ... this is my box ...

http://www.boxmatrix.info/wiki/FRITZ!Box_7362_SL

9

Your device has only 128MB of ram. The weirdness you are seeing could be due to a lack of sufficient ram. You can try specifying --pbkdf pbkdf2 when you do luksFormat to reduce the memory usage, and you may also want to consider using a virtual memory swap file on your hdd.

10

mhmmmm, the problem is still there ...

root@OpenWrt:/# dmesg 
[ 9373.280909] EXT4-fs error (device dm-0): htree_dirblock_to_tree:1042: inode #2966: comm mc: Directory block failed checksum
[ 9373.296535] EXT4-fs error (device dm-0): htree_dirblock_to_tree:1042: inode #2966: comm mc: Directory block failed checksum
[ 9422.695525] EXT4-fs error (device dm-0): htree_dirblock_to_tree:1042: inode #271: comm mc: Directory block failed checksum
[ 9422.711984] EXT4-fs error (device dm-0): htree_dirblock_to_tree:1042: inode #271: comm mc: Directory block failed checksum
[ 9422.738647] EXT4-fs warning (device dm-0): ext4_dirblock_csum_verify:400: inode #74: comm mc: No space for directory leaf checksum. Please run e2fsck -D.
[ 9422.751100] EXT4-fs error (device dm-0): htree_dirblock_to_tree:1042: inode #74: comm mc: Directory block failed checksum
[ 9422.767939] EXT4-fs warning (device dm-0): ext4_dirblock_csum_verify:400: inode #74: comm mc: No space for directory leaf checksum. Please run e2fsck -D.
[ 9422.780381] EXT4-fs error (device dm-0): htree_dirblock_to_tree:1042: inode #74: comm mc: Directory block failed checksum
[ 9422.804547] EXT4-fs error (device dm-0): ext4_lookup:1752: inode #54: comm mc: iget: bad extra_isize 31647 (inode size 256)
[ 9422.839457] EXT4-fs error (device dm-0): ext4_lookup:1752: inode #53: comm mc: iget: bad extra_isize 15264 (inode size 256)
[ 9422.861518] EXT4-fs error (device dm-0): htree_dirblock_to_tree:1042: inode #60: comm mc: Directory block failed checksum
[ 9422.877744] EXT4-fs error (device dm-0): htree_dirblock_to_tree:1042: inode #60: comm mc: Directory block failed checksum
[ 9423.005295] EXT4-fs error (device dm-0): ext4_lookup:1752: inode #161: comm mc: iget: bad extra_isize 17038 (inode size 256)
[ 9423.027257] EXT4-fs error (device dm-0): ext4_lookup:1752: inode #162: comm mc: iget: bad extra_isize 23568 (inode size 256)
[ 9423.910263] EXT4-fs warning (device dm-0): ext4_dirblock_csum_verify:400: inode #1882: comm mc: No space for directory leaf checksum. Please run e2fsck -D.
[ 9423.928482] EXT4-fs warning (device dm-0): ext4_dirblock_csum_verify:400: inode #1882: comm mc: No space for directory leaf checksum. Please run e2fsck -D.
[ 9424.316272] EXT4-fs warning (device dm-0): ext4_dirblock_csum_verify:400: inode #2276: comm mc: No space for directory leaf checksum. Please run e2fsck -D.
[ 9424.334512] EXT4-fs warning (device dm-0): ext4_dirblock_csum_verify:400: inode #2276: comm mc: No space for directory leaf checksum. Please run e2fsck -D.
[ 9429.273956] EXT4-fs error: 44 callbacks suppressed
[ 9429.273978] EXT4-fs error (device dm-0): htree_dirblock_to_tree:1042: inode #7782: comm mc: Directory block failed checksum
[ 9429.294214] EXT4-fs error (device dm-0): htree_dirblock_to_tree:1042: inode #7782: comm mc: Directory block failed checksum
[ 9429.325807] EXT4-fs error (device dm-0): htree_dirblock_to_tree:1042: inode #8089: comm mc: Directory block failed checksum
[ 9429.341460] EXT4-fs error (device dm-0): htree_dirblock_to_tree:1042: inode #8089: comm mc: Directory block failed checksum
[ 9429.599374] EXT4-fs error (device dm-0): htree_dirblock_to_tree:1042: inode #7514: comm mc: Directory block failed checksum
[ 9429.622015] EXT4-fs error (device dm-0): htree_dirblock_to_tree:1042: inode #7514: comm mc: Directory block failed checksum
[ 9429.683154] EXT4-fs error (device dm-0): ext4_lookup:1752: inode #7581: comm mc: iget: bad extra_isize 24577 (inode size 256)
[ 9429.699301] EXT4-fs error (device dm-0): ext4_lookup:1752: inode #7582: comm mc: iget: bad extra_isize 25413 (inode size 256)
[ 9429.714987] EXT4-fs error (device dm-0): ext4_lookup:1752: inode #7583: comm mc: iget: bad extra_isize 31372 (inode size 256)
[ 9429.731402] EXT4-fs error (device dm-0): ext4_lookup:1752: inode #7584: comm mc: iget: bad extra_isize 5464 (inode size 256)
[ 9431.855442] EXT4-fs warning (device dm-0): ext4_dirblock_csum_verify:400: inode #74: comm mc: No space for directory leaf checksum. Please run e2fsck -D.
[ 9431.873535] EXT4-fs warning (device dm-0): ext4_dirblock_csum_verify:400: inode #74: comm mc: No space for directory leaf checksum. Please run e2fsck -D.

On a similar router, I have a 2TB HDD with luks and ext4 and thats works (DOS partition table). I checked the USB stick (GPT) for testing with badblocks. there are no bad blocks on it. But there are errors, too, when I use it with luks and ext4.

mysterious

11

Try clean the port with Isopropyl alcohol.

12

I'm confused. What exactly is your hardware setup? The link you posted for your hardware indicates that the router has two usb 2 ports, not usb 1.1. I'm assuming that the usb hardware for your hdd is either usb 2 or usb 3.

If your hdd is usb 3, and you're connecting it to a usb 1.1 port, that would explain the weirdness. USB 3 storage devices are usually backwards compatible with usb 2, but not with usb 1.1. You will get loads of bit errors if you connect a usb 3 storage device to a usb 1.1 port.

13

This is my second router, similar the first one:

root@dach:~# lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=, Driver=usb-storage, 480M
root@dach:~# dmesg 
root@dach:~# mount
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
/dev/ubi0_1 on /overlay type ubifs (rw,noatime,assert=read-only,ubi=0,vol=1)
overlayfs:/overlay on / type overlay (rw,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,noatime,mode=700)
/dev/mapper/home on /home type ext4 (rw,relatime)
root@dach:~# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 4.3M      4.3M         0 100% /rom
tmpfs                    59.5M    952.0K     58.6M   2% /tmp
/dev/ubi0_1             106.2M     18.3M     83.2M  18% /overlay
overlayfs:/overlay      106.2M     18.3M     83.2M  18% /
tmpfs                   512.0K         0    512.0K   0% /dev
/dev/mapper/home          1.8T    429.7G      1.3T  25% /home

root@dach:~# fdisk /dev/sda

Welcome to fdisk (util-linux 2.36.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): p
Disk /dev/sda: 1.82 TiB, 2000398933504 bytes, 3907029167 sectors
Disk model: Expansion       
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6c9023be

Device     Boot Start        End    Sectors  Size Id Type
/dev/sda1  *       64 3907024128 3907024065  1.8T  7 HPFS/NTFS/exFAT

Command (m for help): 

root@dach:~# cryptsetup luksDump /dev/sda1
LUKS header information
Version:       	2
Epoch:         	3
Metadata area: 	16384 [bytes]
Keyslots area: 	16744448 [bytes]
UUID:          	97a94a20-90cd-4b90-b291-a8ee57cd1444
Label:         	(no label)
Subsystem:     	(no subsystem)
Flags:       	(no flags)

Data segments:
  0: crypt
	offset: 16777216 [bytes]
	length: (whole device)
	cipher: aes-xts-plain64
	sector: 512 [bytes]

Keyslots:
  0: luks2
	Key:        512 bits
	Priority:   normal
	Cipher:     aes-xts-plain64
	Cipher key: 512 bits
	PBKDF:      pbkdf2
	Hash:       sha256
	Iterations: 16148
	Salt:       c1 94 86 ba d3 1b ba 5b 90 ab c2 44 73 d8 49 4f 
	            3e 6f 8c 56 d9 97 fe 48 8a fb 75 54 0d 58 28 e9 
	AF stripes: 4000
	AF hash:    sha256
	Area offset:32768 [bytes]
	Area length:258048 [bytes]
	Digest ID:  0
Tokens:
Digests:
  0: pbkdf2
	Hash:       sha256
	Iterations: 1016
	Salt:       04 44 d7 bf 34 8f 24 e8 22 d4 34 39 77 41 a4 bd 
	            17 fc ff f9 76 51 86 cf cc fe d4 81 e6 95 b5 3a 
	Digest:     e6 e3 dc f8 25 c6 45 8e b8 30 c9 53 82 fe 72 1f 
	            69 5f 2c 58 66 4f a6 bc d1 18 d5 7b 0e ae 22 a0 
root@dach:~#

On the USB Port is 2TB HDD (DOS partitiontable), with luks and ext4 and it works, with no errors. The first box, in my flat with the 4 TB HDD ( the same luks parameters, like the 2 TB HDD ), and ext4 dont works.

Im confused, like you. I think, I make a test and change the HDDs between the to boxes. By the way, I have a third similar Box fpr testing and there the 4 TB HDD dont works, too. But on Debian PCs there are no errors when I use it. The HDDs can USB3, but the Box only can USB1.1? Wrong driver may be?

14

A mysterie ... on the second box ( similar the first one ), the 4TB HDD works, without errors.
an the first box, I tried the 2TB HDD from the second box and there are errors. I dont understand that ...

15

But I know the 2TB HDD works well on the first box a long time ago.

16

The same mashines:

root@dach:~# cat /proc/cpuinfo 
system type             : xRX200 rev 1.2
machine                 : AVM FRITZ!Box 7362 SL
processor               : 0
cpu model               : MIPS 34Kc V5.6
BogoMIPS                : 332.54
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 16
extra interrupt vector  : yes
hardware watchpoint     : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa                     : mips1 mips2 mips32r1 mips32r2
ASEs implemented        : mips16 dsp mt
Options implemented     : tlb 4kex 4k_cache 32fpr prefetch mcheck ejtag llsc dc_aliases userlocal vint perf_cntr_intr_bit perf
shadow register sets    : 1
kscratch registers      : 0
package                 : 0
core                    : 0
VPE                     : 0
VCED exceptions         : not available
VCEI exceptions         : not available

processor               : 1
cpu model               : MIPS 34Kc V5.6
BogoMIPS                : 333.82
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 16
extra interrupt vector  : yes
hardware watchpoint     : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa                     : mips1 mips2 mips32r1 mips32r2
ASEs implemented        : mips16 dsp mt
Options implemented     : tlb 4kex 4k_cache 32fpr prefetch mcheck ejtag llsc dc_aliases userlocal vint perf_cntr_intr_bit perf
shadow register sets    : 1
kscratch registers      : 0
package                 : 0
core                    : 0
VPE                     : 1
VCED exceptions         : not available
VCEI exceptions         : not available


root@OpenWrt:~# cat /proc/cpuinfo 
system type             : xRX200 rev 1.2
machine                 : AVM FRITZ!Box 7362 SL
processor               : 0
cpu model               : MIPS 34Kc V5.6
BogoMIPS                : 331.77
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 16
extra interrupt vector  : yes
hardware watchpoint     : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa                     : mips1 mips2 mips32r1 mips32r2
ASEs implemented        : mips16 dsp mt
Options implemented     : tlb 4kex 4k_cache 32fpr prefetch mcheck ejtag llsc dc_aliases userlocal vint perf_cntr_intr_bit perf
shadow register sets    : 1
kscratch registers      : 0
package                 : 0
core                    : 0
VPE                     : 0
VCED exceptions         : not available
VCEI exceptions         : not available

processor               : 1
cpu model               : MIPS 34Kc V5.6
BogoMIPS                : 334.23
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 16
extra interrupt vector  : yes
hardware watchpoint     : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb]
isa                     : mips1 mips2 mips32r1 mips32r2
ASEs implemented        : mips16 dsp mt
Options implemented     : tlb 4kex 4k_cache 32fpr prefetch mcheck ejtag llsc dc_aliases userlocal vint perf_cntr_intr_bit perf
shadow register sets    : 1
kscratch registers      : 0
package                 : 0
core                    : 0
VPE                     : 1
VCED exceptions         : not available
VCEI exceptions         : not available
17

Downgrading to 21.x does the trick. no errors any more. On my second box was openWRT 21.x installed. On my first box was openWRT 22.x installed.
Now it works with luks and ext4 and the 4 TB HDD on the first and second box.
There are some bugs in openWRT 22.x? Drivers or luks?

18

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.