blender50
Members
-
Joined
-
Last visited
-
Plugin persistence is a problem for me. I'm on the latest UNRAID release 7.3.1 and the plugin disappears on reboot. I go into 'previously installed' in the app store and reinstall it without issue, and the settings I made previously are picked up.
-
I just installed the update to the plugin and this line (see yellow arrow) caught my eye. It seems to be indicating that the instalation cannot proceed but immediately below that the message indicates a successful install. What gives? Is this just an error reporting bug?
-
I am not looking to 'auto-remove' the images, I was hoping that there would be something I could do so that when the stack is taken down the images would be 'saved' just like a normal docker image from the app store is. That is, when you stop an app store docker app typically the image is saved someplace and no orphan is displayed, and when the docker is brought back online (started) it utilizes the same img as it did previously. Is there not something in the compose file I could add the would 'save' the img like that?
-
Every time I 'Compose Down' a stack the images show up in the Docker tab as 'Orphaned images' I'm new to the compose plugin, but am wondering is there something I can do so that this doesn't happen? I'm not looking to remove them, just to not have UNRAID display them in this way.
-
This should go with our saying, but if export/backup is included, please be sure to include import/restore. The backup restoration script from @petchav works great but not without the occasional hiccup.
-
I'm getting this in my Calibre log, repeating every 6-7 seconds. I'm on the latest version as well... sed: couldn't flush stdout: Invalid argument Is there anything I can do to track this down and eliminate it?
-
Ok, since the diags were of no use I decided to rerun the upgrade. I access my server using wireguard, and was troubled with some crappy performance, I remembered that I had 'File Activity' logging enabled and disabled it. The GUI is now way snappier. Next I reran the update and waited.... It took 30 min for the array to come back up, but at least it's up. If the 30 min seems unusual, I am adding diags..... blender-diagnostics-20240907-1635_6.12.13.zip
-
I edited my original post adding diagnostics I just saved.
-
The title says it all, I updated and the array got stuck 'mounting disks'. I disabled my scheduled user scripts based on another post but to no avail. Since then I've downgraded and tried a second time, still no joy. Now I'm back to .11 and am wondering if others have had the same experience. Basically I am looking for some things I can try to smooth things out... I forgot to collect diagnostics when I was trying to boot .13. If nobody has any ideas for me to try to I will rerun the update and grab them. blender-diagnostics-20240906-0951_6.12.11.zip
-
I took the above script as a starting point, added a few things that made its use more useful to me. Disclaimer: I'm no BASH god, and I'm sure it can be improved upon, but for me it does the trick. There are some use remarks in the comments at the top of the script. #!/bin/bash # It takes a number of seconds as an argument. That controls how often the script updates. # # To run the script save it to /tmp and set it to execute (chmod +x scriptname) # then do # "/tmp/syncscript xx" where xx is the refresh time in seconds (without the quotes ;-) # # You can leave this script running while pausing and resuming the parity check from the GUI Main page without issue. :-) # # To stop the script Press [CTRL+C] # # This script will display like this: # # RUNNING # Press [CTRL+C] to stop. # Array Status: STARTED # Parity Check: Running # Speed: 119.9 MB/sec # Progress: 1 GB of 12000 GB # # (0.0%) # Completing in: 27h 48m # On approximately: Sat Sep 16 18:38:31 PDT 2023 # Total Errors: 0 # Refreshing in 0 # # PAUSED # Press [CTRL+C] to stop. # Array Status: STARTED # Parity Check: Paused # Speed: 0 MB/sec # Progress: 13 GB of 0 GB # # (0%) # Completing in: N/A # On approximately: N/A # Total Errors: 0 # Refreshing in 9 # # STOPPED # Press [CTRL+C] to stop. # Array Status: STARTED # Parity Check: Not Running # Speed: 0 MB/sec # Progress: 0 GB of 0 GB # # (0%) # Completing in: N/A # On approximately: N/A # Total Errors: 0 # Refreshing in 6 # Check to see the argument is provided. Otherwise exit with helpful message. if [ -z "$1" ] then echo " To run this script please supply a refresh time in x seconds, like: # /tmp/syncstatus x" exit 0 fi # Define Colored text for use in countdown RED='\033[0;31m' NC='\033[0m' # No Color # Main loop of script while true do # Set refresh to the arguments value plus 1 (necessary for the countdown) refresh=$(($1+1)) # clear the screen and display the script at the top of the window (one row down for readability) tput clear tput cup 1 0 # grab various datapoints from the output of mdcmd status command status=$(mdcmd status | sed -n 's/mdState=//p' ) size=$(mdcmd status | sed -n 's/mdResync=//p' ) pos=$(mdcmd status | sed -n 's/mdResyncPos=//p' ) dt=$(mdcmd status | sed -n 's/mdResyncDt=//p' ) db=$(mdcmd status | sed -n 's/mdResyncDb=//p' ) # calculating sizes and data processed gbsize=$(awk "BEGIN{printf \"%.0f\", $size * 1024 / 1000^3}" ) gbpos=$(awk "BEGIN{printf \"%.0f\", $pos * 1024 / 1000^3}" ) # error checking for stopped, paused, ... if [ $size == 0 ] then progress="0" else progress=$(awk "BEGIN{printf \"%.1f\", ($pos / $size) * 100}" ) fi # checking for 0 speed. Indicating stopped or paused if [ $dt == 0 ] then speed="0" else speed=$(awk "BEGIN{printf \"%.1f\", ($db / $dt) * 1024 / 1000^2}" ) fi # if there is a speed value greater than 0, then the check is running and we report the amount of time left if [ $speed == 0 ] then finish="N/A" else # since it is running we can calculate and display the projected end date finish=$(awk "BEGIN{ m=(($dt*(($size-$pos)/($db/100+1)))/100)/60 print int(m/60) \"h \" int(m%60) \"m\" }") fi # check to see if Parity check is paused, stopped or running if [[ $gbpos -gt "0" ]] && [[ $gbsize == 0 ]] then parityCheck="Paused" elif [ $size == 0 ] then parityCheck="Not Running" else parityCheck="Running" fi # Begin outputting info echo "Press [CTRL+C] to stop." echo "Array Status: $status" echo "Parity Check: $parityCheck" echo "Speed: $speed MB/sec" echo "Progress: $gbpos GB of $gbsize GB" # round progress to nearest whole number for progress bar display progressRounded=$(printf %.0f $progress) # calc progress bar and display %age completed for i in $(eval echo "{0..$progressRounded}") do echo -n "#" done echo " (${progress}%)" echo "Completing in: $finish" # account for stopped or paused processs if [[ $parityCheck="Running" ]] then # calc end date # Extract hours and minutes hours=$(echo "$finish" | awk '{print $1}' | sed 's/h//') minutes=$(echo "$finish" | awk '{print $2}' | sed 's/m//') # Convert to seconds if [[ -n "$hours" ]] && [[ -n "$minutes" ]] then seconds_left=$((hours*3600 + minutes*60)) endDate=$(date -d "now + $seconds_left seconds") else endDate="N/A" fi echo "On approximately: $endDate" fi # Parse all mdcmd status data and summing all rdevNumErrors values input_string=$(mdcmd status) # Use grep to filter lines starting with rdevNumErrors rdev_errors=$(echo "$input_string" | grep -Eo 'rdevNumErrors\.[0-9]+=[0-9]+' | awk -F= '{sum+=$2} END{print sum}') # Print the total value echo "Total Errors: $rdev_errors" # Countdown display count displays in red from 5 to 0 before refresh while [ $refresh -gt 0 ] do refresh=$((refresh-1)) if [ $refresh -le 5 ] then printf " Refreshing in ${RED}$refresh${NC} " printf "\r" sleep 1 else printf " Refreshing in $refresh " printf "\r" sleep 1 fi done # end of countdown while done # end of 'whole script' while I hope others find it useful.
-
This problem is causing parity checks which are taking a bunch of time and are returning all ok. So at lease that's some good news. I'm attaching diagnostics and here is the last piece of the syslog I collected prior to the crash... (I'm using a raspberry Pi as a syslog server) It looks like everything goes pear shaped at Mar 31 14:00:06 Any help is much appreciated. My feeling is that this is RC4 related, since RC3 didn't pose any issues for me..... Cheers Steve From the raspiPi.... Last login: Wed Mar 30 11:45:31 2022 from 23.120.16.38 blender@raspberrypi3:~ $ sudo tail -f /var/log/syslog-unraid.log Mar 31 12:16:40 blender kernel: Code: 89 e7 e8 65 43 01 00 48 8d 54 1d ff 31 c9 48 89 ee 4c 89 ef e8 e2 00 01 00 4d 63 e6 5b 4c 89 e0 5d 41 5c 41 5d 41 5e 41 5f c3 <f0> 48 0f b3 3e c3 48 8b 07 48 8b 88 f0 01 00 00 81 b9 04 0d 00 00 Mar 31 12:16:40 blender kernel: RSP: 0018:ffffc9000b6f7ba0 EFLAGS: 00010246 Mar 31 12:16:40 blender kernel: RAX: ffff888153b2dbc8 RBX: ffff8898aa491c08 RCX: 00000000801c000d Mar 31 12:16:40 blender kernel: RDX: 00000000801c000e RSI: 0000000000000068 RDI: 0000000000000000 Mar 31 12:16:40 blender kernel: RBP: ffff8898aa491df8 R08: ffff8881a0ba4bd0 R09: 00000000801c000d Mar 31 12:16:40 blender kernel: R10: ffff8881a0ba4bd0 R11: ffff8881a0ba4bd0 R12: ffff888107926800 Mar 31 12:16:40 blender kernel: R13: ffff8898aa491c00 R14: ffff889371944000 R15: 0000000000000000 Mar 31 12:16:40 blender kernel: FS: 000014803d2b5700(0000) GS:ffff88903fcc0000(0000) knlGS:0000000000000000 Mar 31 12:16:40 blender kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 31 12:16:40 blender kernel: CR2: 0000000000000068 CR3: 00000011d89f8006 CR4: 00000000000626e0 Mar 31 12:22:15 blender emhttpd: spinning down /dev/sdd Mar 31 12:22:15 blender emhttpd: spinning down /dev/sde Mar 31 12:22:15 blender emhttpd: spinning down /dev/sdc Mar 31 12:22:15 blender emhttpd: spinning down /dev/sdn Mar 31 12:22:15 blender emhttpd: spinning down /dev/sdo Mar 31 12:22:15 blender emhttpd: spinning down /dev/sdl Mar 31 12:22:15 blender SAS Assist v0.86: Spinning down device /dev/sdo Mar 31 12:22:15 blender SAS Assist v0.86: Spinning down device /dev/sdn Mar 31 12:22:45 blender emhttpd: spinning down /dev/sdj Mar 31 12:22:45 blender emhttpd: spinning down /dev/sdk Mar 31 12:22:45 blender emhttpd: spinning down /dev/sdp Mar 31 12:22:45 blender SAS Assist v0.86: Spinning down device /dev/sdk Mar 31 12:22:45 blender SAS Assist v0.86: Spinning down device /dev/sdj Mar 31 12:22:45 blender SAS Assist v0.86: Spinning down device /dev/sdp Mar 31 12:25:02 blender kernel: mdcmd (45): set md_write_method 0 Mar 31 12:25:02 blender kernel: Mar 31 12:48:20 blender emhttpd: read SMART /dev/sdj Mar 31 12:48:20 blender emhttpd: read SMART /dev/sdn Mar 31 13:11:54 blender kernel: mdcmd (46): set md_num_stripes 1280 Mar 31 13:11:54 blender kernel: mdcmd (47): set md_queue_limit 80 Mar 31 13:11:54 blender kernel: mdcmd (48): set md_sync_limit 5 Mar 31 13:11:54 blender kernel: mdcmd (49): set md_write_method Mar 31 13:33:20 blender emhttpd: cmd: /usr/local/emhttp/plugins/DevPack/scripts/devmanager --download Mar 31 13:33:20 blender devpack: Processing Packages... Mar 31 13:33:20 blender devpack: Installing autoconf-2.69 package... Mar 31 13:33:21 blender devpack: Installing automake-1.16.1 package... Mar 31 13:33:22 blender devpack: Installing binutils-2.31.1 package... Mar 31 13:33:23 blender devpack: Installing flex-2.6.4 package... Mar 31 13:33:24 blender devpack: Installing gc-8.0.4 package... Mar 31 13:33:24 blender devpack: Installing gcc-9.2.0 package... Mar 31 13:33:29 blender devpack: Installing gcc-gplus-9.2.0 package... Mar 31 13:33:31 blender devpack: Installing glibc-2.30 package... Mar 31 13:33:31 blender devpack: Installing guile-2.2.3 package... Mar 31 13:33:33 blender devpack: Installing kernel-headers-4.14.37 package... Mar 31 13:33:34 blender devpack: Installing libmpc-1.1.0 package... Mar 31 13:33:34 blender devpack: Installing m4-1.4.18 package... Mar 31 13:33:34 blender devpack: Installing make-4.2.1 package... Mar 31 13:33:35 blender devpack: Cleaning up packages... Mar 31 13:33:35 blender devpack: All packages processed... Mar 31 14:00:06 blender kernel: BUG: kernel NULL pointer dereference, address: 0000000000000009 Mar 31 14:00:06 blender kernel: #PF: supervisor write access in kernel mode Mar 31 14:00:06 blender kernel: #PF: error_code(0x0002) - not-present page Mar 31 14:00:06 blender kernel: PGD 800000126e9ae067 P4D 800000126e9ae067 PUD 126e9af067 PMD 0 Mar 31 14:00:06 blender kernel: Oops: 0002 [#2] SMP PTI Mar 31 14:00:06 blender kernel: CPU: 14 PID: 4719 Comm: docker-proxy Tainted: G D W 5.15.30-Unraid #1 Mar 31 14:00:06 blender kernel: Hardware name: Supermicro X9DRD-7LN4F(-JBOD)/X9DRD-EF/X9DRD-7LN4F, BIOS 3.3 08/23/2018 Mar 31 14:00:06 blender kernel: RIP: 0010:nf_nat_setup_info+0x70e/0x773 [nf_nat] Mar 31 14:00:06 blender kernel: Code: 8b 05 f7 64 00 00 48 8d 8b 98 00 00 00 4a 8d 14 e0 48 8b 02 48 89 93 a0 00 00 00 48 89 83 98 00 00 00 48 85 c0 48 89 0a 74 04 <48> 89 48 08 4c 89 ef e8 19 a5 6c e1 eb 19 41 83 fc 01 48 8b 83 80 Mar 31 14:00:06 blender kernel: RSP: 0018:ffffc900093779f0 EFLAGS: 00010202 Mar 31 14:00:06 blender kernel: RAX: 0000000000000001 RBX: ffff88839be5b340 RCX: ffff88839be5b3d8 Mar 31 14:00:06 blender kernel: RDX: ffff888153b2dbc8 RSI: bd2a841968799d0f RDI: ffffffffa0110404 Mar 31 14:00:06 blender kernel: RBP: ffffc90009377ac0 R08: ba7b8b957b421b02 R09: 6d816606d4b994be Mar 31 14:00:06 blender kernel: R10: ca5f36c0b3036a5c R11: 461b209f52c7bbe5 R12: 0000000000025b79 Mar 31 14:00:06 blender kernel: R13: ffffffffa0110404 R14: 0000000000000000 R15: ffffc90009377a18 Mar 31 14:00:06 blender kernel: FS: 000000c000100890(0000) GS:ffff88a03fb80000(0000) knlGS:0000000000000000 Mar 31 14:00:06 blender kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 31 14:00:06 blender kernel: CR2: 0000000000000009 CR3: 00000014467e6001 CR4: 00000000000626e0 Mar 31 14:00:06 blender kernel: Call Trace: Mar 31 14:00:06 blender kernel: <TASK> Mar 31 14:00:06 blender kernel: __nf_nat_alloc_null_binding+0x68/0x7f [nf_nat] Mar 31 14:00:06 blender kernel: nf_nat_inet_fn+0xa6/0x187 [nf_nat] Mar 31 14:00:06 blender kernel: nf_nat_ipv4_out+0x15/0x8b [nf_nat] Mar 31 14:00:06 blender kernel: nf_hook_slow+0x3e/0x93 Mar 31 14:00:06 blender kernel: nf_hook+0xaf/0xd6 Mar 31 14:00:06 blender kernel: ? __ip_finish_output+0x14e/0x14e Mar 31 14:00:06 blender kernel: ip_output+0x82/0x8f Mar 31 14:00:06 blender kernel: ? __ip_finish_output+0x14e/0x14e Mar 31 14:00:06 blender kernel: __ip_queue_xmit+0x303/0x33d Mar 31 14:00:06 blender kernel: __tcp_transmit_skb+0x84e/0x8c0 Mar 31 14:00:06 blender kernel: tcp_connect+0x768/0x7f7 Mar 31 14:00:06 blender kernel: tcp_v4_connect+0x402/0x45b Mar 31 14:00:06 blender kernel: __inet_stream_connect+0xd8/0x2cf Mar 31 14:00:06 blender kernel: inet_stream_connect+0x39/0x4e Mar 31 14:00:06 blender kernel: __sys_connect+0x67/0xa2 Mar 31 14:00:06 blender kernel: ? __sys_socket+0x88/0xb7 Mar 31 14:00:06 blender kernel: __x64_sys_connect+0x14/0x17 Mar 31 14:00:06 blender kernel: do_syscall_64+0x83/0xa5 Mar 31 14:00:06 blender kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae Mar 31 14:00:06 blender kernel: RIP: 0033:0x49c99b Mar 31 14:00:06 blender kernel: Code: fc ff eb bd e8 46 a8 fc ff e9 61 ff ff ff cc e8 9b 81 fc ff 48 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 Mar 31 14:00:06 blender kernel: RSP: 002b:000000c0003758b0 EFLAGS: 00000202 ORIG_RAX: 000000000000002a Mar 31 14:00:06 blender kernel: RAX: ffffffffffffffda RBX: 000000c00001e000 RCX: 000000000049c99b Mar 31 14:00:06 blender kernel: RDX: 0000000000000010 RSI: 000000c0003ca0ec RDI: 0000000000000005 Mar 31 14:00:06 blender kernel: RBP: 000000c0003758f8 R08: 00000000005067c0 R09: 0000000000000000 Mar 31 14:00:06 blender kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000001 Mar 31 14:00:06 blender kernel: R13: 0000000000000001 R14: 0000000000000008 R15: ffffffffffffffff Mar 31 14:00:06 blender kernel: </TASK> Mar 31 14:00:06 blender kernel: Modules linked in: vhost_net vhost vhost_iotlb tap kvm_intel kvm md_mod xt_connmark xt_comment iptable_raw xt_mark cmac cifs asn1_decoder cifs_arc4 cifs_md4 oid_registry xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle tun xt_nat xt_tcpudp veth macvlan xt_conntrack nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter xfs iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables igb i2c_algo_bit x86_pkg_temp_thermal intel_powerclamp coretemp ipmi_ssif crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl mpt3sas intel_cstate intel_uncore i2c_i801 ahci sr_mod i2c_smbus raid_class input_leds cdrom libahci led_class i2c_core scsi_transport_sas Mar 31 14:00:06 blender kernel: acpi_ipmi wmi ipmi_si acpi_pad button [last unloaded: md_mod] Mar 31 14:00:06 blender kernel: CR2: 0000000000000009 Mar 31 14:00:06 blender kernel: ---[ end trace 0be523834a4c13bc ]--- Mar 31 14:00:06 blender kernel: RIP: 0010:clear_bit+0x0/0x6 Mar 31 14:00:06 blender kernel: Code: 89 e7 e8 65 43 01 00 48 8d 54 1d ff 31 c9 48 89 ee 4c 89 ef e8 e2 00 01 00 4d 63 e6 5b 4c 89 e0 5d 41 5c 41 5d 41 5e 41 5f c3 <f0> 48 0f b3 3e c3 48 8b 07 48 8b 88 f0 01 00 00 81 b9 04 0d 00 00 Mar 31 14:00:06 blender kernel: RSP: 0018:ffffc9000b6f7ba0 EFLAGS: 00010246 Mar 31 14:00:06 blender kernel: RAX: ffff888153b2dbc8 RBX: ffff8898aa491c08 RCX: 00000000801c000d Mar 31 14:00:06 blender kernel: RDX: 00000000801c000e RSI: 0000000000000068 RDI: 0000000000000000 blender-diagnostics-20220331-1726.zip
