-- Logs begin at Thu 2019-02-14 13:11:58 MSK, end at Sun 2024-04-28 16:07:08 MSK. -- Apr 28 16:06:21 volumio-nvme ntpd[783]: receive: Unexpected origin timestamp 0xe9d7a2f9.207d8b36 does not match aorg 0000000000.00000000 from server@85.21.78.91 xmt 0xe9d8c84d.21443103 Apr 28 16:06:21 volumio-nvme ntpd[783]: receive: Unexpected origin timestamp 0xe9d7a2f9.207cea81 does not match aorg 0000000000.00000000 from server@213.33.141.134 xmt 0xe9d8c84d.2293c8eb Apr 28 16:06:21 volumio-nvme ntpd[783]: receive: Unexpected origin timestamp 0xe9d7a2f9.207bfc8b does not match aorg 0000000000.00000000 from server@193.192.36.3 xmt 0xe9d8c84d.2118cdef Apr 28 16:06:23 volumio-nvme ntpd[783]: receive: Unexpected origin timestamp 0xe9d7a2f9.207e48c5 does not match aorg 0000000000.00000000 from server@94.247.111.10 xmt 0xe9d8c84d.25e175b1 Apr 28 16:06:23 volumio-nvme ntpd[783]: receive: Unexpected origin timestamp 0xe9d7a2f9.207f054b does not match aorg 0xe9d8c84f.29c3f879 from server@192.36.143.130 xmt 0xe9d8c84d.25fd016c Apr 28 16:06:28 volumio-nvme kernel: nvme0n1: I/O Cmd(0x2) @ LBA 416854152, 40 blocks, I/O Error (sct 0x3 / sc 0x71) Apr 28 16:06:28 volumio-nvme kernel: I/O error, dev nvme0n1, sector 416854152 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2 Apr 28 16:06:28 volumio-nvme kernel: nvme0n1: I/O Cmd(0x2) @ LBA 416781480, 8 blocks, I/O Error (sct 0x3 / sc 0x71) Apr 28 16:06:28 volumio-nvme kernel: I/O error, dev nvme0n1, sector 416781480 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Apr 28 16:06:28 volumio-nvme kernel: nvme0n1: I/O Cmd(0x2) @ LBA 418354272, 256 blocks, I/O Error (sct 0x3 / sc 0x71) Apr 28 16:06:28 volumio-nvme kernel: I/O error, dev nvme0n1, sector 418354272 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 2 Apr 28 16:06:28 volumio-nvme kernel: nvme0n1: I/O Cmd(0x2) @ LBA 418345720, 176 blocks, I/O Error (sct 0x3 / sc 0x71) Apr 28 16:06:28 volumio-nvme kernel: I/O error, dev nvme0n1, sector 418345720 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Apr 28 16:06:28 volumio-nvme kernel: nvme0n1: I/O Cmd(0x2) @ LBA 418322712, 80 blocks, I/O Error (sct 0x3 / sc 0x71) Apr 28 16:06:28 volumio-nvme kernel: I/O error, dev nvme0n1, sector 418322712 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 Apr 28 16:06:28 volumio-nvme volumio[1071]: error: error Apr 28 16:06:28 volumio-nvme systemd[1]: Starting Daily man-db regeneration... Apr 28 16:06:28 volumio-nvme kernel: nvme 0000:01:00.0: Unable to change power state from D3cold to D0, device inaccessible Apr 28 16:06:31 volumio-nvme systemd[1]: Starting Daily apt download activities... Apr 28 16:06:31 volumio-nvme kernel: nvme nvme0: Removing after probe failure status: -19 Apr 28 16:06:31 volumio-nvme volumio[1071]: info: Discovery: A device disappeared from network Apr 28 16:06:31 volumio-nvme volumio[1071]: Upnp client error: Error: This socket has been ended by the other party Apr 28 16:06:31 volumio-nvme volumio[1071]: info: Discovery: A device disappeared from network Apr 28 16:06:31 volumio-nvme kernel: nvme0n1: detected capacity change from 500118192 to 0 Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12976503: lblock 0: comm crashpad_handle: error -5 reading directory block Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12976638: comm ThreadPoolForeg: reading directory lblock 0 Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12976504: lblock 0: comm crashpad_handle: error -5 reading directory block Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): ext4_end_bio:347: I/O error 10 writing to inode 12845260 starting block 53088782) Apr 28 16:06:31 volumio-nvme kernel: Buffer I/O error on device nvme0n1p3, logical block 52405262 Apr 28 16:06:31 volumio-nvme kernel: Aborting journal on device nvme0n1p3-8. Apr 28 16:06:31 volumio-nvme kernel: Buffer I/O error on dev nvme0n1p3, logical block 30441472, lost sync page write Apr 28 16:06:31 volumio-nvme kernel: JBD2: I/O error when updating journal superblock for nvme0n1p3-8. Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): ext4_journal_check_start:83: comm node: Detected aborted journal Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5868: Journal has aborted Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): ext4_journal_check_start:83: comm crashpad_handle: Detected aborted journal Apr 28 16:06:31 volumio-nvme kernel: Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): ext4_journal_check_start:83: comm node: Detected aborted journal Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): ext4_dirty_inode:6072: inode #12976619: comm ThreadPoolForeg: mark_inode_dirty error Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12976638: comm ThreadPoolForeg: reading directory lblock 0 Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs (nvme0n1p3): I/O error while writing superblock Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3) in ext4_dirty_inode:6073: Journal has aborted Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs (nvme0n1p3): previous I/O error to superblock detected Apr 28 16:06:31 volumio-nvme kernel: Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): ext4_journal_check_start:83: comm ThreadPoolForeg: Detected aborted journal Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs (nvme0n1p3): previous I/O error to superblock detected Apr 28 16:06:31 volumio-nvme kernel: Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs (nvme0n1p3): I/O error while writing superblock Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs (nvme0n1p3): Remounting filesystem read-only Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs (nvme0n1p3): Remounting filesystem read-only Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12976505: lblock 0: comm crashpad_handle: error -5 reading directory block Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12976506: lblock 0: comm crashpad_handle: error -5 reading directory block Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12976504: lblock 0: comm crashpad_handle: error -5 reading directory block Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12976505: lblock 0: comm crashpad_handle: error -5 reading directory block Apr 28 16:06:31 volumio-nvme kernel: Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs (nvme0n1p3): I/O error while writing superblock Apr 28 16:06:31 volumio-nvme kernel: Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs (nvme0n1p3): I/O error while writing superblock Apr 28 16:06:31 volumio-nvme kernel: Buffer I/O error on dev nvme0n1p3, logical block 51380242, lost async page write Apr 28 16:06:31 volumio-nvme kernel: Buffer I/O error on dev nvme0n1p3, logical block 51380260, lost async page write Apr 28 16:06:31 volumio-nvme kernel: Buffer I/O error on dev nvme0n1p3, logical block 51380262, lost async page write Apr 28 16:06:31 volumio-nvme kernel: Buffer I/O error on dev nvme0n1p3, logical block 51380263, lost async page write Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5868: Journal has aborted Apr 28 16:06:31 volumio-nvme nmbd[1745]: [2024/04/28 16:06:31.326915, 0] ../source3/nmbd/nmbd_winsserver.c:2508(wins_write_database) Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs (nvme0n1p3): I/O error while writing superblock Apr 28 16:06:31 volumio-nvme nmbd[1745]: wins_write_database: Can't open /var/lib/samba/wins.dat.1745: Read-only file system Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs (nvme0n1p3): previous I/O error to superblock detected Apr 28 16:06:31 volumio-nvme winbindd[1730]: [2024/04/28 16:06:31.334446, 0] ../source3/lib/util.c:493(reinit_after_fork) Apr 28 16:06:31 volumio-nvme smbd[1742]: [2024/04/28 16:06:31.334502, 0] ../source3/lib/util.c:493(reinit_after_fork) Apr 28 16:06:31 volumio-nvme nmbd[1744]: [2024/04/28 16:06:31.335571, 0] ../source3/lib/util.c:493(reinit_after_fork) Apr 28 16:06:31 volumio-nvme winbindd[1730]: messaging_reinit() failed: NT_STATUS_MEDIA_WRITE_PROTECTED Apr 28 16:06:31 volumio-nvme smbd[1742]: messaging_reinit() failed: NT_STATUS_MEDIA_WRITE_PROTECTED Apr 28 16:06:31 volumio-nvme nmbd[1744]: messaging_reinit() failed: NT_STATUS_MEDIA_WRITE_PROTECTED Apr 28 16:06:31 volumio-nvme systemd[1740]: apt-daily.service: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1740]: apt-daily.service: Failed at step EXEC spawning /usr/lib/apt/apt-helper: Input/output error Apr 28 16:06:31 volumio-nvme kernel: I/O error, dev loop0, sector 476896 op 0x0:(READ) flags 0x800 phys_seg 13 prio class 2 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0xe8dc205: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read fragment cache entry [e8dc205] Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read fragment cache entry [e8dc205] Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read page, block e8dc205, size c1c7 Apr 28 16:06:31 volumio-nvme volumio[1071]: info: Discovery: adding 93bc908e-dfb8-455e-9574-6dafc5ba46c4 Apr 28 16:06:31 volumio-nvme volumio[1071]: info: Discovery: Found device Volumio NVME Apr 28 16:06:31 volumio-nvme volumio[1071]: info: CoreCommandRouter::volumioGetState Apr 28 16:06:31 volumio-nvme volumio[1071]: info: Discovery: this is already registered, 93bc908e-dfb8-455e-9574-6dafc5ba46c4 Apr 28 16:06:31 volumio-nvme volumio[1071]: info: Discovery: Found device Volumio NVME Apr 28 16:06:31 volumio-nvme volumio[1071]: info: CoreCommandRouter::volumioGetState Apr 28 16:06:31 volumio-nvme volumio[1071]: info: ERROR LOADING JSON Error: EIO: i/o error, read Apr 28 16:06:31 volumio-nvme volumio[1071]: error: touch_display: Could not fetch UI configuration: Error Apr 28 16:06:31 volumio-nvme volumio[1071]: info: ERROR LOADING JSON Error: EIO: i/o error, read Apr 28 16:06:31 volumio-nvme volumio[1071]: error: touch_display: Could not fetch UI configuration: Error Apr 28 16:06:31 volumio-nvme volumio[1071]: error: Failed to update update history file: function createApplication() { Apr 28 16:06:31 volumio-nvme volumio[1071]: var app = function(req, res, next) { Apr 28 16:06:31 volumio-nvme volumio[1071]: app.handle(req, res, next); Apr 28 16:06:31 volumio-nvme volumio[1071]: }; Apr 28 16:06:31 volumio-nvme volumio[1071]: mixin(app, EventEmitter.prototype, false); Apr 28 16:06:31 volumio-nvme volumio[1071]: mixin(app, proto, false); Apr 28 16:06:31 volumio-nvme volumio[1071]: // expose the prototype that will get set on requests Apr 28 16:06:31 volumio-nvme volumio[1071]: app.request = Object.create(req, { Apr 28 16:06:31 volumio-nvme volumio[1071]: app: { configurable: true, enumerable: true, writable: true, value: app } Apr 28 16:06:31 volumio-nvme volumio[1071]: }) Apr 28 16:06:31 volumio-nvme volumio[1071]: // expose the prototype that will get set on responses Apr 28 16:06:31 volumio-nvme volumio[1071]: app.response = Object.create(res, { Apr 28 16:06:31 volumio-nvme volumio[1071]: app: { configurable: true, enumerable: true, writable: true, value: app } Apr 28 16:06:31 volumio-nvme volumio[1071]: }) Apr 28 16:06:31 volumio-nvme volumio[1071]: app.init(); Apr 28 16:06:31 volumio-nvme volumio[1071]: return app; Apr 28 16:06:31 volumio-nvme volumio[1071]: } Apr 28 16:06:31 volumio-nvme systemd[1748]: apt-daily.service: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1748]: apt-daily.service: Failed at step EXEC spawning /usr/lib/apt/apt.systemd.daily: Input/output error Apr 28 16:06:31 volumio-nvme find[1746]: /usr/bin/find: ‘/var/cache/man’: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: apt-daily.service: Main process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read fragment cache entry [e8dc205] Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read fragment cache entry [e8dc205] Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read page, block e8dc205, size c1c7 Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12850138: lblock 0: comm find: error -5 reading directory block Apr 28 16:06:31 volumio-nvme kernel: Aborting journal on device nvme0n1p2-8. Apr 28 16:06:31 volumio-nvme kernel: JBD2: I/O error when updating journal superblock for nvme0n1p2-8. Apr 28 16:06:31 volumio-nvme systemd[1]: apt-daily.service: Failed with result 'exit-code'. Apr 28 16:06:31 volumio-nvme systemd[1]: Failed to start Daily apt download activities. Apr 28 16:06:31 volumio-nvme systemd[1]: Starting Daily apt upgrade and clean activities... Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read fragment cache entry [e8dc205] Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read page, block e8dc205, size c1c7 Apr 28 16:06:31 volumio-nvme volumio[1071]: info: Partition removed: {"syspath":"/sys/devices/platform/axi/1000110000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p2","ACTION":"remove","DEVLINKS":"/dev/disk/by-path/platform-1000110000.pcie-pci-0000:01:00.0-nvme-1-part2 /dev/disk/by-id/nvme-nvme.10ec-32333036564332533033384430303432-5361694368692047383030204e564d45203235364742-00000001-part2 /dev/disk/by-partuuid/f5e5206a-02 /dev/disk/by-id/nvme-SaiChi_G800_NVME_256GB_2306VC2S038D0042-part2 /dev/disk/by-uuid/5b8b18f8-5183-46fa-bab6-d8306276f824 /dev/disk/by-label/volumio","DEVNAME":"/dev/nvme0n1p2","DEVPATH":"/devices/platform/axi/1000110000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p2","DEVTYPE":"partition","DISKSEQ":"25","ID_FS_LABEL":"volumio","ID_FS_LABEL_ENC":"volumio","ID_FS_TYPE":"ext4","ID_FS_USAGE":"filesystem","ID_FS_UUID":"5b8b18f8-5183-46fa-bab6-d8306276f824","ID_FS_UUID_ENC":"5b8b18f8-5183-46fa-bab6-d8306276f824","ID_FS_VERSION":"1.0","ID_MODEL":"SaiChi G800 NVME 256GB","ID_PART_ENTRY_DISK":"259:0","ID_PART_ENTRY_NUMBER":"2","ID_PART_ENTRY_OFFSET":"188416","ID_PART_ENTRY_SCHEME":"dos","ID_PART_ENTRY_SIZE":"5279744","ID_PART_ENTRY_TYPE":"0x83","ID_PART_ENTRY_UUID":"f5e5206a-02","ID_PART_TABLE_TYPE":"dos","ID_PART_TABLE_UUID":"f5e5206a","ID_PATH":"platform-1000110000.pcie-pci-0000:01:00.0-nvme-1","ID_PATH_TAG":"platform-1000110000_pcie-pci-0000_01_00_0-nvme-1","ID_REVISION":"VC2S038D","ID_SERIAL":"SaiChi G800 NVME 256GB_2306VC2S038D0042","ID_SERIAL_SHORT":"2306VC2S038D0042","ID_WWN":"nvme.10ec-32333036564332533033384430303432-5361694368692047383030204e564d45203235364742-00000001","MAJOR":"259","MINOR":"2","PARTN":"2","SEQNUM":"2218","SUBSYSTEM":"block","TAGS":":systemd:","USEC_INITIALIZED":"7771537"} Apr 28 16:06:31 volumio-nvme systemd[1]: man-db.service: Main process exited, code=exited, status=1/FAILURE Apr 28 16:06:31 volumio-nvme systemd[1]: man-db.service: Failed with result 'exit-code'. Apr 28 16:06:31 volumio-nvme systemd[1752]: apt-daily-upgrade.service: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1752]: apt-daily-upgrade.service: Failed at step EXEC spawning /usr/lib/apt/apt-helper: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: Failed to start Daily man-db regeneration. Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read fragment cache entry [e8dc205] Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read page, block e8dc205, size c1c7 Apr 28 16:06:31 volumio-nvme systemd[1]: Stopped target Local File Systems. Apr 28 16:06:31 volumio-nvme systemd[1756]: apt-daily-upgrade.service: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1756]: apt-daily-upgrade.service: Failed at step EXEC spawning /usr/lib/apt/apt.systemd.daily: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1]: apt-daily-upgrade.service: Main process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: apt-daily-upgrade.service: Failed with result 'exit-code'. Apr 28 16:06:31 volumio-nvme volumio[1071]: info: Partition removed: {"syspath":"/sys/devices/platform/axi/1000110000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p1","ACTION":"remove","DEVLINKS":"/dev/disk/by-partuuid/f5e5206a-01 /dev/disk/by-uuid/11A3-9E63 /dev/disk/by-label/boot /dev/disk/by-id/nvme-SaiChi_G800_NVME_256GB_2306VC2S038D0042-part1 /dev/disk/by-path/platform-1000110000.pcie-pci-0000:01:00.0-nvme-1-part1 /dev/disk/by-id/nvme-nvme.10ec-32333036564332533033384430303432-5361694368692047383030204e564d45203235364742-00000001-part1","DEVNAME":"/dev/nvme0n1p1","DEVPATH":"/devices/platform/axi/1000110000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p1","DEVTYPE":"partition","DISKSEQ":"25","ID_FS_LABEL":"boot","ID_FS_LABEL_ENC":"boot","ID_FS_TYPE":"vfat","ID_FS_USAGE":"filesystem","ID_FS_UUID":"11A3-9E63","ID_FS_UUID_ENC":"11A3-9E63","ID_FS_VERSION":"FAT32","ID_MODEL":"SaiChi G800 NVME 256GB","ID_PART_ENTRY_DISK":"259:0","ID_PART_ENTRY_FLAGS":"0x80","ID_PART_ENTRY_NUMBER":"1","ID_PART_ENTRY_OFFSET":"1","ID_PART_ENTRY_SCHEME":"dos","ID_PART_ENTRY_SIZE":"187500","ID_PART_ENTRY_TYPE":"0xc","ID_PART_ENTRY_UUID":"f5e5206a-01","ID_PART_TABLE_TYPE":"dos","ID_PART_TABLE_UUID":"f5e5206a","ID_PATH":"platform-1000110000.pcie-pci-0000:01:00.0-nvme-1","ID_PATH_TAG":"platform-1000110000_pcie-pci-0000_01_00_0-nvme-1","ID_REVISION":"VC2S038D","ID_SERIAL":"SaiChi G800 NVME 256GB_2306VC2S038D0042","ID_SERIAL_SHORT":"2306VC2S038D0042","ID_WWN":"nvme.10ec-32333036564332533033384430303432-5361694368692047383030204e564d45203235364742-00000001","MAJOR":"259","MINOR":"1","PARTN":"1","SEQNUM":"2217","SUBSYSTEM":"block","TAGS":":systemd:","USEC_INITIALIZED":"7786332"} Apr 28 16:06:31 volumio-nvme systemd[1]: Failed to start Daily apt upgrade and clean activities. Apr 28 16:06:31 volumio-nvme systemd[1757]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1757]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme volumio[1071]: info: Partition removed: {"syspath":"/sys/devices/platform/axi/1000110000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p3","ACTION":"remove","DEVLINKS":"/dev/disk/by-partuuid/f5e5206a-03 /dev/disk/by-id/nvme-SaiChi_G800_NVME_256GB_2306VC2S038D0042-part3 /dev/disk/by-label/volumio_data /dev/disk/by-id/nvme-nvme.10ec-32333036564332533033384430303432-5361694368692047383030204e564d45203235364742-00000001-part3 /dev/disk/by-path/platform-1000110000.pcie-pci-0000:01:00.0-nvme-1-part3 /dev/disk/by-uuid/7d2b4b4c-b090-4c9b-bc6c-f407b0d7cd94","DEVNAME":"/dev/nvme0n1p3","DEVPATH":"/devices/platform/axi/1000110000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p3","DEVTYPE":"partition","DISKSEQ":"25","ID_FS_LABEL":"volumio_data","ID_FS_LABEL_ENC":"volumio_data","ID_FS_TYPE":"ext4","ID_FS_USAGE":"filesystem","ID_FS_UUID":"7d2b4b4c-b090-4c9b-bc6c-f407b0d7cd94","ID_FS_UUID_ENC":"7d2b4b4c-b090-4c9b-bc6c-f407b0d7cd94","ID_FS_VERSION":"1.0","ID_MODEL":"SaiChi G800 NVME 256GB","ID_PART_ENTRY_DISK":"259:0","ID_PART_ENTRY_NUMBER":"3","ID_PART_ENTRY_OFFSET":"5468160","ID_PART_ENTRY_SCHEME":"dos","ID_PART_ENTRY_SIZE":"494649344","ID_PART_ENTRY_TYPE":"0x83","ID_PART_ENTRY_UUID":"f5e5206a-03","ID_PART_TABLE_TYPE":"dos","ID_PART_TABLE_UUID":"f5e5206a","ID_PATH":"platform-1000110000.pcie-pci-0000:01:00.0-nvme-1","ID_PATH_TAG":"platform-1000110000_pcie-pci-0000_01_00_0-nvme-1","ID_REVISION":"VC2S038D","ID_SERIAL":"SaiChi G800 NVME 256GB_2306VC2S038D0042","ID_SERIAL_SHORT":"2306VC2S038D0042","ID_WWN":"nvme.10ec-32333036564332533033384430303432-5361694368692047383030204e564d45203235364742-00000001","MAJOR":"259","MINOR":"3","PARTN":"3","SEQNUM":"2219","SUBSYSTEM":"block","TAGS":":systemd:","USEC_INITIALIZED":"7691612"} Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1758]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1758]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864135: lblock 0: comm run-parts: error -5 reading directory block Apr 28 16:06:31 volumio-nvme systemd[1760]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1760]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1763]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1763]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1765]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1765]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1766]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1766]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1767]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1767]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1768]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): dx_probe:822: inode #12978360: lblock 0: comm lsb_release: error -5 reading directory block Apr 28 16:06:31 volumio-nvme systemd[1768]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1770]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1770]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1771]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1771]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1773]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1773]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1777]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1777]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1778]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1778]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1779]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1779]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1780]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1780]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1781]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme kernel: I/O error, dev loop0, sector 923054 op 0x0:(READ) flags 0x800 phys_seg 6 prio class 2 Apr 28 16:06:31 volumio-nvme kernel: I/O error, dev loop0, sector 942490 op 0x0:(READ) flags 0x800 phys_seg 4 prio class 2 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1cc33577: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1c2b5d04: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read fragment cache entry [1c2b5d04] Apr 28 16:06:31 volumio-nvme kernel: I/O error, dev loop0, sector 942536 op 0x0:(READ) flags 0x800 phys_seg 4 prio class 2 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1cc391c6: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read fragment cache entry [1c2b5d04] Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1c2b5d04, size 50c4 Apr 28 16:06:31 volumio-nvme kernel: I/O error, dev loop0, sector 942490 op 0x0:(READ) flags 0x800 phys_seg 5 prio class 2 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1cc33577: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [1cc33577] Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1cc33577, size 5c4f Apr 28 16:06:31 volumio-nvme systemd[1781]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme volumio[1071]: An internal error occurred while serving an albumart. Details: Error: EIO: i/o error, read Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device. Stopping, too. Apr 28 16:06:31 volumio-nvme systemd[1]: Unmounting /boot... Apr 28 16:06:31 volumio-nvme systemd[1782]: boot.mount: Failed to execute command: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1782]: boot.mount: Failed at step EXEC spawning /bin/umount: Input/output error Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Mount process exited, code=exited, status=203/EXEC Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1b3c767d: -5 Apr 28 16:06:31 volumio-nvme systemd[1]: Failed unmounting /boot. Apr 28 16:06:31 volumio-nvme systemd[1]: boot.mount: Unit is bound to inactive unit dev-disk-by\x2duuid-11A3\x2d9E63.device, but not stopping since we tried this too often recently. Apr 28 16:06:31 volumio-nvme systemd[1]: systemd-fsck@dev-disk-by\x2duuid-11A3\x2d9E63.service: Succeeded. Apr 28 16:06:31 volumio-nvme systemd[1]: Stopped File System Check on /dev/disk/by-uuid/11A3-9E63. Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1b3e767d: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1b40767d: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1b3c767d: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [1b3c767d] Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1b3c767d, size 1020000 Apr 28 16:06:31 volumio-nvme volumio[1071]: Error: EIO: i/o error, read Apr 28 16:06:31 volumio-nvme volumio[1071]: Error: EIO: i/o error, read Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [1b3c767d] Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1b3c767d, size 1020000 Apr 28 16:06:31 volumio-nvme volumio[1071]: An internal error occurred while serving an albumart. Details: Error: EIO: i/o error, read Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1cab2976: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1cabe1c7: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1cab2976: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [1cab2976] Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1cab2976, size b851 Apr 28 16:06:31 volumio-nvme volumio[1071]: An internal error occurred while serving an albumart. Details: Error: EIO: i/o error, read Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1c7c5f8f: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1c7cd13d: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1c7c5f8f: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [1c7c5f8f] Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1c7c5f8f, size 71ae Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1b3c767d: -5 Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [1b3c767d] Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1b3c767d, size 1020000 Apr 28 16:06:31 volumio-nvme volumio[1071]: Error: EIO: i/o error, read Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [1b3c767d] Apr 28 16:06:31 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1b3c767d, size 1020000 Apr 28 16:06:31 volumio-nvme volumio[1071]: Error: EIO: i/o error, read Apr 28 16:06:36 volumio-nvme kernel: EXT4-fs warning: 256 callbacks suppressed Apr 28 16:06:36 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12976529: lblock 0: comm Chrome_IOThread: error -5 reading directory block Apr 28 16:06:36 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864135: lblock 0: comm run-parts: error -5 reading directory block Apr 28 16:06:36 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): dx_probe:822: inode #12978360: lblock 0: comm lsb_release: error -5 reading directory block Apr 28 16:06:36 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): dx_probe:822: inode #12978360: lblock 0: comm lsb_release: error -5 reading directory block Apr 28 16:06:36 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12845113: lblock 0: comm dpkg-query: error -5 reading directory block Apr 28 16:06:36 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:36 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:36 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:36 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:36 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm ThreadPoolForeg: error -5 reading directory block Apr 28 16:06:37 volumio-nvme kernel: EXT4-fs error: 26 callbacks suppressed Apr 28 16:06:37 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12845132: comm nmbd: reading directory lblock 0 Apr 28 16:06:37 volumio-nvme nmbd[758]: [2024/04/28 16:06:37.395716, 0] ../source3/nmbd/nmbd_serverlistdb.c:317(write_browse_list) Apr 28 16:06:37 volumio-nvme nmbd[758]: write_browse_list: Can't open file /var/cache/samba/browse.dat.: Input/output error Apr 28 16:06:37 volumio-nvme nmbd[758]: [2024/04/28 16:06:37.396446, 0] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log) Apr 28 16:06:37 volumio-nvme nmbd[758]: tdb(/var/cache/samba/gencache.tdb): tdb_transaction: fsync failed Apr 28 16:06:37 volumio-nvme nmbd[758]: [2024/04/28 16:06:37.396502, 0] ../lib/tdb_wrap/tdb_wrap.c:64(tdb_wrap_log) Apr 28 16:06:37 volumio-nvme nmbd[758]: tdb(/var/cache/samba/gencache.tdb): tdb_transaction_prepare_commit: failed to setup recovery data Apr 28 16:06:41 volumio-nvme kernel: EXT4-fs warning: 270 callbacks suppressed Apr 28 16:06:41 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): dx_probe:822: inode #12978360: lblock 0: comm lsb_release: error -5 reading directory block Apr 28 16:06:41 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12845113: lblock 0: comm dpkg-query: error -5 reading directory block Apr 28 16:06:41 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:41 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:41 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:41 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:41 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm ThreadPoolForeg: error -5 reading directory block Apr 28 16:06:41 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm ThreadPoolForeg: error -5 reading directory block Apr 28 16:06:41 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12976451: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:41 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12976435: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:42 volumio-nvme volumio[1071]: info: touch_display: Setting screensaver timeout to 120 seconds. Apr 28 16:06:42 volumio-nvme volumio[1071]: info: touch_display: Using Xserver unix domain socket /tmp/.X11-unix/X0 Apr 28 16:06:46 volumio-nvme kernel: EXT4-fs warning: 265 callbacks suppressed Apr 28 16:06:46 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864135: lblock 0: comm run-parts: error -5 reading directory block Apr 28 16:06:46 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): dx_probe:822: inode #12978360: lblock 0: comm lsb_release: error -5 reading directory block Apr 28 16:06:46 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): dx_probe:822: inode #12978360: lblock 0: comm lsb_release: error -5 reading directory block Apr 28 16:06:46 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12845113: lblock 0: comm dpkg-query: error -5 reading directory block Apr 28 16:06:46 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:46 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:46 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:46 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:46 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm ThreadPoolForeg: error -5 reading directory block Apr 28 16:06:46 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm ThreadPoolForeg: error -5 reading directory block Apr 28 16:06:49 volumio-nvme volumio[1071]: An internal error occurred while serving an albumart. Details: Error: EIO: i/o error, read Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read fragment cache entry [1c2b5d04] Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1c2b5d04, size 50c4 Apr 28 16:06:49 volumio-nvme volumio[1071]: Error: EIO: i/o error, read Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [1b3c767d] Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1b3c767d, size 1020000 Apr 28 16:06:49 volumio-nvme volumio[1071]: An internal error occurred while serving an albumart. Details: Error: EIO: i/o error, read Apr 28 16:06:49 volumio-nvme kernel: blk_print_req_error: 11 callbacks suppressed Apr 28 16:06:49 volumio-nvme kernel: I/O error, dev loop0, sector 942490 op 0x0:(READ) flags 0x800 phys_seg 7 prio class 2 Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1cc33577: -5 Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [1cc33577] Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1cc33577, size 5c4f Apr 28 16:06:49 volumio-nvme volumio[1071]: Error: EIO: i/o error, read Apr 28 16:06:49 volumio-nvme kernel: I/O error, dev loop0, sector 892474 op 0x0:(READ) flags 0x800 phys_seg 33 prio class 2 Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1b3c767d: -5 Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [1b3c767d] Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1b3c767d, size 1020000 Apr 28 16:06:49 volumio-nvme volumio[1071]: An internal error occurred while serving an albumart. Details: Error: EIO: i/o error, read Apr 28 16:06:49 volumio-nvme kernel: I/O error, dev loop0, sector 939412 op 0x0:(READ) flags 0x800 phys_seg 13 prio class 2 Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1cab2976: -5 Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [1cab2976] Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1cab2976, size b851 Apr 28 16:06:49 volumio-nvme kernel: I/O error, dev loop0, sector 933422 op 0x0:(READ) flags 0x800 phys_seg 9 prio class 2 Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1c7c5f8f: -5 Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [1c7c5f8f] Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1c7c5f8f, size 71ae Apr 28 16:06:49 volumio-nvme volumio[1071]: An internal error occurred while serving an albumart. Details: Error: EIO: i/o error, read Apr 28 16:06:49 volumio-nvme volumio[1071]: Error: EIO: i/o error, read Apr 28 16:06:49 volumio-nvme kernel: I/O error, dev loop0, sector 892474 op 0x0:(READ) flags 0x800 phys_seg 33 prio class 2 Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Failed to read block 0x1b3c767d: -5 Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [1b3c767d] Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1b3c767d, size 1020000 Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [1b3c767d] Apr 28 16:06:49 volumio-nvme kernel: SQUASHFS error: Unable to read page, block 1b3c767d, size 1020000 Apr 28 16:06:49 volumio-nvme volumio[1071]: Error: EIO: i/o error, read Apr 28 16:06:51 volumio-nvme kernel: EXT4-fs warning: 261 callbacks suppressed Apr 28 16:06:51 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12976529: lblock 0: comm Chrome_IOThread: error -5 reading directory block Apr 28 16:06:51 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864135: lblock 0: comm run-parts: error -5 reading directory block Apr 28 16:06:51 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): dx_probe:822: inode #12978360: lblock 0: comm lsb_release: error -5 reading directory block Apr 28 16:06:51 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): dx_probe:822: inode #12978360: lblock 0: comm lsb_release: error -5 reading directory block Apr 28 16:06:51 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12845113: lblock 0: comm dpkg-query: error -5 reading directory block Apr 28 16:06:51 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:51 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:51 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:51 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:51 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm ThreadPoolForeg: error -5 reading directory block Apr 28 16:06:56 volumio-nvme kernel: EXT4-fs warning: 266 callbacks suppressed Apr 28 16:06:56 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12976529: lblock 0: comm Chrome_IOThread: error -5 reading directory block Apr 28 16:06:56 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864135: lblock 0: comm run-parts: error -5 reading directory block Apr 28 16:06:56 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): dx_probe:822: inode #12978360: lblock 0: comm lsb_release: error -5 reading directory block Apr 28 16:06:56 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): dx_probe:822: inode #12978360: lblock 0: comm lsb_release: error -5 reading directory block Apr 28 16:06:56 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12845113: lblock 0: comm dpkg-query: error -5 reading directory block Apr 28 16:06:56 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:56 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:56 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:56 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:06:56 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm ThreadPoolForeg: error -5 reading directory block Apr 28 16:06:57 volumio-nvme nmbd[758]: [2024/04/28 16:06:57.423116, 0] ../source3/nmbd/nmbd_serverlistdb.c:317(write_browse_list) Apr 28 16:06:57 volumio-nvme nmbd[758]: write_browse_list: Can't open file /var/cache/samba/browse.dat.: Input/output error Apr 28 16:06:57 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12845132: comm nmbd: reading directory lblock 0 Apr 28 16:06:57 volumio-nvme volumio[1071]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo Apr 28 16:06:57 volumio-nvme volumio[1071]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice Apr 28 16:06:57 volumio-nvme volumio[1071]: info: Discovery: Getting this device information Apr 28 16:06:57 volumio-nvme volumio[1071]: info: CoreCommandRouter::volumioGetState Apr 28 16:06:57 volumio-nvme volumio[1071]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses Apr 28 16:06:59 volumio-nvme volumio[1071]: info: CoreCommandRouter::getUIConfigOnPlugin Apr 28 16:06:59 volumio-nvme volumio[1071]: info: CoreCommandRouter::executeOnPlugin: system , getAdvancedSettingsStatus Apr 28 16:06:59 volumio-nvme volumio[1071]: info: CoreCommandRouter::executeOnPlugin: network , getInfoNetwork Apr 28 16:06:59 volumio-nvme sudo[7782]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ethtool eth0 Apr 28 16:06:59 volumio-nvme sudo[7782]: pam_unix(sudo:session): session opened for user root by (uid=0) Apr 28 16:06:59 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12983091: comm sh: reading directory lblock 0 Apr 28 16:06:59 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12983091: comm sh: reading directory lblock 0 Apr 28 16:06:59 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12849224: comm sh: reading directory lblock 0 Apr 28 16:06:59 volumio-nvme kernel: I/O error, dev loop0, sector 342380 op 0x0:(READ) flags 0x800 phys_seg 17 prio class 2 Apr 28 16:06:59 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12849224: comm sh: reading directory lblock 0 Apr 28 16:06:59 volumio-nvme sudo[7788]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/iwconfig wlan0 Apr 28 16:06:59 volumio-nvme sudo[7788]: pam_unix(sudo:session): session opened for user root by (uid=0) Apr 28 16:06:59 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12978479: comm sh: reading directory lblock 0 Apr 28 16:06:59 volumio-nvme kernel: SQUASHFS error: Failed to read block 0xa72d8f9: -5 Apr 28 16:06:59 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12983091: comm sh: reading directory lblock 0 Apr 28 16:06:59 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12978479: comm sh: reading directory lblock 0 Apr 28 16:06:59 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12849224: comm sh: reading directory lblock 0 Apr 28 16:06:59 volumio-nvme kernel: I/O error, dev loop0, sector 342380 op 0x0:(READ) flags 0x800 phys_seg 17 prio class 2 Apr 28 16:06:59 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12983091: comm sh: reading directory lblock 0 Apr 28 16:06:59 volumio-nvme kernel: SQUASHFS error: Failed to read block 0xa72d8f9: -5 Apr 28 16:06:59 volumio-nvme sudo[7782]: pam_unix(sudo:session): session closed for user root Apr 28 16:06:59 volumio-nvme volumio[1071]: info: CoreCommandRouter::executeOnPlugin: network , getWirelessNetworksScanCache Apr 28 16:06:59 volumio-nvme kernel: SQUASHFS error: Unable to read data cache entry [a72d8f9] Apr 28 16:06:59 volumio-nvme kernel: SQUASHFS error: Unable to read page, block a72d8f9, size 105ae Apr 28 16:06:59 volumio-nvme sudo[7792]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/iwconfig wlan0 Apr 28 16:06:59 volumio-nvme sudo[7792]: pam_unix(sudo:session): session opened for user root by (uid=0) Apr 28 16:06:59 volumio-nvme sudo[7810]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/iwconfig wlan0 Apr 28 16:06:59 volumio-nvme sudo[7817]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig eth0 Apr 28 16:06:59 volumio-nvme sudo[7817]: pam_unix(sudo:session): session opened for user root by (uid=0) Apr 28 16:06:59 volumio-nvme sudo[7788]: pam_unix(sudo:session): session closed for user root Apr 28 16:06:59 volumio-nvme sudo[7810]: pam_unix(sudo:session): session opened for user root by (uid=0) Apr 28 16:06:59 volumio-nvme sudo[7820]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 Apr 28 16:06:59 volumio-nvme sudo[7820]: pam_unix(sudo:session): session opened for user root by (uid=0) Apr 28 16:06:59 volumio-nvme sudo[7817]: pam_unix(sudo:session): session closed for user root Apr 28 16:06:59 volumio-nvme sudo[7820]: pam_unix(sudo:session): session closed for user root Apr 28 16:06:59 volumio-nvme volumio[1071]: info: CoreCommandRouter::executeOnPlugin: network , getWirelessNetworks Apr 28 16:06:59 volumio-nvme sudo[7792]: pam_unix(sudo:session): session closed for user root Apr 28 16:06:59 volumio-nvme sudo[7810]: pam_unix(sudo:session): session closed for user root Apr 28 16:06:59 volumio-nvme volumio[1071]: error: Could not parse Wireless Speed: Error: Command failed: /usr/bin/sudo /sbin/iwconfig wlan0 | grep 'Bit Rate' | awk '{print $2,$3}' | tr -d 'Rate:' | xargs Apr 28 16:06:59 volumio-nvme volumio[1071]: /bin/sh: 1: xargs: Input/output error Apr 28 16:06:59 volumio-nvme volumio[1071]: error: Could not parse Etherned Speed: Error: Command failed: /usr/bin/sudo /sbin/ethtool eth0 | grep -i speed | tr -d 'Speed:' | xargs Apr 28 16:06:59 volumio-nvme volumio[1071]: /bin/sh: 1: xargs: Input/output error Apr 28 16:06:59 volumio-nvme volumio[1071]: sudo: unable to execute /sbin/ethtool: Input/output error Apr 28 16:06:59 volumio-nvme sudo[7852]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/iwlist wlan0 scan Apr 28 16:06:59 volumio-nvme sudo[7852]: pam_unix(sudo:session): session opened for user root by (uid=0) Apr 28 16:06:59 volumio-nvme volumio[1071]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo Apr 28 16:06:59 volumio-nvme volumio[1071]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice Apr 28 16:06:59 volumio-nvme volumio[1071]: info: Discovery: Getting this device information Apr 28 16:06:59 volumio-nvme volumio[1071]: info: CoreCommandRouter::volumioGetState Apr 28 16:06:59 volumio-nvme volumio[1071]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses Apr 28 16:07:01 volumio-nvme kernel: EXT4-fs warning: 272 callbacks suppressed Apr 28 16:07:01 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12976529: lblock 0: comm Chrome_IOThread: error -5 reading directory block Apr 28 16:07:01 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864135: lblock 0: comm run-parts: error -5 reading directory block Apr 28 16:07:01 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): dx_probe:822: inode #12978360: lblock 0: comm lsb_release: error -5 reading directory block Apr 28 16:07:01 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): dx_probe:822: inode #12978360: lblock 0: comm lsb_release: error -5 reading directory block Apr 28 16:07:01 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12845113: lblock 0: comm dpkg-query: error -5 reading directory block Apr 28 16:07:01 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:07:01 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:07:01 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:07:01 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:07:01 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm ThreadPoolForeg: error -5 reading directory block Apr 28 16:07:03 volumio-nvme sudo[7852]: pam_unix(sudo:session): session closed for user root Apr 28 16:07:03 volumio-nvme volumiologrotate[643]: ls: cannot access '/var/log/samba/log.wb-VOLUMIO': No such file or directory Apr 28 16:07:03 volumio-nvme volumiologrotate[643]: ls: cannot access 'NVME': No such file or directory Apr 28 16:07:06 volumio-nvme kernel: EXT4-fs warning: 265 callbacks suppressed Apr 28 16:07:06 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864135: lblock 0: comm run-parts: error -5 reading directory block Apr 28 16:07:06 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): dx_probe:822: inode #12978360: lblock 0: comm lsb_release: error -5 reading directory block Apr 28 16:07:06 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): dx_probe:822: inode #12978360: lblock 0: comm lsb_release: error -5 reading directory block Apr 28 16:07:06 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12845113: lblock 0: comm dpkg-query: error -5 reading directory block Apr 28 16:07:06 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:07:06 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:07:06 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:07:06 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm chromium-browse: error -5 reading directory block Apr 28 16:07:06 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864316: lblock 0: comm ThreadPoolForeg: error -5 reading directory block Apr 28 16:07:06 volumio-nvme kernel: EXT4-fs warning (device nvme0n1p3): htree_dirblock_to_tree:1082: inode #12864318: lblock 0: comm ThreadPoolForeg: error -5 reading directory block Apr 28 16:07:07 volumio-nvme kernel: EXT4-fs error: 3 callbacks suppressed Apr 28 16:07:07 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12845132: comm nmbd: reading directory lblock 0 Apr 28 16:07:07 volumio-nvme nmbd[758]: [2024/04/28 16:07:07.443124, 0] ../source3/nmbd/nmbd_serverlistdb.c:317(write_browse_list) Apr 28 16:07:07 volumio-nvme nmbd[758]: write_browse_list: Can't open file /var/cache/samba/browse.dat.: Input/output error Apr 28 16:07:07 volumio-nvme nmbd[9615]: [2024/04/28 16:07:07.455546, 0] ../source3/nmbd/nmbd_winsserver.c:2508(wins_write_database) Apr 28 16:07:07 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12845098: comm nmbd: reading directory lblock 0 Apr 28 16:07:07 volumio-nvme kernel: EXT4-fs error (device nvme0n1p3): __ext4_find_entry:1684: inode #12845132: comm nmbd: reading directory lblock 0 Apr 28 16:07:07 volumio-nvme nmbd[9615]: wins_write_database: Can't open /var/lib/samba/wins.dat.9615: Input/output error Apr 28 16:07:07 volumio-nvme nmbd[758]: [2024/04/28 16:07:07.467555, 0] ../source3/nmbd/nmbd_serverlistdb.c:317(write_browse_list) Apr 28 16:07:07 volumio-nvme nmbd[758]: write_browse_list: Can't open file /var/cache/samba/browse.dat.: Input/output error Apr 28 16:07:08 volumio-nvme volumio[1071]: |||||||||||||||||||||||| WARNING: FATAL ERROR ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| Apr 28 16:07:08 volumio-nvme volumio[1071]: Error: EIO: i/o error, scandir '/data/plugins/' Apr 28 16:07:08 volumio-nvme volumio[1071]: at Object.readdirSync (fs.js:1021:3) Apr 28 16:07:08 volumio-nvme volumio[1071]: at PluginManager.getInstalledPlugins (/volumio/app/pluginmanager.js:1627:30) Apr 28 16:07:08 volumio-nvme volumio[1071]: at CoreCommandRouter.getInstalledPlugins (/volumio/app/index.js:1515:29) Apr 28 16:07:08 volumio-nvme volumio[1071]: at Socket. (/volumio/app/plugins/user_interface/websocket/index.js:1300:45) Apr 28 16:07:08 volumio-nvme volumio[1071]: at Socket.emit (events.js:315:20) Apr 28 16:07:08 volumio-nvme volumio[1071]: at /volumio/node_modules/socket.io/lib/socket.js:503:12 Apr 28 16:07:08 volumio-nvme volumio[1071]: at processTicksAndRejections (internal/process/task_queues.js:75:11) { Apr 28 16:07:08 volumio-nvme volumio[1071]: errno: -5, Apr 28 16:07:08 volumio-nvme volumio[1071]: syscall: 'scandir', Apr 28 16:07:08 volumio-nvme volumio[1071]: code: 'EIO', Apr 28 16:07:08 volumio-nvme volumio[1071]: path: '/data/plugins/' Apr 28 16:07:08 volumio-nvme volumio[1071]: } Apr 28 16:07:08 volumio-nvme volumio[1071]: ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| Apr 28 16:07:08 volumio-nvme sudo[9844]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/journalctl --since=2024-04-28 16:06 Apr 28 16:07:08 volumio-nvme sudo[9844]: pam_unix(sudo:session): session opened for user root by (uid=0) PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" VOLUMIO_BUILD_VERSION="8c0a8dce3a0435348590f0697c09ba39bd364767" VOLUMIO_FE_VERSION="614d7b13ffdcb0cc5a6072e7d06f59d52e323e71" VOLUMIO_FE3_VERSION="570aaed971c1346d45d1172dc445b086b258c6d1" VOLUMIO_BE_VERSION="c45f0e51c865f04fd4ec5869da59c5cfafdd1447" VOLUMIO_ARCH="arm" VOLUMIO_VARIANT="volumio" VOLUMIO_TEST="FALSE" VOLUMIO_BUILD_DATE="Wed 13 Mar 2024 09:16:28 PM CET" VOLUMIO_VERSION="3.639" VOLUMIO_HARDWARE="pi-uuid" VOLUMIO_DEVICENAME="Raspberry Pi" VOLUMIO_HASH="5ba27c8c056b5ac07204061da58c4e30"