Description: I would like to request that dm_mod.so be included in TrueNAS as it is a core piece in using cryptsetup and LUKS. It was previously included and in 24.10.2 was removed. This vote would be to support bringing back the dm_mod.so file so that cryptsetup can manually be used.
With this, but not the primary reason, I also propose that support for the transfer of large hard drives in TrueNAS be improved. Specifically, the hardware of today’s NAS systems with USB 3.2 (e.g., UGREEN DXP4800 Plus) should contribute to performing data backups outside the network efficiently. Additionally, support for mounting LUKS-encrypted drives with ext4 filesystem should be reinstated. This functionality does not necessarily need to be accessible through the GUI; the ability to perform this via the console, as in previous versions, would suffice.
Benefits:
Increased Data Transfer Speed: USB 3.2 offers faster data transfer rates, significantly speeding up the transfer of large amounts of data.
Enhanced Security: Support for LUKS allows secure encryption of drives, protecting sensitive data from unauthorized access.
Compatibility: Many users utilize ext4 as the standard filesystem for their drives. Supporting this ensures seamless integration and usage.
Flexibility in Data Backup: With the support of modern NAS hardware, users can directly connect large hard drives via USB 3.2 and perform data backups outside the network.
Versatility: The ability to mount LUKS-encrypted drives with ext4 filesystem provides users with more options for secure and efficient data management.
User Story: As a TrueNAS user, I want to be able to connect large hard drives via USB 3.2 to perform data backups outside the network. Additionally, I want to mount LUKS-encrypted drives with ext4 filesystem to securely store my data while benefiting from the performance and reliability of ext4. This functionality does not necessarily need to be accessible through the GUI; the ability to perform this via the console, as in previous versions, would suffice. This allows me to transfer data faster and make the backup of my important data more efficient and secure.
Implementation Details:
Integration: Support for USB 3.2, LUKS-encrypted drives, and ext4 filesystem should be seamlessly integrated into TrueNAS.
Documentation: Detailed documentation on using these features should be provided to facilitate users’ getting started.
Voting Option: This topic includes a voting option. Each forum user has a limited number of votes that can be cast for this feature at any time. The higher the user’s trust level, the more votes they can cast.
As mentioned before, LUKS is not supported, and it appears it won’t be. However, regular USB-connected ext4 drives are supported just fine; that’s how I do backups currently, since it’s much faster than doing a backup to a USB drive over a GbE connection.
basically it is not a request for a new function. during the cleanup dm_mod.so simply fell victim. this module is essential for cryptsetup , it is just a hint: “either pregnant , or not”. a little cryptsetup for formatting is nonsense if it cannot be mounted ! no big development environment has to be created to enable this function “AGAIN”. just don’t forget dm_mod.so in the kernel as in previous versions
This is not what you proposed in the original posting here and it is very different. I am not sure if you can edit your original posting however if you are not able, if you send me a message with “exactly” what you would like the posting to say, I will be happy to change it for you.
And remember, you do need to solicit for the votes. 10+ votes almost guarantees serious consideration. Also adding a single kernel module is easy for iXsystem to include. iXsystems has been hardening the system and sometimes if affects certain people. So, unless it poses a security concern or there was some valid reason for removing it, iX may easily put it back in.
In TrueNAS version 24.04.2.3, the kernel module dm_mod.so was still present. Starting from TrueNAS version 24.10.2, only remnants of cryptsetup (during hardening) remain. There has been neither a roadmap announcement nor a release note about LUKS being removed as part of the hardening process.
The fact that this feature was not available in the GUI is completely fine. However, the sudden disappearance of existing functionalities without any announcements is alarming. The main issue here is the inability to load dm_mod.so when needed. Any help to address this would be greatly appreciated. Thank you for your support!
Feel free to make any adjustments or let me know if you need further assistance!
I made a change to the posting. If it is not what you desire, please provide something I can cut/paste and I will do that.
In the meantime, and I understand this is not ideal, have you tried to build and manually install the file? It is fairly (sort of) easy but you need to know what you are doing and you need to use Developer Mode. The real issue here is any upgrade of TrueNAS, it will be gone and you have to rebuild again. If you are having problems accessing your data, I believe this is still an option.
Thank you very much for your support and the changes - very well done! My English phrasing is limited. Yes, the option to use developer mode after each update would be Plan B. I don’t have the impression that this module negatively impacts the hardening of the system. Implementing the appropriate module would also be entirely sufficient - activation via insmod dm_mo.so is done manually. That would be a good compromise, wouldn’t it?
i hope and assume that the missing module is a bug and not a feature - something like that can happen. removing only the corresponding module without the cryptsetup tool indicates that it was not thought through to the end, or simply overlooked. i hope ixsystem can deal with the request honestly and respectfully. if no one votes - it was all for nothing
