wesman

I also, replaced the "go" and my_bashproile files with ones from from my backup system (as they have stuff I wanted in there) Would that have caused this

I just installed this system, I rebooted it, and now its flipping out. 1.) It keeps losing one of the cache drives 2.) started calling itself TOWER even though that's not its name. 3.) Terminal colors are missing rebooting does the same thing (log in screen says Winterfelll) then it get to the main page, says it missing a cache disk, then starts calling itself TOWER tower-syslog-20200404-1948.zip tower-diagnostics-20200404-1449.zip update: DISK_ASSIGNMENTS.txt appears to be completely missing

Hi All, a little help please!!! Sorry for the exclamation points, i'm in a bit of a panic. I rebooted my server after it finished its April 1 parity check, and it came back up without the disk assignments. I know the layout of the disks, its like this. but, those blue squares indicate it's going to format those disks, right? I think I can check this to say the parity is already valid, but, its asking for (two) passphrases, like its going to overwrite the data!! Since it just did a parity check finding zero errors before the reboot, I know its right.. what is the proper steps to get this working again? Thank you!

@dmacias given that /usr/bin/borg and /usr/bin/borgfs on both 6.7.2 and 6.8.3 have the same dependancies, which are at the same level, can I just move copy them into the 6.7.2 folder and would it work?

Anyone seen this before in the install? you can see it didnt complete the PULL's in the top section. Unable to find image 'linuxserver/tautulli:latest' locally its been sitting at this screen for 5 minute, and not the Docker tab will not load

thought? is there a procedure somewhere?

Thanks, I've been trying to research this, but there does not appear to be much information on this out there. is this the correct procedure? 1.) Install Slackware on a temp box somewhere. (lastest version I assume) 2.) Install Borg and all its dependancies. 3.) move the freshly compiled slackware '/usr/bin/borg' to my unraid '/usr/bin/borg' 4.) reboot unraid? Am I close?

yes, I liked it two posts up. and it has several diagnostics and sys logs posted in it. and the only difference between the two servers are these intel i7-7700 ----> intel i9-9900 ASUS Z170-A Mobo. ----> Asrock z390 Taichi Ultimate Virtually everything else is the same. SOOOOOO Now I am thinking: The only other difference is that the old server started on 6.7.2 then went to 6.8.3 the new server started at 6.8.3 is anything pulled forward in the upgrade path, that is different in fresh install path that might cause this?

@trurl I ask these, because in 6.8.x it appears to have issues revolving around dockers hanging and freezing etc. not no real logs errors in syslog

@trurl That's a great question, with no answer. As you might remember (or might not, I am sure you see 1000's of these all day), from this post. 6.8.3, continually crashed and ran Parity Checks every 3 days or so. I ran down every possible error log, scrubbed through, 100's of log files, posted several times - No fix. No Fixes. I was really tearing my hear out, especially considering my old server is at 6.8.3 and running like a champ. new server, not so much. tried everything, including completely reinstalling, twice. and the only difference between the two are these intel i7-7700 ----> intel i9-9900 ASUS Z170-A Mobo. ----> Asrock z390 Taichi Ultimate Virtually everything else is the same. SOOOOOO Now I am thinking: The only other difference is that the old server started on 6.7.2 then went to 6.8.3 the new server started at 6.8.3 I reinstalled (fresh) the new server at 6.7.2 and its been running like a champ since 14 March 2020. I am completely installing all my programs, then I am going to upgrade it to 6.8.3 Is there anything pulled up from 6.7.2 to 6.8.x that would not be the same if it was just a 6.8.3 fresh install? maybe the docker image? if it goes back to being on stable at 6.8.X i'll just go back to 6.7.2. just need to figure out how to get my borg updated

Thanks, I've been trying to research this, but there does not appear to be much information on this out there. is this the correct procedure? 1.) Install Slackware on a temp box somewhere. (lastest version I assume) 2.) Install Borg and all its dependancies. 3.) move the freshly compiled slackware '/usr/bin/borg' to my unraid '/usr/bin/borg' 4.) reboot unraid? Am I close?

Yes, I know its in NerdPack - But the developer isn't updating 6.7.2 anymore. And for reasons, I need to stay at 6.7.2 for the time being, its not normally network facing, only for this update, so, not totally concerned about that. but is there a CLI command to update borg to 1.1.11? will the "sudo apt-get install package" still work??

Sorry. I only update the current stable for the most part. I just don't have the time to keep up with betas and past version compatibility. I understand, since its an install, will the basic "sudo apt-get install package" get what I need on unraid?

I hope this isn't the case, on my old server 6.8 doesn't want to be stable, i've tried several times but I am keeping this one at 6.7.2 until I can get that fixed

Hi @dmacias my target unraid server, is still at 6.7.2, and it still shows borg 1.1.10 as the latest? are there two different updates for this? could you update that as well?

Thanks, you're the best

@gfjardim I am currently on the 2020.03.14a version of the plug in. And my log it littered with this error every 6 seconds. I am not actually using the Pre-Clear at the moment.

