Install Statistics Plugin?

[ptmuldoon]

I wanted to check the status of 2 drives I have pre-clearing (separate topic on that) this morning.

 

But when I log into the GUI, I am being asked via popup to Install the Statistics Plugin, which I believe is already installed.    I do try to install it and then get an error the below.

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

 

And I choose Dismiss it just pops back up asking to install and I can't see to check anything in the GUI?

 

Is the best thing to do a manual shutdown via command line?  And if so, what would be the correct commands to stop the array first before a reboot?

[ptmuldoon]

Well,

 

I logged in to my UnRaid Server and it appears my entire boot directory is either missing or empty which is quite strange since the system is currently up and running.  I have no idea what could have caused that and do/did have preclear running on 2 drives as well that are currently stuck or 'frozen'

 

I'm hesitant to reboot the Server remotely with the fear it may not reboot. I am out of town and the wife does like to stream exercise videos each morning.  My Unraid is running as a VM in ESXi, so unsure what could have caused the boot directory to show as empty.   

 

So before likely having to do a forced reboot, any suggestions?  Seems with an empty/missing /boot directory I can't seem to shutdown the array via CLI either?

Edited February 28, 2017 by ptmuldoon

[trurl]

Since your flash isn't there it won't be able to write a clean shutdown anyway.

[ptmuldoon]

This has happened now 3 time for me recently, and have no idea what could causing it.    I run Unraid as a VM on ESXI and the USB stick shows correctly on the VM.  Yet when I log into Unraid, I can greeted with this Popup message and only way around is to reboot the machine.

 

I think its part of the preclear plugin and i'm going to remove/uninstall that in trying to learn if that is the cause.  I can navigate my shares fine from another PC and seems all is in order.  But can't do anything within the unraid GUI with this pop up message occurring.

[RobJ]

3 hours ago, ptmuldoon said:

I think its part of the preclear plugin and i'm going to remove/uninstall that in trying to learn if that is the cause.

 

That's part of the new Preclear statistics function, apparently not working for you.  Preclear has been updated, try updating it to the latest and see if it still happens.  If it does, post again in the Preclear plugin support thread.

[gfjardim]

4 hours ago, ptmuldoon said:

This has happened now 3 time for me recently, and have no idea what could causing it.    I run Unraid as a VM on ESXI and the USB stick shows correctly on the VM.  Yet when I log into Unraid, I can greeted with this Popup message and only way around is to reboot the machine.

 

I think its part of the preclear plugin and i'm going to remove/uninstall that in trying to learn if that is the cause.  I can navigate my shares fine from another PC and seems all is in order.  But can't do anything within the unraid GUI with this pop up message occurring.

 

 

When you hit the DISMISS button, a file is written into your flash device (/boot directory) and that choice remains valid until the plugin gets updated. In your case, the only think you can do is remove /usr/local/emhttp/plugins/preclear.disk/StatsInstall.page file until you fix the flash disk problem.

 

Sorry for the inconvenience.

[Squid]

14 minutes ago, gfjardim said:

When you hit the DISMISS button, a file is written into your flash device (/boot directory) and that choice remains valid until the plugin gets updated

Wouldn't it be better and less intrusive to have it that once you dismiss the option then it's dismissed forever until you uninstall / reinstall the plugin?

[nia]

I'm starting to see the same behaviour - also on ESXi (version 6.0.0). 

 

Could it be that the passthrough of the USB is not quite stable, and this triggers this? 

 

Also - my syslog has this pattern repeating quickly filling the 3 generations saved in /var/log folder.

 

Please note: /boot folder is empty when looking at it from console login.

 

