The Crazy Squirrel

Is this a possible TPM module fault? My system logs just get flooded with this error message. Jul 16 11:18:27 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:18:39 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:18:51 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:19:04 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:19:16 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:19:28 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:19:41 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:19:53 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:20:05 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:20:17 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:20:30 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:20:42 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:20:54 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:21:07 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:21:19 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:21:31 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:21:43 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:21:56 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:22:08 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:22:20 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:22:33 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:22:45 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:22:57 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:23:10 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:23:22 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:23:34 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:23:46 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:23:59 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:24:11 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:24:23 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:24:36 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:24:48 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:25:00 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:25:12 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:25:25 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:25:37 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:25:49 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:26:02 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:26:14 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:26:26 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:26:38 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:26:51 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:27:03 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:27:15 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:27:28 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:27:40 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:27:52 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:28:04 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:28:17 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:28:29 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:28:41 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 Jul 16 11:28:54 Cthulhu kernel: tpm tpm0: tpm_try_transmit: send(): error -62 syslog-10.42.71.10 (1).log

Did I just have a CPU failure? This most recent problem started July 5th at 10:36, and it caused the entire system to become completely unresponsive. Jul 5 10:36:10 Cthulhu kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 Jul 5 10:36:10 Cthulhu kernel: #PF: supervisor read access in kernel mode Jul 5 10:36:10 Cthulhu kernel: #PF: error_code(0x0000) - not-present page Jul 5 10:36:10 Cthulhu kernel: PGD 80000003632f7067 P4D 80000003632f7067 PUD 20f41a067 PMD 0 Jul 5 10:36:10 Cthulhu kernel: Oops: Oops: 0000 [#1] PREEMPT SMP PTI Jul 5 10:36:10 Cthulhu kernel: CPU: 1 UID: 0 PID: 23781 Comm: nv_queue Tainted: P O 6.12.24-Unraid #1 Jul 5 10:36:10 Cthulhu kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE Jul 5 10:36:10 Cthulhu kernel: Hardware name: Supermicro PIO-617R-TLN4F+-ST031/X9DRi-LN4+/X9DR3-LN4+, BIOS 3.4 11/20/2019 Jul 5 10:36:10 Cthulhu kernel: RIP: 0010:_nv036336rm+0x51/0xc0 [nvidia] Jul 5 10:36:10 Cthulhu kernel: Code: ff 84 c0 74 79 48 8b 7d 28 48 c7 c6 40 8b c6 a6 e8 04 bd 36 00 48 85 c0 74 df 80 b8 90 01 00 00 00 75 d6 48 8b 80 78 01 00 00 <48> 8b 18 48 85 db 75 20 eb c5 0f 1f 44 00 00 48 8b 80 58 01 00 00 Jul 5 10:36:10 Cthulhu kernel: RSP: 0000:ffffc900086a3d90 EFLAGS: 00010246 Jul 5 10:36:10 Cthulhu kernel: RAX: 0000000000000000 RBX: ffff88893f282008 RCX: ffff88832332f460 Jul 5 10:36:10 Cthulhu kernel: RDX: ffffffffa6c973c0 RSI: 0000000000ec6de1 RDI: ffff888276fd2010 Jul 5 10:36:10 Cthulhu kernel: RBP: ffff8881a51c5fa0 R08: ffff888276fd2008 R09: 0000000000000000 Jul 5 10:36:10 Cthulhu kernel: R10: ffff8881a51c5f30 R11: ffff88895ef86a40 R12: ffff8889515b8008 Jul 5 10:36:10 Cthulhu kernel: R13: ffff88893f282008 R14: ffff8889515b8008 R15: ffffc900082f3d48 Jul 5 10:36:10 Cthulhu kernel: FS: 0000000000000000(0000) GS:ffff88885fa40000(0000) knlGS:0000000000000000 Jul 5 10:36:10 Cthulhu kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 5 10:36:10 Cthulhu kernel: CR2: 0000000000000000 CR3: 00000008da1a4006 CR4: 00000000001726f0 Jul 5 10:36:10 Cthulhu kernel: Call Trace: Jul 5 10:36:10 Cthulhu kernel: <TASK> Jul 5 10:36:10 Cthulhu kernel: ? _nv013522rm+0x16e/0x340 [nvidia] Jul 5 10:36:10 Cthulhu kernel: ? _nv013519rm+0x21/0x50 [nvidia] Jul 5 10:36:10 Cthulhu kernel: ? rm_execute_work_item+0x141/0x1f0 [nvidia] Jul 5 10:36:10 Cthulhu kernel: ? nv_kmem_cache_alloc_stack.constprop.0+0x21/0x50 [nvidia] Jul 5 10:36:10 Cthulhu kernel: ? os_execute_work_item+0x46/0x90 [nvidia] Jul 5 10:36:10 Cthulhu kernel: ? _main_loop+0xf2/0x120 [nvidia] Jul 5 10:36:10 Cthulhu kernel: ? __pfx__main_loop+0x10/0x10 [nvidia] Jul 5 10:36:10 Cthulhu kernel: ? kthread+0xef/0x100 Jul 5 10:36:10 Cthulhu kernel: ? __pfx_kthread+0x10/0x10 Jul 5 10:36:10 Cthulhu kernel: ? ret_from_fork+0x24/0x40 Jul 5 10:36:10 Cthulhu kernel: ? __pfx_kthread+0x10/0x10 Jul 5 10:36:10 Cthulhu kernel: ? ret_from_fork_asm+0x1a/0x30 Jul 5 10:36:10 Cthulhu kernel: </TASK> Jul 5 10:36:10 Cthulhu kernel: Modules linked in: tun cmac cifs cifs_arc4 nls_ucs2_utils cifs_md4 dns_resolver nf_conntrack_netlink veth xt_nat xt_tcpudp nvidia_uvm(PO) ipvlan xt_conntrack xt_MASQUERADE nfnetlink xfrm_user ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nfsd auth_rpcgss lockd grace sunrpc md_mod ntfs3 tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc bonding tls igb ixgbe xfrm_algo mdio nvidia_drm(PO) nvidia_modeset(PO) zfs(PO) intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp spl(O) ses enclosure coretemp kvm_intel nvidia(PO) kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 drm_ttm_helper aesni_intel ttm mgag200 crypto_simd video drm_shmem_helper cryptd tpm_tis drm_kms_helper rapl tpm_tis_core intel_cstate drm i2c_i801 ipmi_ssif mpt3sas isci tpm nvme agpgart mei_me backlight i2c_smbus i2c_algo_bit acpi_ipmi libsas libaescfb ahci raid_class intel_uncore Jul 5 10:36:10 Cthulhu kernel: ecdh_generic input_leds nvme_core i2c_core mei ipmi_si scsi_transport_sas libahci wmi ecc led_class joydev acpi_pad button [last unloaded: igb] Jul 5 10:36:10 Cthulhu kernel: CR2: 0000000000000000 Jul 5 10:36:10 Cthulhu kernel: ---[ end trace 0000000000000000 ]--- Jul 5 10:36:10 Cthulhu kernel: RIP: 0010:_nv036336rm+0x51/0xc0 [nvidia] Jul 5 10:36:10 Cthulhu kernel: Code: ff 84 c0 74 79 48 8b 7d 28 48 c7 c6 40 8b c6 a6 e8 04 bd 36 00 48 85 c0 74 df 80 b8 90 01 00 00 00 75 d6 48 8b 80 78 01 00 00 <48> 8b 18 48 85 db 75 20 eb c5 0f 1f 44 00 00 48 8b 80 58 01 00 00 Jul 5 10:36:10 Cthulhu kernel: RSP: 0000:ffffc900086a3d90 EFLAGS: 00010246 Jul 5 10:36:10 Cthulhu kernel: RAX: 0000000000000000 RBX: ffff88893f282008 RCX: ffff88832332f460 Jul 5 10:36:10 Cthulhu kernel: RDX: ffffffffa6c973c0 RSI: 0000000000ec6de1 RDI: ffff888276fd2010 Jul 5 10:36:10 Cthulhu kernel: RBP: ffff8881a51c5fa0 R08: ffff888276fd2008 R09: 0000000000000000 Jul 5 10:36:10 Cthulhu kernel: R10: ffff8881a51c5f30 R11: ffff88895ef86a40 R12: ffff8889515b8008 Jul 5 10:36:10 Cthulhu kernel: R13: ffff88893f282008 R14: ffff8889515b8008 R15: ffffc900082f3d48 Jul 5 10:36:10 Cthulhu kernel: FS: 0000000000000000(0000) GS:ffff88885fa40000(0000) knlGS:0000000000000000 Jul 5 10:36:10 Cthulhu kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 5 10:36:10 Cthulhu kernel: CR2: 0000000000000000 CR3: 00000008da1a4006 CR4: 00000000001726f0 Jul 5 10:36:10 Cthulhu kernel: note: nv_queue[23781] exited with irqs disabled Jul 5 10:36:31 Cthulhu kernel: BUG: unable to handle page fault for address: ffffc900086a3e40 Jul 5 10:36:31 Cthulhu kernel: #PF: supervisor read access in kernel mode Jul 5 10:36:31 Cthulhu kernel: #PF: error_code(0x0000) - not-present page Jul 5 10:36:31 Cthulhu kernel: PGD 100000067 P4D 100000067 PUD 100240067 PMD 10a2aa067 PTE 0 Jul 5 10:36:31 Cthulhu kernel: Oops: Oops: 0000 [#2] PREEMPT SMP PTI syslog-10.42.71.10.log

