Nach MX-21.3-Update erkennt MX-Installer alte Root-Partition nicht  [Solved]

Message
Author
thebookkeeper

Nach MX-21.3-Update erkennt MX-Installer alte Root-Partition nicht

#1 Post by thebookkeeper »

Das MX-Installationsprogramm kann nach dieser MX-21.3-Aktualisierung

Code: Select all

Start-Date: 2023-12-14  02:17:29
Commandline: apt install seamonkey
Requested-By: bookkeeper (1000)
Upgrade: seamonkey:amd64 (2.53.17.1~mozillabinaries-1mx21+1, 2.53.18~mozillabinaries-1mx21+1)
End-Date: 2023-12-14  02:17:45

Start-Date: 2023-12-14  02:18:30
Commandline: apt install tzdata
Requested-By: bookkeeper (1000)
Upgrade: tzdata:amd64 (2021a-1+deb11u10, 2021a-1+deb11u11)
End-Date: 2023-12-14  02:18:38

Start-Date: 2023-12-14  02:50:10
Commandline: apt dist-upgrade
Requested-By: bookkeeper (1000)
Upgrade: mx-repo-list:amd64 (23.11, 23.12), lo-backports-helper:amd64 (23.07.12mx21, 23.07.13x21), mx-packageinstaller-pkglist:amd64 (23.07.12mx21, 23.07.13x21)
End-Date: 2023-12-14  02:50:17

Start-Date: 2023-12-14  02:54:59
Commandline: /usr/sbin/synaptic
Requested-By: bookkeeper (1000)
Install: waterfox-g3-kpe:amd64 (2.0-0.1~mx21+1, automatic), waterfox-g3-i18n-de:amd64 (2.0-0.1~mx21+1)
End-Date: 2023-12-14  02:55:21

Start-Date: 2023-12-14  10:51:52
Commandline: apt-get install dpkg-repack
Requested-By: bookkeeper (1000)
Install: dpkg-repack:amd64 (1.47)
End-Date: 2023-12-14  10:52:01

Start-Date: 2023-12-14  16:45:38
Commandline: apt dist-upgrade
Requested-By: bookkeeper (1000)
Upgrade: mx-conky-data:amd64 (20230627, 20231201)
End-Date: 2023-12-14  16:45:45

kein MX-Snapshot-Backup mehr installieren,
weil die Root-Partition nicht mehr erkannt wird bzw. nicht mehr überschrieben wird.

Code: Select all

Snapshot created on: 20231114_0458
System:    Kernel: 6.1.0-0.deb11.13-amd64 [6.1.55-1~bpo11+1] x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-0.deb11.13-amd64 root=UUID=<filter> ro quiet 
           splash fsck.mode=auto fsck.repair=preen security=apparmor apparmor=1 
           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: MX-21.3_x64 Wildflower November 14  2023 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: Dell product: Dell DV051 v: N/A serial: <filter> Chassis: type: 6 
           serial: <filter> 
           Mobo: Dell model: 0JC474 serial: <filter> BIOS: Dell v: A03 date: 10/08/2005 