May 13 04:40:01 Tower liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.23.0" x-pid="1779" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
May 13 04:40:01 Tower root: 
May 13 04:40:01 Tower 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
May 13 04:40:01 Tower kernel: fat__get_entry: 86 callbacks suppressed
May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed
May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed
May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed
May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed
May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed
May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed
May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed
May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed
May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed
May 13 04:40:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed
May 13 04:40:01 Tower root: 
May 13 04:40:01 Tower 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
May 13 04:40:01 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0
May 13 04:40:01 Tower kernel: floppy: error -5 while reading block 0
May 13 04:40:55 Tower kernel: usb 1-1: reset high-speed USB device number 3 using ehci-pci
May 13 04:40:55 Tower kernel: sd 6:0:0:0: [sdr] 3987456 512-byte logical blocks: (2.04 GB/1.90 GiB)
May 13 04:40:55 Tower kernel: sdr: sdr1
May 13 04:41:01 Tower root: 
May 13 04:41:01 Tower 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
May 13 04:41:01 Tower kernel: fat__get_entry: 86 callbacks suppressed
May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed
May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed
May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed
May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed
May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed
May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed
May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed
May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed
May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed
May 13 04:41:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed
May 13 04:41:01 Tower root: 
May 13 04:41:01 Tower 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
May 13 04:41:01 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0
May 13 04:41:01 Tower kernel: floppy: error -5 while reading block 0
May 13 04:42:01 Tower root: 
May 13 04:42:01 Tower 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
May 13 04:42:01 Tower kernel: fat__get_entry: 86 callbacks suppressed
May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed
May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed
May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed
May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed
May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed
May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed
May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed
May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed
May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed
May 13 04:42:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed
May 13 04:42:01 Tower root: 
May 13 04:42:01 Tower 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
May 13 04:42:01 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0
May 13 04:42:01 Tower kernel: floppy: error -5 while reading block 0
May 13 04:42:59 Tower kernel: usb 1-1: reset high-speed USB device number 3 using ehci-pci
May 13 04:42:59 Tower kernel: sd 6:0:0:0: [sdr] 3987456 512-byte logical blocks: (2.04 GB/1.90 GiB)
May 13 04:42:59 Tower kernel: sdr: sdr1
May 13 04:43:01 Tower kernel: fat__get_entry: 86 callbacks suppressed
May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed
May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed
May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed
May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed
May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed
May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed
May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed
May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed
May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed
May 13 04:43:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed
May 13 04:43:01 Tower root: 
May 13 04:43:01 Tower 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
May 13 04:43:01 Tower root: 
May 13 04:43:01 Tower 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
May 13 04:43:01 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0
May 13 04:43:01 Tower kernel: floppy: error -5 while reading block 0
May 13 04:43:53 Tower kernel: usb 1-1: reset high-speed USB device number 3 using ehci-pci
May 13 04:43:53 Tower kernel: sd 6:0:0:0: [sdr] 3987456 512-byte logical blocks: (2.04 GB/1.90 GiB)
May 13 04:43:53 Tower kernel: sdr: sdr1
May 13 04:44:01 Tower root: 
May 13 04:44:01 Tower 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
May 13 04:44:01 Tower kernel: fat__get_entry: 86 callbacks suppressed
May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed
May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed
May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed
May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed
May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed
May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed
May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed
May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed
May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed
May 13 04:44:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed
May 13 04:44:01 Tower root: 
May 13 04:44:01 Tower 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
May 13 04:44:01 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0
May 13 04:44:01 Tower kernel: floppy: error -5 while reading block 0
May 13 04:45:01 Tower root: 
May 13 04:45:01 Tower 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
May 13 04:45:01 Tower kernel: fat__get_entry: 86 callbacks suppressed
May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed
May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed
May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed
May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed
May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed
May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed
May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed
May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed
May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed
May 13 04:45:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed
May 13 04:45:01 Tower root: 
May 13 04:45:01 Tower 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
May 13 04:45:01 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0
May 13 04:45:01 Tower kernel: floppy: error -5 while reading block 0
May 13 04:46:02 Tower root: 
May 13 04:46:02 Tower 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
May 13 04:46:02 Tower kernel: fat__get_entry: 86 callbacks suppressed
May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed
May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed
May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed
May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed
May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed
May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed
May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed
May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed
May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed
May 13 04:46:02 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed
May 13 04:46:02 Tower root: 
May 13 04:46:02 Tower 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
May 13 04:46:02 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0
May 13 04:46:02 Tower kernel: floppy: error -5 while reading block 0
May 13 04:46:15 Tower kernel: usb 1-1: reset high-speed USB device number 3 using ehci-pci
May 13 04:46:15 Tower kernel: sd 6:0:0:0: [sdr] 3987456 512-byte logical blocks: (2.04 GB/1.90 GiB)
May 13 04:46:15 Tower kernel: sdr: sdr1
May 13 04:46:16 Tower kernel: fat__get_entry: 54 callbacks suppressed
May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed
May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed
May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed
May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed
May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed
May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed
May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed
May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed
May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed
May 13 04:46:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed
May 13 04:47:01 Tower kernel: fat__get_entry: 22 callbacks suppressed
May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed
May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed
May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 498) failed
May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 499) failed
May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 500) failed
May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 501) failed
May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 502) failed
May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 503) failed
May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 504) failed
May 13 04:47:01 Tower kernel: FAT-fs (sdq1): Directory bread(block 505) failed
May 13 04:47:01 Tower root: 
May 13 04:47:01 Tower 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
May 13 04:47:01 Tower root: 
May 13 04:47:01 Tower 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
May 13 04:47:01 Tower kernel: blk_update_request: I/O error, dev fd0, sector 0
May 13 04:47:01 Tower kernel: floppy: error -5 while reading block 0
May 13 04:47:15 Tower kernel: usb 1-1: reset high-speed USB device number 3 using ehci-pci
May 13 04:47:15 Tower kernel: sd 6:0:0:0: [sdr] 3987456 512-byte logical blocks: (2.04 GB/1.90 GiB)
May 13 04:47:15 Tower kernel: sdr: sdr1
May 13 04:47:16 Tower kernel: fat__get_entry: 54 callbacks suppressed
May 13 04:47:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 496) failed
May 13 04:47:16 Tower kernel: FAT-fs (sdq1): Directory bread(block 497) failed

 

