April 19, 20179 yr I am on 6.3.2 and when i go to the gui page i get a staticstics error message and hit install and get " 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 then i just get the gui header. Everything else is running. If this is the boot disk is there a way i can save everything from flash and move it to another boot disk? Scared to reboot. Also I can run diagnostics but it doesnt create the file in boot/logs since it is empty. Can I redirect it? Thanks, Timbiotic
April 19, 20179 yr Where are you running the diagnostics from--- The command line or the GUI? From the command line, it saves it to the Flash Drive. From the GUI, it saves to your default download directory for your browser.
April 19, 20179 yr I think this must be the preclear statistics plugin. But it sounds like your flash drive has become unmounted somehow. It's not entirely clear from your post. Can you use the webUI at all? Sounds like you have attempted to run diagnostics at the command line, but since the flash drive isn't mounted you can't get anything saved there. But you should be able to get the syslog(s) manually the old way, since they are in /var/log. You can type "//tower/log/syslog" in your browser address bar (if you changed the name of your server, use that name instead of 'tower'). Then select/copy/paste the text, put into a txt file, and attach to your post. Also try //tower/log/syslog.1 and //tower/log/syslog.2 in case there are older logs in there too. If that doesn't work we can try something from the command line. Are you using puTTY to get to the command line? Ultimately, I think you are going to have to reboot, but it shouldn't be a problem for your data even if you have to get another flash drive going. Do you know your drive assignments?
April 19, 20179 yr Author 32 minutes ago, trurl said: I think this must be the preclear statistics plugin. But it sounds like your flash drive has become unmounted somehow. It's not entirely clear from your post. Can you use the webUI at all? Sounds like you have attempted to run diagnostics at the command line, but since the flash drive isn't mounted you can't get anything saved there. But you should be able to get the syslog(s) manually the old way, since they are in /var/log. You can type "//tower/log/syslog" in your browser address bar (if you changed the name of your server, use that name instead of 'tower'). Then select/copy/paste the text, put into a txt file, and attach to your post. Also try //tower/log/syslog.1 and //tower/log/syslog.2 in case there are older logs in there too. If that doesn't work we can try something from the command line. Are you using puTTY to get to the command line? Ultimately, I think you are going to have to reboot, but it shouldn't be a problem for your data even if you have to get another flash drive going. Do you know your drive assignments? I can only use the header for the webui and it keeps prompting for preclear statistics install. I dont know my drive assignments and it looks like maybe the flash drive has gone south. Attached is syslog syslog.zip
April 19, 20179 yr Author yes i am using putty and my plugins are all running and the os appears fine
April 19, 20179 yr That syslog is just full of problems accessing flash. Did you try to get any of the earlier syslogs like I suggested? If we could get an earlier one we would be able to see your drive assignments. It may be the flash drive itself is OK but the port it is plugged into was flaky and so unRAID lost it at some point after it booted. Not sure what you mean by this 6 minutes ago, Timbiotic said: I can only use the header for the webui Maybe a screenshot would clear that up.
April 19, 20179 yr Author I dismiss the statistics demand prompt and I get just the headers. Attached is historic log syslog1.zip
April 19, 20179 yr OK, that syslog has your drive assignments Feb 19 12:53:38 lillis emhttp: Samsung_SSD_840_PRO_Series_S1ATNEAD554329V (sdd) 250059064 Feb 19 12:53:38 lillis kernel: mdcmd (1): import 0 sdk 2930266532 0 ST33000650SS_Z290WQTB00009143U6HG_35000c50034d2b90b Feb 19 12:53:38 lillis kernel: md: import disk0: (sdk) ST33000650SS_Z290WQTB00009143U6HG_35000c50034d2b90b size: 2930266532 Feb 19 12:53:38 lillis kernel: mdcmd (2): import 1 sda 976762552 0 WDC_WD1002FBYS-02A6B0_WD-WMATV1662378 Feb 19 12:53:38 lillis kernel: md: import disk1: (sda) WDC_WD1002FBYS-02A6B0_WD-WMATV1662378 size: 976762552 Feb 19 12:53:38 lillis kernel: mdcmd (3): import 2 sdb 976762552 0 WDC_WD1002FBYS-02A6B0_WD-WMATV1881602 Feb 19 12:53:38 lillis kernel: md: import disk2: (sdb) WDC_WD1002FBYS-02A6B0_WD-WMATV1881602 size: 976762552 Feb 19 12:53:38 lillis kernel: mdcmd (4): import 3 sdh 2930266532 0 ST33000650SS_Z290DD3B00009139NM1X_35000c5003504301b Feb 19 12:53:38 lillis kernel: md: import disk3: (sdh) ST33000650SS_Z290DD3B00009139NM1X_35000c5003504301b size: 2930266532 Feb 19 12:53:38 lillis kernel: mdcmd (5): import 4 sdi 2930266532 0 ST33000650SS_Z290AVDQ0000S110VSQ2_35000c50034fd34d3 Feb 19 12:53:38 lillis kernel: md: import disk4: (sdi) ST33000650SS_Z290AVDQ0000S110VSQ2_35000c50034fd34d3 size: 2930266532 Feb 19 12:53:38 lillis kernel: mdcmd (6): import 5 sde 976762552 0 WDC_WD1002FBYS-02A6B0_WD-WMATV1660558 Feb 19 12:53:38 lillis kernel: md: import disk5: (sde) WDC_WD1002FBYS-02A6B0_WD-WMATV1660558 size: 976762552 Feb 19 12:53:38 lillis kernel: mdcmd (7): import 6 sdj 2930266532 0 ST33000650SS_Z290WSAH00009152KX7X_35000c50034d2921f Feb 19 12:53:38 lillis kernel: md: import disk6: (sdj) ST33000650SS_Z290WSAH00009152KX7X_35000c50034d2921f size: 2930266532 Feb 19 12:53:38 lillis kernel: mdcmd (8): import 7 sdg 976762552 0 Hitachi_HUA722010CLA330_JPW9K0N11UL80L Feb 19 12:53:38 lillis kernel: md: import disk7: (sdg) Hitachi_HUA722010CLA330_JPW9K0N11UL80L size: 976762552 Feb 19 12:53:38 lillis kernel: mdcmd (9): import 8 sdf 976762552 0 Hitachi_HUA722010CLA330_JPW9K0N11UN3TL Feb 19 12:53:38 lillis kernel: md: import disk8: (sdf) Hitachi_HUA722010CLA330_JPW9K0N11UN3TL size: 976762552 Feb 19 12:53:38 lillis emhttp: import 30 cache device: sdd Shutdown at the command line with poweroff If it doesn't poweroff after a few minutes you will have to hold the power button. Put the flash in your PC and let it checkdisk. While it's in your PC, edit config/disk.cfg and change startArray to no. Try a different USB port on your server, preferably USB2, boot up, and see what we get.
April 19, 20179 yr Author 1 minute ago, trurl said: OK, that syslog has your drive assignments Feb 19 12:53:38 lillis emhttp: Samsung_SSD_840_PRO_Series_S1ATNEAD554329V (sdd) 250059064 Feb 19 12:53:38 lillis kernel: mdcmd (1): import 0 sdk 2930266532 0 ST33000650SS_Z290WQTB00009143U6HG_35000c50034d2b90b Feb 19 12:53:38 lillis kernel: md: import disk0: (sdk) ST33000650SS_Z290WQTB00009143U6HG_35000c50034d2b90b size: 2930266532 Feb 19 12:53:38 lillis kernel: mdcmd (2): import 1 sda 976762552 0 WDC_WD1002FBYS-02A6B0_WD-WMATV1662378 Feb 19 12:53:38 lillis kernel: md: import disk1: (sda) WDC_WD1002FBYS-02A6B0_WD-WMATV1662378 size: 976762552 Feb 19 12:53:38 lillis kernel: mdcmd (3): import 2 sdb 976762552 0 WDC_WD1002FBYS-02A6B0_WD-WMATV1881602 Feb 19 12:53:38 lillis kernel: md: import disk2: (sdb) WDC_WD1002FBYS-02A6B0_WD-WMATV1881602 size: 976762552 Feb 19 12:53:38 lillis kernel: mdcmd (4): import 3 sdh 2930266532 0 ST33000650SS_Z290DD3B00009139NM1X_35000c5003504301b Feb 19 12:53:38 lillis kernel: md: import disk3: (sdh) ST33000650SS_Z290DD3B00009139NM1X_35000c5003504301b size: 2930266532 Feb 19 12:53:38 lillis kernel: mdcmd (5): import 4 sdi 2930266532 0 ST33000650SS_Z290AVDQ0000S110VSQ2_35000c50034fd34d3 Feb 19 12:53:38 lillis kernel: md: import disk4: (sdi) ST33000650SS_Z290AVDQ0000S110VSQ2_35000c50034fd34d3 size: 2930266532 Feb 19 12:53:38 lillis kernel: mdcmd (6): import 5 sde 976762552 0 WDC_WD1002FBYS-02A6B0_WD-WMATV1660558 Feb 19 12:53:38 lillis kernel: md: import disk5: (sde) WDC_WD1002FBYS-02A6B0_WD-WMATV1660558 size: 976762552 Feb 19 12:53:38 lillis kernel: mdcmd (7): import 6 sdj 2930266532 0 ST33000650SS_Z290WSAH00009152KX7X_35000c50034d2921f Feb 19 12:53:38 lillis kernel: md: import disk6: (sdj) ST33000650SS_Z290WSAH00009152KX7X_35000c50034d2921f size: 2930266532 Feb 19 12:53:38 lillis kernel: mdcmd (8): import 7 sdg 976762552 0 Hitachi_HUA722010CLA330_JPW9K0N11UL80L Feb 19 12:53:38 lillis kernel: md: import disk7: (sdg) Hitachi_HUA722010CLA330_JPW9K0N11UL80L size: 976762552 Feb 19 12:53:38 lillis kernel: mdcmd (9): import 8 sdf 976762552 0 Hitachi_HUA722010CLA330_JPW9K0N11UN3TL Feb 19 12:53:38 lillis kernel: md: import disk8: (sdf) Hitachi_HUA722010CLA330_JPW9K0N11UN3TL size: 976762552 Feb 19 12:53:38 lillis emhttp: import 30 cache device: sdd Shutdown at the command line with poweroff If it doesn't poweroff after a few minutes you will have to hold the power button. Put the flash in your PC and let it checkdisk. While it's in your PC, edit config/disk.cfg and change startArray to no. Try a different USB port on your server, preferably USB2, boot up, and see what we get. Thanks so much for the help, i am at work now but will try this when i get home. I will update you with the results.
April 19, 20179 yr Author Check disk found no errors and usb2 worked great. I've made a backup and have setup crashplan to backup the boot directory. Thanks again!!
April 19, 20179 yr 24 minutes ago, Timbiotic said: Check disk found no errors and usb2 worked great. I've made a backup and have setup crashplan to backup the boot directory. Thanks again!! Keep an eye on your system and post back if the problem reoccurs. I have been suspecting the issue you experienced and some others that were quite similar is that the handoff from the USB2/3 drivers used for the USB3 ports in some BIOS to the syslinux booter and through the unRAID OS boot process occasionally gets hosed-up resulting in the boot drive getting 'lost' somewhere along the way. There have not been enough cases to determine a pattern. Just enough to indicate that there is the potential for a problem in using the USB3 ports to boot from. Luckily, unRAID uses the boot drive for such a short period of time (basically at boot and shutdown) that overall performance is not affected.
April 20, 20179 yr 4 hours ago, Timbiotic said: Check disk found no errors and usb2 worked great. I've made a backup and have setup crashplan to backup the boot directory. Thanks again!! Community Applications Backup has a feature to backup the flash drive. There is one important thing you need to be aware of with flash backups. You must never restore config/super.dat from a backup that doesn't match your current disk assignments. Also, config/super.dat keeps track of whether your array was started/stopped, so if you make a backup while the array is started, then boot from that backup, unRAID will think the array wasn't stopped and will begin a correcting parity check due to unclean shutdown.
April 20, 20179 yr 8 hours ago, trurl said: There is one important thing you need to be aware of with flash backups. You must never restore config/super.dat from a backup that doesn't match your current disk assignments. Also, config/super.dat keeps track of whether your array was started/stopped, so if you make a backup while the array is started, then boot from that backup, unRAID will think the array wasn't stopped and will begin a correcting parity check due to unclean shutdown. CA Appdata Backup doesn't backup super.dat because of this (and other reasons), and instead creates a text file detailing the current drive assignments
Archived
This topic is now archived and is closed to further replies.