Mounting overlay failed: No data available [Solved]

[Discostu]

When booting my persistent live USB system, I was greeted with errors:

Code: Select all

Error: find: /dev/usb: no such file or directory
Error: find: /dev/hidraw2: No such file or directory
Error: find: /dev/hidraw0: No such file or directory

And later, after decrypting the drive:

Code: Select all

Error: mount: mounting overlay on /live/aufs failed: No data available

I searched the forum and found a suggestion by @fehlix to add this parameter to grub;

Code: Select all

overlay.index=0

It did help but this leaves me with two questions:
- What might have been the reason for the error and how can I prevent it from happening again?
- What does that parameter do? Should I always use it or only in case of error?

Code: Select all

Snapshot created on: 20241015_2100
System:
  Kernel: 6.11.4-1-liquorix-amd64 [6.11-7.1~bookworm] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
    intel_pstate=disable BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash lang=de_DE kbd=de
    tz=Europe/Berlin persist_all splasht= overlay.index=0
  Desktop: KDE Plasma v: 5.27.5 wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.4_x64 Libretto October
    15 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: HP product: HP Laptop 15-fc0xxx v: N/A serial: <superuser required> Chassis:
    type: 10 serial: <superuser required>
  Mobo: HP model: 8B2F v: 52.40 serial: <superuser required> UEFI: AMI v: F.07 date: 03/13/2023
Battery:
  ID-1: BAT0 charge: 23.5 Wh (63.7%) condition: 36.9/36.9 Wh (100.0%) volts: 11.1 min: 11.2
    model: HP Primary type: Li-ion serial: <filter> status: discharging cycles: 91
CPU:
  Info: model: AMD Ryzen 5 7520U with Radeon Graphics bits: 64 type: MT MCP arch: Zen 2 gen: 3
    level: v3 note: check built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23)
    model-id: 0xA0 (160) stepping: 0 microcode: 0x8A00006
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 663 high: 1512 min/max: 400/4384 boost: enabled scaling:
    driver: amd-pstate-epp governor: performance cores: 1: 1512 2: 400 3: 400 4: 400 5: 1397 6: 400
    7: 400 8: 400 bogomips: 44715
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP protection
  Type: spec_rstack_overflow mitigation: Safe RET
  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: Retpolines; IBPB: conditional; STIBP: always-on; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Mendocino vendor: Hewlett-Packard driver: amdgpu v: kernel arch: RDNA-2
    code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, Writeback-1 bus-ID: 03:00.0 chip-ID: 1002:1506
    class-ID: 0300 temp: 45.0 C
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: eDP-1 mapped: eDP model: ChiMei InnoLux 0x153b built: 2020 res: 1920x1080 hz: 60
    dpi: 142 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6 Mesa 24.2.2-1~mx23ahs renderer: AMD Radeon 610M (radeonsi raphael_mendocino
    LLVM 15.0.6 DRM 3.59 6.11.4-1-liquorix-amd64) direct-render: Yes
Audio:
  Device-1: AMD Rembrandt Radeon High Definition Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.1
    chip-ID: 1002:1640 class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Hewlett-Packard driver: snd_pci_acp6x
    v: kernel alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_acp_pci,
    snd_rpl_pci_acp6x, snd_pci_ps, snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh,
    snd_sof_amd_acp63 pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.5 chip-ID: 1022:15e2
    class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 03:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.11.4-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek vendor: Hewlett-Packard driver: rtw89_8852be v: kernel modules: wl pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 02:00.0 chip-ID: 10ec:b85b class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-2:2 chip-ID: 0bda:b85d
    class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter>
  Info: acl-mtu: 1021:6 sco-mtu: 255:12 link-policy: rswitch hold sniff park
    link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
    telephony
