Crewe

I first attempted to created a KVM using kemps instructions, but there's no way to load a .disk file in the unRAID VM manager. https://support.kemptechnologies.com/hc/en-us/community/posts/4863998051469-install-kemp-on-kvm?page=1#community_comment_5599497764621 I think it might be an out of date version of virt-manager 2.2 in mber5/virt-manager:latest by RedVex in [CA] vs 4.0 that is current. So then I thought I might create a docker and experiment, but I can't find any guides on how to do such a thing, all I know is that I need some sort of template, and I need to create a repository in GitHub? So no traction there... But I learned they have a docker (https://hub.docker.com/r/kemptech/clm) I want to just run on my server and at least get to a point were I can configure it... Where do I even begin?

Took me a while to locate exactly where that 'New Config' was but I managed to find it thanks.

One last issue. It won't let me start up the server because it says there are too many wrong and/or missing disks. How do I reset that?

Cool, thanks for all the help! I'll fire it up now. Then onto re-adding all my containers and plugins...

As suspected the drive I presumed to be parity was. Neat little workaround. The thing I was concerned about, as it was mentioned in posts/articles I had read was to ensure the order of disks and whatnot when adding a disk as I could lose data. Is the order of my disks still an issue at this point? Or because I have no config and I'm rebuilding the parity my data will remain intact? Also, why would I want to reassign one of the data disks to the slot where the parity used to be? Edit: Ideally, I'd like to have my SATA and Disk numbers match up (although one's zero index :P) Would it be safe to switch up the order now?

One Parity Disk 4 Data Disks No Cache Drives No Unassigned Devices No other drives in the server. I have all the serial numbers of all 5 the drives, however, I haven't been able to find the preclear log.

So I'm finally able to come back to this, had to get through some renos/work/life, but I have carved out some time to hopefully complete this within the week I was unable to find a screen cap of my most recent setup, but I did find one of just before I added my new parity drive. Based on that, and the drive assignments to my SATA ports I was able to determine the following. SATA | DISK | SDX | SIZE | SERIAL ---------------------------------- 0 | ? | sdb | 2TB | GPL 1 | 1 | sdc | 2TB | BQD 2 | 2 | sdd | 1TB | 3M5 3 | P | sde | 4TB | H0Z 4 | ? | sdf* | 4TB | E5C ---------------------------------- P - Parity ? - Unkown Disk Number * - Presumed drive assignment I'm currently in the process of creating a new USB and then to go through with the key change as I still have the email with my license. The couple things I need to know are which what disk number is which. I know I wouldn't have done anything crazy when adding the new drives, but I feel it would be safe to assume that SATA0 is now disk 3 and SATA4 is disk 4, with respect to unRAID. Prior to the above, the last configuration I had was this: SATA | DISK | SDX | SIZE | SERIAL ---------------------------------- 0 | P | sdb | 2TB | GPL 1 | 1 | sdc | 2TB | BQD 2 | 2 | sdd | 1TB | 3M5 3 | - | sde | 4TB | H0Z ---------------------------------- SATA3 Was precleared for use as the new parity but was not assigned yet.

There were many Bad links, which I corrected, but I still see no files on the USB Disk H:\>chkdsk /F The type of the file system is FAT32. Cannot lock current drive. Chkdsk cannot run because the volume is in use by another process. Chkdsk may run if this volume is dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to force a dismount on this volume? (Y/N) y Volume dismounted. All opened handles to this volume are now invalid. Volume Serial Number is 34EE-C82C Windows is verifying files and folders... Removing trailing folder entries from \ File and folder verification is complete. Bad links in lost chain at cluster 218882 corrected. Bad links in lost chain at cluster 221056 corrected. Bad links in lost chain at cluster 221057 corrected. Bad links in lost chain at cluster 221058 corrected. Bad links in lost chain at cluster 221059 corrected. ... [~2800 Lines] ... Bad links in lost chain at cluster 242684 corrected. Bad links in lost chain at cluster 242685 corrected. Bad links in lost chain at cluster 242686 corrected. Bad links in lost chain at cluster 242687 corrected. Convert lost chains to files (Y/N)? y 536240128 bytes in 3416 recovered files. Windows has made corrections to the file system. No further action is required. 1,000,407,040 bytes total disk space. 4,096 bytes in 1 hidden files. 110,592 bytes in 1 folders. 536,248,320 bytes in 3,418 files. 464,039,936 bytes available on disk. 4,096 bytes in each allocation unit. 244,240 total allocation units on disk. 113,291 allocation units available on disk. H:\> However, after opening it on my Linux box there's a `FOUND.000` folder with ~3400 `FILE####.CHK` files... I highly doubt I'll be able to boot with it. Are there any keywords that I would find in the `config` file that I could potentially search on?

I'll see if I can get chkdsk to work tonight, but it appears that I don't have a backup of the config/remember where I may have stored it... Might have been on the server

After trying to upgrade some plugins I encountered an error and the Web UI crashed. So I initiated a reboot from SSH, after several failed attempts to boot I connected the USB to my computer and it couldn't read it. Not sure what my next steps are to get my system up and running again.

That seemed to solve the issue. Wasn't being detected in USB 3 port. Got a bunch of kernel errors on boot, for the bad port. So it looks like some sort of hardware failure. Thanks.

I noticed this several days ago and left well enough alone until I had time. To start, I would like to point out that everything appears to be functional under the hood, at least with storage, accessing shares, and my dockers and apps. Which I consider strange if my flash drive is dead/dying. tldr; My flash potentially bit the dust, what do I do? So when I log into the GUI I'm immediately shown a pop-up to 'Install Statistics Plugin'. When I do this I get: plugin: installing: https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/statistics.sender.plg plugin: downloading https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/statistics.sender.plg plugin: downloading: https://raw.githubusercontent.com/gfjardim/unRAID-plugins/master/plugins/statistics.sender.plg ... done Warning: simplexml_load_file(): I/O warning : failed to load external entity "/boot/config/plugins/statistics.sender.plg" in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 214 plugin: xml parse error If I dismiss it, it goes away, but my screen is blank with the exception of the Lime Tech banner and the menu bar. So I started an SSH session and tried to go to the problem directory /boot/config/plugins but I can't get any farther than /boot because it's empty... root@Limebox:/boot# ls -lah total 4.0K drwxrwxrwx 10 root root 4.0K Dec 31 1969 ./ drwxr-xr-x 18 root root 440 Oct 28 18:03 ../ root@Limebox:/boot# Which leads me to believe that my flash may be corrupted? What are my next steps? Here's an excerpt from my syslog: Nov 8 21:38:01 Limebox root: Nov 8 21:38:01 Limebox root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 Nov 8 21:38:01 Limebox kernel: fat__get_entry: 14 callbacks suppressed Nov 8 21:38:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8192) failed Nov 8 21:38:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8193) failed Nov 8 21:38:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8194) failed Nov 8 21:38:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8195) failed Nov 8 21:38:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8196) failed Nov 8 21:38:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8197) failed Nov 8 21:38:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8198) failed Nov 8 21:38:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8199) failed Nov 8 21:38:01 Limebox root: Nov 8 21:38:01 Limebox root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 Nov 8 21:38:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8192) failed Nov 8 21:38:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8193) failed Nov 8 21:39:01 Limebox root: Nov 8 21:39:01 Limebox root: Warning: file_put_contents(/boot/config/docker.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerconfig.php on line 35 Nov 8 21:39:01 Limebox kernel: fat__get_entry: 14 callbacks suppressed Nov 8 21:39:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8192) failed Nov 8 21:39:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8193) failed Nov 8 21:39:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8194) failed Nov 8 21:39:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8195) failed Nov 8 21:39:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8196) failed Nov 8 21:39:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8197) failed Nov 8 21:39:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8198) failed Nov 8 21:39:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8199) failed Nov 8 21:39:01 Limebox root: Nov 8 21:39:01 Limebox root: Warning: file_put_contents(/boot/config/domain.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/scripts/libvirtconfig.php on line 39 Nov 8 21:39:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8192) failed Nov 8 21:39:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8193) failed syslog

