MX live usb maker fails creating writable system  [Solved]

Report Bugs, Issues and non- package Requests
Message
Author
tizianomattei
Posts: 24
Joined: Thu Jan 06, 2022 4:20 pm

MX live usb maker fails creating writable system

#1 Post by tizianomattei »

Hi all,
I've tried this on different machines running different versions of MX, and with different ISO's, and I never seem to get it right.
MX live usb maker isn't able to flash an MX iso in FULL mode, i.e. creating a writable system that can be used with persistency.
This is the log after my last attempt, using MX23 64bit and flashing the same iso on an 8Gb microsd drive (yes, the sd is a fake 2Tb one, but I've been unsuccessful even with good and real usb sticks or sd cards before... also, on the same microsd card I can flash an ISO in dd mode with no problem at all...)
Thank you for your time
Tiziano

Code: Select all

=====================================================================
/usr/local/bin/live-usb-maker gui -N -C off --from=/home/snapshot/MX-23.1_x64.iso -t /dev/sdb
        program: live-usb-maker
        started: mar 17 ott 2023, 12:06:03, CEST
        version: 2.41.19-2302 (Sat, 25 Feb 2023 12:45:10 -0500)
         kernel: 6.1.0-13-amd64
             OS: MX 23 (Libretto)
      found lib: /usr/local/lib/cli-shell-utils/cli-shell-utils.bash
    lib version: 2.41.05-2302 (Sat, 25 Feb 2023 12:45:10 -0500)
---------------------------------------------------------------------

Found man page: live-usb-maker.1
Verrà utilizzato il dispositivo di destinazione /dev/sdb (2T SD/MMC Card Reader)
Verrà utilizzata la sorgente file /home/snapshot/MX-23.1_x64.iso
Distro: MX-23.1_x64 Libretto October 15, 2023
Trovata configurazione di grub 2.0
Estimated extfs overhead for 2047949M is 44M

                          Totale     Usato     Extra
          intera unità  1.95 TiB 1.95 TiB     1 MiB
 partizione principale  1.95 TiB 2.13 GiB  1.95 TiB
       partizione uefi    50 MiB   32 MiB    18 MiB

Pronto per la creazione di live-usb sul dispositivo sdb
... per Copia in corso file /home/snapshot/MX-23.1_x64.iso

>> partition-clear
Total bytes: 2147483648000
Total blocks: 4194304000
 > dd status=none if=/dev/zero of=/dev/sdb bs=512 count=34
 > dd status=none if=/dev/zero of=/dev/sdb bs=512 count=34 seek=64
 > dd status=none conv=notrunc if=/dev/zero of=/dev/sdb bs=512 count=34 seek=4194303966
 > partprobe /dev/sdb

>> partition-make
Utilizzo del partizionamento msdos
 > parted --script --align optimal /dev/sdb unit MiB mklabel msdos
 > dd status=none if=/dev/zero of=/dev/sdb seek=1024 bs=1K count=128
 > parted --script --align optimal /dev/sdb unit MiB mkpart primary 1 2047949
 > parted --script --align optimal /dev/sdb unit MiB set 1 boot on
 > dd status=none if=/dev/zero of=/dev/sdb seek=2097099776 bs=1K count=128
 > parted --script --align optimal /dev/sdb unit MiB mkpart primary 2047949 2047998
 > parted --script --align optimal /dev/sdb unit MiB set 2 esp on
 > partprobe /dev/sdb
 > wait_for_file /dev/sdb1

>> makefs-bios
 > mkfs.ext4 -O ^64bit -m0 -i16384 -J size=32 /dev/sdb1
mke2fs 1.47.0 (5-Feb-2023)
64-bit filesystem support is not enabled.  The larger fields afforded by this feature enable full-strength checksumming.  Pass -O 64bit to rectify.
Creazione del file system con 524274688 4k blocchi e 131072000 inode
Etichetta del file system=65d46df6-5d86-4bf6-937b-5eedc2f5296b
Backup del superblocco salvati nei blocchi: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
	102400000, 214990848, 512000000

Allocating group tables:     0/16000           fatto                           
Scrittura delle tavole degli inode:     0/16000           fatto                           
Creating journal (8192 blocks): fatto
Scrittura delle informazioni dei super-blocchi e dell'accounting del file system:     0/16000    1/16000           fatto

 > tune2fs -L MX-Live-usb /dev/sdb1
tune2fs 1.47.0 (5-Feb-2023)
 > wait_for_file /dev/sdb2

>> makefs-uefi
 > mkfs.vfat -F 32 -n MX-UEFI /dev/sdb2
mkfs.fat 4.2 (2021-01-31)
 > partprobe /dev/sdb
 > wait_for_file /dev/sdb1
 > mkdir -p /run/live-usb-maker/main
 > mount -t ext4 /dev/sdb1 /run/live-usb-maker/main
mount: /run/live-usb-maker/main: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
       dmesg(1) may have more information after failed mount system call.
Errore: Could not mount /dev/sdb1 at /run/live-usb-maker/main

live-usb-maker took 46 seconds.

User avatar
j2mcgreg
Global Moderator
Posts: 6955
Joined: Tue Oct 23, 2007 12:04 pm

Re: MX live usb maker fails creating writable system

#2 Post by j2mcgreg »

Please post the QSI for the computer on which this latest failure occurred.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

User avatar
Adrian
Developer
Posts: 9033
Joined: Wed Jul 12, 2006 1:42 am

Re: MX live usb maker fails creating writable system  [Solved]

#3 Post by Adrian »

mount: /run/live-usb-maker/main: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.
Also try "dmesg" to see if there's anything related to /dev/sdb1 there. It says "bad superblock" among other things, it's possible you have a problem with the drive, can you try another one?

User avatar
dolphin_oracle
Developer
Posts: 22393
Joined: Sun Dec 16, 2007 12:17 pm

Re: MX live usb maker fails creating writable system

#4 Post by dolphin_oracle »

FWIW, I've been making usbs and comparing logs, and up to the point that the mount fails, the OP's log looks normal.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

tizianomattei
Posts: 24
Joined: Thu Jan 06, 2022 4:20 pm

Re: MX live usb maker fails creating writable system

#5 Post by tizianomattei »

Hi and thank you all.

This is dmesg after I tried flashing it again:

Code: Select all

[  409.475757] loop0: detected capacity change from 0 to 4382720
[  409.526065] ISO 9660 Extensions: Microsoft Joliet Level 3
[  409.526163] ISO 9660 Extensions: RRIP_1991A
[  413.861583]  sdb:
[  415.260274]  sdb: sdb1
[  416.181991]  sdb: sdb1
[  417.335291]  sdb: sdb1 sdb2
[  418.460315]  sdb: sdb1 sdb2
[  419.546207]  sdb: sdb1 sdb2
[  455.928189] JBD2: no valid journal superblock found
[  455.928198] EXT4-fs (sdb1): error loading journal
Here is the QSI:

Code: Select all

System:
  Kernel: 6.1.0-13-amd64 [6.1.55-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=<filter> ro quiet splash
    resume=UUID=<filter> resume_offset=6330368
  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.26.0 Distro: MX-23_x64 Libretto July 31  2023 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop E203NA v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: E203NA v: 1.0 serial: <superuser required> UEFI: American Megatrends
    v: E203NA.322 date: 01/28/2021
Battery:
  ID-1: BAT0 charge: 3.2 Wh (12.4%) condition: 25.9/38.0 Wh (68.1%) volts: 7.6 min: 7.6
    model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: discharging cycles: 138
CPU:
  Info: model: Intel Celeron N3350 bits: 64 type: MCP arch: Goldmont level: v2 built: 2016
    process: Intel 14nm family: 6 model-id: 0x5C (92) stepping: 9 microcode: 0x48
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 112 KiB desc: d-2x24 KiB; i-2x32 KiB
    L2: 2 MiB desc: 2x1024 KiB
  Speed (MHz): avg: 897 high: 900 min/max: 800/2400 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 895 2: 900 bogomips: 4377
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  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 status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Not affected
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB
    filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel HD Graphics 500 vendor: ASUSTeK driver: i915 v: kernel arch: Gen-9
    process: Intel 14n built: 2015-16 ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:5a85 class-ID: 0300
  Device-2: Chicony USB2.0 VGA UVC WebCam type: USB driver: uvcvideo bus-ID: 1-6:4
    chip-ID: 04f2:b54b class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
  Monitor-1: eDP-1 model: ChiMei InnoLux 0x1130 built: 2013 res: 1366x768 hz: 60 dpi: 136
    gamma: 1.2 size: 256x144mm (10.08x5.67") diag: 294mm (11.6") ratio: 16:9 modes: 1366x768
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 500 (APL 2) direct-render: Yes
Audio:
  Device-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_apl bus-ID: 00:0e.0
    chip-ID: 8086:5a98 class-ID: 0403
  API: ALSA v: k6.1.0-13-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 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: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: AzureWave
    driver: ath10k_pci v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 01:00.0
    chip-ID: 168c:0042 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: IMC Networks type: USB driver: btusb v: 0.8 bus-ID: 1-5:3 chip-ID: 13d3:3501
    class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2
    sub-v: 25a hci-v: 4.2
  Info: acl-mtu: 1024:8 sco-mtu: 50:8 link-policy: rswitch hold sniff
    link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio,
    telephony
Drives:
  Local Storage: total: 2.21 TiB used: 53.95 GiB (2.4%)
  ID-1: /dev/mmcblk0 maj-min: 179:0 vendor: HP model: DF4032 size: 29.12 GiB block-size:
    physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 0x8 scheme: GPT
  SMART Message: Unknown smartctl error. Unable to generate data.
  ID-2: /dev/sda maj-min: 8:0 type: USB model: Multiple Card Reader size: 238.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?
  ID-3: /dev/sdb maj-min: 8:16 type: USB model: SD MMC Card Reader size: 1.95 TiB block-size:
    physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 28.87 GiB size: 28.25 GiB (97.85%) used: 13.3 GiB (47.1%) fs: ext4
    dev: /dev/mmcblk0p2 maj-min: 179:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/mmcblk0p1 maj-min: 179:1
  ID-3: /home raw-size: 238.04 GiB size: 238.04 GiB (100.00%) used: 40.64 GiB (17.1%) fs: f2fs
    dev: /dev/sda2 maj-min: 8:2
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 5.69 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 34.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0
Repos:
  Packages: pm: dpkg pkgs: 2063 libs: 1044 tools: apt,apt-get,aptitude,nala,synaptic 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://it.mxrepo.com/mx/repo/ bookworm main non-free
Info:
  Processes: 210 Uptime: 12m wakeups: 3 Memory: 3.69 GiB used: 1.81 GiB (49.1%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12 Client: shell wrapper
  v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
At the moment I don't have any other card or stick to try, but please note that the drive works perfectly when I choose the "dd" method...

User avatar
Adrian
Developer
Posts: 9033
Joined: Wed Jul 12, 2006 1:42 am

Re: MX live usb maker fails creating writable system

#6 Post by Adrian »

Try to wipe it first. I think you can do

Code: Select all

sudo live-usb-maker partition-clear -t /dev/sdb
Please make sure /dev/sdb is the correct drive.

tizianomattei
Posts: 24
Joined: Thu Jan 06, 2022 4:20 pm

Re: MX live usb maker fails creating writable system

#7 Post by tizianomattei »

Tried right now, no difference...

tizianomattei
Posts: 24
Joined: Thu Jan 06, 2022 4:20 pm

Re: MX live usb maker fails creating writable system

#8 Post by tizianomattei »

Also tried wiping it out completely using Gparted before, no change...
By the way, this is the error given by Gparted in the full info about the partition:

Code: Select all

<i>dumpe2fs 1.47.0 (5-Feb-2023)
Journal superblock magic number invalid!</i>

User avatar
Adrian
Developer
Posts: 9033
Joined: Wed Jul 12, 2006 1:42 am

Re: MX live usb maker fails creating writable system

#9 Post by Adrian »


tizianomattei
Posts: 24
Joined: Thu Jan 06, 2022 4:20 pm

Re: MX live usb maker fails creating writable system

#10 Post by tizianomattei »

I've done that.
At first, mke2fs complains it found a dos partition table on the device.
I tell it to proceed anyway, it prints out the superblock backups list, I plug them into fsck but any of them fails:

Code: Select all

sudo fsck -b 32768 /dev/sda
fsck da util-linux 2.38.1
e2fsck 1.47.0 (5-Feb-2023)
fsck.ext2: Valore magic non corretto nel super-blocco nell'aprire /dev/sda

The super-blocco could not be read or does not describe a valid ext2/ext3/ext4
file system.  If the device is valid and it really contains an ext2/ext3/ext4
file system (and not swap or ufs or something else), then the super-blocco
is corrupt, and you might try running e2fsck with an alternate super-blocco:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

Found a dos partition table in /dev/sda

Post Reply

Return to “Bugs and Non-Package Requests Forum”