Regarding the dmesg output.
On Tuesday, 3 September 2024 19:49:12 AEST Andrew Greig wrote: > [ 2.671616] UBSAN: shift-out-of-bounds in > /build/linux-3d8Wab/linux-5.15.0/drivers/scsi/aic7xxx/aic7xxx_core.c:5281:31 > [ 2.671623] shift exponent -1 is negative Are you using SCSI disks on an Adaptec controller? If so this could be related to the problem. https://wiki.ubuntu.com/Kernel/Bugs In any case this is something to report as a bug to Ubuntu. [ 11.871269] BTRFS info (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 3, gen 0 [ 78.057485] BTRFS warning (device sda3): checksum verify failed on 231866368 wanted 0x34378b97 found 0x9bed8a68 level 0 [ 79.482363] BTRFS warning (device sda3): checksum verify failed on 231866368 wanted 0x34378b97 found 0x9bed8a68 level 0 This is the cause of your problem. Your sda device has corruption and BTRFS recognises it and gives an IO error as opposed to Ext4 and other lesser filesystems that will just return bad data. # btrfs fi df / Data, RAID1: total=718.22GiB, used=668.40GiB System, RAID1: total=32.00MiB, used=160.00KiB Metadata, RAID1: total=8.00GiB, used=4.74GiB GlobalReserve, single: total=512.00MiB, used=0.00B Above is an example of a system running BTRFS RAID-1, what does it give on your system? # btrfs dev sta / [/dev/mapper/root0].write_io_errs 0 [/dev/mapper/root0].read_io_errs 0 [/dev/mapper/root0].flush_io_errs 0 [/dev/mapper/root0].corruption_errs 0 [/dev/mapper/root0].generation_errs 0 [/dev/mapper/root1].write_io_errs 0 [/dev/mapper/root1].read_io_errs 0 [/dev/mapper/root1].flush_io_errs 0 [/dev/mapper/root1].corruption_errs 0 [/dev/mapper/root1].generation_errs 0 Above is an example of the command to get the statistics of devices in a BTRFS filesystem, you hope for all zeros as in the above example but from the dmesg output it looks like sda3 will have a corruption count of at least 5. After we solve the BTRFS issues (get it into a good RAID-1 state) the next issue is fixing the dpkg setup. Run "sudo rm -f /var/lib/dpkg/info/mutter-common.list" then run "sudo apt --reinstall install mutter-common" and then after that your system should be in a reasonable state. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ _______________________________________________ luv-main mailing list -- [email protected] To unsubscribe send an email to [email protected]
