Fatal Error – Encryption kernel module dm-crypt not found

Forum Forums Official Releases antiX-19 “Marielle Franco, Hannie Schaft, Manolis Glezos, Grup Yorum, Wobblies” Fatal Error – Encryption kernel module dm-crypt not found

  • This topic has 24 replies, 4 voices, and was last updated Dec 14-3:16 pm by BitJam.
Viewing 8 posts - 16 through 23 (of 23 total)
  • Author
    Posts
  • #30488
    Forum Admin
    BitJam
      Helpful
      Up
      0
      ::

      If I understand the mechanism I think this methodology of leaving copies is good under circumstances as it makes this cloning process work (at least under the original antiX 4.9 kernel. So even if you consider this approach a ‘false laziness’ this allows cloning functionality to work.

      It’s false laziness because it allowed a certain type of cloning to work but it causes many other problems later on. IMO redundant information is the root of a lot of evil and this is a perfect example. LUM finds the extra initrd and vmlinuz files and things everything’s hunky-dory when it’s not. A similar problem happened recently when fehlix used my live-repair script to add some initrd changes to a elive-usb. The script ran successfully but the fix didn’t happen. This is because the script only looked for initrd.gz on the main partition. It happily updated this file but the initrd.gz that is actually used resides on the boot partition and wasn’t touched. In this case it would have been much better for live-repair to have errored out instead of updating the wrong initrd.gz.

      I plan to remove those spare/bogus copies of initrd.gz and vmlinuz but that might be a deeper change. I also need to make a fix when toram + encrypted is used. In that case I need to mount the boot partition and copy almost all its files to the the to-ram tmpfs file system.

      Considering that encryption is a necessity for Live USB and cloning of running system is extremely important would you suggest the course oaction:
      – A update to LUM will be possible

      I’m working on a fix now. It was an interesting puzzle. When I clone from a elive-usb I mount the boot partition and clone all the required files from it except the linuxfs file (and persistence files, if needed). So the clone will get all the files that were used in booting the elive-usb. This works.

      Hit an added complication. When cloning from an encrypted live-usb to a non-encrypted one then I need to rebuild the copied initrd.gz in order to disable encryption mode.

      I’m delighted you have explored some of these nooks and crannies (perhaps they are not nooks and crannies to you). With all our different options, the system is rather complicated and we haven’t been doing enough testing or enough systematic testing. Are you a beta tester? If not, would you like to become one? IMO this is the area where we need to most help now.

      Context is worth 80 IQ points -- Alan Kay

      #30506
      Member
      olsztyn
        Helpful
        Up
        0
        ::

        Thanks very much BitJam for additional insight and your plan to re-develop relevant parts of LUM to resolve these issues… This is greatly appreciated.
        I am not (an official at least) beta tester but will gladly participate in beta testing of critical functions such as this to the best of my ability.

        Live antiX Boot Options (Previously posted by Xecure):
        https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

        #30515
        Forum Admin
        BitJam
          Helpful
          Up
          0
          ::

          I pushed version 2.41.17 to my github repo. I tested it here and it seemed to work but the changes were a little complicated so there may be a few problems.

          I still need to fix/test encrypt + toram + live-remaster. I also need to fix encrypt + toram + clone. I’d also like to stop adding vmlinuz and initrd.gz to the main partition when we encrypt. But I did address the problems you found. encrypt + clone should be working now.

          Context is worth 80 IQ points -- Alan Kay

          #30516
          Member
          olsztyn
            Helpful
            Up
            0
            ::

            Thank you BitJam for working on this so late at night. I was trying to add your github repo to list of repositories in synaptic to test (if you require me to test it at this point yet) but somehow synaptic did not include it. What spec should I use for this repo to be recognized by synaptic or is there another way?
            I am so glad there is recognition of the importance of LUM by antiX team…

            Live antiX Boot Options (Previously posted by Xecure):
            https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

            #30551
            Forum Admin
            BitJam
              Helpful
              Up
              0
              ::

              Thank you BitJam for working on this so late at night. I was trying to add your github repo to list of repositories in synaptic to test (if you require me to test it at this point yet) but somehow synaptic did not include it. What spec should I use for this repo to be recognized by synaptic or is there another way?

              Whoops! Sorry. They are two different kinds of repos, a git repo versus a Debian based repo.

              If you have git installed, then you can get my entire git repo with:
              git clone https://github.com/BitJam/live-usb-maker
              as it says on the readme page. There is also a link to a tarball of the repo that you can download. The cool thing about git is that after you clone you can use the command “git pull” to update to the latest and greatest. If you plan to help with testing then I highly recommend you install git (if needed) and clone the two repos suggested in the readme:

              
              git clone https://github.com/BitJam/live-usb-maker
              git clone https://github.com/BitJam/cli-shell-utils

              When you do the two git clones in the same directory then the cloned live-usb-maker will automatically use the cloned cli-shell-utils library so this is and extremely fast and handy way to test my latest code. I can change things and you can get the changes very quickly. Often the longest part is me writing down what the change does and bumping the version number. This is much more alpha testing than beta testing.

              You can “git clone” from a directory. I’ve sometimes done this in /Live-usb-storage/root/ on a live-usb plugged into a host system so I’m testing the very latest code and I don’t have to set up a network connection on the target live-usb.

              I am so glad there is recognition of the importance of LUM by antiX team…

              I am so glad there is a recognition of its importance by some of our users! Which reminds me. If you want to help out with testing, it often makes sense to working on things are you interested in and familiar with. If you are always or mostly running live, there is a ton of live testing we could use. One thing I’d like to work on soon is a simple checklist of the various combinations that can be used mixing together things like:

              encrypted
              data-first (various file systems)
              toram
              live-remaster
              live-kernel-updater
              LUM clone
              ...

              The checklist would include the various combinations and perhaps simple paths to hit several items on the list in one series of tests.

              BTW: you can get my updates to my live system by cloning my live-initrd repo. If you do this then make sure you set “branch antiX-19” to get the latest (I should fix this). Let’s say it’s in the directory ../live-initrd, then I update a live-usb (plugged into my host system) with:
              sudo ./live-usb-maker --initrd=../live-initrd
              There is also a flag you can use to test for silly typos in the code. I almost always run live-usb-maker from my live-usb-maker repo which is why I call it with ./live-usb-maker. This means to use the local copy and not a copy found on the PATH.

              Context is worth 80 IQ points -- Alan Kay

              #30558
              Member
              olsztyn
                Helpful
                Up
                0
                ::

                This is much more alpha testing than beta testing.

                Understood. This redevelopment of LUM is significant and may take time.
                On my side this git development framework is quite new to me. Not familiar yet but I will try to figure this out soon, hopefully before I leave to Europe this Sunday for Christmas season. Considering short winter days (North part of Poland) I will have time to do testing from over there…
                Thanks to dexterous and efficient architecture of antiX the entire Live/eLive infrastructure of antiX (including persistence, LUM, remastering) sets antiX apart from other distros and deserves attention to make it solid and bulletproof…

                Live antiX Boot Options (Previously posted by Xecure):
                https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

                #30634
                Forum Admin
                anticapitalista
                  Helpful
                  Up
                  0
                  ::

                  @Bitjam

                  Latest lum fixed this issue here (using runit!)

                  Thanks

                  Should appear in repos soon.

                  Philosophers have interpreted the world in many ways; the point is to change it.

                  antiX with runit - leaner and meaner.

                  #30705
                  Forum Admin
                  BitJam
                    Helpful
                    Up
                    0
                    ::

                    Excellent!

                    Context is worth 80 IQ points -- Alan Kay

                  Viewing 8 posts - 16 through 23 (of 23 total)
                  • You must be logged in to reply to this topic.