@Hoopster thanks! @dmacias Thanks for the awesome plug in!, is it possible to request an update for BorgBackup? Thank YOU for your awesome work!

Does anyone know how to request an update to Nerd Pack? I noticed that Borg Backup was moved to 1.1.11 due to an error in the 1.1.10 that is current in Nerd Pack. I am sure it will get updated eventually but thought I could draw someones attention to it. If you're affected you can follow directions here to fix it, after the update in Nerd Pack, of course.

it might be 7.5 years old, but I still get this issue all the time. Following the above does fix it, until it does it again.

Thanks @johnnie.black I see this loop again and again, it does start with WARNING: CPU: 7 PID: 916 at fs/btrfs/extent_io.c:435 insert_state+0x30/0xe1 but I thought it was referencing the ncidia_uvm, i was thinking it might be related to plex and the video card. Mar 14 11:17:15 Valyria kernel: ------------[ cut here ]------------ Mar 14 11:17:15 Valyria kernel: BTRFS: end < start 4095 18446612749489541176 Mar 14 11:17:15 Valyria kernel: WARNING: CPU: 7 PID: 916 at fs/btrfs/extent_io.c:435 insert_state+0x30/0xe1 Mar 14 11:17:15 Valyria kernel: Modules linked in: nvidia_uvm(O) veth macvlan xt_CHECKSUM ipt_REJECT ip6table_mangle ip6table_nat nf_nat_ipv6 iptable_mangle ip6table_filter ip6_tables vhost_net tun vhost tap xt_nat ipt_MASQUERADE iptable_filter iptable_nat nf_nat_ipv4 nf_nat ip_tables xfs dm_crypt dm_mod dax nfsd lockd grace sunrpc md_mod nct6775 hwmon_vid atlantic e1000e igb(O) nvidia_drm(PO) nvidia_modeset(PO) x86_pkg_temp_thermal nvidia(PO) intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate wmi_bmof intel_wmi_thunderbolt mxm_wmi drm_kms_helper mpt3sas drm btusb btrtl btbcm btintel raid_class rsnvme(PO) bluetooth scsi_transport_sas nvme nvme_core wmi intel_uncore agpgart i2c_i801 ahci intel_rapl_perf Mar 14 11:17:15 Valyria kernel: syscopyarea sr_mod video sysfillrect i2c_core pcc_cpufreq ecdh_generic sysimgblt libahci backlight fb_sys_fops cdrom button acpi_pad [last unloaded: atlantic] Mar 14 11:17:15 Valyria kernel: CPU: 7 PID: 916 Comm: kswapd0 Tainted: P W O 4.19.98-Unraid #1 Mar 14 11:17:15 Valyria kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z390 Taichi Ultimate, BIOS P4.20 07/23/2019 Mar 14 11:17:15 Valyria kernel: RIP: 0010:insert_state+0x30/0xe1 Mar 14 11:17:15 Valyria kernel: Code: 89 c7 41 56 4d 89 ce 41 55 49 89 fd 41 54 49 89 d4 55 48 89 f5 53 48 89 cb 73 11 48 89 ce 48 c7 c7 54 88 d5 81 e8 26 aa e1 ff <0f> 0b 48 8b 4c 24 40 4c 89 ef 4c 89 65 00 48 89 ee 48 8b 54 24 38 Mar 14 11:17:15 Valyria kernel: RSP: 0018:ffffc90006703a90 EFLAGS: 00010286 Mar 14 11:17:15 Valyria kernel: RAX: 0000000000000000 RBX: 0000000000000fff RCX: 0000000000000007 Mar 14 11:17:15 Valyria kernel: RDX: 000000072af20962 RSI: 0000000000000002 RDI: ffff88903ddd64f0 Mar 14 11:17:15 Valyria kernel: RBP: ffff888037fd24b0 R08: 0000000000000003 R09: 0000000000003000 Mar 14 11:17:15 Valyria kernel: R10: 0000000000000000 R11: 000000000000004c R12: ffff888fb2841038 Mar 14 11:17:15 Valyria kernel: R13: ffff88815308f738 R14: ffffc90006703b18 R15: ffffc90006703b10 Mar 14 11:17:15 Valyria kernel: FS: 0000000000000000(0000) GS:ffff88903ddc0000(0000) knlGS:0000000000000000 Mar 14 11:17:15 Valyria kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 14 11:17:15 Valyria kernel: CR2: 000015162a65d000 CR3: 0000000001e0a001 CR4: 00000000003606e0 Mar 14 11:17:15 Valyria kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Mar 14 11:17:15 Valyria kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Mar 14 11:17:15 Valyria kernel: Call Trace: Mar 14 11:17:15 Valyria kernel: __set_extent_bit+0x132/0x430 Mar 14 11:17:15 Valyria kernel: lock_extent_bits+0x54/0x1d8 Mar 14 11:17:15 Valyria kernel: btrfs_evict_inode+0x141/0x420 Mar 14 11:17:15 Valyria kernel: evict+0xb8/0x16e Mar 14 11:17:15 Valyria kernel: dispose_list+0x30/0x39 Mar 14 11:17:15 Valyria kernel: prune_icache_sb+0x56/0x74 Mar 14 11:17:15 Valyria kernel: super_cache_scan+0x11a/0x16d Mar 14 11:17:15 Valyria kernel: do_shrink_slab+0x128/0x194 Mar 14 11:17:15 Valyria kernel: shrink_slab+0x20c/0x276 Mar 14 11:17:15 Valyria kernel: shrink_node+0x108/0x3cb Mar 14 11:17:15 Valyria kernel: kswapd+0x451/0x58a Mar 14 11:17:15 Valyria kernel: ? __switch_to_asm+0x41/0x70 Mar 14 11:17:15 Valyria kernel: ? __switch_to_asm+0x41/0x70 Mar 14 11:17:15 Valyria kernel: ? mem_cgroup_shrink_node+0xa4/0xa4 Mar 14 11:17:15 Valyria kernel: kthread+0x10c/0x114 Mar 14 11:17:15 Valyria kernel: ? kthread_park+0x89/0x89 Mar 14 11:17:15 Valyria kernel: ret_from_fork+0x1f/0x40 Mar 14 11:17:15 Valyria kernel: ---[ end trace ec01f8e5369e34db ]--- Mar 14 11:17:15 Valyria kernel: ------------[ cut here ]------------

