MX Linux Forum

Support for MX and antiX Linux distros
http://www.forum.mxlinux.org/

persistence file load on boot fails :(

http://www.forum.mxlinux.org/viewtopic.php?t=81949

Page 1 of 1

persistence file load on boot fails :(

Posted: Thu Sep 12, 2024 4:32 am
by signaloss
hello friends,

my persistence file (rootfs?) on my usb drive doesnt get loaded into RAM while booting. it used to do that normally, suddenly it has failed. it will only let me poweroff or reboot. it says things like:

overlay on /live/aufs has failed. no data available.

also says things like:

failed to verify index ...
failed index directory cleanup
try deleting index directory mounting with '-o index=off' to disable inodes index.

please help as my un-snapshotted data is all on the persistence file :(

Code: Select all

Snapshot created on: 20240807_1532
System:    Kernel: 6.5.7-1-liquorix-amd64 [6.5-8~mx21+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: audit=0 intel_pstate=disable hpet=disable rcupdate.rcu_expedited=1 
           BOOT_IMAGE=/antiX/vmlinuz 
           Desktop: Xfce 4.18.1 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.18.0 vt: 7 
           dm: LightDM 1.26.0 Distro: swissix-21.3_x64 liquorix-kernel August 07  2024 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: AZW model: Speed S serial: <filter> UEFI: American Megatrends 
           v: 5.13 date: 02/18/2022 
CPU:       Info: Quad Core model: Intel Core i5-8279U bits: 64 type: MT MCP arch: Kaby Lake 
           note: check family: 6 model-id: 8E (142) stepping: A (10) microcode: E0 cache: 
           L2: 6 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 38400 
           Speed: 3201 MHz min/max: 400/2401 MHz boost: enabled Core speeds (MHz): 1: 3200 2: 3200 
           3: 3200 4: 3200 5: 1115 6: 700 7: 400 8: 1635 
           Vulnerabilities: Type: gather_data_sampling status: Vulnerable: No microcode 
           Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable 
           Type: retbleed mitigation: IBRS 
           Type: spec_rstack_overflow status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional, RSB filling, 
           PBRSB-eIBRS: Not affected 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel CoffeeLake-U GT3e [Iris Plus Graphics 655] driver: i915 v: kernel 
           bus-ID: 00:02.0 chip-ID: 8086:3ea5 class-ID: 0300 
           Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.18.0 driver: 
           loaded: modesetting unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") 
           s-diag: 583mm (23") 
           Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 142 size: 344x193mm (13.5x7.6") 
           diag: 394mm (15.5") 
           Monitor-2: HDMI-1 res: 1920x1080 hz: 60 dpi: 142 size: 344x193mm (13.5x7.6") 
           diag: 394mm (15.5") 
           OpenGL: renderer: Mesa Intel Iris Plus Graphics 655 (CFL GT3) v: 4.6 Mesa 22.0.5 
           direct render: Yes 
Audio:     Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel v: kernel 
           alternate: snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:9dc8 class-ID: 0403 
           Device-2: Generalplus USB Audio Device type: USB 
           driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-4.1:5 chip-ID: 1b3f:2007 
           class-ID: 0300 
           Device-3: KTMicro KT USB Audio type: USB driver: hid-generic,snd-usb-audio,usbhid 
           bus-ID: 1-5:4 chip-ID: 31b2:0010 class-ID: 0300 serial: <filter> 
           Sound Server-1: ALSA v: k6.5.7-1-liquorix-amd64 running: yes 
           Sound Server-2: PulseAudio v: 15.0 running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           v: kernel port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Wireless 3165 driver: iwlwifi v: kernel port: 3000 bus-ID: 02:00.0 
           chip-ID: 8086:3165 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 
           bus-ID: 1-9:6 chip-ID: 8087:0a2a class-ID: e001 
           Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2 
           sub-v: 1000 hci-v: 4.2 rev: 1000 
           Info: acl-mtu: 1021:5 sco-mtu: 96:6 link-policy: rswitch hold sniff 
           link-mode: slave accept 
           service-classes: rendering, capturing, object transfer, audio, telephony 
Drives:    Local Storage: total: 534.24 GiB used: 485.59 GiB (90.9%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKNW512G8 size: 476.94 GiB 
           block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD 
           serial: <filter> rev: 004C temp: 38.9 C scheme: GPT 
           ID-2: /dev/sda maj-min: 8:0 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 57.3 GiB 
           block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 
           scheme: MBR 
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -2 
           file: /live/boot-dev/swap-file 
Sensors:   System Temperatures: cpu: 51.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 2108 lib: 1058 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian/ bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free
           No active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
           Active apt repos in: /etc/apt/sources.list.d/liquorix.list 
           1: deb [arch=amd64 signed-by=/etc/apt/keyrings/liquorix-keyring.gpg] https://liquorix.net/debian bullseye main
           2: deb-src [arch=amd64 signed-by=/etc/apt/keyrings/liquorix-keyring.gpg] https://liquorix.net/debian bullseye main
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirrors.piconets.webwerks.in/mx-mirror/packages/mx/repo/ bullseye main non-free
           2: deb http://mirrors.piconets.webwerks.in/mx-mirror/packages/mx/repo/ bullseye ahs
           No active apt repos in: /etc/apt/sources.list.d/xanmod-release.list 
Info:      Processes: 263 Uptime: 18h 53m wakeups: 8 Memory: 15.53 GiB used: 2.55 GiB (16.4%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Client: shell wrapper v: 5.1.4-release inxi: 3.3.06 
Boot Mode: UEFI

Re: persistence file load on boot fails :(

Posted: Thu Sep 12, 2024 5:46 am
by fehlix
signaloss wrote: Thu Sep 12, 2024 4:32 am hello friends,

my persistence file (rootfs?) on my usb drive doesnt get loaded into RAM while booting. it used to do that normally, suddenly it has failed. it will only let me poweroff or reboot. it says things like:

overlay on /live/aufs has failed. no data available.

also says things like:

failed to verify index ...
failed index directory cleanup
try deleting index directory mounting with '-o index=off' to disable inodes index.

please help as my un-snapshotted data is all on the persistence file :(
Seems corrupted filesystem on the persistence file.
Maybe due to an uncontrolled shutdown/poweroff
You may try to sneak into the rootfs persistence file,
e.g. with help of MX Remaster Controle Center -> Persistence tab
and select Exploration -> rootfs.
This will (try) to mount rootfs-file. in case it opens,
you can try to manually copy data from underneath the "upper" directory.
E,g to the Live-usb-storage folder within home-directory.
The Live-usb-storage folder is "bind mounted" on the USB,
where you can access the data directly from outside the Live-booted system.
If that works remove/rename rootfs, so it will ask next time to re-create a new rootfs.
+++EDIT+++
After you have save/copied data, you may also try to
repair the filesystem on rootfs, with the build-in option provided by the live system:
Do add to the live-boot parameter the option

Code: Select all

checkfs
in addition to the normal persistence option you use.
The boot option "checkfs" is also available within the"Boot Options" submenu under Advanced options.
The checkfs option tries the run a repairing ext4-fsck, and may help to restore/repair the filesystem issues.

Re: persistence file load on boot fails :(

Posted: Wed Sep 18, 2024 3:06 am
by signaloss
thank you that worked :)

but sometimes the files are like character files with 0 size and so on. i was able to copy my data but i didnt understand why this was so.

thanks anyway.

Re: persistence file load on boot fails :(

Posted: Wed Sep 18, 2024 5:51 am
by fehlix
signaloss wrote: Wed Sep 18, 2024 3:06 am thank you that worked :)
And what was it what worked?
So you managed to repair the filesystem?
signaloss wrote: Wed Sep 18, 2024 3:06 am but sometimes the files are like character files with 0 size and so on. i was able to copy my data but i didnt understand why this was so.
WHen you have all you data, and you won't be able to repair, perhaps remove/rename to persistence rootfs-file on the USB-stick.
And start with fresh persistence.
All times are UTC-04:00
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited