Dave-Kay

Just a small update. The friend was told to send the board in, after it failed on luks under debian....

ok, thanks...and fuck, this is a really good idea, while i tested other Ports (of course) i left my controller in the closet The mini-SAS cable is in the package btw.

The asrockstuff is serious stuff. i have a C2550D4I and it is really nice. there was even the bug in the CPU an asrock changed it for a new one without the bug, after it had some trouble. The board my friend has ist even more advanced and the performance with unraid was outstanding. But i didn't have the time to sort all features out, because i was focused on this problem. I think the best what could happen was, that there is a hardwareerror for real and asrock changes this board, too... but for that, we need to find out more, there is, at the moment, no real thing to prove hardwareerrors. and above all that, i told him to choose asrock and to choose unraid...so i feel kind of responsible in a way 🙂

I think i found, what was going on with this. It is some kind of virtualization capability of the board. I think there must have been a cmos reset or setup default loading in between, which activated the virtual devices in Bios.

You're right, but i don't think its broken in general, there would be at least some more posts about it. The difficulty here is a few steps higer even, because there is nothing pointing to any problems on the system... until you use encryption, sryl NOTHING! It runs flawlessly with even a bunch of Vms and a bunch of dockers.

yeah, i think im going to test it on my system this weekend (the other is the brandnew system of bubiman) but i think testing it on my unraid, will not prove much, either way.

i did a complete memtest from the bootmenu, without any errors. And i switched the ram afterwards, with the same result.

to what points this, if it was indeed a hardware-issue?

Hello, Thanks for the replies. First, there is no way, that this is about performance of the CPU. It would work anyway, but it would cost cpu-time. But I don't think that it would with this CPU. Look it up. We had drive encryption for a long time now and we did it with Much smaller cpus, even without AES-NI Then @limetech is there anything you could point me to? And about separation and plugins. Yes, without any plug in and yes single drive only tested. I even tested without parity. No cross shares ever. The share was only on the encrypted drive and everything else was excluded.

ok, i give up, it is broken

6.6.7 didn't work either. I'm lost.

You're right. That didn't help. I had 6.7.3.rc1 installed for testing, which didn't change anything. Now i downgraded to 6.6.7 and i am waiting for parity ceck once again...

Yeah, thats what i think. but i really don't know which Hardware... however, next step, changing RAM.

It's just the same, if i try to copy the files in MC. That's highly disappointing.

i tried to understand the 8bit datawidth and read a bit,m but i still don't get it, why has this DDR4 Memorychip 8bit and my DDR3 has 64Bit? ------------------------------------------------------------------ Mine: --------------------------------- Total Width:64 bits Data Width:64 bits Size:8192 MB Form Factor:DIMM Set:None Locator:DIMM0 Bank Locator:BANK 0 Type:DDR3 Type Detail:Synchronous Unbuffered (Unregistered) Speed:1600 MT/s Manufacturer:Micron Serial Number:18201217 Asset Tag:1BANK 0 DIMM0 AssetTag Part Number:18KSF1G72AZ-1G6P1 Rank:2 Configured Memory Speed:1600 MT/s ---------------------------------------------------------------- The one in the Server with Problems: ---------------------------------------------------------------- Total Width:8 bits  <<<<<<!!! Data Width:8 bits  <<<<<<!!! Size:16384 MB Form Factor:DIMM Set:None Locator:DIMM1 Bank Locator:BANK 0 Type:DDR4 Type Detail:Synchronous Unbuffered (Unregistered) Speed:2400 MT/s Manufacturer:Samsung Serial Number:38F1142D Asset Tag:BANK 0 DIMM1 AssetTag Part Number:M378A2K43BB1-CRC Rank:2 Configured Memory Speed:2400 MT/s Minimum Voltage:1.2 V Maximum Voltage:1.2 V Configured Voltage:1.2 V

thanky you, for your reply, will test that tomorrow. first i have to check parity again....

i finally got one diagnostic after the process to copy files on the encrypted disk stopped. tower-diagnostics-20190725-1552.zip

as i am new to luks... does this help in any way? ------------------------------------------------------------------------------------ root@Tower:~# cryptsetup benchmark # Tests are approximate using memory only (no storage IO). PBKDF2-sha1 489074 iterations per second for 256-bit key PBKDF2-sha256 604715 iterations per second for 256-bit key PBKDF2-sha512 406424 iterations per second for 256-bit key PBKDF2-ripemd160 392431 iterations per second for 256-bit key PBKDF2-whirlpool 233639 iterations per second for 256-bit key # Algorithm | Key | Encryption | Decryption aes-cbc 128b 312.0 MiB/s 294.1 MiB/s serpent-cbc 128b 41.2 MiB/s 101.5 MiB/s twofish-cbc 128b 88.9 MiB/s 105.1 MiB/s aes-cbc 256b 237.3 MiB/s 245.4 MiB/s serpent-cbc 256b 44.0 MiB/s 101.5 MiB/s twofish-cbc 256b 92.0 MiB/s 105.0 MiB/s aes-xts 256b 293.8 MiB/s 283.8 MiB/s serpent-xts 256b 91.1 MiB/s 97.0 MiB/s twofish-xts 256b 97.4 MiB/s 100.1 MiB/s aes-xts 512b 237.6 MiB/s 238.4 MiB/s serpent-xts 512b 96.7 MiB/s 97.0 MiB/s twofish-xts 512b 99.8 MiB/s 99.9 MiB/s

Oh, i didn't find anything here in the forum. But i didn't even consider performance-Problems in any way. So there shoulkd be Problems with any linux and luks on the machine, too?

Thank you for your reply! Yes! After the friend failed to get it working and i suspected the encryption the first approach was of course to just test the system on this Hardware, without any encryption. I installed it and put plugins in it, VMs and Docker-instances. Everthing worked just fine, for 2 days. After that i wanted to add encryption and immediatels the sytem had gone nuts as described.

as i wasn't able to pull diagnostic after the appearing Problems, i pulled one after systemstart now. Memtest didn't find anything tower-diagnostics-20190724-1504.zip

found something interesting though... both modules show like this in dynamix System Information Memory Device Total Width:8 bits <<<<<<!!! Data Width:8 bits <<<<<<!!! Size:16384 MB Form Factor:DIMM Set:None Locator:DIMM1 Bank Locator:BANK 0 Type:DDR4 Type Detail:Synchronous Unbuffered (Unregistered) Speed:2400 MT/s Manufacturer:Samsung Serial Number:38F1142D Asset Tag:BANK 0 DIMM1 AssetTag Part Number:M378A2K43BB1-CRC Rank:2 Configured Memory Speed:2400 MT/s Minimum Voltage:1.2 V Maximum Voltage:1.2 V Configured Voltage:1.2 V

So it seems, there is nothing really written to the encrypted drive. As i said, i had to hard reset the server, as he told me, he was syncing the filesystem. after next boot i accessed the share and it was empty. i have never seen anything like that before. (of course there is no cache drive.)

So i had to hard reset the server because he wouldn't neither finish the sync, nor tell me what is going on in any way. after next boot this appeared out of nowhere. (see image)

So i tried again, and ist seems to be failing again. hardware is ASRock C3758D4I-4L 32GB Memory 2x WD-Red 4TB 1 x WDC_WD20EZRX At the moment it seems to be endles syncing drives to stop array. 2 out of 8 cpus are at 100% I'm stuck with this. tower-syslog-20190723-1549.zip