MX Linux Forum

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

QSI: no partition data found

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

Page 1 of 1

QSI: no partition data found

Posted: Mon Jul 15, 2024 11:54 am
by thomasl
Apparently, this bit of the QSI is not as expected:

Code: Select all

Partition:
  Message: No partition data found.
I've seen the same message in other QSIs recently from a variety of different PCs.

There's no problem, malfunction or trouble spot that I am aware of. In fact, I very rarely look into the QSI.

Code: Select all

Snapshot created on: 20240213_1535
System:
  Kernel: 6.1.0-18-amd64 [6.1.76-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/MX23/vmlinuz quiet checkfs loglevel=0 hostname=makalu from=hd bdir=MX23
    persist=root!,home! toram=min rootdelay=1
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.32.0 Distro: MX-23.3_x64 Libretto February 16  2024 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Laptop System: LENOVO product: 20U6S3EG00 v: ThinkPad L14 Gen 1
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: LENOVO model: 20U6S3EG00 v: SDK0J40697 WIN serial: <superuser required> UEFI: LENOVO
    v: R19ET36W (1.20 ) date: 07/12/2021
Battery:
  ID-1: BAT0 charge: 42.6 Wh (95.3%) condition: 44.7/45.3 Wh (98.6%) volts: 12.2 min: 11.1
    model: SMP LNV-5B10W13895 type: Li-poly serial: <filter> status: not charging cycles: 10
CPU:
  Info: model: AMD Ryzen 5 PRO 4650U 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: 0x60 (96)
    stepping: 1 microcode: 0x8600106
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB
    desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 8 MiB desc: 2x4 MiB
  Speed (MHz): avg: 1397 high: 1400 min/max: 1400/2100 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 1397 2: 1400 3: 1397 4: 1384 5: 1396 6: 1397
    7: 1400 8: 1397 9: 1400 10: 1400 11: 1400 12: 1400 bogomips: 50306
  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: 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
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Renoir vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 code: Vega
    process: GF 14nm built: 2017-20 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1
    off: eDP-1 empty: DP-1,DP-2 bus-ID: 06:00.0 chip-ID: 1002:1636 class-ID: 0300 temp: 45.0 C
  Device-2: Bison Integrated Camera driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
    mode: 2.0 bus-ID: 3-3:3 chip-ID: 5986:212b class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 508x318mm (20.00x12.52") s-diag: 599mm (23.6")
  Monitor-1: HDMI-A-1 mapped: HDMI-A-0 pos: primary model: Idek Iiyama PLE2607WSD
    serial: <filter> built: 2010 res: 1920x1200 hz: 60 dpi: 89 gamma: 1.2
    size: 550x344mm (21.65x13.54") diag: 649mm (25.5") ratio: 16:10 modes: max: 1920x1200
    min: 720x400
  Monitor-2: eDP-1 mapped: eDP note: disabled model: ChiMei InnoLux 0x14d4 built: 2016
    res: 1920x1200 dpi: 158 gamma: 1.2 size: 309x173mm (12.17x6.81") diag: 354mm (13.9") ratio: 16:9
    modes: max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon Graphics (renoir LLVM 15.0.6 DRM 3.49
    6.1.0-18-amd64) direct-render: Yes
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 06:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo driver: N/A
    alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x, snd_pci_acp6x pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 06:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel pcie:
    gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 06:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.1.0-18-amd64 status: kernel-api tools: alsactl,alsamixer,amixer
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Lenovo driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 2400 bus-ID: 02:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eth0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
    bus-ID: 03:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  IF-ID-1: vboxnet0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1
    mode: 1.1 bus-ID: 3-4:5 chip-ID: 8087:0029 class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 2 state: down bt-service: N/A rfk-block: hardware: no
    software: no address: <filter>
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
Drives:
  Local Storage: total: 1.18 TiB used: 511.27 GiB (42.1%)
  ID-1: /dev/mmcblk0 maj-min: 179:0 vendor: SanDisk model: SD64G size: 57.95 GiB block-size:
    physical: 512 B logical: 512 B tech: SSD serial: <filter> scheme: MBR
  SMART Message: Unknown smartctl error. Unable to generate data.
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-2: /dev/nvme0n1 maj-min: 259:0 vendor: Crucial model: CT1000P3SSD8 size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: P9CR30A temp: 36.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: SanDisk model: SDSSDA240G size: 223.57 GiB block-size:
    physical: 4096 B logical: 512 B type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
    tech: SSD serial: <filter> fw-rev: 3202 scheme: MBR
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 4 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 1024 MiB used: 0 KiB (0.0%) priority: -2
    file: /live/boot-dev/Live-usb-storage/root/swapfile2
Sensors:
  System Temperatures: cpu: 67.0 C mobo: N/A gpu: amdgpu temp: 46.0 C
  Fan Speeds (RPM): fan-1: 0
Repos:
  Packages: pm: dpkg pkgs: 1885 libs: 961 tools: apt,apt-get,aptitude 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://mxrepo.com/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
    1: deb [arch=amd64] https://repo.vivaldi.com/stable/deb/ stable main
Info:
  Processes: 327 Uptime: 1h 46m wakeups: 39 Memory: total: 24 GiB note: est. available: 22.84 GiB
  used: 8.46 GiB (37.0%) 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.28
Boot Mode: UEFI

Re: QSI: no partition data found

Posted: Mon Jul 15, 2024 12:28 pm
by dolphin_oracle
doesn't necessarily surprise me running live.

Re: QSI: no partition data found

Posted: Mon Jul 15, 2024 1:22 pm
by thomasl
Thanks, DO. So if booting live/frugal, contrary to what @m_pav implied here, this is supposedly normal?

If so, perhaps this factlet should be general knowledge.

Re: QSI: no partition data found

Posted: Mon Jul 15, 2024 2:41 pm
by fehlix
thomasl wrote: Mon Jul 15, 2024 11:54 am Apparently, this bit of the QSI is not as expected:

Code: Select all

Partition:
  Message: No partition data found.
Perhaps, explain what you would expected, or with other words, suggest what you want to see in regards to partitions.
B/c there are different views with different expectations, like all partions, only mounted, only those in fstab etc ppp

Re: QSI: no partition data found

Posted: Mon Jul 15, 2024 3:40 pm
by dolphin_oracle
fehlix wrote: Mon Jul 15, 2024 2:41 pm
thomasl wrote: Mon Jul 15, 2024 11:54 am Apparently, this bit of the QSI is not as expected:

Code: Select all

Partition:
  Message: No partition data found.
Perhaps, explain what you would expected, or with other words, suggest what you want to see in regards to partitions.
B/c there are different views with different expectations, like all partions, only mounted, only those in fstab etc ppp
inxi usually shows the home and root partitions.

Re: QSI: no partition data found

Posted: Mon Jul 15, 2024 3:49 pm
by fehlix
dolphin_oracle wrote: Mon Jul 15, 2024 3:40 pm
fehlix wrote: Mon Jul 15, 2024 2:41 pm
thomasl wrote: Mon Jul 15, 2024 11:54 am Apparently, this bit of the QSI is not as expected:

Code: Select all

Partition:
  Message: No partition data found.
Perhaps, explain what you would expected, or with other words, suggest what you want to see in regards to partitions.
B/c there are different views with different expectations, like all partions, only mounted, only those in fstab etc ppp
inxi usually shows the home and root partitions.
depends on "usually" meaning:
QSI is using these inxi options:
-Fxxxra
where -F includes -P, which man inxi reports as:

Code: Select all

-P , --partitions

      Show  basic  Partition  information.   Shows, if detected: / 
      /boot /boot/efi /home /opt /tmp /usr /usr/home /var /var/tmp 
      /var/log (for android, shows /cache /data /firmware /system).  If 
      --swap is not used, shows active swap partitions (never shows 
      file or zram type swap). Use -p to see all mounted partitions.

      To show partition labels or UUIDs (when available and relevant), 
      use with -l or -u.
in contrast to full partition list with "-p"

Code: Select all

-p , --partitions-full

      Show full Partition information (-P plus all other detected 
      mounted partitions).

      To show partition labels or UUIDs (when available and relevant), 
      use with -l or -u.

Re: QSI: no partition data found

Posted: Mon Jul 15, 2024 4:14 pm
by dolphin_oracle
fehlix wrote: Mon Jul 15, 2024 3:49 pm
dolphin_oracle wrote: Mon Jul 15, 2024 3:40 pm
fehlix wrote: Mon Jul 15, 2024 2:41 pm Perhaps, explain what you would expected, or with other words, suggest what you want to see in regards to partitions.
B/c there are different views with different expectations, like all partions, only mounted, only those in fstab etc ppp
inxi usually shows the home and root partitions.
depends on "usually" meaning:
QSI is using these inxi options:
-Fxxxra
where -F includes -P, which man inxi reports as:

Code: Select all

-P , --partitions

      Show  basic  Partition  information.   Shows, if detected: / 
      /boot /boot/efi /home /opt /tmp /usr /usr/home /var /var/tmp 
      /var/log (for android, shows /cache /data /firmware /system).  If 
      --swap is not used, shows active swap partitions (never shows 
      file or zram type swap). Use -p to see all mounted partitions.

      To show partition labels or UUIDs (when available and relevant), 
      use with -l or -u.
in contrast to full partition list with "-p"

Code: Select all

-p , --partitions-full

      Show full Partition information (-P plus all other detected 
      mounted partitions).

      To show partition labels or UUIDs (when available and relevant), 
      use with -l or -u.
ok in this instance, the stuff qsi usually displays on an installed system

Re: QSI: no partition data found

Posted: Mon Jul 15, 2024 4:48 pm
by fehlix
dolphin_oracle wrote: Mon Jul 15, 2024 4:14 pm ok in this instance, the stuff qsi usually displays on an installed system
And we should probably keep "-P"/"--partitions" (within "-Z") as default, to avoid
seeing all users or other mounts.
Maybe an option when running QSI "show all partitions" with "--partitions-full" in case users like to see those also included.

Re: QSI: no partition data found

Posted: Mon Jul 15, 2024 6:23 pm
by dolphin_oracle
fehlix wrote: Mon Jul 15, 2024 4:48 pm
dolphin_oracle wrote: Mon Jul 15, 2024 4:14 pm ok in this instance, the stuff qsi usually displays on an installed system
And we should probably keep "-P"/"--partitions" (within "-Z") as default, to avoid
seeing all users or other mounts.
Maybe an option when running QSI "show all partitions" with "--partitions-full" in case users like to see those also included.
I think you are missing what is being thrown :happy:

the -P and -p (and the -Z partitions info) do not work on the live system.

Re: QSI: no partition data found

Posted: Mon Jul 15, 2024 6:57 pm
by fehlix
dolphin_oracle wrote: Mon Jul 15, 2024 6:23 pm
fehlix wrote: Mon Jul 15, 2024 4:48 pm
dolphin_oracle wrote: Mon Jul 15, 2024 4:14 pm ok in this instance, the stuff qsi usually displays on an installed system
And we should probably keep "-P"/"--partitions" (within "-Z") as default, to avoid
seeing all users or other mounts.
Maybe an option when running QSI "show all partitions" with "--partitions-full" in case users like to see those also included.
I think you are missing what is being thrown :happy:

the -P and -p (and the -Z partitions info) do not work on the live system.
Probably mixed -F and -Z:

Here the part QSI on KDE Live with "-F" ( which includes "-P" )
with a manually mounted ESP to /boot/efi:

Code: Select all

Partition:
  ID-1: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/vdd2 maj-min: 253:50
and here with added -p , where now all other partitions are shown,
mount-clicked in dolphin, including luks:

Code: Select all

Partition:
  ID-1: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/vdd2 maj-min: 253:50
  ID-2: /media/demo/BOOT_VDD3 raw-size: 1024 MiB size: 973.4 MiB (95.06%) used: 232.2 MiB (23.8%)
    fs: ext4 dev: /dev/vdd3 maj-min: 253:51
  ID-3: /media/demo/LUKS_MX233 raw-size: 15.98 GiB size: 15.63 GiB (97.77%)
    used: 13.02 GiB (83.3%) fs: ext4 dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-<filter>
  ID-4: /media/demo/fedora_boot raw-size: 1020 MiB size: 969.4 MiB (95.04%)
    used: 309.8 MiB (32.0%) fs: ext4 dev: /dev/vdb2 maj-min: 253:18
  ID-5: /media/demo/fedora_localhost-live raw-size: 28.41 GiB size: 28.41 GiB (100.00%)
    used: 12.63 GiB (44.5%) fs: btrfs dev: /dev/vdb3 maj-min: 253:19
  ID-6: /media/demo/mx233ahs_vda2 raw-size: 31.75 GiB size: 31.08 GiB (97.89%)
    used: 14.87 GiB (47.9%) fs: ext4 dev: /dev/vda2 maj-min: 253:2
  ID-7: /media/demo/mx233kde_vdc2 raw-size: 31.75 GiB size: 31.08 GiB (97.89%)
    used: 13.43 GiB (43.2%) fs: ext4 dev: /dev/vdc2 maj-min: 253:34

Re: QSI: no partition data found

Posted: Mon Jul 15, 2024 7:12 pm
by dolphin_oracle
fehlix wrote: Mon Jul 15, 2024 6:57 pm
dolphin_oracle wrote: Mon Jul 15, 2024 6:23 pm
fehlix wrote: Mon Jul 15, 2024 4:48 pm
And we should probably keep "-P"/"--partitions" (within "-Z") as default, to avoid
seeing all users or other mounts.
Maybe an option when running QSI "show all partitions" with "--partitions-full" in case users like to see those also included.
I think you are missing what is being thrown :happy:

the -P and -p (and the -Z partitions info) do not work on the live system.
Probably mixed -F and -Z:

Here the part QSI on KDE Live with "-F" ( which includes "-P" )
with a manually mounted ESP to /boot/efi:

Code: Select all

Partition:
  ID-1: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/vdd2 maj-min: 253:50
and here with added -p , where now all other partitions are shown,
mount-clicked in dolphin, including luks:

Code: Select all

Partition:
  ID-1: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/vdd2 maj-min: 253:50
  ID-2: /media/demo/BOOT_VDD3 raw-size: 1024 MiB size: 973.4 MiB (95.06%) used: 232.2 MiB (23.8%)
    fs: ext4 dev: /dev/vdd3 maj-min: 253:51
  ID-3: /media/demo/LUKS_MX233 raw-size: 15.98 GiB size: 15.63 GiB (97.77%)
    used: 13.02 GiB (83.3%) fs: ext4 dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-<filter>
  ID-4: /media/demo/fedora_boot raw-size: 1020 MiB size: 969.4 MiB (95.04%)
    used: 309.8 MiB (32.0%) fs: ext4 dev: /dev/vdb2 maj-min: 253:18
  ID-5: /media/demo/fedora_localhost-live raw-size: 28.41 GiB size: 28.41 GiB (100.00%)
    used: 12.63 GiB (44.5%) fs: btrfs dev: /dev/vdb3 maj-min: 253:19
  ID-6: /media/demo/mx233ahs_vda2 raw-size: 31.75 GiB size: 31.08 GiB (97.89%)
    used: 14.87 GiB (47.9%) fs: ext4 dev: /dev/vda2 maj-min: 253:2
  ID-7: /media/demo/mx233kde_vdc2 raw-size: 31.75 GiB size: 31.08 GiB (97.89%)
    used: 13.43 GiB (43.2%) fs: ext4 dev: /dev/vdc2 maj-min: 253:34
ok fair, but not / and /home

Re: QSI: no partition data found

Posted: Mon Jul 15, 2024 7:20 pm
by fehlix
In case you want to add the --partion-full inxi option -p like this into QSI:
inxi -Fxxxra -p $filters -c$inxi_color
we might also add to the sed-filtter,
something like this sed-filter:

Code: Select all

           s:/media/$(logname)/:/media/<filter>/:g;
           s:/home/[^/]+/:/home/<filter>/:g;
so the sed looks like this:

Code: Select all

sed -r -e "/Kernel:/s/$UNAMER/$UNAMER${UNAMEV:+ \[$UNAMEV\]}/;
           /mapped:/s/luks-${uuid_filter}/luks-<filter>/;
           s:/media/$(logname)/:/media/<filter>/:g;
           s:/home/[^/]+/:/home/<filter>/:g;
           "
which would than filter out the usernames from /media
and potentially other mounts to current user or other users home

Code: Select all

Partition:
  ID-1: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/vdd2 maj-min: 253:50
  ID-2: /media/<filter>/BOOT_VDD3 raw-size: 1024 MiB size: 973.4 MiB (95.06%) used: 232.2 MiB (23.8%)
    fs: ext4 dev: /dev/vdd3 maj-min: 253:51
  ID-3: /media/<filter>/LUKS_MX233 raw-size: 15.98 GiB size: 15.63 GiB (97.77%)
    used: 13.02 GiB (83.3%) fs: ext4 dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-<filter>
  ID-4: /media/<filter>/fedora_boot raw-size: 1020 MiB size: 969.4 MiB (95.04%)
    used: 309.8 MiB (32.0%) fs: ext4 dev: /dev/vdb2 maj-min: 253:18
  ID-5: /media/<filter>/fedora_localhost-live raw-size: 28.41 GiB size: 28.41 GiB (100.00%)
    used: 12.63 GiB (44.5%) fs: btrfs dev: /dev/vdb3 maj-min: 253:19
  ID-6: /media/<filter>/mx233ahs_vda2 raw-size: 31.75 GiB size: 31.08 GiB (97.89%)
    used: 14.87 GiB (47.9%) fs: ext4 dev: /dev/vda2 maj-min: 253:2
  ID-7: /media/<filter>/mx233kde_vdc2 raw-size: 31.75 GiB size: 31.08 GiB (97.89%)
    used: 13.43 GiB (43.2%) fs: ext4 dev: /dev/vdc2 maj-min: 253:34

Re: QSI: no partition data found

Posted: Mon Jul 15, 2024 7:44 pm
by dolphin_oracle
I don’t really.

Re: QSI: no partition data found

Posted: Tue Jul 16, 2024 7:57 am
by thomasl
Folks, please don't get your knickers in a twist. I have zero problems with the way QSI works ATM and if I have a sudden urge to study partition data, I know where I can find them.

I started this whole hullabaloo simply because @m_pav wrote in another thread:
m_pav wrote: Sat Jul 13, 2024 4:54 pmA fully encrypted drive needs to have an unencrypted boot partition to read the bootloader out from. Your QSI shows, no partitions data found which might point to the source of the problem.
... which I took to mean that no partition data found is not to be expected. As @dolphin_oracle has made clear, for a live system this seems to be normal.

Re: QSI: no partition data found

Posted: Tue Jul 16, 2024 8:26 am
by dolphin_oracle
thomasl wrote: Tue Jul 16, 2024 7:57 am Folks, please don't get your knickers in a twist.
my knickers remain untwisted :p
All times are UTC-04:00
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited