[Risolto] kubuntu 24.04.1 errore I/O

[massipinam]

Ciao, ho aggiornato 10gg fa kubuntu a 24.04.1 kernel 6.8.0-44 e da allora il sistema monta i dischi, con Dolphin vedo tutte le cartelle ma non apre i documenti, foto, pdf etc che ho in due dischi esterni per i salvataggi con errore generale di I/O. Nel vecchio pc con la versione precedente kernel 5.15.0-119 nessun problema li monta e vi accedo normalmente con Dolphin. Cosa devo modificare? In blkid il disco che non riesco a leggere è maxseagate new

Codice: Seleziona tutto

root@massimo-HP-Laptop-15s:~# blkid
/dev/nvme0n1p3: UUID="9ebc8cd3-cfd2-4cbe-b4c9-62cf4515c0c5" TYPE="swap" PARTUUID="707b129f-b14a-4dfb-b152-69b60b055052"
/dev/nvme0n1p4: UUID="ee2e22f2-6bc5-4dec-bc8a-10b71eb1c421" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0de76311-6be3-4178-8f91-ed61d190e787"
/dev/loop29: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop19: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/nvme0n1p5: UUID="62315e57-395d-49b2-a825-480e6ffa71d5" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="f2bb815f-61f3-4850-a5a5-729fbff60579"
/dev/nvme0n1p1: LABEL="SYSTEM" UUID="1C0A-FAD9" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="26005e10-f350-4f35-ab31-cccf2c0524c2"
/dev/nvme0n1p2: UUID="9053-407C" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="0bed1f02-711a-470e-983f-5b170757227f"
/dev/loop27: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop17: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop8: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop25: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/sdb1: LABEL="maxseagate new" UUID="3d3b9c79-2fba-42dc-9892-f75d7772e045" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="3e2bedae-76e5-c74d-9118-78b9e711f970"
/dev/loop15: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop6: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop23: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop13: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop4: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop21: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop11: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop2: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop28: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop18: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop9: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop26: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop16: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop7: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop24: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/sda1: LABEL="Max ssd" BLOCK_SIZE="512" UUID="4212979112978915" TYPE="ntfs" PARTUUID="02004441-a781-9746-8b84-e9df013ee6a5"
/dev/loop14: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop5: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop22: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop12: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop3: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop30: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop20: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop10: BLOCK_SIZE="131072" TYPE="squashfs"

Codice: Seleziona tutto

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p4 during installation
UUID=ee2e22f2-6bc5-4dec-bc8a-10b71eb1c421 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p2 during installation
UUID=9053-407C  /boot/efi       vfat    umask=0077      0       1
# /home was on /dev/nvme0n1p5 during installation
UUID=62315e57-395d-49b2-a825-480e6ffa71d5 /home           ext4    defaults        0       2
# swap was on /dev/nvme0n1p3 during installation
UUID=9ebc8cd3-cfd2-4cbe-b4c9-62cf4515c0c5 none            swap    sw              0       0

[OMBRA_Linux]

Prima di tutto aggiorna tutto con:

Codice: Seleziona tutto

sudo apt update
sudo apt upgrade

Dopo di che posta l'output di questo comando:

Codice: Seleziona tutto

dmesg | grep -i error

[steff]

Includi per favore il listato tra tag codice.
Puoi provare la voce "verifica" nel editor di partizione KDE per /dev/sdb1, devi cliccare "applica" anche.

[massipinam]

Prima di tutto aggiorna tutto con:

Codice: Seleziona tutto

sudo apt update
sudo apt upgrade

Dopo di che posta l'output di questo comando:

Codice: Seleziona tutto

dmesg | grep -i error

Eccolo

Codice: Seleziona tutto

root@massimo-HP-Laptop-15s:~# dmesg | grep -i error
[    0.276038] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.28.EC0], AE_NOT_FOUND (20230628/dswload2-162)
[    0.276046] ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230628/psobject-220)
[    0.760837] RAS: Correctable Errors collector initialized.
[11164.511049] traps: kscreenlocker_g[10208] general protection fault ip:7f666fe9f578 sp:7ffd46e76bd8 error:0 in libQt5Qml.so.5.15.13[7f666fca0000+30d000]
[11618.910138] EXT4-fs (sdb1): warning: mounting fs with errors, running e2fsck is recommended
[11620.342277] EXT4-fs error (device sdb1): ext4_validate_block_bitmap:423: comm ext4lazyinit: bg 781: bad block bitmap checksum
[11691.273598] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[12111.057928] EXT4-fs warning (device sdb1): ext4_clear_journal_err:6289: Filesystem error recorded from previous mount: IO failure
[12111.100032] EXT4-fs (sdb1): warning: mounting fs with errors, running e2fsck is recommended
[12116.763164] EXT4-fs error (device sdb1): ext4_validate_block_bitmap:423: comm ext4lazyinit: bg 781: bad block bitmap checksum
[12423.758828] EXT4-fs (sdb1): error count since last fsck: 160
[12423.758849] EXT4-fs (sdb1): initial error at time 1650607410: ext4_validate_block_bitmap:385
[12423.758860] EXT4-fs (sdb1): last error at time 1726067088: ext4_validate_block_bitmap:423
[13443.079175] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[13463.231796] EXT4-fs warning (device sdb1): ext4_clear_journal_err:6289: Filesystem error recorded from previous mount: IO failure
[13463.274073] EXT4-fs (sdb1): warning: mounting fs with errors, running e2fsck is recommended
[13465.655523] EXT4-fs error (device sdb1): ext4_validate_block_bitmap:423: comm ext4lazyinit: bg 781: bad block bitmap checksum
[13767.229586] EXT4-fs (sdb1): error count since last fsck: 161
[13767.229630] EXT4-fs (sdb1): initial error at time 1650607410: ext4_validate_block_bitmap:385
[13767.229649] EXT4-fs (sdb1): last error at time 1726068437: ext4_validate_block_bitmap:423
[14941.089512] sd 2:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=3s
[14941.089525] I/O error, dev sdc, sector 2048 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[14941.089574] device offline error, dev sdc, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[14941.089584] Buffer I/O error on dev sdc1, logical block 0, async page read
[14945.314475] sd 2:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[14945.314760] device offline error, dev sdc, sector 1953519600 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[14945.314809] device offline error, dev sdc, sector 1953519600 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[14945.314820] Buffer I/O error on dev sdc1, logical block 244189694, async page read
[16149.819195] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[16168.746633] EXT4-fs warning (device sdb1): ext4_clear_journal_err:6289: Filesystem error recorded from previous mount: IO failure
[16168.783145] EXT4-fs (sdb1): warning: mounting fs with errors, running e2fsck is recommended
[16172.269756] EXT4-fs error (device sdb1): ext4_validate_block_bitmap:423: comm ext4lazyinit: bg 781: bad block bitmap checksum
[16486.940324] EXT4-fs (sdb1): error count since last fsck: 162
[16486.940350] EXT4-fs (sdb1): initial error at time 1650607410: ext4_validate_block_bitmap:385
[16486.940364] EXT4-fs (sdb1): last error at time 1726071143: ext4_validate_block_bitmap:423
[16775.494931] sd 1:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK

[massipinam]

e2fsck -p e tutto si è risolto positivamente. Rimane per me un mistero che con la release precedente i file dei dischi corrotti venivano caricati ed aperti correttamente

[OMBRA_Linux]

Va benissimo che hai risolto.
Comunque dagli errori riportati si nota che

1° ACPI BIOS Error.
Questo errore indica che il BIOS non riesce a risolvere un simbolo specifico e che potrebbe essere utile aggiornare il BIOS quindi un controllo io lo farei.

2°General Protection Fault in kscreenlocker_g
Questo errore potrebbe essere causato da un problema con la libreria libQt5Qml.so.5.15.13.
Qui puoi provare a reinstallare il pacchetto Qt5 con:

Codice: Seleziona tutto

sudo apt-get install --reinstall libqt5qml5

3° EXT4-fs Errors.
Gli errori relativi al filesystem EXT4 indicano che ci sono problemi con il disco sdb1.
Quindi è consigliabile eseguire ''e2fsck'' per controllare e riparare il filesystem con:

Codice: Seleziona tutto

sudo e2fsck -f /dev/sdb1

4° I/O Errors on sdc.
Gli errori di I/O sul disco sdc indicano che il dispositivo potrebbe avere problemi hardware.
Quindi prova a scollegare e ricollegare il disco, oppure verifica se ci sono aggiornamenti firmware disponibili per il disco.

5° Synchronize Cache Failed.
Quest'altro errore può essere correlato ai problemi di I/O.
Quindi se l'errore persiste, potrebbe essere necessario sostituire il disco.

Edit: Nel tuo caso specifico andava fatto un e2fsck.

Ora che hai risolto ridai quel comando per vedere se da sempre gli stessi errori.