I couldn't do anything after fstrim.
I have reinstalled util-linux which contains fstrim and now fstrim does not blow up the machine.
I guess I will find out for certain next Monday whether it crashes when next triggered by fstrim.timer
Edit: I lied. The command now completes but the machine has crashed.
I have reinstalled util-linux which contains fstrim and now fstrim does not blow up the machine.
Code:
sudo fstrim -av/boot/firmware: 442.9 MiB (464455680 bytes) trimmed on /dev/mmcblk0p1/: 8.1 GiB (8684417024 bytes) trimmed on /dev/mmcblk0p2Edit: I lied. The command now completes but the machine has crashed.
Code:
[ 164.575384] mmc_erase: erase error -110, status 0x800[ 165.938782] mmc0: card never left busy state[ 165.938802] mmc0: tried to HW reset card, got error -110[ 165.938816] I/O error, dev mmcblk0, sector 33486448 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 2[ 165.941931] mmc_erase: group start error -123, status 0x0[ 165.941949] I/O error, dev mmcblk0, sector 33701888 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2[ 165.942039] Aborting journal on device mmcblk0p2-8.[ 165.942084] mmc0: card 0001 removed[ 165.942130] JBD2: I/O error when updating journal superblock for mmcblk0p2-8.[ 165.942159] EXT4-fs error (device mmcblk0p2): ext4_journal_check_start:84: comm systemd-journal: Detected aborted journal[ 165.942295] EXT4-fs (mmcblk0p2): I/O error while writing superblock[ 165.942309] EXT4-fs (mmcblk0p2): Remounting filesystem read-only[ 166.074422] EXT4-fs warning (device mmcblk0p2): dx_probe:822: inode #4034: lblock 0: comm systemd-udevd: error -5 reading directory block[ 167.452429] mmc0: card never left busy state[ 167.452444] mmc0: error -110 whilst initialising SD card[ 168.835381] mmc0: card never left busy state[ 168.835394] mmc0: error -110 whilst initialising SD card[ 170.256609] mmc0: card never left busy state[ 170.256625] mmc0: error -110 whilst initialising SD card[ 171.616750] mmc0: card never left busy state[ 171.616775] mmc0: error -110 whilst initialising SD card[ 171.904220] EXT4-fs warning (device mmcblk0p2): dx_probe:822: inode #125441: lblock 0: comm systemd-journal: error -5 reading directory block[ 173.001396] mmc0: card never left busy state[ 173.001417] mmc0: error -110 whilst initialising SD card[ 174.428846] mmc0: card never left busy state[ 174.428869] mmc0: error -110 whilst initialising SD card[ 176.818694] mmc0: card never left busy state[ 176.818717] mmc0: error -110 whilst initialising SD card[ 178.206246] mmc0: card never left busy state[ 178.206267] mmc0: error -110 whilst initialising SD card[ 179.637342] mmc0: card never left busy state[ 179.637365] mmc0: error -110 whilst initialising SD card[ 182.033232] mmc0: card never left busy state[ 182.033256] mmc0: error -110 whilst initialising SD card[ 183.416069] mmc0: card never left busy state[ 183.416093] mmc0: error -110 whilst initialising SD card[ 184.848228] mmc0: card never left busy state[ 184.848248] mmc0: error -110 whilst initialising SD card[ 187.217239] mmc0: card never left busy state[ 187.217263] mmc0: error -110 whilst initialising SD card[ 188.607077] mmc0: card never left busy state[ 188.607099] mmc0: error -110 whilst initialising SD card[ 190.038171] mmc0: card never left busy state[ 190.038188] mmc0: error -110 whilst initialising SD card[ 192.433841] mmc0: card never left busy state[ 192.433864] mmc0: error -110 whilst initialising SD card[ 193.821774] mmc0: card never left busy state[ 193.821791] mmc0: error -110 whilst initialising SD card[ 195.253024] mmc0: card never left busy state[ 195.253046] mmc0: error -110 whilst initialising SD card[ 197.649688] mmc0: card never left busy state[ 197.649708] mmc0: error -110 whilst initialising SD card[ 199.033031] mmc0: card never left busy stateStatistics: Posted by MotoBlue — Mon Mar 18, 2024 8:57 pm