If I need to post this over at the Crashplan docker support site, I will do so.A guide to uninstall Code42 from your systemCode42 is a computer program. I normally swap out disks twice a week, so I don't understand why this hasn't happened on a previous swap out. The backup process normally carries on with the replaced disk. To swap out the disks, I turn off the docker, unmount the disks, remove the disks, swap the disks and restart the docker. This time, the problem appears to have started after I swapped out back up hard drives that I use for Crashplan (Code42) docker 3 days ago (and as such, I am unsure if I should be posting here or in the Crashplan support pages). This has happened previously and restarting the server cleared the problem and on this occasion all was well for 2 weeks or so before the problem returned.

When I look at the drives I have after this error occurs, I note that there is nothing mounted at sdd1, so it looks like the server is hunting for a mount that is no longer present. Dec 17 18:35:59 Speedy kernel: EXT4-fs error (device sdd1): ext4_find_entry:1455: inode #2: comm Code42Service: reading directory lblock 0ĭec 17 18:36:09 Speedy kernel: EXT4-fs error (device sdd1): ext4_find_entry:1455: inode #2: comm MdePeer1WeDftWk: reading directory lblock 0ĭec 17 18:36:59 Speedy kernel: EXT4-fs error (device sdd1): ext4_find_entry:1455: inode #2: comm W1544923155_Mai: reading directory lblock 0ĭec 17 18:36:59 Speedy kernel: EXT4-fs error (device sdd1): ext4_find_entry:1455: inode #2: comm W510768909_Main: reading directory lblock 0ĭec 17 18:36:59 Speedy kernel: EXT4-fs error (device sdd1): ext4_find_entry:1455: inode #2: comm pool-16-thread-: reading directory lblock 0ĭec 17 18:37:59 Speedy kernel: EXT4-fs error (device sdd1): ext4_find_entry:1455: inode #2: comm pool-16-thread-: reading directory lblock 0

Code42service