Edited May 15, 2017 by nia
Added logfile section

[Squid]

Your flash drive is dropping offline which plays havoc with the system when you change a setting, install an app, reboot, etc.  Try a different USB controller

[nia]

1 hour ago, Squid said:

Your flash drive is dropping offline which plays havoc with the system when you change a setting, install an app, reboot, etc.  Try a different USB controller

Thanks for the suggestion and fast response :-) (PS: Also just just discovered and installed your Ransomware Protection - thanks!)

 

According to your suggestion, I changed passthrough to one of the USB headers on the motherboard (connected to a USB bracket I had lying around) and mapped that through. Also in earlier I tried changing to FreeBSD64 bit in stead od 32 bit as someone in a different thread suggested. Unfortunately, the resets remain, and probably at some point the USB key will drop off again. BTW i have also tried mapping a second USB port through (another suggested fix) to no avail. This is an ongoing unRAID on ESXi issue, and unfortunately these suggestions did not solve it. 

 

Also - this discussion is drifting off-topic fast, so to address the issue at hand in this thread, I have uninstalled preclear script, so the blocking pop-up should not pop up later if/when the USB key drops off again. Let's see how that pans out...

[truetype]

I have this problem too, but I am not running ESXi, just normal unraid and have been running it for 2.5 years now without this issue.

This started with the previous update. I installed the Statistics Plugin like 1 year ago.

 

Any solution to this? This is really frustrating

 

And anyone know how I can shut the server down a safe way using SSH?

Just typing "powerdown" did the trick to shutdown, but when it boots up again it starts doing a parity check for 12 hours...

Edited June 7, 2017 by truetype

[Squid]

No matter what you do, if the flash drive drops offline or it can't be written to you will wind up with having a parity check being done at startup. (entirely up to you if you choose to let it continue)

Sent from my LG-D852 using Tapatalk

[truetype]

25 minutes ago, Squid said:

No matter what you do, if the flash drive drops offline or it can't be written to you will wind up with having a parity check being done at startup. (entirely up to you if you choose to let it continue)

Sent from my LG-D852 using Tapatalk
 