It's been nearly two weeks since the latest USB drive replacement, and my system has been working. So now this is where I add my voice to the numerous requests for Limetech to please allow users to tie their system boot drive to something other than a USB drive. After having a new USB drive that I took out of the packaging immediately fail, is a worse than terrible user experience. Because after having the new USB drive immediately fail in the same way as the previous drive, I assumed that the fault must be in some other component of the system. What are the chances of that actually happening? Well looking through various forum posts across the internet I find that this does, on rare occasions, happen to some people. And please don't respond with "my USB drive has been working for years, so there isn't a problem." or "If a USB drive fails, it's real easy to replace, so there isn't a problem." I don't find these type of responses to be very helpful, and only really goes to frustrate anyone who has had unusual problems with the USB drive requirement. Anyway, I would like to thank JorgeB for the response to try a different brand/model of USB drive, since I probably would have just gone with a third Samsung FIT. I did have a single error show up in the syslog a few days after the switch to the PNY USB drive... Jun 13 02:38:52 Cthulhu kernel: usb 2-1.1: reset high-speed USB device number 3 using ehci-pci Jun 13 02:38:52 Cthulhu kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=DRIVER_OK cmd_age=2s Jun 13 02:38:52 Cthulhu kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 10 a4 78 00 00 f0 00 Jun 13 02:38:52 Cthulhu kernel: I/O error, dev sda, sector 1090680 op 0x0:(READ) flags 0x84700 phys_seg 30 prio class 0Since my system appears to be running properly, and this error has only occured once, I think I'm OK. But I'm not sure what this error is. This might just be a bad block in the USB drive. If anyone else has any ideas what this error might be I would appreciate the assistance. I'm including this here instead of starting a new tread just in case this is somehow related to the problem I was having earlier, and there really is something wrong with the hardware of my system.