Anyone have any ideas?

Yep! Uploaded the log too, worked this time, I zipped it, perhaps it liked that better valyria-diagnostics-20200312-0907.zip syslog-192.168.29.30.log.zip

@trurl Thanks, I figured it out, eventually. Not the best at this sort of thing @itimpi @Squid Got in install on a USB and ran the complete suit of tests for 48 hours. zero Memory issues. @johnnie.black After the memtest I ran with the case cover off to see if that would be the issue (airflow), with the case open, no more CPU warnings, but still crashing SYSLOG - Mar 11 07:07:XX - about this time it was updating plug ins - Looks like I rebooted shortly after that, maybe... then put in a wrong password - looks like it started loading disks at Mar 11 07:10:06 - Somthing happened with the NVIDIA card at 11 10:38:35 Valyria kernel: Modules linked in: nvidia_uvm(O) - Something is happening at, call stack? I have no idea Mar 11 10:38:35 Valyria kernel: Workqueue: events macvlan_process_broadcast [macvlan] - This is ODD as I know I was sleeping by this time (is this just sending email? I didnt get an email) Mar 11 11:24:14 Valyria login[31887]: ROOT LOGIN on '/dev/pts/0' Mar 11 11:51:47 Valyria sSMTP[6500]: Creating SSL connection to host Mar 11 11:51:47 Valyria sSMTP[6500]: SSL connection using TLS_AES_256_GCM_SHA384 Mar 11 11:51:53 Valyria sSMTP[6500]: Sent mail for [email protected] (221 2.0.0 closing connection o12sm6023436pjs.6 - gsmtp) uid=0 username=root - Then it appears that the GPU Crashes, it loops on this message for a while Mar 11 20:50:00 Valyria kernel: NVRM: GPU 0000:01:00.0: RmInitAdapter failed! (0x23:0x56:515) Mar 11 20:50:00 Valyria kernel: NVRM: GPU 0000:01:00.0: rm_init_adapter failed, device minor number 0 ** At Mar 11 20:50:00 Everything appears to enter a disabled state. Valyria kernel: vethd02192f: renamed from eth0 - Network appears to go down, dockers becomes disabled - ?? It install: a Mar 11 20:53:58 Valyria root: # Nerd Tools unRAID Plugin - ?? super weird why its trying to install all the plugins at 20:54:16 -- ?? appears to trying to stop and start the array Mar 11 20:59:19 Valyria kernel: mdcmd (63): start STOPPED -- alot of this happens as my MAC trys to remount its volumes Mar 11 21:48:16 Valyria webGUI: Successful login user root from 192.168.29.105 Mar 11 21:49:18 Valyria kernel: docker0: port 1(veth524682b) entered blocking state Mar 11 21:49:18 Valyria kernel: docker0: port 1(veth524682b) entered disabled state Mar 11 21:49:18 Valyria kernel: device veth524682b entered promiscuous mode Mar 11 21:49:18 Valyria kernel: IPv6: ADDRCONF(NETDEV_UP): veth524682b: link is not ready -- later in the log it looks like another NVIDIA crash - ** followed by a bunch of stack traces, which appear to loop until I reset it. Log attached below in another comment [10de:2184] 01:00.0 VGA compatible controller: NVIDIA Corporation TU116 [GeForce GTX 1660] (rev a1) using the @linuxserver.io unraid 6.8.2

Ah, thanks for the tip, I'll see what I can do. If I download it and install it, will it replace the memtest that is in the menu to launch the correct program?