March 17, 20179 yr An update to my Plex docker hung and I had to manually kill and rebuild the container. Plex is running fine and I haven't experienced any other issues, but I keep getting error messages. I'm worried that my Flash Device is becoming corrupted. Any advice on troubleshooting and correcting these errors would be much appreciated. The log is spitting out: Mar 17 14:11:53 SuperBob kernel: FAT-fs (sdb1): error, invalid access to FAT (entry 0x20924080) Mar 17 14:11:53 SuperBob kernel: FAT-fs (sdb1): error, invalid access to FAT (entry 0x06802322) Mar 17 14:11:53 SuperBob kernel: FAT-fs (sdb1): error, invalid access to FAT (entry 0x06802322) Mar 17 14:11:53 SuperBob kernel: FAT-fs (sdb1): error, invalid access to FAT (entry 0x46219208) On the Dashboard page, below the apps heading I'm getting this repeating error message Warning: DOMDocument::load(): Start tag expected, '<' not found in /boot/config/plugins/dockerMan/templates/limetech/PlexMediaServer.xml, line: 1 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 224 Warning: DOMDocument::load(): Start tag expected, '<' not found in /boot/config/plugins/dockerMan/templates/linuxserver.io/tvheadend.xml, line: 1 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 224 Warning: DOMDocument::load(): Start tag expected, '<' not found in /boot/config/plugins/dockerMan/templates/linuxserver.io/ombi.xml, line: 1 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 224 Warning: DOMDocument::load(): Start tag expected, '<' not found in /boot/config/plugins/dockerMan/templates/linuxserver.io/domoticz.xml, line: 1 in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 224 Warning:
March 17, 20179 yr Author Looks like it had some allocation errors. Got this message: Repairing file system. ** /dev/rdisk6s1 ** Phase 1 - Preparing FAT ** Phase 2 - Checking Directories Item /logs does not appear to be a subdirectory Correct? yes /logs has too many clusters allocated (logical=0, physical=16384) Drop superfluous clusters? yes /.preclear has entries after end of directory Truncate? yes Item /.Trashes/501 does not appear to be a subdirectory Correct? yes /.Trashes/501 has too many clusters allocated (logical=0, physical=16384) Drop superfluous clusters? yes /.Trashes has entries after end of directory Truncate? yes /SYSLINUX has entries after end of directory Truncate? yes /CONFIG has entries after end of directory Truncate? yes Item /CONFIG/PLUGINS/tablesorter does not appear to be a subdirectory Correct? yes /CONFIG/PLUGINS/tablesorter has too many clusters allocated (logical=0, physical=16384) Drop superfluous clusters? yes Item /CONFIG/PLUGINS/ipmi does not appear to be a subdirectory Correct? yes /CONFIG/PLUGINS/ipmi has too many clusters allocated (logical=0, physical=16384) Drop superfluous clusters? yes Item /CONFIG/PLUGINS/preclear.disk does not appear to be a subdirectory Correct? yes /CONFIG/PLUGINS/preclear.disk has too many clusters allocated (logical=0, physical=16384) Drop superfluous clusters? yes Item /CONFIG/PLUGINS/dynamix.system.info does not appear to be a subdirectory Correct? yes /CONFIG/PLUGINS/dynamix.system.info has too many clusters allocated (logical=0, physical=16384) Drop superfluous clusters? yes Item /CONFIG/PLUGINS/dynamix.system.stats does not appear to be a subdirectory Correct? yes /CONFIG/PLUGINS/dynamix.system.stats has too many clusters allocated (logical=0, physical=16384) Drop superfluous clusters? yes /CONFIG/PLUGINS/dynamix.ssd.trim has entries after end of directory Truncate? yes /CONFIG/PLUGINS/statistics.sender has entries after end of directory Truncate? yes Item /CONFIG/PLUGINS/unassigned.devices/packages does not appear to be a subdirectory Correct? yes /CONFIG/PLUGINS/unassigned.devices/packages has too many clusters allocated (logical=0, physical=16384) Drop superfluous clusters? yes /CONFIG/PLUGINS/unassigned.devices has entries after end of directory Truncate? yes /CONFIG/PLUGINS/ca.backup has entries after end of directory Truncate? yes Item /CONFIG/PLUGINS/dockerMan/templates-user does not appear to be a subdirectory Correct? yes /CONFIG/PLUGINS/dockerMan/templates-user has too many clusters allocated (logical=0, physical=16384) Drop superfluous clusters? yes Item /CONFIG/PLUGINS/dockerMan/templates/limetech does not appear to be a subdirectory Correct? yes /CONFIG/PLUGINS/dockerMan/templates/limetech has too many clusters allocated (logical=0, physical=16384) Drop superfluous clusters? yes /CONFIG/PLUGINS/dockerMan/templates has entries after end of directory Truncate? yes ** Phase 3 - Checking for Orphan Clusters Found orphan cluster(s) Fix? yes Marked 483 clusters as free Free space in FSInfo block (1933989) not correct (1934482) Fix? yes 386 files, 30951712 KiB free (1934482 clusters) ***** FILE SYSTEM WAS MODIFIED ***** File system check exit code is 0. Updating boot support partitions for the volume as required. Operation successful.
March 17, 20179 yr Author Hmm... Now it won't boot up. Loading /bizimage... ok Loading /bzroot... ok No Setup signature found... Stops on the last line
March 17, 20179 yr Community Expert 16 minutes ago, elogg said: Hmm... Now it won't boot up. Loading /bizimage... ok Loading /bzroot... ok No Setup signature found... Stops on the last line Do you have a backup?
March 17, 20179 yr Author I have one from about a month ago when I updated unraid versions. I've made some changes since then. Is my install toast? Edited March 17, 20179 yr by elogg
March 17, 20179 yr Community Expert If you haven't changed any disks that backup should be fine. If you have changed any disks you should not restore config/super.dat from the backup. Just prepare the flash as for a new install and copy your config folder from the backup. Do you know what changes you made since the backup?
March 17, 20179 yr Author A while back I temporarily added a disk to the array, but removed it due to disk errors. I did reset the disk configuration to remove it from the assigned devices list, does that count? Besides that, added several plugins.
March 18, 20179 yr Community Expert Unless you are absolutely sure that the currently assigned disks are the same as those in your backup, you should start without config/super.dat. You will have to assign your disks.
March 18, 20179 yr Author Back up and running!! Decided to go with the re-install, and copy in the config. Everything seems ok! Going to work next on scheduled backups :-) I really appreciate your patience and assistance in resolving this!
Archived
This topic is now archived and is closed to further replies.