Netflix, Aussie Addons, Oz Weather, Embuary Info, Cu LRC Lyrics - Python exceptions

    Hi

    I had a power outage 2 days ago and my LibreElec box didn't shutdown gracefully. The subsequent restart prompted me to allow the filesystem to be repaired, which I allowed to occur. The OS then restarted. On the face of it, the system seemed ok, however a number of Addons that were working fine prior to the power outage have stopped functioning.

    Seeking assistance to determine the issue. Have I lost Python files?


    Log is attached. positive-deer.log.txt.zip

    First of all, for future reference. Make a backup once in a while. I do it every other week for LE.

    You can find all installed/downloaded packages under /storage/.kodi/addons/packages.

    Make a LE backup first and then try installing them manually one-by-one (pick lastest version)

    Quote from dartheejit

    Log is attached. positive-deer.log.txt.zip

    Why!??? .. all you had to do was share the URL the paste function generated (https://paste.libreelec.tv/positive-deer.log) which shows the filesystem on the USB drive was force-checked:

    but even with fsck there's loads of this:

    Code
    Apr 06 07:30:55.157302 LibreELEC kernel: sd 4:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Apr 06 07:30:55.157923 LibreELEC kernel: sd 4:0:0:0: [sda] tag#0 Sense Key : 0x3 [current] 
Apr 06 07:30:55.158357 LibreELEC kernel: sd 4:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0 
Apr 06 07:30:55.158758 LibreELEC kernel: sd 4:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 02 11 42 88 00 00 08 00
Apr 06 07:30:55.159165 LibreELEC kernel: critical medium error, dev sda, sector 34685576 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 2
Apr 06 07:30:55.159217 LibreELEC kernel: EXT4-fs error (device sda2): __ext4_find_entry:1683: inode #1051944: comm mount-swap: reading directory lblock 0

    And then:

    Code
    Apr 06 07:31:07.955704 kodiLounge kernel: EXT4-fs error (device sda2): __ext4_find_entry:1683: inode #1052028: comm kodi.bin: reading directory lblock 0
Apr 06 07:31:08.000646 kodiLounge kernel: EXT4-fs error (device sda2): __ext4_find_entry:1694: inode #1052028: comm kodi.bin: checksumming directory block 0
Apr 06 07:31:10.457599 kodiLounge kernel: EXT4-fs error (device sda2): htree_dirblock_to_tree:1083: inode #1052028: comm kodi.bin: Directory block failed checksum
Apr 06 07:31:13.098569 kodiLounge kernel: EXT4-fs error (device sda2): __ext4_find_entry:1694: inode #1052028: comm kodi.bin: checksumming directory block 0
Apr 06 07:31:13.191377 kodiLounge kernel: EXT4-fs error (device sda2): __ext4_find_entry:1694: inode #1052028: comm kodi.bin: checksumming directory block 0
Apr 06 07:31:13.260223 kodiLounge kernel: EXT4-fs error (device sda2): __ext4_find_entry:1694: inode #1052028: comm kodi.bin: checksumming directory block 0
Apr 06 07:31:13.308411 kodiLounge kernel: EXT4-fs error (device sda2): htree_dirblock_to_tree:1083: inode #1052028: comm kodi.bin: Directory block failed checksum
Apr 06 07:31:13.355379 kodiLounge kernel: EXT4-fs error (device sda2): __ext4_find_entry:1694: inode #1052028: comm kodi.bin: checksumming directory block 0

    So the USB drive is bad (critical medium error) and this impacts data read from /dev/sda2 which is mounted as /storage. I think it is unlikely that the power outage caused the issue. It's more likely the drive went bad all on its own, but the outage results in unclean shutdown of the filesystem so the filesystem is in a 'dirty' state causing fsck to be run on boot, and this then finds or runs into the underlying media problem. On a memory device medium errors are failed cells in the flash memory chip that's inside.

    I wouldn't waste time attempting to repair the USB drive as once cells start to fail the only outcome is more cells failing. If it's still possible (not guaranteed) you can backup the essential Kodi userdata like sources.xml, passwords.xml, DB files, and add-on settings files somewhere. Then make a clean install on a replacement USB drive, stop Kodi, and copy the userdata bits back.