December 22, 20178 yr I messaged @Squid and he told me about the DVB Edition plugin so I could downgrade back to RC14. Back to 100% operation now, will upgrade again when RC18 hits.
December 22, 20178 yr I did an experiment with parity drives that resulted in parity errors due to me overlooking that parity drives are partitioned. For more info see As part of the experiment I did a parity check with "write corrections to parity" deselected. I got 80 errors ("Last check completed on Thursday, 2017-12-21, 05:08 (yesterday), finding 80 errors"), but the "Main" page still states "Parity is valid". I find this confusing as with 80 uncorrected errors parity is obviously not valid. BTW if someone from lime-technology would have time to look at my questions in the post mentioned above (I assume that at least for one of the questions only they know the answer), this would be great, but I want to make it clear that it's not about a bug and therefore I also understand if there is no time for that.
December 22, 20178 yr Author 6 minutes ago, tstor said: the "Main" page still states "Parity is valid" That simply means that a parity sync operation has been completed.
December 22, 20178 yr 4 minutes ago, limetech said: That simply means that a parity sync operation has been completed. Then it would maybe make sense to state just that, e.g. "Parity check completed" instead of "Parity is valid". What do you think?
December 22, 20178 yr Author 10 minutes ago, tstor said: Then it would maybe make sense to state just that, e.g. "Parity check completed" instead of "Parity is valid". What do you think? I think it's not worth changing.
December 22, 20178 yr I'm getting a very bizarre set of errors when I try to shut down the machine. The server is stating it is waiting for 90s to gather diagnositcs, no problem there. I come back 20 min later (I timed it), the server is still stuck on gathering diagnostics. Why is that?
December 22, 20178 yr Author 22 minutes ago, Bigdady92 said: I'm getting a very bizarre set of errors when I try to shut down the machine. The server is stating it is waiting for 90s to gather diagnositcs, no problem there. I come back 20 min later (I timed it), the server is still stuck on gathering diagnostics. Why is that? This is -rc17b?
December 22, 20178 yr Author 1 minute ago, Bigdady92 said: yes How did you reboot, via webgui, or command line, or ?
December 22, 20178 yr Just now, limetech said: How did you reboot, via webgui, or command line, or ? I told the system to reboot from the UI, then i had a monitor hooked into the system to watch it's progress as it was taking a rather long time to restart. I had to physically power the server down in order to reboot.
December 22, 20178 yr Author 1 minute ago, Bigdady92 said: I told the system to reboot from the UI, then i had a monitor hooked into the system to watch it's progress as it was taking a rather long time to restart. I had to physically power the server down in order to reboot. What was running in your server, vm's? docker containers? It prob did create diags.
December 22, 20178 yr 1 minute ago, limetech said: What was running in your server, vm's? docker containers? It prob did create diags. This system is doing one and only one thing: preclearing drives. I had all the drives finished , no jobs running, and then shutdown the server as I was getting some odd latency starting/stopping the preclear jobs.
December 22, 20178 yr Now i"m getting a mountain of these errors: ErrorWarningSystemArrayLogin Dec 22 15:44:47 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdeDec 22 15:44:47 Tower emhttpd: device /dev/sde problem getting sizeDec 22 15:44:47 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdbDec 22 15:44:47 Tower emhttpd: device /dev/sdb problem getting sizeDec 22 15:44:47 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdfDec 22 15:44:47 Tower emhttpd: device /dev/sdf problem getting sizeDec 22 15:44:47 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdcDec 22 15:44:47 Tower emhttpd: device /dev/sdc problem getting sizeDec 22 15:44:48 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sddDec 22 15:44:48 Tower emhttpd: device /dev/sdd problem getting sizeDec 22 15:44:48 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdeDec 22 15:44:48 Tower emhttpd: device /dev/sde problem getting sizeDec 22 15:44:48 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdbDec 22 15:44:48 Tower emhttpd: device /dev/sdb problem getting sizeDec 22 15:44:48 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdfDec 22 15:44:48 Tower emhttpd: device /dev/sdf problem getting sizeDec 22 15:44:48 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdcDec 22 15:44:48 Tower emhttpd: device /dev/sdc problem getting sizeDec 22 15:44:49 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sddDec 22 15:44:49 Tower emhttpd: device /dev/sdd problem getting sizeDec 22 15:44:49 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdeDec 22 15:44:49 Tower emhttpd: device /dev/sde problem getting sizeDec 22 15:44:49 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdbDec 22 15:44:49 Tower emhttpd: device /dev/sdb problem getting sizeDec 22 15:44:49 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdfDec 22 15:44:49 Tower emhttpd: device /dev/sdf problem getting sizeDec 22 15:44:49 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdcDec 22 15:44:49 Tower emhttpd: device /dev/sdc problem getting sizeDec 22 15:44:50 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sddDec 22 15:44:50 Tower emhttpd: device /dev/sdd problem getting sizeDec 22 15:44:50 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdeDec 22 15:44:50 Tower emhttpd: device /dev/sde problem getting sizeDec 22 15:44:50 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdbDec 22 15:44:50 Tower emhttpd: device /dev/sdb problem getting sizeDec 22 15:44:50 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdfDec 22 15:44:50 Tower emhttpd: device /dev/sdf problem getting sizeDec 22 15:44:50 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdcDec 22 15:44:50 Tower emhttpd: device /dev/sdc problem getting sizeDec 22 15:44:51 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sddDec 22 15:44:51 Tower emhttpd: device /dev/sdd problem getting sizeDec 22 15:44:51 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdeDec 22 15:44:51 Tower emhttpd: device /dev/sde problem getting sizeDec 22 15:44:51 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdbDec 22 15:44:51 Tower emhttpd: device /dev/sdb problem getting sizeDec 22 15:44:51 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdfDec 22 15:44:51 Tower emhttpd: device /dev/sdf problem getting sizeDec 22 15:44:51 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdcDec 22 15:44:51 Tower emhttpd: device /dev/sdc problem getting sizeDec 22 15:44:52 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sddDec 22 15:44:52 Tower emhttpd: device /dev/sdd problem getting sizeDec 22 15:44:52 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdeDec 22 15:44:52 Tower emhttpd: device /dev/sde problem getting sizeDec 22 15:44:52 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdbDec 22 15:44:52 Tower emhttpd: device /dev/sdb problem getting sizeDec 22 15:44:52 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdfDec 22 15:44:52 Tower emhttpd: device /dev/sdf problem getting sizeDec 22 15:44:52 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdcDec 22 15:44:52 Tower emhttpd: device /dev/sdc problem getting sizeDec 22 15:44:53 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sddDec 22 15:44:53 Tower emhttpd: device /dev/sdd problem getting size
December 22, 20178 yr 57 minutes ago, Bigdady92 said: Now i"m getting a mountain of these errors: ErrorWarningSystemArrayLogin Dec 22 15:44:47 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdeDec 22 15:44:47 Tower emhttpd: device /dev/sde problem getting sizeDec 22 15:44:47 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdbDec 22 15:44:47 Tower emhttpd: device /dev/sdb problem getting sizeDec 22 15:44:47 Tower emhttpd: error: get_device_size, 1421: No medium found (123): open: /dev/sdfDec 22 15:44:47 Tower emhttpd: device /dev/sdf problem getting size Sounds like the same issue I'm having, maybe add your details here too?
December 22, 20178 yr I posted there as well as attached my system logs tower-diagnostics-20171222-1646.zip
December 22, 20178 yr Before I downgraded back to RC14 when I reboot the system it would hold on 'killing docker" but never reboot and had to cold boot the server to get it to boot back up, since downgrading it reboots normally too.
December 23, 20178 yr the 6.4 is not working for me. (10b, 16b,17b) have system call. I am worried the final release will have the same issue. whats the problem? anyone can help? diagnostic for 6.3.5 syslog after tower-diagnostics-20171208-0809.zip syslog
December 23, 20178 yr Nothing major, but individual CPU activity not displaying in Chrome. No errors in the console...
December 23, 20178 yr 54 minutes ago, Cessquill said: but individual CPU activity not displaying in Chrome Click on "Per CPU load" to toggle between full and summary view.
December 23, 20178 yr 2 minutes ago, bonienl said: Click on "Per CPU load" to toggle between full and summary view. D'OH! Thanks
December 24, 20178 yr was watching a movie on plex and it just stopped. web gui dashboard showed this: Apps Warning: exec(): Unable to fork [pgrep 'dockerd'] in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 190 Warning: exec(): Unable to fork [pgrep 'libvirtd'] in /usr/local/emhttp/plugins/dynamix/include/Helpers.php on line 190 No apps available to show Statistics Warning: exec(): Unable to fork [cat /sys/devices/system/cpu/*/topology/thread_siblings_list|sort -nu] in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(380) : eval()'d code on line 14 Warning: exec(): Unable to fork [sensors -uA 2>/dev/null|grep -c 'fan[0-9]_input'] in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(380) : eval()'d code on line 15 Warning: exec(): Unable to fork [awk '/^MemTotal/{print $2*1024/1.048576}' /proc/meminfo] in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(380) : eval()'d code on line 25 Warning: exec(): Unable to fork [ls /sys/class/net|grep -Po '^(lo|(bond|eth)\d+)$'] in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(380) : eval()'d code on line 26 Warning: exec(): Unable to fork [dmidecode -t 17 | awk -F: '/^ Size: [0-9]+ MB$/{t+=$2} /^ Size: [0-9]+ GB$/{t+=$2*1024} END{print t}'] in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(380) : eval()'d code on line 28 Warning: exec(): Unable to fork [dmidecode -t 16 | awk -F: '/^ Maximum Capacity: [0-9]+ GB$/{t+=$2} END{print t}'] in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(380) : eval()'d code on line 29 and the logs at that time show this: Dec 23 21:00:02 Brahms1 root: /etc/libvirt: 923.6 MiB (968404992 bytes) trimmed Dec 23 21:00:02 Brahms1 root: /var/lib/docker: 16.7 GiB (17870413824 bytes) trimmed Dec 23 21:00:02 Brahms1 root: /mnt/disks/Sam120Pro: 49.2 GiB (52810985472 bytes) trimmed Dec 23 21:00:02 Brahms1 root: /mnt/disks/King120: 103.5 GiB (111080337408 bytes) trimmed Dec 23 21:00:02 Brahms1 root: /mnt/cache: 337.7 GiB (362610475008 bytes) trimmed Dec 23 21:19:34 Brahms1 kernel: php[32481]: segfault at 0 ip 0000000000603e0d sp 00007ffc7fbd9750 error 4 in php[400000+74a000] Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdb 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdc 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdd 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sde 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdf 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdg 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdh 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdi 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdj 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdk 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdl 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdm 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdn 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'timeout -s 9 60 udevadm info --query=property --name /dev/sdo 2>/dev/null' in /etc/rc.d/rc.diskinfo on line 369 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'df --exclude-type=devtmpfs --block-size=1 --output=used,source /dev/sdc1 2>/dev/null|tail -n +2|awk '{print $1}'' in /etc/rc.d/rc.diskinfo on line 621 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'lsof +L -Fk '/mnt/disks/Sam120Pro' 2>/dev/null | wc -l' in /etc/rc.d/rc.diskinfo on line 621 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'df --exclude-type=devtmpfs --block-size=1 --output=used,source /dev/sdf1 2>/dev/null|tail -n +2|awk '{print $1}'' in /etc/rc.d/rc.diskinfo on line 621 Dec 23 21:20:03 Brahms1 rc.diskinfo[8832]: PHP Warning: shell_exec(): Unable to execute 'lsof +L -Fk '/mnt/disks/King120' 2>/dev/null | wc -l' in /etc/rc.d/rc.diskinfo on line 621 Dec 23 21:20:18 Brahms1 avahi-daemon[8793]: Interface vnet1.IPv6 no longer relevant for mDNS. Dec 23 21:20:18 Brahms1 avahi-daemon[8793]: Leaving mDNS multicast group on interface vnet1.IPv6 with address fe80::fc54:ff:feee:342e. Dec 23 21:20:18 Brahms1 kernel: br0: port 2(vnet1) entered disabled state Dec 23 21:20:18 Brahms1 kernel: device vnet1 left promiscuous mode Dec 23 21:20:18 Brahms1 kernel: br0: port 2(vnet1) entered disabled state After closing the browser tab and reopening a few times, it seemed to fix itself, and I could restart watching the movie. I pulled full diagnostics at the time too. let me know if they are needed. ---edit the disks referenced, sdc and sdf , are mounted via unassigned devices. sdc was running a vm, which looks to have crashed either causing it, or crashed because of whatever happened. usb_desc_get_descriptor: 1 unknown type 33 (len 10) 2017-12-24 02:20:18.287+0000: shutting down, reason=crashed Edited December 24, 20178 yr by 1812
December 24, 20178 yr 3 hours ago, bonienl said: Looks like related to the preclear plugin. Can you uninstall and retry? Uninstall and then reinstall?
December 24, 20178 yr 1 hour ago, 1812 said: Uninstall and then reinstall? Uninstall and check if the problem disappeared. My suspicion it conflicts somehow with udev.
December 24, 20178 yr I was having trouble with the latest RC17b so I decided to reinstall a fresh copy on the same usb and reformat the cache drive (appdata and system) yet I'm still having some same issue. under tools the log works perfectly but the log tab isnt working correctly as it takes forever to load. I'm not sure if others have the same problem EDIT: after timing it, it takes exactly 60 seconds to load. Edited December 24, 20178 yr by PSYCHOPATHiO
Archived
This topic is now archived and is closed to further replies.