December 24, 20178 yr Whats the issue? where to dig? diagnostic before syslog after syslog tower-diagnostics-20171208-0809.zip
December 24, 20178 yr Diagnostics don't include the call trace, and while the separate syslog does, it implies that the reason for the trace is something related to the hard drive's file system, which may appear if you run a new set of diagnostics.
December 24, 20178 yr Author while I am with the new version and after the call trace, I have tried to run the diagnostic, but it was stuck, saying "downloading" without any result. is there another way to run it? in terminal maybe?
December 24, 20178 yr 34 minutes ago, dadarara said: in terminal maybe? diagnostics It may take a while, but it will ultimately succeed
December 24, 20178 yr Author switched off the docker and the virtual manager installed the new version run the diagnostics in terminal was waiting for more than two hours to finish. and it is still going .... also the Array is STARTING...... I found the diagnostic zip file under the boot/log/ not really sure if this is it. the time stamp is more or less correct. there are many errors in the libvirt.txt error log. its looking for VM files that are no longer exist actually. some errors I dont know what to do about like: qemuStorageLimitsRefresh:11550 : cannot stat file '/mnt/disks/WDC_WD20NPVT_00Z2TT0_WD_WXA1E42PMZ58/Yoli-Win10/vdisk1.img': Bad file descriptor syslog.zip tower-diagnostics-20171224-2118.zip Edited December 25, 20178 yr by dadarara
December 29, 20178 yr Author any help is appreciated please look in to the logs. Happy and successful new year everyone !!
January 2, 20188 yr The diagnostics you posted on 24th December are for version 6.3.5 of unRAID and contain no call traces. Which version do you think you are running?
January 2, 20188 yr Author John, I am trying to install the 6.4 with the errors above. and reverting to the 6.3.5 after failure. I have posted the 6.3.5 diagnostic from 08/12 as requested just to see the pre upgrade status. this file from 24th is the diagnostics file I found after running diagnostics in terminal (under 15b i think) I am not sure if this is a good file as the command never finished with a result. so it might be that the system does not execute the diagnostics at all. if I can manually copy files , please tell me which ones
January 3, 20188 yr Regarding the diagnostics dated 24th December, it definitely came from version 6.3.5, not a 6.4rc - the contents confirm that as a fact. I don't see any major issues in the syslog but there is information missing - the SMART reports, for example. In your position, here's what I'd do. First, I'd make sure my server was running well with version 6.3.5 - so, assuming you're currently running 6.3.5, reboot then start the array and whatever applications you normally use and then grab diagnostics and post them here. Once you and anyone who helps here is happy with that version, turn off auto-starting Dockers and VMs then upgrade to 6.4 and just start the array - don't try to use Dockers or virtualisation - and grab diagnostics. If that shows a problem you can work on fixing it, otherwise you can start your Dockers and grab diagnostics again. If all is good you can start up your VMs. That way the problem is broken down into more manageable pieces. When I'm troubleshooting I make copious notes on a pad of old fashioned paper and grab diagnostics often. Good luck.
January 3, 20188 yr Author John thanks. unfortunately, after the upgrade the diagnostics does not work, pls read bellow.. please advice, what can I copy/attached other than the full diagnostics ? attached is the diagnostics file for 6.3.5 that runs ok. the only issue I have is that probably the Network UPS Tools (NUT) is causing a periodic reset of the USB controller. The only consequence as far as I see is the disconnection of the Bluetooth dongle I have attached. I dont see this affecting the USB Flash drive. I would love to hear if there are any other issues in the system. meanwhile I have done the upgrade, while having the virtual manager and the docker switched off. immediately after reboot, I get the system call. the array shows in the WEBGUI as "starting..." in the tools/diagnostics manu, it is stuck on "downloading" after trying to execute it in the terminal as well: root@Tower:/boot# diagnostics Starting diagnostics collection... attached is the syslog. also bellow are the last entries of syslog after about 7hours. took a capture of HTOP output Jan 3 23:59:05 Tower afpd[32218]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:06 Tower afpd[32244]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:07 Tower afpd[32270]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:07 Tower afpd[32272]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:08 Tower afpd[32308]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:08 Tower afpd[32310]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:09 Tower afpd[32321]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:09 Tower afpd[32347]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:10 Tower afpd[32350]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:10 Tower afpd[32376]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:11 Tower afpd[32378]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:11 Tower afpd[32404]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:12 Tower afpd[32406]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:12 Tower afpd[32432]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:13 Tower afpd[32454]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:13 Tower afpd[32480]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:13 Tower afpd[32502]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:14 Tower afpd[32504]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:14 Tower afpd[32530]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:14 Tower afpd[32541]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:27 Tower afpd[394]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:27 Tower afpd[396]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:28 Tower afpd[398]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:28 Tower afpd[424]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:29 Tower afpd[426]: dsi_stream_read: len:0, unexpected EOF Jan 3 23:59:29 Tower afpd[452]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:00 Tower afpd[1309]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:01 Tower speedtest: Internet bandwidth test started Jan 4 00:00:01 Tower Plugin Auto Update: Checking for available plugin updates Jan 4 00:00:01 Tower root: Executing /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 60 Jan 4 00:00:01 Tower root: CA Turbo Mode Schedule Starting. Killing Automatic Mode Jan 4 00:00:01 Tower kernel: mdcmd (40): set md_write_method 0 Jan 4 00:00:01 Tower kernel: Jan 4 00:00:01 Tower afpd[1311]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:02 Tower afpd[1377]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:02 Tower afpd[1380]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:03 Tower afpd[1430]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:03 Tower afpd[1432]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:04 Tower afpd[1461]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:04 Tower afpd[1463]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:05 Tower afpd[1491]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:06 Tower afpd[1496]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:12 Tower afpd[1721]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:13 Tower afpd[1725]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:13 Tower afpd[1755]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:14 Tower afpd[1767]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:14 Tower afpd[1800]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:15 Tower afpd[1815]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:15 Tower afpd[1844]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:16 Tower afpd[1846]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:16 Tower afpd[1872]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:17 Tower afpd[1879]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:00:33 Tower Plugin Auto Update: Community Applications Plugin Auto Update finished Jan 4 00:00:35 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Jan 4 00:00:35 Tower speedtest: Ping (Lowest): 195.709 ms | Download (Max): 98.92 Mbit/s | Upload (Max): 1.84 Mbit/s Jan 4 00:00:35 Tower speedtest: Internet bandwidth test completed Jan 4 00:01:12 Tower afpd[3559]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:01:13 Tower afpd[3585]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:01:13 Tower afpd[3611]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:01:14 Tower afpd[3613]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:01:14 Tower afpd[3639]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:01:15 Tower afpd[3650]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:01:15 Tower afpd[3676]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:01:16 Tower afpd[3678]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:01:16 Tower afpd[3680]: dsi_stream_read: len:0, unexpected EOF Jan 4 00:01:16 Tower afpd[3706]: dsi_stream_read: len:0, unexpected EOF Jan 4 01:00:01 Tower root: Restarting CA Auto Turbo Mode Jan 4 01:00:01 Tower speedtest: Internet bandwidth test started Jan 4 01:00:01 Tower root: Executing /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 60 Jan 4 01:00:01 Tower root: CA Turbo Mode Schedule Starting. Killing Automatic Mode Jan 4 01:00:01 Tower kernel: mdcmd (41): set md_write_method 1 Jan 4 01:00:01 Tower kernel: Jan 4 01:00:01 Tower kernel: mdcmd (42): set md_write_method 0 Jan 4 01:00:01 Tower kernel: Jan 4 01:00:02 Tower root: /mnt/cache: 241.7 GiB (259555053568 bytes) trimmed Jan 4 01:00:34 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Jan 4 01:00:34 Tower speedtest: Ping (Lowest): 125.517 ms | Download (Max): 97.61 Mbit/s | Upload (Max): 1.70 Mbit/s Jan 4 01:00:34 Tower speedtest: Internet bandwidth test completed Jan 4 02:00:01 Tower root: Restarting CA Auto Turbo Mode Jan 4 02:00:01 Tower speedtest: Internet bandwidth test started Jan 4 02:00:01 Tower root: Executing /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 60 Jan 4 02:00:01 Tower root: CA Turbo Mode Schedule Starting. Killing Automatic Mode Jan 4 02:00:01 Tower kernel: mdcmd (43): set md_write_method 1 Jan 4 02:00:01 Tower kernel: Jan 4 02:00:01 Tower kernel: mdcmd (44): set md_write_method 0 Jan 4 02:00:01 Tower kernel: Jan 4 02:00:34 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Jan 4 02:00:34 Tower speedtest: Ping (Lowest): 138.638 ms | Download (Max): 99.09 Mbit/s | Upload (Max): 1.76 Mbit/s Jan 4 02:00:34 Tower speedtest: Internet bandwidth test completed Jan 4 03:00:01 Tower root: Restarting CA Auto Turbo Mode Jan 4 03:00:01 Tower speedtest: Internet bandwidth test started Jan 4 03:00:01 Tower root: Executing /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 60 Jan 4 03:00:01 Tower root: CA Turbo Mode Schedule Starting. Killing Automatic Mode Jan 4 03:00:01 Tower kernel: mdcmd (45): set md_write_method 0 Jan 4 03:00:01 Tower kernel: Jan 4 03:00:26 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Jan 4 03:00:26 Tower speedtest: Ping (Lowest): 191.781 ms | Download (Max): 99.12 Mbit/s | Upload (Max): 1.86 Mbit/s Jan 4 03:00:26 Tower speedtest: Internet bandwidth test completed Jan 4 03:02:28 Tower kernel: usb 2-1.2: USB disconnect, device number 12 Jan 4 03:02:29 Tower kernel: usb 2-1.2: new low-speed USB device number 13 using ehci-pci Jan 4 03:02:29 Tower kernel: hid-generic 0003:0665:5161.0008: hiddev96,hidraw0: USB HID v1.00 Device [INNO TECH USB to Serial] on usb-0000:00:1d.0-1.2/input0 Jan 4 04:00:01 Tower root: Restarting CA Auto Turbo Mode Jan 4 04:00:01 Tower speedtest: Internet bandwidth test started Jan 4 04:00:01 Tower root: Executing /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 60 Jan 4 04:00:01 Tower root: CA Turbo Mode Schedule Starting. Killing Automatic Mode Jan 4 04:00:01 Tower kernel: mdcmd (46): set md_write_method 0 Jan 4 04:00:01 Tower kernel: Jan 4 04:00:35 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Jan 4 04:00:35 Tower speedtest: Ping (Lowest): 162.597 ms | Download (Max): 98.81 Mbit/s | Upload (Max): 1.76 Mbit/s Jan 4 04:00:35 Tower speedtest: Internet bandwidth test completed Jan 4 05:00:01 Tower speedtest: Internet bandwidth test started Jan 4 05:00:01 Tower root: Restarting CA Auto Turbo Mode Jan 4 05:00:01 Tower kernel: mdcmd (47): set md_write_method 1 Jan 4 05:00:01 Tower kernel: Jan 4 05:00:25 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Jan 4 05:00:25 Tower speedtest: Ping (Lowest): 184.882 ms | Download (Max): 99.48 Mbit/s | Upload (Max): 2.07 Mbit/s Jan 4 05:00:25 Tower speedtest: Internet bandwidth test completed Jan 4 05:01:01 Tower root: Executing /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 60 Jan 4 05:01:01 Tower root: CA Turbo Mode Schedule Starting. Killing Automatic Mode Jan 4 05:01:01 Tower kernel: mdcmd (48): set md_write_method 0 Jan 4 05:01:01 Tower kernel: Jan 4 06:00:01 Tower speedtest: Internet bandwidth test started Jan 4 06:00:37 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Jan 4 06:00:37 Tower speedtest: Ping (Lowest): 150.875 ms | Download (Max): 98.74 Mbit/s | Upload (Max): 1.66 Mbit/s Jan 4 06:00:37 Tower speedtest: Internet bandwidth test completed Jan 4 06:01:01 Tower root: Restarting CA Auto Turbo Mode Jan 4 06:01:01 Tower kernel: mdcmd (49): set md_write_method 1 Jan 4 06:01:01 Tower kernel: Jan 4 06:02:01 Tower root: Executing /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 60 Jan 4 06:02:01 Tower root: CA Turbo Mode Schedule Starting. Killing Automatic Mode Jan 4 06:02:01 Tower kernel: mdcmd (50): set md_write_method 0 Jan 4 06:02:01 Tower kernel: Jan 4 07:00:01 Tower speedtest: Internet bandwidth test started Jan 4 07:00:35 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Jan 4 07:00:35 Tower speedtest: Ping (Lowest): 185.647 ms | Download (Max): 51.66 Mbit/s | Upload (Max): 1.76 Mbit/s Jan 4 07:00:35 Tower speedtest: Internet bandwidth test completed Jan 4 07:02:01 Tower root: Restarting CA Auto Turbo Mode Jan 4 07:02:01 Tower kernel: mdcmd (51): set md_write_method 1 Jan 4 07:02:01 Tower kernel: Jan 4 07:03:01 Tower root: Executing /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 60 Jan 4 07:03:01 Tower root: CA Turbo Mode Schedule Starting. Killing Automatic Mode Jan 4 07:03:01 Tower kernel: mdcmd (52): set md_write_method 0 Jan 4 07:03:01 Tower kernel: Jan 4 08:00:01 Tower speedtest: Internet bandwidth test started Jan 4 08:00:25 Tower speedtest: Host: Triple C (Petah Tikva) [22.27 km] Jan 4 08:00:25 Tower speedtest: Ping (Lowest): 192.118 ms | Download (Max): 98.58 Mbit/s | Upload (Max): 2.10 Mbit/s Jan 4 08:00:25 Tower speedtest: Internet bandwidth test completed Jan 4 08:03:01 Tower root: Restarting CA Auto Turbo Mode Jan 4 08:03:01 Tower kernel: mdcmd (53): set md_write_method 1 Jan 4 08:03:01 Tower kernel: Jan 4 08:04:01 Tower root: Executing /usr/local/emhttp/plugins/ca.turbo/scripts/turboSchedule.php disable 60 Jan 4 08:04:01 Tower root: CA Turbo Mode Schedule Starting. Killing Automatic Mode Jan 4 08:04:01 Tower kernel: mdcmd (54): set md_write_method 0 Jan 4 08:04:01 Tower kernel: tower-diagnostics-20180103-2305.zip syslog.txt Edited January 4, 20188 yr by dadarara
January 4, 20188 yr Author this weekend I will try to install from scratch. in any case, can the "call trace " information point to the "culprit" ?
January 6, 20188 yr Author installed 6.4-19b scratch install with one disk in an array. without any of the old data/dockers/VMs/plugins/etc. it worked without errors. Its hard to imagine how to move all the VMs and Dockers to a new install. disaster. Edited January 6, 20188 yr by dadarara
Archived
This topic is now archived and is closed to further replies.