#26 Le 26/05/2025, à 20:03
- steph810
Re : Problèmes après installation de Kubuntu 24.04
geole a écrit :
Bonjour
Donne ces retoursjournalctl --no-pager -b -n 100 -p errjournalctl --no-pager -b -n 100 -p warningjournalctl --no-pager -b -n 100 -p notice
Je me permet de raccourcir la commande uniquement pour le journal.
"-p, --priority=", "emerg" (0), "alert" (1), "crit" (2), "err" (3), "warning" (4), "notice" (5), "info" (6), "debug" (7) a écrit :
journalctl --no-pager -b -n 100 -p3 -p4 -p5 | pastebinit
si le paquet pastebinit non installer installer le.
Partager le lien générer https.
Dernière modification par steph810 (Le 26/05/2025, à 20:10)
Hors ligne
#27 Le 04/06/2025, à 19:37
- Ciseur68
Re : Problèmes après installation de Kubuntu 24.04
cesar@cesar-ms7917:~$ journalctl --no-pager -b -n 100 -p err
mai 27 18:42:18 cesar-ms7917 kernel:
mai 27 18:42:20 cesar-ms7917 thermald[1083]: Thermal DTS or hwmon: No Zones present Need to configure manually
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Device: /dev/sdb [SAT], 8 Currently unreadable (pending) sectors
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Warning via /usr/share/smartmontools/smartd-runner to root produced unexpected output (183 bytes) to STDOUT/STDERR:
mai 27 18:42:20 cesar-ms7917 smartd[1068]: /etc/smartmontools/run.d/10mail:
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Your system does not have /usr/bin/mail. Install the mailx or mailutils package
mai 27 18:42:20 cesar-ms7917 smartd[1068]: run-parts: /etc/smartmontools/run.d/10mail exited with return code 1
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Warning via /usr/share/smartmontools/smartd-runner to root: failed (32-bit/8-bit exit status: 256/1)
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Device: /dev/sdb [SAT], 8 Offline uncorrectable sectors
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Warning via /usr/share/smartmontools/smartd-runner to root produced unexpected output (183 bytes) to STDOUT/STDERR:
mai 27 18:42:20 cesar-ms7917 smartd[1068]: /etc/smartmontools/run.d/10mail:
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Your system does not have /usr/bin/mail. Install the mailx or mailutils package
mai 27 18:42:20 cesar-ms7917 smartd[1068]: run-parts: /etc/smartmontools/run.d/10mail exited with return code 1
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Warning via /usr/share/smartmontools/smartd-runner to root: failed (32-bit/8-bit exit status: 256/1)
cesar@cesar-ms7917:~$cesar@cesar-ms7917:~$ journalctl --no-pager -b -n 100 -p warning
mai 27 18:42:17 cesar-ms7917 kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
mai 27 18:42:17 cesar-ms7917 kernel: pci 0000:04:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format)
mai 27 18:42:17 cesar-ms7917 kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
mai 27 18:42:17 cesar-ms7917 kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
mai 27 18:42:17 cesar-ms7917 kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
mai 27 18:42:17 cesar-ms7917 kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
mai 27 18:42:17 cesar-ms7917 kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
mai 27 18:42:17 cesar-ms7917 kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
mai 27 18:42:17 cesar-ms7917 kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
mai 27 18:42:17 cesar-ms7917 kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
mai 27 18:42:17 cesar-ms7917 kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
mai 27 18:42:17 cesar-ms7917 kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
mai 27 18:42:17 cesar-ms7917 kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
mai 27 18:42:17 cesar-ms7917 kernel: ata1.00: supports DRM functions and may not be fully accessible
mai 27 18:42:17 cesar-ms7917 kernel: ata1.00: NCQ Send/Recv Log not supported
mai 27 18:42:17 cesar-ms7917 kernel: ata1.00: supports DRM functions and may not be fully accessible
mai 27 18:42:17 cesar-ms7917 kernel: ata1.00: NCQ Send/Recv Log not supported
mai 27 18:42:17 cesar-ms7917 systemd-journald[344]: File /var/log/journal/97e6f75fb74e4b0e950ca1672030bb8c/system.journal corrupted or uncleanly shut down, renaming and replacing.
mai 27 18:42:17 cesar-ms7917 systemd-udevd[421]: /run/systemd/network/10-netplan-NM-99ea83e0-96ba-41a9-a462-17bf3e24d0b8.link: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add OriginalName=* in the [Match] section.
mai 27 18:42:17 cesar-ms7917 (udev-worker)[452]: sdb: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb' failed with exit code 1.
mai 27 18:42:17 cesar-ms7917 (udev-worker)[462]: sda: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda' failed with exit code 1.
mai 27 18:42:17 cesar-ms7917 (udev-worker)[462]: sda1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda1' failed with exit code 1.
mai 27 18:42:17 cesar-ms7917 (udev-worker)[438]: sda2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda2' failed with exit code 1.
mai 27 18:42:17 cesar-ms7917 (udev-worker)[462]: sdb1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb1' failed with exit code 1.
mai 27 18:42:17 cesar-ms7917 (udev-worker)[457]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
mai 27 18:42:18 cesar-ms7917 kernel: nvidia: loading out-of-tree module taints kernel.
mai 27 18:42:18 cesar-ms7917 kernel: nvidia: module license 'NVIDIA' taints kernel.
mai 27 18:42:18 cesar-ms7917 kernel: Disabling lock debugging due to kernel taint
mai 27 18:42:18 cesar-ms7917 kernel: nvidia: module license taints kernel.
mai 27 18:42:18 cesar-ms7917 kernel:
mai 27 18:42:18 cesar-ms7917 kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 550.144.03 Mon Dec 30 17:44:08 UTC 2024
mai 27 18:42:20 cesar-ms7917 (udev-worker)[460]: card2-DVI-I-2: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[468]: card1: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[469]: card2-HDMI-A-2: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[460]: card1-DVI-I-1: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[469]: card2-DP-2: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[460]: card1-HDMI-A-1: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[469]: card2-DVI-D-2: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[460]: card1-DP-1: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[460]: card1-DVI-D-1: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
mai 27 18:42:20 cesar-ms7917 (cron)[1047]: cron.service: Referenced but unset environment variable evaluates to an empty string: EXTRA_OPTS
mai 27 18:42:20 cesar-ms7917 (smartd)[1068]: smartmontools.service: Referenced but unset environment variable evaluates to an empty string: smartd_opts
mai 27 18:42:20 cesar-ms7917 thermald[1083]: NO RAPL sysfs present
mai 27 18:42:20 cesar-ms7917 thermald[1083]: NO RAPL sysfs present
mai 27 18:42:20 cesar-ms7917 thermald[1083]: Thermal DTS: No coretemp sysfs found
mai 27 18:42:20 cesar-ms7917 thermald[1083]: Thermal DTS or hwmon: No Zones present Need to configure manually
mai 27 18:42:20 cesar-ms7917 kernel: kauditd_printk_skb: 142 callbacks suppressed
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Device: /dev/sdb [SAT], 8 Currently unreadable (pending) sectors
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Warning via /usr/share/smartmontools/smartd-runner to root produced unexpected output (183 bytes) to STDOUT/STDERR:
mai 27 18:42:20 cesar-ms7917 smartd[1068]: /etc/smartmontools/run.d/10mail:
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Your system does not have /usr/bin/mail. Install the mailx or mailutils package
mai 27 18:42:20 cesar-ms7917 smartd[1068]: run-parts: /etc/smartmontools/run.d/10mail exited with return code 1
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Warning via /usr/share/smartmontools/smartd-runner to root: failed (32-bit/8-bit exit status: 256/1)
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Device: /dev/sdb [SAT], 8 Offline uncorrectable sectors
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Warning via /usr/share/smartmontools/smartd-runner to root produced unexpected output (183 bytes) to STDOUT/STDERR:
mai 27 18:42:20 cesar-ms7917 smartd[1068]: /etc/smartmontools/run.d/10mail:
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Your system does not have /usr/bin/mail. Install the mailx or mailutils package
mai 27 18:42:20 cesar-ms7917 smartd[1068]: run-parts: /etc/smartmontools/run.d/10mail exited with return code 1
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Warning via /usr/share/smartmontools/smartd-runner to root: failed (32-bit/8-bit exit status: 256/1)
mai 27 18:42:20 cesar-ms7917 systemd-udevd[421]: /run/systemd/network/10-netplan-NM-99ea83e0-96ba-41a9-a462-17bf3e24d0b8.link: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add OriginalName=* in the [Match] section.
mai 27 18:42:21 cesar-ms7917 systemd[1]: kerneloops.service: Found left-over process 1322 (kerneloops) in control group while starting unit. Ignoring.
mai 27 18:42:21 cesar-ms7917 systemd[1]: kerneloops.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
mai 27 18:42:21 cesar-ms7917 (rneloops)[1324]: kerneloops.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
mai 27 18:42:21 cesar-ms7917 systemd[1]: Cannot find unit for notify message of PID 1407, ignoring.
mai 27 18:42:24 cesar-ms7917 systemd-journald[344]: File /var/log/journal/97e6f75fb74e4b0e950ca1672030bb8c/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
mai 27 18:42:24 cesar-ms7917 pipewire[1486]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files
mai 27 18:42:24 cesar-ms7917 wireplumber[1488]: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
mai 27 18:42:24 cesar-ms7917 systemd-udevd[421]: /run/systemd/network/10-netplan-NM-99ea83e0-96ba-41a9-a462-17bf3e24d0b8.link: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add OriginalName=* in the [Match] section.
mai 27 18:42:24 cesar-ms7917 xdg-desktop-por[1644]: Choosing gtk.portal for org.freedesktop.impl.portal.Lockdown as a last-resort fallback
mai 27 18:42:24 cesar-ms7917 xdg-desktop-por[1644]: The preferred method to match portal implementations to desktop environments is to use the portals.conf(5) configuration file
mai 27 18:42:26 cesar-ms7917 org.kde.powerdevil.backlighthelper[1834]: org.kde.powerdevil: no kernel backlight interface found
mai 27 18:42:27 cesar-ms7917 systemd[1474]: app-nvidia\x2dsettings\x2dautostart@autostart.service: Failed with result 'exit-code'.
mai 27 18:42:28 cesar-ms7917 packagekitd[2040]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
mai 27 18:42:29 cesar-ms7917 packagekitd[2040]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
mai 27 18:42:29 cesar-ms7917 packagekitd[2040]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
cesar@cesar-ms7917:~$cesar@cesar-ms7917:~$ journalctl --no-pager -b -n 100 -p notice
mai 27 18:42:17 cesar-ms7917 systemd-journald[344]: File /var/log/journal/97e6f75fb74e4b0e950ca1672030bb8c/system.journal corrupted or uncleanly shut down, renaming and replacing.
mai 27 18:42:17 cesar-ms7917 systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway.
mai 27 18:42:17 cesar-ms7917 systemd-udevd[421]: /run/systemd/network/10-netplan-NM-99ea83e0-96ba-41a9-a462-17bf3e24d0b8.link: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add OriginalName=* in the [Match] section.
mai 27 18:42:17 cesar-ms7917 udevadm[435]: systemd-udev-settle.service is deprecated. Please fix sddm.service not to pull it in.
mai 27 18:42:17 cesar-ms7917 (udev-worker)[452]: sdb: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb' failed with exit code 1.
mai 27 18:42:17 cesar-ms7917 (udev-worker)[462]: sda: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda' failed with exit code 1.
mai 27 18:42:17 cesar-ms7917 (udev-worker)[462]: sda1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda1' failed with exit code 1.
mai 27 18:42:17 cesar-ms7917 (udev-worker)[438]: sda2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sda2' failed with exit code 1.
mai 27 18:42:17 cesar-ms7917 (udev-worker)[462]: sdb1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sdb1' failed with exit code 1.
mai 27 18:42:17 cesar-ms7917 (udev-worker)[457]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
mai 27 18:42:18 cesar-ms7917 kernel: nvidia: loading out-of-tree module taints kernel.
mai 27 18:42:18 cesar-ms7917 kernel: nvidia: module license 'NVIDIA' taints kernel.
mai 27 18:42:18 cesar-ms7917 kernel: Disabling lock debugging due to kernel taint
mai 27 18:42:18 cesar-ms7917 kernel: nvidia: module license taints kernel.
mai 27 18:42:18 cesar-ms7917 kernel:
mai 27 18:42:18 cesar-ms7917 kernel: audit: type=1400 audit(1748364138.503:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="Discord" pid=619 comm="apparmor_parser"
mai 27 18:42:18 cesar-ms7917 kernel: audit: type=1400 audit(1748364138.504:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="1password" pid=618 comm="apparmor_parser"
mai 27 18:42:18 cesar-ms7917 kernel: audit: type=1400 audit(1748364138.504:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="busybox" pid=625 comm="apparmor_parser"
mai 27 18:42:18 cesar-ms7917 kernel: audit: type=1400 audit(1748364138.504:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="QtWebEngineProcess" pid=621 comm="apparmor_parser"
mai 27 18:42:18 cesar-ms7917 kernel: audit: type=1400 audit(1748364138.504:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="buildah" pid=624 comm="apparmor_parser"
mai 27 18:42:18 cesar-ms7917 kernel: audit: type=1400 audit(1748364138.504:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="brave" pid=623 comm="apparmor_parser"
mai 27 18:42:18 cesar-ms7917 kernel: audit: type=1400 audit(1748364138.504:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name=4D6F6E676F444220436F6D70617373 pid=620 comm="apparmor_parser"
mai 27 18:42:18 cesar-ms7917 kernel: audit: type=1400 audit(1748364138.504:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="balena-etcher" pid=622 comm="apparmor_parser"
mai 27 18:42:18 cesar-ms7917 kernel: audit: type=1400 audit(1748364138.505:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="cam" pid=626 comm="apparmor_parser"
mai 27 18:42:18 cesar-ms7917 kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 550.144.03 Mon Dec 30 17:44:08 UTC 2024
mai 27 18:42:20 cesar-ms7917 (udev-worker)[460]: card2-DVI-I-2: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[468]: card1: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[469]: card2-HDMI-A-2: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[460]: card1-DVI-I-1: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[469]: card2-DP-2: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[460]: card1-HDMI-A-1: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[469]: card2-DVI-D-2: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[460]: card1-DP-1: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 (udev-worker)[460]: card1-DVI-D-1: Process '/bin/rm /dev/dri/card0' failed with exit code 1.
mai 27 18:42:20 cesar-ms7917 kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
mai 27 18:42:20 cesar-ms7917 anacron[1044]: Anacron 2.3 started on 2025-05-27
mai 27 18:42:20 cesar-ms7917 anacron[1044]: Will run job `cron.daily' in 5 min.
mai 27 18:42:20 cesar-ms7917 anacron[1044]: Will run job `cron.weekly' in 10 min.
mai 27 18:42:20 cesar-ms7917 anacron[1044]: Jobs will be executed sequentially
mai 27 18:42:20 cesar-ms7917 (cron)[1047]: cron.service: Referenced but unset environment variable evaluates to an empty string: EXTRA_OPTS
mai 27 18:42:20 cesar-ms7917 (smartd)[1068]: smartmontools.service: Referenced but unset environment variable evaluates to an empty string: smartd_opts
mai 27 18:42:20 cesar-ms7917 nvidia-persistenced[1075]: Started (1075)
mai 27 18:42:20 cesar-ms7917 udisksd[1085]: udisks daemon version 2.10.1 starting
mai 27 18:42:20 cesar-ms7917 thermald[1083]: NO RAPL sysfs present
mai 27 18:42:20 cesar-ms7917 thermald[1083]: 13 CPUID levels; family:model:stepping 0x6:3c:3 (6:60:3)
mai 27 18:42:20 cesar-ms7917 thermald[1083]: NO RAPL sysfs present
mai 27 18:42:20 cesar-ms7917 thermald[1083]: 13 CPUID levels; family:model:stepping 0x6:3c:3 (6:60:3)
mai 27 18:42:20 cesar-ms7917 thermald[1083]: Thermal DTS: No coretemp sysfs found
mai 27 18:42:20 cesar-ms7917 thermald[1083]: sensor id 2 : No temp sysfs for reading raw temp
mai 27 18:42:20 cesar-ms7917 thermald[1083]: sensor id 2 : No temp sysfs for reading raw temp
mai 27 18:42:20 cesar-ms7917 thermald[1083]: sensor id 2 : No temp sysfs for reading raw temp
mai 27 18:42:20 cesar-ms7917 thermald[1083]: Config file /etc/thermald/thermal-conf.xml does not exist
mai 27 18:42:20 cesar-ms7917 thermald[1083]: Config file /etc/thermald/thermal-conf.xml does not exist
mai 27 18:42:20 cesar-ms7917 thermald[1083]: Thermal DTS or hwmon: No Zones present Need to configure manually
mai 27 18:42:20 cesar-ms7917 thermald[1083]: Config file /etc/thermald/thermal-conf.xml does not exist
mai 27 18:42:20 cesar-ms7917 thermald[1083]: Polling mode is enabled: 4
mai 27 18:42:20 cesar-ms7917 kernel: kauditd_printk_skb: 142 callbacks suppressed
mai 27 18:42:20 cesar-ms7917 kernel: audit: type=1400 audit(1748364140.587:153): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="rsyslogd" pid=1103 comm="apparmor_parser"
mai 27 18:42:20 cesar-ms7917 polkitd[1060]: Loading rules from directory /etc/polkit-1/rules.d
mai 27 18:42:20 cesar-ms7917 polkitd[1060]: Loading rules from directory /usr/share/polkit-1/rules.d
mai 27 18:42:20 cesar-ms7917 polkitd[1060]: Finished loading, compiling and executing 9 rules
mai 27 18:42:20 cesar-ms7917 polkitd[1060]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
mai 27 18:42:20 cesar-ms7917 wpa_supplicant[1172]: Successfully initialized wpa_supplicant
mai 27 18:42:20 cesar-ms7917 ModemManager[1174]: <msg> ModemManager (version 1.23.4) starting in system bus...
mai 27 18:42:20 cesar-ms7917 udisksd[1085]: Acquired the name org.freedesktop.UDisks2 on the system message bus
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Device: /dev/sdb [SAT], 8 Currently unreadable (pending) sectors
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Warning via /usr/share/smartmontools/smartd-runner to root produced unexpected output (183 bytes) to STDOUT/STDERR:
mai 27 18:42:20 cesar-ms7917 smartd[1068]: /etc/smartmontools/run.d/10mail:
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Your system does not have /usr/bin/mail. Install the mailx or mailutils package
mai 27 18:42:20 cesar-ms7917 smartd[1068]: run-parts: /etc/smartmontools/run.d/10mail exited with return code 1
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Warning via /usr/share/smartmontools/smartd-runner to root: failed (32-bit/8-bit exit status: 256/1)
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Device: /dev/sdb [SAT], 8 Offline uncorrectable sectors
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Warning via /usr/share/smartmontools/smartd-runner to root produced unexpected output (183 bytes) to STDOUT/STDERR:
mai 27 18:42:20 cesar-ms7917 smartd[1068]: /etc/smartmontools/run.d/10mail:
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Your system does not have /usr/bin/mail. Install the mailx or mailutils package
mai 27 18:42:20 cesar-ms7917 smartd[1068]: run-parts: /etc/smartmontools/run.d/10mail exited with return code 1
mai 27 18:42:20 cesar-ms7917 smartd[1068]: Warning via /usr/share/smartmontools/smartd-runner to root: failed (32-bit/8-bit exit status: 256/1)
mai 27 18:42:20 cesar-ms7917 systemd-udevd[421]: /run/systemd/network/10-netplan-NM-99ea83e0-96ba-41a9-a462-17bf3e24d0b8.link: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add OriginalName=* in the [Match] section.
mai 27 18:42:21 cesar-ms7917 systemd[1]: kerneloops.service: Found left-over process 1322 (kerneloops) in control group while starting unit. Ignoring.
mai 27 18:42:21 cesar-ms7917 systemd[1]: kerneloops.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
mai 27 18:42:21 cesar-ms7917 (rneloops)[1324]: kerneloops.service: Referenced but unset environment variable evaluates to an empty string: DAEMON_ARGS
mai 27 18:42:21 cesar-ms7917 kernel: audit: type=1400 audit(1748364141.327:154): apparmor="DENIED" operation="capable" class="cap" profile="/usr/sbin/cupsd" pid=1309 comm="cupsd" capability=12 capname="net_admin"
mai 27 18:42:21 cesar-ms7917 systemd[1]: Cannot find unit for notify message of PID 1407, ignoring.
mai 27 18:42:24 cesar-ms7917 systemd-journald[344]: File /var/log/journal/97e6f75fb74e4b0e950ca1672030bb8c/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
mai 27 18:42:24 cesar-ms7917 pipewire[1486]: mod.jackdbus-detect: Failed to receive jackdbus reply: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files
mai 27 18:42:24 cesar-ms7917 wireplumber[1488]: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
mai 27 18:42:24 cesar-ms7917 wireplumber[1488]: PipeWire's libcamera SPA missing or broken. libcamera not supported.
mai 27 18:42:24 cesar-ms7917 wireplumber[1488]: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
mai 27 18:42:24 cesar-ms7917 wireplumber[1488]: BlueZ system service is not available
mai 27 18:42:24 cesar-ms7917 systemd-udevd[421]: /run/systemd/network/10-netplan-NM-99ea83e0-96ba-41a9-a462-17bf3e24d0b8.link: No valid settings found in the [Match] section, ignoring file. To match all interfaces, add OriginalName=* in the [Match] section.
mai 27 18:42:24 cesar-ms7917 xdg-desktop-por[1644]: Choosing gtk.portal for org.freedesktop.impl.portal.Lockdown as a last-resort fallback
mai 27 18:42:24 cesar-ms7917 xdg-desktop-por[1644]: The preferred method to match portal implementations to desktop environments is to use the portals.conf(5) configuration file
mai 27 18:42:26 cesar-ms7917 org.kde.powerdevil.backlighthelper[1834]: org.kde.powerdevil: no kernel backlight interface found
mai 27 18:42:26 cesar-ms7917 polkitd[1060]: Registered Authentication Agent for unix-session:1 (system bus name :1.62 [/usr/lib/x86_64-linux-gnu/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8)
mai 27 18:42:27 cesar-ms7917 systemd[1474]: app-nvidia\x2dsettings\x2dautostart@autostart.service: Main process exited, code=exited, status=1/FAILURE
mai 27 18:42:27 cesar-ms7917 systemd[1474]: app-nvidia\x2dsettings\x2dautostart@autostart.service: Failed with result 'exit-code'.
mai 27 18:42:28 cesar-ms7917 packagekitd[2040]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
mai 27 18:42:29 cesar-ms7917 packagekitd[2040]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
mai 27 18:42:29 cesar-ms7917 packagekitd[2040]: pk_package_set_update_severity: assertion 'update_severity == PK_INFO_ENUM_UNKNOWN || update_severity == PK_INFO_ENUM_LOW || update_severity == PK_INFO_ENUM_NORMAL || update_severity == PK_INFO_ENUM_IMPORTANT || update_severity == PK_INFO_ENUM_CRITICAL' failed
mai 27 18:42:51 cesar-ms7917 dbus-daemon[1048]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
cesar@cesar-ms7917:~$cesar@cesar-ms7917:~$ ls -l /var/crash
total 41844
-rw-r----- 1 cesar whoopsie 3367320 mai 20 20:06 _usr_bin_fcitx5.1000.crash
-rw-r----- 1 cesar whoopsie 7166522 mai 20 21:54 _usr_bin_kded5.1000.crash
-rw-r----- 1 cesar whoopsie 9262036 mai 19 19:03 _usr_bin_kwin_x11.1000.crash
-rw-r----- 1 root whoopsie 2363280 mai 19 19:49 _usr_libexec_packagekitd.0.crash
-rw-r----- 1 root whoopsie 299522 mai 19 22:02 _usr_lib_systemd_systemd-executor.0.crash
-rw-r----- 1 root whoopsie 1954415 mai 20 21:55 _usr_lib_x86_64-linux-gnu_libexec_org_kde_powerdevil.1000.crash
-rw-r----- 1 root whoopsie 12529659 mai 20 19:28 _usr_lib_xorg_Xorg.0.crash
-rw-r----- 1 root whoopsie 5887199 mai 19 20:54 _usr_share_apport_apport.0.crash
cesar@cesar-ms7917:~$steph810 a écrit :
geole a écrit :Bonjour
Donne ces retoursjournalctl --no-pager -b -n 100 -p errjournalctl --no-pager -b -n 100 -p warningjournalctl --no-pager -b -n 100 -p noticeJe me permet de raccourcir la commande uniquement pour le journal.
"-p, --priority=", "emerg" (0), "alert" (1), "crit" (2), "err" (3), "warning" (4), "notice" (5), "info" (6), "debug" (7) a écrit :journalctl --no-pager -b -n 100 -p3 -p4 -p5 | pastebinitsi le paquet pastebinit non installer installer le.
Partager le lien générer https.
Comme je disais plus tôt, je ne peux plus me connecter au réseau (alors que le même ordinateur accède à internet en bootant sur une live usb).
Merci beaucoup pour votre soutien.
Hors ligne
#28 Le 10/06/2025, à 10:20
- Ciseur68
Re : Problèmes après installation de Kubuntu 24.04
Bonjour @geole,
Une idée par rapport à mon retour ?
Hors ligne
#29 Le 10/06/2025, à 10:32
- iznobe
Re : Problèmes après installation de Kubuntu 24.04
Bonjour , montre :
sudo smartctl -s on -x /dev/sdbton disque dur sdb comporte des secteurs corrompus .
et
df -Thretour COMPLET et utilisable de commande | script montage partitions
MSI Z490A-pro , i7 10700 , 32 GB RAM .
Hors ligne
#30 Le 10/06/2025, à 15:39
- Ciseur68
Re : Problèmes après installation de Kubuntu 24.04
cesar@cesar-ms7917:~$ sudo smartctl -s on -x /dev/sdb
[sudo] Mot de passe de cesar :
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.11.0-26-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST2000DM001-1ER164
Serial Number: W4Z18N4R
LU WWN Device Id: 5 000c50 07d41832a
Firmware Version: CC25
User Capacity: 2000398934016 bytes [2,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database 7.3/5528
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Tue Jun 10 15:34:44 2025 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM level is: 254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is: Enabled
DSN feature is: Unavailable
ATA Security is: Disabled, frozen [SEC2]
Wt Cache Reorder: Unavailable
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 89) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 216) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x1085) SCT Status supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 113 094 006 - 57483792
3 Spin_Up_Time PO---- 096 096 000 - 0
4 Start_Stop_Count -O--CK 093 093 020 - 7826
5 Reallocated_Sector_Ct PO--CK 100 100 010 - 128
7 Seek_Error_Rate POSR-- 075 060 030 - 39581808
9 Power_On_Hours -O--CK 087 087 000 - 11426
10 Spin_Retry_Count PO--C- 100 100 097 - 0
12 Power_Cycle_Count -O--CK 097 097 020 - 3286
183 Runtime_Bad_Block -O--CK 100 100 000 - 0
184 End-to-End_Error -O--CK 100 100 099 - 0
187 Reported_Uncorrect -O--CK 001 001 000 - 365
188 Command_Timeout -O--CK 100 100 000 - 0 0 0
189 High_Fly_Writes -O-RCK 099 099 000 - 1
190 Airflow_Temperature_Cel -O---K 077 060 045 - 23 (Min/Max 20/23)
191 G-Sense_Error_Rate -O--CK 100 100 000 - 0
192 Power-Off_Retract_Count -O--CK 100 100 000 - 27
193 Load_Cycle_Count -O--CK 065 065 000 - 70600
194 Temperature_Celsius -O---K 023 040 000 - 23 (0 9 0 0 0)
197 Current_Pending_Sector -O--C- 100 100 000 - 8
198 Offline_Uncorrectable ----C- 100 100 000 - 8
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
240 Head_Flying_Hours ------ 100 253 000 - 5266h+58m+45.283s
241 Total_LBAs_Written ------ 100 253 000 - 34219876349
242 Total_LBAs_Read ------ 100 253 000 - 386560500217
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 5 Comprehensive SMART error log
0x03 GPL R/O 5 Ext. Comprehensive SMART error log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x21 GPL R/O 1 Write stream error log
0x22 GPL R/O 1 Read stream error log
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa1 GPL,SL VS 20 Device vendor specific log
0xa2 GPL VS 4496 Device vendor specific log
0xa8 GPL,SL VS 129 Device vendor specific log
0xa9 GPL,SL VS 1 Device vendor specific log
0xab GPL VS 1 Device vendor specific log
0xb0 GPL VS 5176 Device vendor specific log
0xbe-0xbf GPL VS 65535 Device vendor specific log
0xc0 GPL,SL VS 1 Device vendor specific log
0xc1 GPL,SL VS 10 Device vendor specific log
0xc3 GPL,SL VS 8 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
Device Error Count: 365 (device log contains only the most recent 20 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 365 [4] occurred at disk power-on lifetime: 11266 hours (469 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 a2 e1 4e 00 00 00 Error: UNC at LBA = 0xa2e14e00 = 2732674560
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 a2 e1 4e 00 40 00 07:52:46.181 READ FPDMA QUEUED
61 00 00 00 38 00 00 88 f0 3b 70 40 00 07:52:46.181 WRITE FPDMA QUEUED
61 00 00 00 80 00 00 64 66 f2 a0 40 00 07:52:46.181 WRITE FPDMA QUEUED
61 00 00 00 48 00 00 64 66 ea d8 40 00 07:52:46.180 WRITE FPDMA QUEUED
2f 00 00 00 01 00 00 00 00 00 10 28 00 07:52:45.940 READ LOG EXT
Error 364 [3] occurred at disk power-on lifetime: 11266 hours (469 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 a2 e1 4e 00 00 00 Error: UNC at LBA = 0xa2e14e00 = 2732674560
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 a2 e1 4e 00 40 00 07:52:42.320 READ FPDMA QUEUED
61 00 00 00 68 00 00 64 66 da 20 40 00 07:52:42.319 WRITE FPDMA QUEUED
61 00 00 00 80 00 00 64 66 f2 20 40 00 07:52:42.317 WRITE FPDMA QUEUED
61 00 00 01 00 00 00 64 66 f1 20 40 00 07:52:42.317 WRITE FPDMA QUEUED
61 00 00 01 00 00 00 64 66 f0 20 40 00 07:52:42.317 WRITE FPDMA QUEUED
Error 363 [2] occurred at disk power-on lifetime: 11266 hours (469 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 a2 e1 4e 00 00 00 Error: UNC at LBA = 0xa2e14e00 = 2732674560
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 a2 e1 4e 00 40 00 07:52:38.581 READ FPDMA QUEUED
61 00 00 00 80 00 00 64 66 c9 a0 40 00 07:52:38.579 WRITE FPDMA QUEUED
61 00 00 01 00 00 00 64 66 c8 a0 40 00 07:52:38.579 WRITE FPDMA QUEUED
61 00 00 00 08 00 00 00 5a 36 30 40 00 07:52:38.578 WRITE FPDMA QUEUED
61 00 00 01 00 00 00 64 66 c7 a0 40 00 07:52:38.578 WRITE FPDMA QUEUED
Error 362 [1] occurred at disk power-on lifetime: 11266 hours (469 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 a2 e1 4e 00 00 00 Error: UNC at LBA = 0xa2e14e00 = 2732674560
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 a2 e1 4e 00 40 00 07:52:34.748 READ FPDMA QUEUED
61 00 00 00 80 00 00 64 66 c2 20 40 00 07:52:34.747 WRITE FPDMA QUEUED
60 00 00 00 08 00 00 a2 e1 4d f8 40 00 07:52:34.747 READ FPDMA QUEUED
61 00 00 00 80 00 00 64 66 c1 20 40 00 07:52:34.744 WRITE FPDMA QUEUED
61 00 00 01 00 00 00 64 66 c0 20 40 00 07:52:34.744 WRITE FPDMA QUEUED
Error 361 [0] occurred at disk power-on lifetime: 11266 hours (469 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 a2 e1 4e 00 00 00 Error: UNC at LBA = 0xa2e14e00 = 2732674560
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 01 00 00 00 a2 e1 50 88 40 00 07:52:30.917 READ FPDMA QUEUED
60 00 00 01 00 00 00 a2 e1 4f 88 40 00 07:52:30.917 READ FPDMA QUEUED
60 00 00 01 00 00 00 a2 e1 4e 88 40 00 07:52:30.917 READ FPDMA QUEUED
60 00 00 01 00 00 00 a2 e1 4d 88 40 00 07:52:30.917 READ FPDMA QUEUED
61 00 00 00 80 00 00 88 f0 53 a8 40 00 07:52:30.915 WRITE FPDMA QUEUED
Error 360 [19] occurred at disk power-on lifetime: 11266 hours (469 days + 10 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 a2 e1 4e 00 00 00 Error: UNC at LBA = 0xa2e14e00 = 2732674560
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 01 00 00 00 a2 e1 50 88 40 00 07:52:26.748 READ FPDMA QUEUED
60 00 00 01 00 00 00 a2 e1 4f 88 40 00 07:52:26.748 READ FPDMA QUEUED
60 00 00 01 00 00 00 a2 e1 4e 88 40 00 07:52:26.748 READ FPDMA QUEUED
60 00 00 01 00 00 00 a2 e1 4d 88 40 00 07:52:26.748 READ FPDMA QUEUED
60 00 00 01 00 00 00 a2 e1 4c 88 40 00 07:52:26.748 READ FPDMA QUEUED
Error 359 [18] occurred at disk power-on lifetime: 9892 hours (412 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 a2 df 9b 48 00 00 Error: UNC at LBA = 0xa2df9b48 = 2732563272
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 01 00 00 00 a2 df a6 20 40 00 01:09:47.601 READ FPDMA QUEUED
60 00 00 01 00 00 00 a2 df a5 20 40 00 01:09:47.601 READ FPDMA QUEUED
60 00 00 01 00 00 00 a2 df a4 20 40 00 01:09:47.600 READ FPDMA QUEUED
60 00 00 01 00 00 00 a2 df a3 20 40 00 01:09:47.600 READ FPDMA QUEUED
60 00 00 01 00 00 00 a2 df a2 20 40 00 01:09:47.600 READ FPDMA QUEUED
Error 358 [17] occurred at disk power-on lifetime: 9825 hours (409 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 a3 19 48 f0 00 00 Error: UNC at LBA = 0xa31948f0 = 2736343280
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 15 5f dd c0 40 00 00:06:24.801 READ FPDMA QUEUED
60 00 00 00 08 00 00 15 5f dd 98 40 00 00:06:24.797 READ FPDMA QUEUED
60 00 00 00 08 00 00 a3 19 48 f0 40 00 00:06:24.794 READ FPDMA QUEUED
60 00 00 00 08 00 00 15 5f dd 90 40 00 00:06:24.793 READ FPDMA QUEUED
60 00 00 00 08 00 00 15 5f dd 88 40 00 00:06:24.792 READ FPDMA QUEUED
SMART Extended Self-test Log Version: 1 (1 sectors)
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
SCT Status Version: 3
SCT Version (vendor specific): 522 (0x020a)
Device State: Active (0)
Current Temperature: 22 Celsius
Power Cycle Min/Max Temperature: 20/22 Celsius
Lifetime Min/Max Temperature: 8/39 Celsius
Under/Over Temperature Limit Count: 0/0
SCT Data Table command not supported
SCT Error Recovery Control command not supported
Device Statistics (GP/SMART Log 0x04) not supported
Pending Defects log (GP Log 0x0c) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x000a 2 2 Device-to-host register FISes sent due to a COMRESET
0x0001 2 0 Command failed due to ICRC error
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
cesar@cesar-ms7917:~$cesar@cesar-ms7917:~$ df -Th
Sys. de fichiers Type Taille Utilisé Dispo Uti% Monté sur
tmpfs tmpfs 1,6G 1,5M 1,6G 1% /run
/dev/sda2 ext4 228G 14G 203G 7% /
tmpfs tmpfs 7,8G 0 7,8G 0% /dev/shm
tmpfs tmpfs 5,0M 0 5,0M 0% /run/lock
efivarfs efivarfs 128K 105K 19K 86% /sys/firmware/efi/efivars
tmpfs tmpfs 7,8G 12K 7,8G 1% /tmp
/dev/sda1 vfat 300M 6,2M 294M 3% /boot/efi
tmpfs tmpfs 1,6G 88K 1,6G 1% /run/user/1000
cesar@cesar-ms7917:~$Hors ligne
#31 Le 10/06/2025, à 16:01
- iznobe
Re : Problèmes après installation de Kubuntu 24.04
ton disque SDB a bien subi des erreurs .
il faudrait voir ce qu ' en pense @geole ou quelqu ' un de mieux placé que moi a ce niveau là .
Mais comme tu n' utilises à priori pas ce disque pour ubuntu , ca devrait ne rien à voir avec ton probleme actuel .
retour COMPLET et utilisable de commande | script montage partitions
MSI Z490A-pro , i7 10700 , 32 GB RAM .
Hors ligne
#32 Le 10/06/2025, à 16:03
- geole
Re : Problèmes après installation de Kubuntu 24.04
Ciseur68 a écrit :
Bonjour @geole,
Une idée par rapport à mon retour ?
Bonjour
Je n ai rien vu qui pourrait expliquer les crashs.
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne