March 29, 20224 yr Hello, I've been experiencing some random server crashes. Not exactly sure what could be causing it as it happens at different intervals. Sometimes I can go days without any issues. When it happens, I lose network access, access to the web interface, and access to SSH or local terminal (at the machine). Can someone help take a look at my logs to see if I'm missing something obvious? Thanks thetower-diagnostics-20220328-1953.zip
March 29, 20224 yr Not much in the logs since they are stored in RAM and are lost on a reboot. Did you check that : https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173 ?
March 29, 20224 yr Author @ChatNoir no I wasn't aware of that. But I'll certainly check and try that. I do have a Gen 1 Threadripper processor so it's quite possible that some bios update / tuning is required. I'll take a look at that as a start and report back. Question, is there anyway to get syslogs to be persistent? That way if i experience another crash we could have access to the log information and not lose it to reboot?
March 29, 20224 yr Google "unraid syslog server" or check unraid wiki, it's in there. Pretty simples. Edited March 29, 20224 yr by superloopy1
April 4, 20224 yr Author Hello, This weekend went into the BIOs and disabled Global C-States However, this morning the server crashed again. This time though, I had a monitor hooked up to the server and was able to take a image of the screen <code> a(PO) drm backlight agpgart w83795 i5500_temp ip6table_filter ip6_tables iptable _filter ip_tables x_tables be2net igb i2c_algo_bit atlantic edac_mce_amd kvm_ama kvm btusb btrt1 crct10dif_pclmul crc32_pclmul btbcm crc32c_intel btintel ghash_ clmulni_intel aesni_intel crypto_simd bluetooth mxm_wmi cryptd wmi_bmof glue_he I per mpt3sas izc_piix4 raid_class ecdh_generic input_leds ecc nume rapl scsi_tran sport_sas ahci i2c_core led_class nume_core k10temp wmi ccp libahci button acpi-_ cpufreq [last unloaded : be2net] --- end trace 306897cb8606c0c5 ]--- RIP: 0010:nf_nat_setup_info+0x129/0x6aa [nf_nat] Code: ff 48 8b 15 ef 6a 00 00 89 c0 48 8d 04 c2 48 8b 10 48 85 d2 74 80 48 81 ea 98 00 00 00 48 85 d2 of 84 70 ff ff ff 8a 44 24 46 <38> 42 46 74 09 48 8b 92 98 00 00 00 eb d9 48 8b 4a 20 48 8b 42 28 RSP: 0018:ffffc9000075c700 EFLAGS: 00010202 RAX: ffff8881bf5e5d11 RBX: ffff8884cb2d6940 RCX: 0000000000000000 RDX: 41a68045a11c4623 RSI: 0000000017213a45 RDI: ffffc9000075c720 RBP: ffffc9000075c7c8 R08: 00000000251a42d2 R09: ffff8881bec61680 R10: ffff8881432ec388 R11: ffffffff815cbe4b R12: 0000000000000000 R13: ffffc9000075c720 R14: ffffc9000075c7dc R15: ffffffff8210b440 FS: 0000150126d5b640(0000) GS:ffff889ffd340000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CRO: 0000000080050033 CR2: 0000148053281800 CR3: 000000013e810000 CR4: 00000000003506e0 Kernel panic not syncing: Fatal exception in interrupt Kernel Offset: disabled --- [ end Kernel panic not syncing: Fatal exception in interrupt ]--- </code> Any clue what this is referring to?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.