I don't even know if the Flash drive went offline or anything, do you think this is the cause? A faulty flash drive?

I perfer letting it complete the parity check if it wants to do one.  

[trurl]

2 hours ago, truetype said:

I perfer letting it complete the parity check if it wants to do one.

It would be more accurate to say that it is performing a parity check because it has forgotten that it doesn't need to. You get a parity check if you start from an unclean shutdown. A clean shutdown is recorded on your flash drive, but if flash is missing, it can't record it.

 

When you start the array, the fact that it is started is written into config/super.dat (which also contains your disk assignments). When you shutdown, the array is stopped first, and the fact that it is stopped is written into config/super.dat.

 

If your flash is missing, it can't remember that you stopped the array because config/super.dat says it wasn't stopped. So it does a parity check.

[truetype]

2 minutes ago, trurl said:

It would be more accurate to say that it is performing a parity check because it has forgotten that it doesn't need to. 

Ooh, okey so that's how it works. Thanks for explaining.

So now when we got the proof that it is sometimes getting disconnected, what could be the cause of it and how could it be fixed? Any suggestions how to troubleshoot it? 

[trurl]

3 minutes ago, truetype said:

Ooh, okey so that's how it works. Thanks for explaining.

So now when we got the proof that it is sometimes getting disconnected, what could be the cause of it and how could it be fixed? Any suggestions how to troubleshoot it? 

Try a different USB port.

[truetype]

2 minutes ago, trurl said:

Try a different USB port.

I'll start there

[Squid]

4 hours ago, truetype said:

do you think this is the cause? A faulty flash drive?

The reason why I suggested the flash drive dropping offline is because you posted in a thread saying that you had the same problem, and the thread is about the flash drive dropping offline.

 

[johnny121b]

Apparently this is still a thing- even with UnRAID 6 and an up-to-date preclear plugin, because my system has suddenly started giving the "Preclear Disks Install Statistics Plugin" prompt. 

 

It looks as though I'm going to be forced to restart my server via commandline- NONE of my SMB shares are accessible via my PC, though PLEX/Sonarr/NZBGet dockers are all humming right along.  I've read the earlier comments- along the lines that it's caused by my USB drive dropping offline, but I doubt that theory, since my server's been running for months w/o incident.  I [am] more inclined to believe there's something wonky with the USB port handling- since the only thing that's new about this scenario, is that two days ago I begun a preclear on a drive connected via a USB docking station.  The last email update I received was at 9:15am this morning, stating that "Post-Read started on...."

 

At this point, is there anything I can do that can get me past the incessant "Preclear Disks Install Statistics Plugin" prompt and do a CLEAN shutdown while NOT potentially wasting the last 3 days' activity in preclearing the drive???

[Squid]

9 minutes ago, johnny121b said:

At this point, is there anything I can do that can get me past the incessant "Preclear Disks Install Statistics Plugin" prompt and do a CLEAN shutdown while NOT potentially wasting the last 3 days' activity in preclearing the drive???

This continual nagging with wanting to install the Stats plugin happens if the flash drive drops offline (this is a complaint I have with preclear, and the author wasn't interested in making a one line change to fix this).  Only way around it is from the command prompt

powerdown -r

  You will however get a parity check happening after it comes back because the system doesn't think it did a clean shutdown (because the flash was offline), even though it is.  Up to you whether you cancel it or not.

 

EDIT:  BTW, preclear is flagged as being incompatible with 6.4.1+

Edited March 11, 2018 by Squid

[johnny121b]

On 3/11/2018 at 5:54 PM, Squid said:

the author wasn't interested in making a one line change to fix this).

 

EDIT:  BTW, preclear is flagged as being incompatible with 6.4.1+

 

Thanks for letting me know- of the plugin's problem and the author's disposition.  I'm running v6.35, so there was no outward indication anything was amiss when I looked at my plugins list.  I've since uninstalled both it and the stats plugin and read-up on a bit of the plugin's recent discussions.  Apparently preclear is a more heated matter than I would've thought- a real shame;  I liked the idea of sidestepping a command-line entirely.