[Solved] Struggling with persist_home (AntiX-22_386_full)

Forum Forums Official Releases antiX-21/22 “Grup Yorum” [Solved] Struggling with persist_home (AntiX-22_386_full)

  • This topic has 3 replies, 3 voices, and was last updated Nov 13-3:30 am by mcpderez.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #93131
    Member
    mcpderez

      Perhaps I’m misunderstanding how this is supposed to work. I’ve searched the forum, read several threads and watched dolphinoracle’s video from AntiX-17 linked in the FAQ, but I might just have a wrong impression of how home persistence is set up.

      Testing with my IBM ThinkPad T42 today, booting from a flash drive burned with AntiX-22_386_full.iso.
      At the boot screen I use the function keys to select my Time Zone (F3), Persistence as persist_home (F5), and Console as 1024×768 (F7), then Enter to boot.

      I thought that I would be prompted to configure the size of a home persistence file, but instead what happens is I see a few blank lines below “found boot device” and then:

      Look for persist device with label antiX-Persist

      The screen clears and I see:

      Could not find a partition with label antiX-Persist
      
      Please wait while existing partitions are found ...
      
      No suitable devices were found.
      Press <Enter> to continue

      I press Enter, the screen clears, returns to the antiX 22 (Grup Yorum) boot screen, this time it is at the run live scripts stage and again says:
      Look for persist device with label antiX-Persist

      I looked in /var/log/live/initrd.log and it appears that persistence is being disabled because the USB drive is being considered read-only. I tried making it with both Balena Etcher and with dd and I get the same result. Is there some intermediate step I need to take between burning the drive and booting from it, is this a fault with the iso, or does it just not work how I expected it would?

      /var/log/live/initrd.log:

      Run custom code before reading boot codes: /live/custom/antiX/0.sh
      Width of screen in pixels 984
      Try to set line length to 120
      Using size 8
      Set font to Uni2-TerminusBold16
      setfont /live/locale/fonts/Uni2-TerminusBold16.psf -C /dev/console
      New screen width 128
      @ 1.30 starting tsplash
      === initrd bootstrap ==================================================
      initrd init started at 0.06 seconds
      Welcome to antiX 22 (Grup Yorum) 32-bit!
        BusyBox v1.31.1 (2021-02-03 15:54:12 MST) multi-call binary.
        ntfs-3g 2017.3.23AR.3 integrated FUSE 28
                 initrd version: 8.30.14-x08
                   initrd built: Fri, 04 Jun 2021 11:43:21 +0000
                   Total Memory:   493 M
                    Used Memory:    35 M
                   Linux kernel: 4.9.0-326-antix.1-486-smp
                   Screen width: 128
                    Kernel arch: i686
                       Hardware: IBM 2373H12
      Current boot codes:
           vga=791 persist_home tz=America/Chicago quiet splasht disable=lxF
      Found overlay
      Loading hardware specific modules ...
      Scan usb,cd devices.  Look for boot file(s) antiX/linuxfs
      Filtered devices  /dev/sr0
      Retry for 15 seconds .
      Found new device(s) /dev/sda2 /dev/sda1 /dev/sda /dev/sr0
      mount -t vfat -o umask=000,dmask=002,fmask=113,shortname=winnt,uid=1000,gid=1000 /dev/sda2 /live/boot-dev
      mount -t iso9660 -o ro /dev/sda1 /live/boot-dev
      Mounted boot device. Mounted device /dev/sda1 at /live/boot-dev
      boot device filesystem: iso9660
      boot device model: USB Flash Disk
      Spent 1.65 seconds looking for boot file(s) antiX/linuxfs
      loop times: 0.15
      BOOT_MP:    /live/boot-dev
      SQFILE_DEV: /dev/sda1
      SQFILE_MP   /live/boot-dev
      Initializing random number generator ...
      Mount file /live/boot-dev/antiX/linuxfs at /live/linux
      mount -t squashfs -o loop,ro /live/boot-dev/antiX/linuxfs /live/linux
      sqfs_vid: === 0c8833e2fdf15aca1a9fa6ad6a57081d
      Updating grub config to 2.0
      Using BIOS UUID: 
      LD_PATH: /live/linux/lib:/live/linux/lib/i386-linux-gnu:/live/linux/usr/lib
      
      Persistence was requested on a read-only boot device
      Will search for a persistence device with the label antiX-Persist
      
      ----------------------------------------------------------------------
      Begin Mount persistence device (if needed)
      Look for persist device with label antiX-Persist
      Retry for 10 seconds ...................
      Spent 10.74 seconds looking for persist file(s) antiX/homefs.new antiX/homefs
      loop times: 0.18 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17 0.17
      tsplash clear
      
      Could not find a partition with label antiX-Persist
      
      Please wait while existing partitions are found ...
      mount -t vfat -o umask=000,dmask=002,fmask=113,shortname=winnt,uid=1000,gid=1000 /dev/sda2 /tmp/mnt
      No suitable devices were found.
      Press <Enter> to continue
      Disable persistence
      tsplash on
      Loaded 10 module(s)
      nls_utf8 nls_cp437 uas usb_storage shpchp dm_crypt dm_mod overlay battery fotg210_hcd
      Create aufs ram tmpfs at /live/aufs-ram       (366 MB)
      /bin/mount -t tmpfs -o size=366m,noatime tmpfs /live/aufs-ram
      Mount overlayfs at /live/aufs
      mount -t overlay overlay -o lowerdir=/live/linux,upperdir=/live/aufs-ram/upper,workdir=/live/aufs-ram/work /live/aufs
      Load microcode
      Found one video display device
      Create   /media tmpfs at /live/aufs/media     (10 MB)
      /bin/mount -t tmpfs -o size=10m,noatime tmpfs /live/aufs/media
      Create     /run tmpfs at /live/aufs/run       (1111 MB)
      /bin/mount -t tmpfs -o size=1111m,mode=755,nodev,noatime tmpfs /live/aufs/run
      Create    /live tmpfs at /live/aufs/live      (100 MB)
      /bin/mount -t tmpfs -o size=100m,mode=755,noatime tmpfs /live/aufs/live
      Run custom code before: /live/custom/antiX/0.sh
      mount --move /live/aufs-ram /live/aufs/live/aufs-ram
      mount --move /live/boot-dev /live/aufs/live/boot-dev
      mount --move /live/linux /live/aufs/live/linux
      Run custom code after: /live/custom/antiX/0.sh
      Run custom code before running live init.d scripts: /live/custom/antiX/8.sh
      
      The initrd init program took 24.23 seconds
      ======================================================================
      cp /live/config/tsplash/progress /live/aufs/live/config/tsplash/progress
      cp /live/config/tsplash/tsplash.log /live/aufs/live/config/tsplash/tsplash.log

      inxi -Fxz:

      System:
        Kernel: 4.9.0-326-antix.1-486-smp arch: i686 bits: 32 compiler: gcc
          v: 10.2.1 Desktop: IceWM v: 3.0.1
          Distro: antiX-22_386-full Grup Yorum 18 October 2022
          base: Debian GNU/Linux 11 (bullseye)
      Machine:
        Type: Laptop System: IBM product: 2373H12 v: ThinkPad T42
          serial: <superuser required>
        Mobo: IBM model: 2373H12 serial: <superuser required> BIOS: IBM
          v: 1RETDOWW (3.20 ) date: 02/27/2006
      Battery:
        ID-1: BAT0 charge: 9.8 Wh (100.0%) condition: 9.8/47.5 Wh (20.7%)
          volts: 11.9 min: 10.8 model: SANYO IBM-08K8193 status: full
      CPU:
        Info: single core model: Intel Pentium M bits: 32 arch: M Banias rev: 5
          cache: 1024 KiB note: check
        Speed (MHz): 1000 min/max: 600/1500 core: 1: 1000 bogomips: 1998
        Flags: sse sse2
      Graphics:
        Device-1: AMD RV200/M7 [Mobility Radeon 7500]
          vendor: IBM ThinkPad T4x Series driver: radeon v: kernel arch: Rage 7
          bus-ID: 01:00.0
        Display: server: X.Org v: 1.20.11 driver: X: loaded: radeon
          unloaded: fbdev,modesetting,vesa gpu: radeon resolution: 1024x768~60Hz
        OpenGL: renderer: Mesa DRI R100 (RV200 4C57) x86/MMX/SSE2 DRI2
          v: 1.3 Mesa 20.3.5 direct render: Yes
      Audio:
        Device-1: Intel 82801DB/DBL/DBM AC97 Audio vendor: IBM ThinkPad T4x Series
          driver: snd_intel8x0 v: kernel bus-ID: 00:1f.5
        Sound Server-1: ALSA v: k4.9.0-326-antix.1-486-smp running: yes
      Network:
        Device-1: Intel 82540EP Gigabit Ethernet vendor: IBM Thinkpad driver: e1000
          v: 7.3.21-k8-NAPI port: 8000 bus-ID: 02:01.0
        IF: eth0 state: down mac: <filter>
        Device-2: Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter driver: ipw2100
          v: git-1.2.2 bus-ID: 02:02.0
        IF: eth1 state: down mac: <filter>
        IF-ID-1: irda0 state: down mac: <filter>
      Drives:
        Local Storage: total: 71.85 GiB used: 5.7 MiB (0.0%)
        ID-1: /dev/sda type: USB model: General USB Flash Disk size: 14.55 GiB
        ID-2: /dev/sdb type: USB vendor: SanDisk model: USB 3.2Gen1
          size: 57.3 GiB
      Partition:
        Message: No partition data found.
      Swap:
        Alert: No swap data was found.
      Sensors:
        System Temperatures: cpu: 41.0 C mobo: 36.0 C
        Fan Speeds (RPM): fan-1: 0
      Info:
        Processes: 124 Uptime: 10m Memory: 493.2 MiB used: 122.9 MiB (24.9%)
        Init: SysVinit runlevel: 5 Compilers: gcc: 10.2.1 Packages: 1563
        Shell: Bash v: 5.1.4 inxi: 3.3.19

      Note the flash disk in /dev/sdb was not connected during my tests. I was just using it to get the initrd.log and inxi output over to a machine with network access since I’m having issues getting on wifi with the Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter built-in to the ThinkPad.

      • This topic was modified 5 months, 3 weeks ago by mcpderez.
      #93132
      Moderator
      BobC
        Helpful
        Up
        0
        ::

        I think you need to boot from your dd or balena flashdrive with antiX and then use Live USB Maker to burn a normal antiX flashdrive. When you boot from that one, it should have the persistence options.

        #93133
        Moderator
        christophe
          Helpful
          Up
          0
          ::

          Is there some intermediate step I need to take between burning the drive and booting from it, is this a fault with the iso, or does it just not work how I expected it would?

          This is expected behavior. antiX sets up the live-usb to be read/write, unlike dd, etc. To get a live-usb with persistence (which is fully-functional, upgradable, etc.), do as BobC wrote:

          boot from your dd or balena flashdrive with antiX

          then use Live USB Maker to burn a normal antiX flashdrive. When you boot from that one, it [will] have the persistence options.

          confirmed antiX frugaler, since 2019

          #93135
          Member
          mcpderez
            Helpful
            Up
            0
            ::

            Thanks! That did it. I couldn’t fit two flash drives I was willing to overwrite in the tightly spaced ports, so I had to use a VM to boot the iso on a different computer and start live-usb-maker to create the drive. I was not successful in finding a way to use just one flash drive on the T42 with only 512MB of RAM. Either I could load an AntiX 17.5 core toram so it would see the flash drive as writable (but then not see a live image to use) or I could boot from the flash drive and then not be able to write to it.

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