live-remaster error: persistence device not found

Forum › Forums › New users › New Users and General Questions › live-remaster error: persistence device not found

  • This topic has 9 replies, 3 voices, and was last updated Jan 10-6:56 pm by Brian Masinick.
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #96257
    Anonymous

      On an antiX-22-core LiveUSB I have this situation:

      
      >>> # live-remaster
      
      antiX Live Remaster
      live-remaster error :
      The persistence device with UUID fe57[...]c19f was not found
      Please plug in the persistence device and try again
      

      However lsblk clearly shows this device. It is sdb3, with ext4, labeled antiX-persist, UUID fe57[…]c19f, sized 13.5G, used 0% and mounted at /live/persist-dev.
      What am I doing wrong?

      #99458
      Anonymous

        To answer my own question, it seems I was wrong to attempt remaster on a LiveUSB generated just by dd-ing the antiX .iso onto the USB drive. After I created another LiveUSB through the make-live-usb script supplied by antiX, I no longer had any issues.

        #99464
        Brian Masinick
        Moderator

          To answer my own question, it seems I was wrong to attempt remaster on a LiveUSB generated just by dd-ing the antiX .iso onto the USB drive. After I created another LiveUSB through the make-live-usb script supplied by antiX, I no longer had any issues.

          You “can” create a USB read only image using dd. Typically it will require root/system privileged access. Perhaps that was one issue. Input and output specifications have to be precise too. Generally use only the USB device name, such as /dev/sda and do not include a number.

          --
          Brian Masinick
          Alternate "Search B":
          This search page

          #99465
          Brian Masinick
          Moderator

            You’re right that Live USB Maker is easier and it helps avoid unnecessary errors in most common scenarios.

            --
            Brian Masinick
            Alternate "Search B":
            This search page

            #193741
            tlaloc77
            Member

              Jumping in here because I get the same error but I did use the Live USB Maker.

              root@antix1:~# lsblk –fs /dev/sdc
              NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
              sdc
              ├─sdc1 ext4 1.0 antiX-Live-usb de1a2203-0ac6-4399-8f88-b8d5f87fce8e 21.1G 27% /home/demo/Live-usb-storage
              │ /root/Live-usb-storage
              │ /live/boot-dev
              └─sdc2 vfat FAT32 ANTIX-UEFI 8C1E-E731 35.9M 26% /media/ANTIX-UEFI
              root@antix1:~# mount | grep /dev/sdc1
              /dev/sdc1 on /live/boot-dev type ext4 (rw,noatime)
              /dev/sdc1 on /root/Live-usb-storage type ext4 (rw,noatime)
              /dev/sdc1 on /home/demo/Live-usb-storage type ext4 (rw,noatime)
              root@antix1:~#

              • This reply was modified 8 months, 2 weeks ago by tlaloc77.
              #193747
              tlaloc77
              Member

                Is there a way to delete an uploaded screenshot?

                That aside, what’s on here?

                I booted an old antiX 23.2 from an USB stick, then used the Live USB Maker to clone the running system to a 2nd stick, did a shutdown, removed the 1st stick and then booted from the 2nd. Persistence was and is set to “p_static_root”. Then I started synaptic and made a bunch of updates in several steps “by hand”, once that was done, I ran the antiX Updater which reported that my system was up-to-date. Yay so far.
                Then I tried to use “Set Up Life Persistence” from the Control Centre and got the error above – even though the device exist and is mounted r/w.

                What am I missing and how can I save the state of the system to the stick?

                —-

                Also, “Set Up Life Persistence” asks for the “administrative password” (root’s PW) every time, shouldn’t it remember it? I tried both “save for this session” and “save in the keyring”, it still asks every time. Maybe that’s a hint?

                • This reply was modified 8 months, 2 weeks ago by tlaloc77.
                #193749
                Brian Masinick
                Moderator

                  The only thing you have to do when you update an already created image with Live USB Maker after making changes is to run
                  sudo live-remaster. I’ve been doing that for the past several days. If you do not do so, when you reboot your image will revert to whatever it was when you created it, so the live-remaster tool is what saves any alterations and it has to be performed each time you make changes, just before you shutdown or reboot; then you’ll get the results you are looking for. You already created the system to be persistent, but persistence alone does not include changes; persistence includes what you originally created.

                  --
                  Brian Masinick
                  Alternate "Search B":
                  This search page

                  #193755
                  tlaloc77
                  Member

                    Hmm, trying:

                    demo@antix1:~
                    $ sudo life-remaster
                    sudo: life-remaster: command not found
                    demo@antix1:~

                    But typing “li<tab>” as demo shows me a bunch of commands, and life-remaster is among them.
                    It works when I do sudo su - and then life-remaster

                    Thank you very much! It’s running now… done, “mksquashfs took 7:21 mm:ss” (with lz4)

                    (I tried to run “Remaster-Customize Life” from the Control Centre, before I came here to ask for help because I also got the error “persistence device … not found” and then I thought I needed to create a persistence file first, again via the control centre.)

                    The issue with the password being asked over and over and that I need to do “sudo su -” first instead of “sudo life-remaster” directly feels off, maybe I should start over and not clone the running system, what do you think?

                    BRB, rebooting…

                    #193757
                    tlaloc77
                    Member

                      It worked! Thanks again, Brian Masinick – problem solved an I learned something 🙂

                      • This reply was modified 8 months, 2 weeks ago by tlaloc77.
                      #193760
                      Brian Masinick
                      Moderator

                        I hope you eventually entered sudo live-remaster rather than life-remaster! 🙂

                        --
                        Brian Masinick
                        Alternate "Search B":
                        This search page

                      Viewing 10 posts - 1 through 10 (of 10 total)
                      • You must be logged in to reply to this topic.