Ok, I have once again replaced my USB boot drive. This time with a PNY 32GB USB 2.0 drive. I'll cross my fingers and hope for the best. I'll come back to this thread in about a week and give an update. Sooner if I run into problems again.

Current UnRaid Version 7.1.2 syslog-10.42.71.10 (1).log I have moved the USB boot drive to various locations on the motherboard, both inside the chassis on the motherboard and on the rear I/O panel. I have replaced the USB drive once, Samsung FIT Plus 32GB, with a brand new Samsung FIT Plus 32GB. I have upgraded Unraid from 7.0.1 to 7.1.2. I have also replaced the Motherboard Supermicro X9DRi-LN4F+ Rev 1.20A, with an identical Motherboard. I've even tried the plugin "Flash Remount" without success. And yet this problem still remains. After a couple of days it appears as if the USB disconnects and the system effectively crashes. Sometimes I can open the local console and attempt to gracefully reboot, sometimes the console is just unresponsive.

Motherboard replacement didn't fix the problem either.

Today I replaced my motherboard, same model and revision number. Guess I'll see if that will fix this issue. I'll report back in a week or two if this does, or does not work.

So far it seems as if this disconnect sometimes occurs when I try to click on the dashboard tab of the UnRaid webgui.syslog-10.42.71.10.log

I am now having the exact same issue. I've moved the usb boot drive to a different location. From a port on the motherboard inside the chassis, to a port on the rear I/O plate of the motherboard. I've ran chkdsk on the usb boot drive. And I've even replaced the usb drive with a new one. The problem persists.