On Tue, 22 Mar 2022, Ben Koenig wrote:
The error you posted is just a summary reported by logwatch. It's letting you know something happened so you need to find the original error if you want to truly understand the failure.
Ben, It appears to me to be related to the Mediasonic's indigestion last Sunday: syslog.2:Mar 20 07:37:48 salmo kernel: [417990.328116] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:995: inode #167772834: lblock 0: comm mv: error -5 reading directory block syslog.2:Mar 20 07:37:48 salmo kernel: [417990.328155] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:995: inode #167772838: lblock 0: comm mv: error -5 reading directory block syslog.2:Mar 20 07:37:48 salmo kernel: [417990.328199] EXT4-fs warning (device dm-0): htree_dirblock_to_tree:995: inode #167772842: lblock 0: comm mv: error -5 reading directory block That's when the external enclosure had a corrupted LV. Thanks, Rich