Unfortunately I couldn't do anything once I tried to stop the array and it got caught in that loop.

I'm not too sure when this occurred, but I noticed one day that my sickrage and couch potato stopped working, then when I went to see the dashboard it was blank. When I look at the plugin page for sickrage I get this error: Warning: parse_ini_file(/boot/config/plugins/Sickrage/Sickrage.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/Sickrage/include/Sickrage.php on line 70 and on the plugins page I get: Fatal error: Uncaught exception 'UnexpectedValueException' with message 'RecursiveDirectoryIterator::__construct(/boot/config/plugins/dockerMan/templates-user): failed to open dir: No such file or directory' in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php:78 Stack trace: #0 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(78): RecursiveDirectoryIterator->__construct('/boot/config/pl...', 4096) #1 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(109): DockerTemplates->listDir('/boot/config/pl...', 'xml') #2 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(210): DockerTemplates->getTemplates('all') #3 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(361): DockerTemplates->getTemplateValue('linuxserver/bee...', 'Banner') #4 /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php(324): DockerTemplates->getBannerIcon('linuxserver/bee...') #5 /usr/local/emhttp/plugins/dynamix/include in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 78 Warning: parse_ini_file(/boot/config/plugins/Couchpotato/Couchpotato.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/Couchpotato/include/Couchpotato.php on line 70 Most other pages display an error also. I see the following 'bread' error in my syslog: May 24 22:15:01 Limebox sSMTP[11083]: Creating SSL connection to host May 24 22:15:01 Limebox sSMTP[11083]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256 May 24 22:15:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8192) failed May 24 22:15:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8193) failed May 24 22:15:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8194) failed May 24 22:15:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8195) failed May 24 22:15:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8196) failed May 24 22:15:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8197) failed May 24 22:15:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8198) failed May 24 22:15:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8199) failed May 24 22:15:01 Limebox sSMTP[11083]: Authorization failed (535 5.7.8 https://support.google.com/mail/answer/14257 ho7sm6386624igc.16 - gsmtp) May 24 22:16:02 Limebox kernel: FAT-fs (sda1): Directory bread(block 8192) failed May 24 22:16:02 Limebox kernel: FAT-fs (sda1): Directory bread(block 8193) failed May 24 22:16:02 Limebox kernel: FAT-fs (sda1): Directory bread(block 8194) failed May 24 22:16:02 Limebox kernel: FAT-fs (sda1): Directory bread(block 8195) failed May 24 22:16:02 Limebox kernel: FAT-fs (sda1): Directory bread(block 8196) failed May 24 22:16:02 Limebox kernel: FAT-fs (sda1): Directory bread(block 8197) failed May 24 22:16:02 Limebox kernel: FAT-fs (sda1): Directory bread(block 8198) failed May 24 22:16:02 Limebox kernel: FAT-fs (sda1): Directory bread(block 8199) failed May 24 22:17:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8192) failed May 24 22:17:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8193) failed May 24 22:17:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8194) failed May 24 22:17:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8195) failed May 24 22:17:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8196) failed May 24 22:17:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8197) failed May 24 22:17:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8198) failed May 24 22:17:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8199) failed May 24 22:18:01 Limebox kernel: FAT-fs (sda1): Directory bread(block 8192) failed I just tried to stop the array in an attempt to shut it down and now it's stuck trying to unmount the drives: May 25 00:37:53 Limebox kernel: FAT-fs (sda1): FAT read failed (blocknr 5254) May 25 00:37:54 Limebox kernel: FAT-fs (sda1): Directory bread(block 8192) failed May 25 00:37:54 Limebox kernel: FAT-fs (sda1): Directory bread(block 8193) failed May 25 00:37:59 Limebox kernel: fat__get_entry: 30 callbacks suppressed May 25 00:37:59 Limebox kernel: FAT-fs (sda1): Directory bread(block 8192) failed May 25 00:37:59 Limebox kernel: FAT-fs (sda1): Directory bread(block 8193) failed May 25 00:37:59 Limebox kernel: FAT-fs (sda1): Directory bread(block 8194) failed May 25 00:37:59 Limebox kernel: FAT-fs (sda1): Directory bread(block 8195) failed May 25 00:37:59 Limebox kernel: FAT-fs (sda1): Directory bread(block 8196) failed May 25 00:37:59 Limebox kernel: FAT-fs (sda1): Directory bread(block 8197) failed May 25 00:37:59 Limebox kernel: FAT-fs (sda1): Directory bread(block 8198) failed May 25 00:37:59 Limebox kernel: FAT-fs (sda1): Directory bread(block 8199) failed May 25 00:38:00 Limebox kernel: FAT-fs (sda1): Directory bread(block 8192) failed May 25 00:38:00 Limebox kernel: FAT-fs (sda1): Directory bread(block 8193) failed May 25 00:38:00 Limebox kernel: mdcmd (17): nocheck May 25 00:38:00 Limebox kernel: md: nocheck_array: check not active May 25 00:38:00 Limebox emhttp: Stopping Docker... May 25 00:38:00 Limebox logger: stopping docker ... May 25 00:38:01 Limebox logger: b5f2c2746583 May 25 00:38:01 Limebox kernel: vethf855689: renamed from eth0 May 25 00:38:01 Limebox kernel: docker0: port 4(veth206a8ab) entered disabled state May 25 00:38:01 Limebox kernel: docker0: port 4(veth206a8ab) entered disabled state May 25 00:38:01 Limebox avahi-daemon[19548]: Withdrawing workstation service for vethf855689. May 25 00:38:01 Limebox avahi-daemon[19548]: Withdrawing workstation service for veth206a8ab. May 25 00:38:01 Limebox kernel: device veth206a8ab left promiscuous mode May 25 00:38:01 Limebox kernel: docker0: port 4(veth206a8ab) entered disabled state May 25 00:38:02 Limebox logger: 7f4cb273ee4b May 25 00:38:12 Limebox kernel: vethc4708bb: renamed from eth0 May 25 00:38:12 Limebox kernel: docker0: port 2(veth5d80f3c) entered disabled state May 25 00:38:12 Limebox kernel: docker0: port 2(veth5d80f3c) entered disabled state May 25 00:38:12 Limebox avahi-daemon[19548]: Withdrawing workstation service for vethc4708bb. May 25 00:38:12 Limebox avahi-daemon[19548]: Withdrawing workstation service for veth5d80f3c. May 25 00:38:12 Limebox kernel: device veth5d80f3c left promiscuous mode May 25 00:38:12 Limebox kernel: docker0: port 2(veth5d80f3c) entered disabled state May 25 00:38:12 Limebox logger: eff087b8af5c May 25 00:38:12 Limebox kernel: veth8ca9392: renamed from eth0 May 25 00:38:12 Limebox kernel: docker0: port 1(veth577d4c7) entered disabled state May 25 00:38:12 Limebox kernel: docker0: port 1(veth577d4c7) entered disabled state May 25 00:38:12 Limebox avahi-daemon[19548]: Withdrawing workstation service for veth8ca9392. May 25 00:38:12 Limebox kernel: device veth577d4c7 left promiscuous mode May 25 00:38:12 Limebox kernel: docker0: port 1(veth577d4c7) entered disabled state May 25 00:38:12 Limebox avahi-daemon[19548]: Withdrawing workstation service for veth577d4c7. May 25 00:38:12 Limebox logger: 4b615b565fdd May 25 00:38:14 Limebox kernel: vethece4663: renamed from eth0 May 25 00:38:14 Limebox kernel: docker0: port 3(vethbbfdf19) entered disabled state May 25 00:38:14 Limebox kernel: docker0: port 3(vethbbfdf19) entered disabled state May 25 00:38:14 Limebox avahi-daemon[19548]: Withdrawing workstation service for vethece4663. May 25 00:38:14 Limebox avahi-daemon[19548]: Withdrawing workstation service for vethbbfdf19. May 25 00:38:14 Limebox kernel: device vethbbfdf19 left promiscuous mode May 25 00:38:14 Limebox kernel: docker0: port 3(vethbbfdf19) entered disabled state May 25 00:38:14 Limebox logger: 43c94cf230e2 May 25 00:38:15 Limebox logger: unmounting docker loopback May 25 00:38:15 Limebox emhttp: Stopping libvirt... May 25 00:38:15 Limebox logger: libvirt is not running... May 25 00:38:15 Limebox emhttp: Stop AVAHI... May 25 00:38:15 Limebox emhttp: shcmd (166): /etc/rc.d/rc.avahidaemon stop |& logger May 25 00:38:15 Limebox logger: Stopping Avahi mDNS/DNS-SD Daemon: stopped May 25 00:38:15 Limebox avahi-daemon[19548]: Got SIGTERM, quitting. May 25 00:38:15 Limebox avahi-dnsconfd[19557]: read(): EOF May 25 00:38:15 Limebox avahi-daemon[19548]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.35.16. May 25 00:38:15 Limebox avahi-daemon[19548]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.42.1. May 25 00:38:15 Limebox avahi-daemon[19548]: avahi-daemon 0.6.31 exiting. May 25 00:38:16 Limebox emhttp: shcmd (167): /etc/rc.d/rc.avahidnsconfd stop |& logger May 25 00:38:16 Limebox logger: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped May 25 00:38:16 Limebox emhttp: shcmd (168): /etc/rc.d/rc.atalk status May 25 00:38:16 Limebox emhttp: Stop AFP... May 25 00:38:16 Limebox emhttp: shcmd (169): /etc/rc.d/rc.atalk stop |& logger May 25 00:38:16 Limebox emhttp: shcmd (170): rm -f /etc/avahi/services/afp.service May 25 00:38:16 Limebox emhttp: shcmd (171): pidof rpc.mountd &> /dev/null May 25 00:38:16 Limebox emhttp: Stop SMB... May 25 00:38:16 Limebox emhttp: shcmd (172): /etc/rc.d/rc.samba stop |& logger May 25 00:38:16 Limebox logger: cp: cannot create regular file '/boot/config': Input/output error May 25 00:38:16 Limebox emhttp: shcmd (173): rm -f /etc/avahi/services/smb.service May 25 00:38:16 Limebox kernel: fat__get_entry: 6 callbacks suppressed May 25 00:38:16 Limebox kernel: FAT-fs (sda1): Directory bread(block 8192) failed May 25 00:38:16 Limebox kernel: FAT-fs (sda1): Directory bread(block 8193) failed May 25 00:38:16 Limebox kernel: FAT-fs (sda1): Directory bread(block 8194) failed May 25 00:38:16 Limebox kernel: FAT-fs (sda1): Directory bread(block 8195) failed May 25 00:38:16 Limebox kernel: FAT-fs (sda1): Directory bread(block 8196) failed May 25 00:38:16 Limebox kernel: FAT-fs (sda1): Directory bread(block 8197) failed May 25 00:38:16 Limebox kernel: FAT-fs (sda1): Directory bread(block 8198) failed May 25 00:38:16 Limebox kernel: FAT-fs (sda1): Directory bread(block 8199) failed May 25 00:38:16 Limebox kernel: FAT-fs (sda1): Directory bread(block 8192) failed May 25 00:38:16 Limebox kernel: FAT-fs (sda1): Directory bread(block 8193) failed May 25 00:38:16 Limebox kernel: FAT-fs (sda1): FAT read failed (blocknr 5254) May 25 00:38:16 Limebox emhttp: Spinning up all drives... May 25 00:38:16 Limebox kernel: mdcmd (18): spinup 0 May 25 00:38:16 Limebox kernel: mdcmd (19): spinup 1 May 25 00:38:16 Limebox kernel: mdcmd (20): spinup 2 May 25 00:38:16 Limebox ntpd[1549]: Deleting interface #8 docker0, 172.17.42.1#123, interface stats: received=0, sent=0, dropped=0, active_time=976036 secs May 25 00:38:17 Limebox emhttp: Sync filesystems... May 25 00:38:17 Limebox emhttp: shcmd (174): sync May 25 00:38:17 Limebox emhttp: May 25 00:38:17 Limebox emhttp: May 25 00:38:17 Limebox emhttp: shcmd (175): set -o pipefail ; umount /mnt/user |& logger May 25 00:38:17 Limebox logger: umount: /mnt/user: device is busy. May 25 00:38:17 Limebox logger: (In some cases useful info about processes that use May 25 00:38:17 Limebox logger: the device is found by lsof( or fuser(1)) May 25 00:38:17 Limebox emhttp: shcmd: shcmd (175): exit status: 1 May 25 00:38:17 Limebox emhttp: shcmd (176): rmdir /mnt/user |& logger May 25 00:38:17 Limebox logger: rmdir: failed to remove '/mnt/user': Device or resource busy May 25 00:38:17 Limebox emhttp: shcmd (177): rm -f /boot/config/plugins/dynamix/mover.cron May 25 00:38:17 Limebox emhttp: shcmd (178): /usr/local/sbin/update_cron &> /dev/null May 25 00:38:17 Limebox emhttp: Retry unmounting user share(s)... May 25 00:38:22 Limebox emhttp: shcmd (179): set -o pipefail ; umount /mnt/user |& logger May 25 00:38:22 Limebox logger: umount: /mnt/user: device is busy. May 25 00:38:22 Limebox logger: (In some cases useful info about processes that use May 25 00:38:22 Limebox logger: the device is found by lsof( or fuser(1)) May 25 00:38:22 Limebox emhttp: shcmd: shcmd (179): exit status: 1 May 25 00:38:22 Limebox emhttp: shcmd (180): rmdir /mnt/user |& logger May 25 00:38:22 Limebox logger: rmdir: failed to remove '/mnt/user': Device or resource busy May 25 00:38:22 Limebox emhttp: shcmd (181): rm -f /boot/config/plugins/dynamix/mover.cron May 25 00:38:22 Limebox emhttp: shcmd (182): /usr/local/sbin/update_cron &> /dev/null May 25 00:38:22 Limebox emhttp: Retry unmounting user share(s)... May 25 00:38:27 Limebox emhttp: shcmd (183): set -o pipefail ; umount /mnt/user |& logger May 25 00:38:27 Limebox logger: umount: /mnt/user: device is busy. May 25 00:38:27 Limebox logger: (In some cases useful info about processes that use May 25 00:38:27 Limebox logger: the device is found by lsof( or fuser(1)) May 25 00:38:27 Limebox emhttp: shcmd: shcmd (183): exit status: 1 May 25 00:38:27 Limebox emhttp: shcmd (184): rmdir /mnt/user |& logger May 25 00:38:27 Limebox logger: rmdir: failed to remove '/mnt/user': Device or resource busy May 25 00:38:27 Limebox emhttp: shcmd (185): rm -f /boot/config/plugins/dynamix/mover.cron May 25 00:38:27 Limebox emhttp: shcmd (186): /usr/local/sbin/update_cron &> /dev/null May 25 00:38:27 Limebox emhttp: Retry unmounting user share(s)... May 25 00:38:32 Limebox emhttp: shcmd (187): set -o pipefail ; umount /mnt/user |& logger May 25 00:38:32 Limebox logger: umount: /mnt/user: device is busy. May 25 00:38:32 Limebox logger: (In some cases useful info about processes that use May 25 00:38:32 Limebox logger: the device is found by lsof( or fuser(1)) May 25 00:38:32 Limebox emhttp: shcmd: shcmd (187): exit status: 1 May 25 00:38:32 Limebox emhttp: shcmd (188): rmdir /mnt/user |& logger May 25 00:38:32 Limebox logger: rmdir: failed to remove '/mnt/user': Device or resource busy May 25 00:38:32 Limebox emhttp: shcmd (189): rm -f /boot/config/plugins/dynamix/mover.cron May 25 00:38:32 Limebox emhttp: shcmd (190): /usr/local/sbin/update_cron &> /dev/null May 25 00:38:32 Limebox emhttp: Retry unmounting user share(s)... May 25 00:38:37 Limebox emhttp: shcmd (191): set -o pipefail ; umount /mnt/user |& logger May 25 00:38:37 Limebox logger: umount: /mnt/user: device is busy. May 25 00:38:37 Limebox logger: (In some cases useful info about processes that use May 25 00:38:37 Limebox logger: the device is found by lsof( or fuser(1)) May 25 00:38:37 Limebox emhttp: shcmd: shcmd (191): exit status: 1 May 25 00:38:37 Limebox emhttp: shcmd (192): rmdir /mnt/user |& logger May 25 00:38:37 Limebox logger: rmdir: failed to remove '/mnt/user': Device or resource busy May 25 00:38:37 Limebox emhttp: shcmd (193): rm -f /boot/config/plugins/dynamix/mover.cron May 25 00:38:37 Limebox emhttp: shcmd (194): /usr/local/sbin/update_cron &> /dev/null May 25 00:38:37 Limebox emhttp: Retry unmounting user share(s)... May 25 00:38:42 Limebox emhttp: shcmd (195): set -o pipefail ; umount /mnt/user |& logger Not quite sure what to do as it's scheduled to do a parity check, and I can't stop it. I don't know what will happen... Is my only option to hard reset? Should I replace my flash drive? I read that some people had issues due to it being in a USB 3.0 slot, but it had been running without major issue for the past 6 months on the same port. unraid-syslog-may-25-2016.txt

I had check the files, and they seemed okay, but I had to do it a few times for it to "take" but that did the trick. Some plugins failed/are gone but I can live with that. Thanks.