CPU:       Info: Single Core model: Intel Pentium 4 bits: 64 type: MCP arch: Netburst Smithfield 
           family: F (15) model-id: 4 stepping: 3 microcode: 5 cache: L2: 2 MiB 
           flags: lm nx pae sse sse2 sse3 bogomips: 5985 
           Speed: 2993 MHz min/max: N/A Core speed (MHz): 1: 2993 
           Vulnerabilities: Type: gather_data_sampling status: Not affected 
           Type: itlb_multihit status: KVM: VMX unsupported 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data status: Unknown: No mitigations 
           Type: retbleed status: Not affected 
           Type: spec_rstack_overflow status: Not affected 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Retpolines, STIBP: disabled, RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 82915G/GV/910GL Integrated Graphics vendor: Dell driver: i915 v: kernel 
           bus-ID: 00:02.0 chip-ID: 8086:2582 class-ID: 0300 
           Display: x11 server: X.Org 1.20.14 compositor: xfwm4 v: 4.18.0 driver: loaded: intel 
           display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1360x768 s-dpi: 96 s-size: 359x203mm (14.1x8.0") 
           s-diag: 412mm (16.2") 
           Monitor-1: VGA1 res: 1360x768 hz: 60 dpi: 60 size: 580x320mm (22.8x12.6") 
           diag: 662mm (26.1") 
           OpenGL: renderer: Mesa DRI Intel 915G v: 1.4 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel 82801FB/FBM/FR/FW/FRW High Definition Audio vendor: Dell 
           driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:2668 class-ID: 0403 
           Sound Server-1: ALSA v: k6.1.0-0.deb11.13-amd64 running: yes 
           Sound Server-2: PulseAudio v: 15.0 running: yes 
Network:   Device-1: Intel 82562ET/EZ/GT/GZ - PRO/100 VE Ethernet vendor: Dell driver: e100 
           v: kernel port: dcc0 bus-ID: 03:08.0 chip-ID: 8086:1064 class-ID: 0200 
           IF: enp3s8 state: up speed: 100 Mbps duplex: full mac: <filter> 
           Device-2: Belkin F7D1101 v1 Basic Wireless Adapter [Realtek RTL8188SU] type: USB 
           driver: r8712u bus-ID: 1-4:5 chip-ID: 050d:945a class-ID: 0000 serial: <filter> 
           IF: wlxec1a595280f1 state: up mac: <filter> 
Drives:    Local Storage: total: 52.94 GiB used: 17.71 GiB (33.5%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Maxtor model: 6E040L0 size: 38.29 GiB block-size: 
           physical: 512 B logical: 512 B speed: <unknown> type: N/A serial: <filter> rev: 1HA0 
           scheme: MBR 
           ID-2: /dev/sdc maj-min: 8:32 type: USB model: ASolid USB size: 14.65 GiB block-size: 
           physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 0000 scheme: MBR 
           SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Partition: ID-1: / raw-size: 11.17 GiB size: 10.9 GiB (97.52%) used: 9.26 GiB (85.0%) fs: ext4 
           dev: /dev/sda5 maj-min: 8:5 
           ID-2: /home raw-size: 24.32 GiB size: 24.3 GiB (99.95%) used: 8.45 GiB (34.8%) fs: xfs 
           dev: /dev/sda6 maj-min: 8:6 
Swap:      Kernel: swappiness: 35 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 2.79 GiB used: 0 KiB (0.0%) priority: -2 
           dev: /dev/sda1 maj-min: 8:1 
Sensors:   Message: No sensor data found. Is lm-sensors configured? 
Repos:     Packages: note: see --pkg apt: 2150 lib: 1093 flatpak: 0 
           No active apt repos in: /etc/apt/sources.list 
           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://deb.debian.org/debian/ bullseye-updates main contrib non-free
           3: deb http://deb.debian.org/debian/ bullseye-backports main contrib non-free
           4: deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb https://mirror.yandex.ru/mirrors/MX-Linux/MX-Packages/mx/repo/ bullseye non-free main
           2: deb https://mirror.yandex.ru/mirrors/MX-Linux/MX-Packages/mx/testrepo/ bullseye test
Info:      Processes: 188 Uptime: 11m wakeups: 1 Memory: 1.91 GiB used: 1.18 GiB (62.0%) 
           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: BIOS (legacy, CSM, MBR)
Last edited by thebookkeeper on Thu Dec 14, 2023 12:28 pm, edited 1 time in total.

User avatar
Eadwine Rose
Administrator
Posts: 15340
Joined: Wed Jul 12, 2006 2:10 am

Re: Nach MX-21.3-Update erkennt MX-Installer alte Root-Partition nicht

#2 Post by Eadwine Rose »

Teilen Sie bitte immer die vollständige QSI mit.
MX-23.6_x64 July 31 2023 * 6.1.0-40amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030

thebookkeeper

Re: Nach MX-21.3-Update erkennt MX-Installer alte Root-Partition nicht

#3 Post by thebookkeeper »

minstall.log:

Code: Select all

2023-12-14 17:44:01.791 DBG default: Installer version: 23.6.02
2023-12-14 17:44:02.044 DBG default: << void MInstall::startup() >>
2023-12-14 17:44:02.045 DBG default: Detect EFI: 0
2023-12-14 17:44:02.418 DBG default: Check MD5: /live/boot-dev/antiX/initrd.gz
2023-12-14 17:44:03.030 DBG default: Check MD5: /live/boot-dev/antiX/linuxfs
2023-12-14 17:48:45.106 DBG default: Check MD5: /live/boot-dev/antiX/vmlinuz
2023-12-14 17:48:45.533 DBG default: Exec #1: du -scb /live/aufs/boot
2023-12-14 17:48:45.636 DBG default: Exit #1: 0
2023-12-14 17:48:45.640 DBG default: Image size: 12131674112 true "/live/boot-dev/antiX/linuxfs.info"
2023-12-14 17:48:45.640 DBG default: Minimum space: 223266050 (boot), 12131674112 (root)
2023-12-14 17:48:45.640 DBG default: << void MInstall::setupAutoMount(bool) >>
2023-12-14 17:48:45.640 DBG default: Bash #2: ps -e | grep 'udisksd'
2023-12-14 17:48:45.781 DBG default: SOut #2: "   4644 ?        00:00:00 udisksd\n"
2023-12-14 17:48:45.782 DBG default: Exit #2: 0
2023-12-14 17:48:45.782 DBG default: Bash #3: grep -El '^[^#].*mdadm (-I|--incremental)' /lib/udev/rules.d/*
2023-12-14 17:48:45.857 DBG default: Exit #3: 0
2023-12-14 17:48:45.857 DBG default: Bash #4: systemctl list-units --full --all -t mount --no-legend 2>/dev/null | grep -v masked | cut -f1 -d' ' | grep -Ev '^(dev-hugepages|dev-mqueue|proc-sys-fs-binfmt_misc|run-user-.*-gvfs|sys-fs-fuse-connections|sys-kernel-config|sys-kernel-debug)'
2023-12-14 17:48:45.944 DBG default: Exit #4: 1
2023-12-14 17:48:45.946 DBG default: MkPath(SUCCESS): "/run/udev/rules.d"
2023-12-14 17:48:45.946 DBG default: Exec #5: touch /run/udev/rules.d/64-md-raid-assembly.rules
2023-12-14 17:48:45.966 DBG default: Exit #5: 0
2023-12-14 17:48:45.966 DBG default: Bash #6: echo 'SUBSYSTEM=="block", ENV{UDISKS_IGNORE}="1"' > /run/udev/rules.d/91-mx-udisks-inhibit.rules
2023-12-14 17:48:45.979 DBG default: Exit #6: 0
2023-12-14 17:48:45.979 DBG default: Exec #7: udevadm control --reload
2023-12-14 17:48:46.061 DBG default: Exit #7: 0
2023-12-14 17:48:46.061 DBG default: Exec #8: udevadm trigger --subsystem-match=block
2023-12-14 17:48:46.095 DBG default: Exit #8: 0
2023-12-14 17:48:46.894 DBG default: Exec #9: grub-probe -d /dev/sda2
2023-12-14 17:48:48.166 DBG default: SErr #9: "/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda2.  Check your device.map.\n"
2023-12-14 17:48:48.166 DBG default: Exit #9: 1
2023-12-14 17:48:48.167 DBG default: Detect Mac: false
2023-12-14 17:48:48.178 DBG default: Exec #10: find -L /usr/share/zoneinfo/posix -mindepth 2 -type f -printf %P\n
2023-12-14 17:48:48.265 DBG default: Exit #10: 0
2023-12-14 17:48:48.282 DBG default: Bash #11: locale -a | grep -Ev '^(C|POSIX)\.?' | grep -E 'utf8|UTF-8'
2023-12-14 17:48:48.332 DBG default: Exit #11: 0
2023-12-14 17:48:48.335 DBG default: Bash #12: /bin/ls -1 /home | grep -Ev '^(lost\+found|demo|snapshot)$' | grep -q '[a-zA-Z0-9]'
2023-12-14 17:48:48.371 DBG default: Exit #12: 0
2023-12-14 17:48:48.371 DBG default: check for possible snapshot: true
2023-12-14 17:48:48.372 DBG default: Bash #13: dpkg -s samba | grep '^Status.*ok.*' | sed -e 's/.*ok //'
2023-12-14 17:48:48.491 DBG default: Exit #13: 0
2023-12-14 17:48:48.503 DBG default: Exec #14: lsblk -T -bJo TYPE,NAME,PATH,UUID,ROTA,DISC-GRAN,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,LABEL,MODEL,PARTFLAGS
2023-12-14 17:48:48.558 DBG default: Exit #14: 0
2023-12-14 17:48:48.559 DBG default: Exec #15: partprobe -s
2023-12-14 17:48:52.283 DBG default: SOut #15: "/dev/sda: msdos partitions 1 2 <5 6>\n"
2023-12-14 17:48:52.284 DBG default: SErr #15: "Error: Partition(s) 1 on /dev/sdc have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\nWarning: Unable to open /dev/sr1 read-write (Read-only file system).  /dev/sr1 has been opened read-only.\nWarning: The driver descriptor says the physical block size is 512 bytes, but Linux says it is 2048 bytes.\n"
2023-12-14 17:48:52.284 DBG default: Exit #15: 1
2023-12-14 17:48:52.285 DBG default: Exec #16: blkid -c /dev/null
2023-12-14 17:48:52.986 DBG default: SOut #16: "/dev/sda1: LABEL=\"swapMX\" UUID=\"d79ee404-37bd-4ef6-98ec-bc0daef76cc9\" TYPE=\"swap\" PARTUUID=\"b0584570-01\"\n/dev/sda5: LABEL=\"rootMX21\" UUID=\"aaf7063e-e601-40be-93a3-34a07e4f3506\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"b0584570-05\"\n/dev/sda6: LABEL=\"homeMX\" UUID=\"26e460b1-1ec3-47c7-999d-67c447f5f0db\" BLOCK_SIZE=\"512\" TYPE=\"xfs\" PARTUUID=\"b0584570-06\"\n/dev/sr1: BLOCK_SIZE=\"2048\" UUID=\"2010-02-09-09-00-00-00\" LABEL=\"Mobile Partner\" TYPE=\"iso9660\" PTTYPE=\"mac\"\n/dev/sdc1: BLOCK_SIZE=\"2048\" UUID=\"2023-12-14-16-17-24-00\" LABEL=\"MXLIVE\" TYPE=\"iso9660\" PTUUID=\"6b8b4567\" PTTYPE=\"dos\" PARTUUID=\"6b8b4567-01\"\n/dev/sdc2: SEC_TYPE=\"msdos\" LABEL_FATBOOT=\"EFI-LIVE\" LABEL=\"EFI-LIVE\" UUID=\"71FA-F426\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTUUID=\"6b8b4567-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2023-12-14 17:48:52.986 DBG default: Exit #16: 0
2023-12-14 17:48:52.986 DBG default: Exec #17: parted -lm
2023-12-14 17:48:54.992 DBG default: SErr #17: "Warning: Unable to open /dev/sr1 read-write (Read-only file system).  /dev/sr1\nhas been opened read-only.\nWarning: The driver descriptor says the physical block size is 512 bytes, but\nLinux says it is 2048 bytes.\n"
2023-12-14 17:48:54.998 DBG default: Exit #17: 0
2023-12-14 17:48:54.999 DBG default: Bash #18: lsblk -T -bJo TYPE,NAME,PATH,UUID,ROTA,DISC-GRAN,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/*
2023-12-14 17:48:55.036 DBG default: SErr #18: "lsblk: /dev/mapper/control: not a block device\n"
2023-12-14 17:48:55.036 DBG default: Exit #18: 32
2023-12-14 17:51:37.904 DBG default: << bool MInstall::abortUI() >>
2023-12-14 17:51:37.908 DBG default: -- Manual abort --
2023-12-14 17:51:37.915 DBG default: << void MInstall::cleanup(bool) >>
2023-12-14 17:51:37.916 DBG default: << void MInstall::setupAutoMount(bool) >>
2023-12-14 17:51:37.916 DBG default: Bash #19: ps -e | grep 'udisksd'
2023-12-14 17:51:38.028 DBG default: SOut #19: "   4644 ?        00:00:00 udisksd\n"
2023-12-14 17:51:38.028 DBG default: Exit #19: 0
2023-12-14 17:51:38.028 DBG default: Bash #20: grep -El '^[^#].*mdadm (-I|--incremental)' /lib/udev/rules.d/*
2023-12-14 17:51:38.070 DBG default: Exit #20: 0
2023-12-14 17:51:38.070 DBG default: Exec #21: rm -f /run/udev/rules.d/91-mx-udisks-inhibit.rules
2023-12-14 17:51:38.105 DBG default: Exit #21: 0
2023-12-14 17:51:38.105 DBG default: Exec #22: udevadm control --reload
2023-12-14 17:51:38.143 DBG default: Exit #22: 0
2023-12-14 17:51:38.143 DBG default: Exec #23: partprobe -s
2023-12-14 17:51:41.391 DBG default: SOut #23: "/dev/sda: msdos partitions 1 2 <5 6>\n"
2023-12-14 17:51:41.392 DBG default: SErr #23: "Error: Partition(s) 1 on /dev/sdc have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\nWarning: Unable to open /dev/sr1 read-write (Read-only file system).  /dev/sr1 has been opened read-only.\nWarning: The driver descriptor says the physical block size is 512 bytes, but Linux says it is 2048 bytes.\n"
2023-12-14 17:51:41.392 DBG default: Exit #23: 1
2023-12-14 17:51:41.401 DBG default: Sleep #1: 1000ms
2023-12-14 17:51:42.352 DBG default: Sleep #1: exit 0
2023-12-14 17:51:42.352 DBG default: Bash #24: rm -f /run/udev/rules.d/64-md-raid-assembly.rules
2023-12-14 17:51:42.369 DBG default: Exit #24: 0
2023-12-14 17:51:42.370 DBG default: Exec #25: /usr/bin/cp /var/log/minstall.log /mnt/antiX/var/log
2023-12-14 17:51:42.391 DBG default: SErr #25: "/usr/bin/cp: cannot create regular file '/mnt/antiX/var/log': No such file or directory\n"
2023-12-14 17:51:42.391 DBG default: Exit #25: 1
2023-12-14 17:51:42.391 DBG default: Exec #26: /usr/bin/rm -rf /mnt/antiX/mnt/antiX
2023-12-14 17:51:42.406 DBG default: Exit #26: 0
2023-12-14 17:51:42.406 DBG default: Exec #27: /usr/bin/mountpoint -q /mnt/antiX/boot/efi
2023-12-14 17:51:42.427 DBG default: Exit #27: 1
2023-12-14 17:51:42.428 DBG default: Exec #28: /usr/bin/mountpoint -q /mnt/antiX/proc
2023-12-14 17:51:42.444 DBG default: Exit #28: 1
2023-12-14 17:51:42.444 DBG default: Exec #29: /usr/bin/mountpoint -q /mnt/antiX/sys
2023-12-14 17:51:42.461 DBG default: Exit #29: 1
2023-12-14 17:51:42.462 DBG default: Exec #30: /usr/bin/mountpoint -q /mnt/antiX/dev/shm
2023-12-14 17:51:42.478 DBG default: Exit #30: 1
2023-12-14 17:51:42.479 DBG default: Exec #31: /usr/bin/mountpoint -q /mnt/antiX/dev
2023-12-14 17:51:42.496 DBG default: Exit #31: 1
2023-12-14 17:51:52.571 DBG default: Installer version: 23.6.02
2023-12-14 17:51:52.820 DBG default: << void MInstall::startup() >>
2023-12-14 17:51:52.821 DBG default: Detect EFI: 0
2023-12-14 17:51:53.185 DBG default: Check MD5: /live/boot-dev/antiX/initrd.gz
2023-12-14 17:51:53.854 DBG default: Check MD5: /live/boot-dev/antiX/linuxfs
2023-12-14 17:56:30.810 DBG default: Check MD5: /live/boot-dev/antiX/vmlinuz
2023-12-14 17:56:31.226 DBG default: Exec #1: du -scb /live/aufs/boot
2023-12-14 17:56:31.264 DBG default: Exit #1: 0
2023-12-14 17:56:31.271 DBG default: Image size: 12131674112 true "/live/boot-dev/antiX/linuxfs.info"
2023-12-14 17:56:31.271 DBG default: Minimum space: 223266050 (boot), 12131674112 (root)
2023-12-14 17:56:31.271 DBG default: << void MInstall::setupAutoMount(bool) >>
2023-12-14 17:56:31.271 DBG default: Bash #2: ps -e | grep 'udisksd'
2023-12-14 17:56:31.384 DBG default: SOut #2: "   4644 ?        00:00:00 udisksd\n"
2023-12-14 17:56:31.384 DBG default: Exit #2: 0
2023-12-14 17:56:31.384 DBG default: Bash #3: grep -El '^[^#].*mdadm (-I|--incremental)' /lib/udev/rules.d/*
2023-12-14 17:56:31.455 DBG default: Exit #3: 0
2023-12-14 17:56:31.455 DBG default: Bash #4: systemctl list-units --full --all -t mount --no-legend 2>/dev/null | grep -v masked | cut -f1 -d' ' | grep -Ev '^(dev-hugepages|dev-mqueue|proc-sys-fs-binfmt_misc|run-user-.*-gvfs|sys-fs-fuse-connections|sys-kernel-config|sys-kernel-debug)'
2023-12-14 17:56:31.546 DBG default: Exit #4: 1
2023-12-14 17:56:31.547 DBG default: Exec #5: touch /run/udev/rules.d/64-md-raid-assembly.rules
2023-12-14 17:56:31.586 DBG default: Exit #5: 0
2023-12-14 17:56:31.586 DBG default: Bash #6: echo 'SUBSYSTEM=="block", ENV{UDISKS_IGNORE}="1"' > /run/udev/rules.d/91-mx-udisks-inhibit.rules
2023-12-14 17:56:31.610 DBG default: Exit #6: 0
2023-12-14 17:56:31.610 DBG default: Exec #7: udevadm control --reload
2023-12-14 17:56:31.647 DBG default: Exit #7: 0
2023-12-14 17:56:31.647 DBG default: Exec #8: udevadm trigger --subsystem-match=block
2023-12-14 17:56:31.727 DBG default: Exit #8: 0
2023-12-14 17:56:32.516 DBG default: Exec #9: grub-probe -d /dev/sda2
2023-12-14 17:56:33.403 DBG default: SErr #9: "/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda2.  Check your device.map.\n"
2023-12-14 17:56:33.404 DBG default: Exit #9: 1
2023-12-14 17:56:33.404 DBG default: Detect Mac: false
2023-12-14 17:56:33.416 DBG default: Exec #10: find -L /usr/share/zoneinfo/posix -mindepth 2 -type f -printf %P\n
2023-12-14 17:56:33.449 DBG default: Exit #10: 0
2023-12-14 17:56:33.459 DBG default: Bash #11: locale -a | grep -Ev '^(C|POSIX)\.?' | grep -E 'utf8|UTF-8'
2023-12-14 17:56:33.536 DBG default: Exit #11: 0
2023-12-14 17:56:33.540 DBG default: Bash #12: /bin/ls -1 /home | grep -Ev '^(lost\+found|demo|snapshot)$' | grep -q '[a-zA-Z0-9]'
2023-12-14 17:56:33.600 DBG default: Exit #12: 0
2023-12-14 17:56:33.600 DBG default: check for possible snapshot: true
2023-12-14 17:56:33.600 DBG default: Bash #13: dpkg -s samba | grep '^Status.*ok.*' | sed -e 's/.*ok //'
2023-12-14 17:56:33.757 DBG default: Exit #13: 0
2023-12-14 17:56:33.768 DBG default: Exec #14: lsblk -T -bJo TYPE,NAME,PATH,UUID,ROTA,DISC-GRAN,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,LABEL,MODEL,PARTFLAGS
2023-12-14 17:56:33.864 DBG default: Exit #14: 0
2023-12-14 17:56:33.864 DBG default: Exec #15: partprobe -s
2023-12-14 17:56:37.931 DBG default: SOut #15: "/dev/sda: msdos partitions 1 2 <5 6>\n"
2023-12-14 17:56:37.931 DBG default: SErr #15: "Error: Partition(s) 1 on /dev/sdc have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\nWarning: Unable to open /dev/sr1 read-write (Read-only file system).  /dev/sr1 has been opened read-only.\nWarning: The driver descriptor says the physical block size is 512 bytes, but Linux says it is 2048 bytes.\n"
2023-12-14 17:56:37.932 DBG default: Exit #15: 1
2023-12-14 17:56:37.932 DBG default: Exec #16: blkid -c /dev/null
2023-12-14 17:56:38.591 DBG default: SOut #16: "/dev/sda1: LABEL=\"swapMX\" UUID=\"d79ee404-37bd-4ef6-98ec-bc0daef76cc9\" TYPE=\"swap\" PARTUUID=\"b0584570-01\"\n/dev/sda5: LABEL=\"rootMX21\" UUID=\"aaf7063e-e601-40be-93a3-34a07e4f3506\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"b0584570-05\"\n/dev/sda6: LABEL=\"homeMX\" UUID=\"26e460b1-1ec3-47c7-999d-67c447f5f0db\" BLOCK_SIZE=\"512\" TYPE=\"xfs\" PARTUUID=\"b0584570-06\"\n/dev/sr1: BLOCK_SIZE=\"2048\" UUID=\"2010-02-09-09-00-00-00\" LABEL=\"Mobile Partner\" TYPE=\"iso9660\" PTTYPE=\"mac\"\n/dev/sdc1: BLOCK_SIZE=\"2048\" UUID=\"2023-12-14-16-17-24-00\" LABEL=\"MXLIVE\" TYPE=\"iso9660\" PTUUID=\"6b8b4567\" PTTYPE=\"dos\" PARTUUID=\"6b8b4567-01\"\n/dev/sdc2: SEC_TYPE=\"msdos\" LABEL_FATBOOT=\"EFI-LIVE\" LABEL=\"EFI-LIVE\" UUID=\"71FA-F426\" BLOCK_SIZE=\"512\" TYPE=\"vfat\" PARTUUID=\"6b8b4567-02\"\n/dev/loop0: TYPE=\"squashfs\"\n"
2023-12-14 17:56:38.592 DBG default: Exit #16: 0
2023-12-14 17:56:38.592 DBG default: Exec #17: parted -lm
2023-12-14 17:56:40.537 DBG default: SErr #17: "Warning: Unable to open /dev/sr1 read-write (Read-only file system).  /dev/sr1\nhas been opened read-only.\nWarning: The driver descriptor says the physical block size is 512 bytes, but\nLinux says it is 2048 bytes.\n"
2023-12-14 17:56:40.537 DBG default: Exit #17: 0
2023-12-14 17:56:40.538 DBG default: Bash #18: lsblk -T -bJo TYPE,NAME,PATH,UUID,ROTA,DISC-GRAN,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/*
2023-12-14 17:56:40.666 DBG default: SErr #18: "lsblk: /dev/mapper/control: not a block device\n"
2023-12-14 17:56:40.666 DBG default: Exit #18: 32
2023-12-14 17:59:29.259 DBG default: << bool MInstall::abortUI() >>
2023-12-14 17:59:29.275 DBG default: -- Manual abort --
2023-12-14 17:59:29.279 DBG default: << void MInstall::cleanup(bool) >>
2023-12-14 17:59:29.280 DBG default: << void MInstall::setupAutoMount(bool) >>
2023-12-14 17:59:29.280 DBG default: Bash #19: ps -e | grep 'udisksd'
2023-12-14 17:59:29.395 DBG default: SOut #19: "   4644 ?        00:00:01 udisksd\n"
2023-12-14 17:59:29.395 DBG default: Exit #19: 0
2023-12-14 17:59:29.396 DBG default: Bash #20: grep -El '^[^#].*mdadm (-I|--incremental)' /lib/udev/rules.d/*
2023-12-14 17:59:29.453 DBG default: Exit #20: 0
2023-12-14 17:59:29.454 DBG default: Exec #21: rm -f /run/udev/rules.d/91-mx-udisks-inhibit.rules
2023-12-14 17:59:29.498 DBG default: Exit #21: 0
2023-12-14 17:59:29.499 DBG default: Exec #22: udevadm control --reload
2023-12-14 17:59:29.549 DBG default: Exit #22: 0
2023-12-14 17:59:29.550 DBG default: Exec #23: partprobe -s
2023-12-14 17:59:32.985 DBG default: SOut #23: "/dev/sda: msdos partitions 1 2 <5 6>\n"
2023-12-14 17:59:32.985 DBG default: SErr #23: "Error: Partition(s) 1 on /dev/sdc have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.\nWarning: Unable to open /dev/sr1 read-write (Read-only file system).  /dev/sr1 has been opened read-only.\nWarning: The driver descriptor says the physical block size is 512 bytes, but Linux says it is 2048 bytes.\n"
2023-12-14 17:59:32.985 DBG default: Exit #23: 1
2023-12-14 17:59:33.001 DBG default: Sleep #1: 1000ms
2023-12-14 17:59:34.053 DBG default: Sleep #1: exit 0
2023-12-14 17:59:34.053 DBG default: Bash #24: rm -f /run/udev/rules.d/64-md-raid-assembly.rules
2023-12-14 17:59:34.096 DBG default: Exit #24: 0
2023-12-14 17:59:34.097 DBG default: Exec #25: /usr/bin/cp /var/log/minstall.log /mnt/antiX/var/log
2023-12-14 17:59:34.140 DBG default: SErr #25: "/usr/bin/cp: cannot create regular file '/mnt/antiX/var/log': No such file or directory\n"
2023-12-14 17:59:34.141 DBG default: Exit #25: 1
2023-12-14 17:59:34.141 DBG default: Exec #26: /usr/bin/rm -rf /mnt/antiX/mnt/antiX
2023-12-14 17:59:34.182 DBG default: Exit #26: 0
2023-12-14 17:59:34.182 DBG default: Exec #27: /usr/bin/mountpoint -q /mnt/antiX/boot/efi
2023-12-14 17:59:34.223 DBG default: Exit #27: 1
2023-12-14 17:59:34.224 DBG default: Exec #28: /usr/bin/mountpoint -q /mnt/antiX/proc
2023-12-14 17:59:34.266 DBG default: Exit #28: 1
2023-12-14 17:59:34.266 DBG default: Exec #29: /usr/bin/mountpoint -q /mnt/antiX/sys
2023-12-14 17:59:34.308 DBG default: Exit #29: 1
2023-12-14 17:59:34.308 DBG default: Exec #30: /usr/bin/mountpoint -q /mnt/antiX/dev/shm
2023-12-14 17:59:34.351 DBG default: Exit #30: 1
2023-12-14 17:59:34.351 DBG default: Exec #31: /usr/bin/mountpoint -q /mnt/antiX/dev
2023-12-14 17:59:34.393 DBG default: Exit #31: 1
Genaue Fehler-Ansicht im Bild-Anhang:
You do not have the required permissions to view the files attached to this post.

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

Re: Nach MX-21.3-Update erkennt MX-Installer alte Root-Partition nicht

#4 Post by j2mcgreg »

@thebookkeeper

Die Forenregeln schreiben vor, dass einer Hilfeanfrage ein QSI-Bericht beigefügt sein muss und keiner der beiden oben genannten Einträge zulässig ist.
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.

thebookkeeper

Re: Nach MX-21.3-Update erkennt MX-Installer alte Root-Partition nicht

#5 Post by thebookkeeper »

QSI jetzt vollständig und verbesserte APT-History - oben.

thebookkeeper

Re: Nach MX-21.3-Update erkennt MX-Installer alte Root-Partition nicht  [Solved]

#6 Post by thebookkeeper »

Das Update war unschuldig und der 6.1er-Backport-Kernel war schon vorher installiert. Aber nachdem er aktiv gebootet wurde, entstand der Fehler. Das Problem wurde durch Umstellung auf 5.10er-Kernel gelöst und der neue Backport-Kernel wurde wieder deinstalliert.

Code: Select all

bookkeeper@mx-dell:~
$ apt list --installed *5.10*
Auflistung… Fertig
linux-headers-5.10.0-26-amd64/oldstable,now 5.10.197-1 amd64  [installiert]
linux-headers-5.10.0-26-common/oldstable,oldstable,now 5.10.197-1 all  [Installiert,automatisch]
linux-headers-5.10.188-antix.1-amd64-smp/now 5.10.188-antix.1-amd64-smp-1 amd64  [Installiert,lokal]
linux-image-5.10.0-26-amd64/oldstable,now 5.10.197-1 amd64  [installiert]
linux-image-5.10.188-antix.1-amd64-smp/now 5.10.188-antix.1-amd64-smp-1 amd64  [Installiert,lokal]
linux-kbuild-5.10/oldstable,now 5.10.197-1 amd64  [installiert]
bookkeeper@mx-dell:~
$ 
War ein Beweis, dass neue Kernel ungeeignet sind für alte Hardware.
You do not have the required permissions to view the files attached to this post.

loik
Posts: 2314
Joined: Wed Dec 12, 2018 2:01 pm

Re: Nach MX-21.3-Update erkennt MX-Installer alte Root-Partition nicht

#7 Post by loik »

Moin, thebookkeeper
War ein Beweis, dass neue Kernel ungeeignet sind für alte Hardware.
Ja, in diesem Fall

Code: Select all

Info: Single Core model: Intel Pentium 4 bits: 64 type: MCP arch: Netburst Smithfield
eigentlich, für einen geschmeidigen Betrieb nur zu empfehlen:

Code: Select all

antiX 4.9.326 Kernel Meltdown und Spectre gepatcht, 64 bit
Aus dem MxPi -> "Beliebte Anwendungen".
Wenn man die Wahl hat, zwischen PAE oder ohne PEA, dann ohne.

Danke, dass du das nun schon mal vorgetestet hast.
Dann weiß ich nun, dass ich beim Umstieg auf MX-23, es erst mal auf neuerer Hadrware installiere.
Dann im ersten Betrieb gleich den 4.9- Antix-Kernel hinterherinstallieren, neu Starten und den 4.9er Kernel booten, ein MX-Snapshot erstellen und erst dieses dann auf der alten Hardware installieren.

Hat mir nun im Vorfeld schon mal viel Nerv erspart.


Ich hatte bisher den genau umgekehrten Fall erlebt.

Ein entsprechendes Snapshot mit einem 4.9er Kernel war absolut unbootbar bzw überhaupt nicht lauffähig auf Win-Tabbets von ODIS und CSL.
Da musste es dann schon mindestens 4.19 aber besser ein 5.8 oder 5.10 sein.

Post Reply

Return to “Deutsches Forum”