Drives:
  Local Storage: total: 592.63 GiB used: 17.29 GiB (2.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WD PC SN740 SDDPNQD-512G-1006
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: HPS3 temp: 33.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 type: USB vendor: SanDisk model: Ultra USB 3.0 size: 115.69 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?
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2
    file: /live/boot-dev/swap-file
Sensors:
  System Temperatures: cpu: 51.2 C mobo: N/A gpu: amdgpu temp: 46.0 C
  Fan Speeds (RPM): fan-1: 2998 fan-2: 0
Repos:
  Packages: pm: dpkg pkgs: 2556 libs: 1377 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
    pm: flatpak pkgs: 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 bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm main non-free
    2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm ahs
Info:
  Processes: 288 Uptime: 17m wakeups: 27222 Memory: 14.88 GiB used: 4.68 GiB (31.4%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

[Discostu]

- What does that parameter do? Should I always use it or only in case of error?

Ok, problem reappears without the parameter. So what should I do?

[fehlix]

- What does that parameter do? Should I always use it or only in case of error?

Ok, problem reappears without the parameter. So what should I do?

Either keep the parameter preset, or try non-liquorix kernel, which seem not have the issue (I think).
You can read about overlayfs here at kernel.org:
Overlay Filesystem
IMHO, don't see a need to have it enabled within the livesystem.

[Discostu]

Either keep the parameter preset, or try non-liquorix kernel, which seem not have the issue (I think).

How can I keep it, using the live system, without needing to add it manually on each boot?

[fehlix]

Either keep the parameter preset, or try non-liquorix kernel, which seem not have the issue (I think).

How can I keep it, using the live system, without needing to add it manually on each boot?

On a writable Livesystem, the live boot options can be "saved", with live-boot parameter "grubsave" boot option
available within LiveGRUB submenu Advanced->Save Options -> grubsave...
Save parameter get stored int /boot/grub/grubenv.cfg file - on the LiveUSB - which is an ini-like file.
The LiveGRUB menu is available on both UEFI and BIOS boot.
E.g. this is what get saved on my LiveUSB boot:

Code: Select all

#GRUB parameter saved on live system by live-grubsave (version "230518-01")
#saved on: Thu Oct 24 21:07:53 CEST 2024
#[/dev/sda1] @ /live/boot-dev/boot/grub/grubenv.cfg
kbd="de"
kernel="vmlinuz"
lang="en_US"
live_swap="off"
splasht=""
toram="toram"
tz="Europe/Berlin"
extra="module_blacklist=floppy overlay.index=0 hostname=mx234ahs"

where you find the overlay.index=0 within the extra= field.

In case BIOS syslinux LiveBoot menu you can try F8-save options, which may also save the overlay options.
Or use gfxsave from the LiveGRUB menu, which will also "inject" the boot parameter into the Gfx/Syslinux boot menu.

[Discostu]

On a writable Livesystem, the live boot options can be "saved", with live-boot parameter "grubsave" boot option
available within LiveGRUB submenu Advanced->Save Options -> grubsave...

I know but I didn't find a way in the UEFI LiveGRUB to leave the editing window to save the configuration including the parameter. There seem only to be options to boot directly (without saving) or to abort (also without saving).

Save parameter get stored int /boot/grub/grubenv.cfg file - on the LiveUSB - which is an ini-like file.

Can I just edit the file when booted or will that break things?

[Discostu]

But maybe the easier solution is to switch to Debian 6.11 and hope for the best?

[fehlix]

On a writable Livesystem, the live boot options can be "saved", with live-boot parameter "grubsave" boot option
available within LiveGRUB submenu Advanced->Save Options -> grubsave...

I know but I didn't find a way in the UEFI LiveGRUB to leave the editing window to save the configuration including the parameter. There seem only to be options to boot directly (without saving) or to abort (also without saving).

You either select from the options menu or when done add just before boot the missing parameter to the end of the first line, make sure you also have grubsave within that line to get thos saved. and press Ctrl+x or F10 to boot.

Save parameter get stored int /boot/grub/grubenv.cfg file - on the LiveUSB - which is an ini-like file.

Can I just edit the file when booted or will that break things?

Yes, you can manually add stuff-
But it's simpler to run from booted system "live-grubsave":
e.g. this will show currently saved paramter:

Code: Select all

sudo  live-grubsave -p

This will simulate

Code: Select all

sudo  live-grubsave -s

E.g this will add to the curretly used parameter an extra-linie, but overwrite an existing extra= line:

Code: Select all

sudo  live-grubsave extra="overlay.index=0"

actually just tested this will also work:

Code: Select all

sudo  live-grubsave overlay.index=0

b/c it recognize all non-supported (=not shown in the menu) and will add those to the extra-line.

Or if you have already some parameter within extra=,
this will add to existing extra field the paramter overlay.index=0

Code: Select all

sudo  live-grubsave extra+="overlay.index=0"

help with

Code: Select all

sudo  live-grubsave --help

[fehlix]

But maybe the easier solution is to switch to Debian 6.11 and hope for the best?

You can always try other kernels which do not have overlay index enabled.

[Discostu]

You either select from the options menu or when done add just before boot the missing parameter to the end of the first line, make sure you also have grubsave within that line to get thos saved. and press Ctrl+x or F10 to boot.

Thank you, adding

Code: Select all

overlay.index=0 grubsave

to the end of the first line and pressing F10 worked well.

Thank you also for the other options on how to edit it from the command line.