Unraid rebooting when array is started; renamed itself back to "tower" attached is my diagnostics

[Asmithcompute]

Not sure what's going on. in my system logs I'm getting this ( I apologize if I am not giving you guy the correct info, this is the first time ive had a problem like this. Please let me know if you need anything else to help identify the problem.

p.s I got this new CPU about 3 weeks ago, and haven't had an issue until the 28th in which ive been gone a few days after it kept restarting so I left it until now. also I had also switch a raid1 256GB pool into a 1tb pool and separate 250gb pool a day or two before this. not sure if it has anything to do with this

Jul 28 18:56:18 Tower kernel: ------------[ cut here ]------------ Jul 28 18:56:18 Tower kernel: RPM raw-wakeref not held Jul 28 18:56:18 Tower kernel: WARNING: CPU: 0 PID: 2817 at drivers/gpu/drm/i915/intel_runtime_pm.h:127 assert_rpm_wakelock_held+0x2d/0x58 [i915] Jul 28 18:56:18 Tower kernel: Modules linked in: kvmgt(+) kvm mdev i915 drm_buddy i2c_algo_bit ttm drm_display_helper drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd cryptd rapl nvme intel_cstate mei_hdcp mei_pxp wmi_bmof intel_wmi_thunderbolt i2c_i801 i2c_smbus intel_uncore i2c_core nvme_core mei_me e1000e video ahci mei libahci tpm_tis tpm_tis_core tpm thermal fan wmi backlight intel_pmc_core acpi_pad button unix Jul 28 18:56:18 Tower kernel: CPU: 0 PID: 2817 Comm: modprobe Tainted: G U 6.1.38-Unraid #2 Jul 28 18:56:18 Tower kernel: Hardware name: LENOVO INVALID /30D0, BIOS FWKTBFA 06/23/2022 Jul 28 18:56:18 Tower kernel: RIP: 0010:assert_rpm_wakelock_held+0x2d/0x58 [i915] Jul 28 18:56:18 Tower kernel: Code: 40 8a 7f 11 e8 cc ff ff ff 66 85 db 75 1e 80 3d 66 e3 1e 00 00 75 15 48 c7 c7 80 12 7c a0 c6 05 56 e3 1e 00 01 e8 ab fb 9f e0 <0f> 0b c1 eb 10 75 1e 80 3d 42 e3 1e 00 00 75 15 48 c7 c7 9a 12 7c Jul 28 18:56:18 Tower kernel: RSP: 0018:ffffc9000042bcd8 EFLAGS: 00010282 Jul 28 18:56:18 Tower kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027 Jul 28 18:56:18 Tower kernel: RDX: 0000000000000002 RSI: ffffffff82090ebc RDI: 00000000ffffffff Jul 28 18:56:18 Tower kernel: RBP: 00000000000020a8 R08: 0000000000000000 R09: ffffffff82245ed0 Jul 28 18:56:18 Tower kernel: R10: 00007fffffffffff R11: 0000000000000000 R12: ffffc9000042bd80 Jul 28 18:56:18 Tower kernel: R13: 0000000000000000 R14: ffff88813dce8000 R15: ffff88813dce9c40 Jul 28 18:56:18 Tower kernel: FS: 000014fe2a988740(0000) GS:ffff88881dc00000(0000) knlGS:0000000000000000 Jul 28 18:56:18 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 28 18:56:18 Tower kernel: CR2: 00000000006bff58 CR3: 0000000104b32006 CR4: 00000000003706f0 Jul 28 18:56:18 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 28 18:56:18 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jul 28 18:56:18 Tower kernel: Call Trace: Jul 28 18:56:18 Tower kernel: <TASK> Jul 28 18:56:18 Tower kernel: ? __warn+0xab/0x122 Jul 28 18:56:18 Tower kernel: ? report_bug+0x109/0x17e Jul 28 18:56:18 Tower kernel: ? assert_rpm_wakelock_held+0x2d/0x58 [i915] Jul 28 18:56:18 Tower kernel: ? handle_bug+0x41/0x6f Jul 28 18:56:18 Tower kernel: ? exc_invalid_op+0x13/0x60 Jul 28 18:56:18 Tower kernel: ? asm_exc_invalid_op+0x16/0x20 Jul 28 18:56:18 Tower kernel: ? assert_rpm_wakelock_held+0x2d/0x58 [i915] Jul 28 18:56:18 Tower kernel: ? assert_rpm_wakelock_held+0x2d/0x58 [i915] Jul 28 18:56:18 Tower kernel: fwtable_read32+0x24/0xb8 [i915] Jul 28 18:56:18 Tower kernel: handle_mmio+0x4d/0x65 [i915] Jul 28 18:56:18 Tower kernel: iterate_generic_mmio+0x1d/0x5ae9 [i915] Jul 28 18:56:18 Tower kernel: intel_gvt_iterate_mmio_table+0x12/0x194e [i915] Jul 28 18:56:18 Tower kernel: intel_gvt_init_device+0x170/0x23a [i915] Jul 28 18:56:18 Tower kernel: ? intel_gvt_clean_device+0x53/0x53 [i915] Jul 28 18:56:18 Tower kernel: intel_gvt_set_ops+0x5e/0x82 [i915] Jul 28 18:56:18 Tower kernel: ? 0xffffffffa062f000 Jul 28 18:56:18 Tower kernel: kvmgt_init+0x12/0x1000 [kvmgt] Jul 28 18:56:18 Tower kernel: do_one_initcall+0x82/0x19f Jul 28 18:56:18 Tower kernel: ? kmalloc_trace+0x43/0x52 Jul 28 18:56:18 Tower kernel: do_init_module+0x4b/0x1d4 Jul 28 18:56:18 Tower kernel: __do_sys_init_module+0xb6/0xf9 Jul 28 18:56:18 Tower kernel: do_syscall_64+0x68/0x81 Jul 28 18:56:18 Tower kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd Jul 28 18:56:18 Tower kernel: RIP: 0033:0x14fe2aaacdfa Jul 28 18:56:18 Tower kernel: Code: 48 8b 0d 21 20 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ee 1f 0d 00 f7 d8 64 89 01 48 Jul 28 18:56:18 Tower kernel: RSP: 002b:00007ffe747a90b8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af Jul 28 18:56:18 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000429480 RCX: 000014fe2aaacdfa Jul 28 18:56:18 Tower kernel: RDX: 000000000041d480 RSI: 0000000000087428 RDI: 0000000000638b30 Jul 28 18:56:18 Tower kernel: RBP: 000000000041d480 R08: 0000000000000007 R09: 00000000004290a0 Jul 28 18:56:18 Tower kernel: R10: 0000000000000005 R11: 0000000000000246 R12: 0000000000638b30 Jul 28 18:56:18 Tower kernel: R13: 0000000000000000 R14: 0000000000429590 R15: 0000000000000000 Jul 28 18:56:18 Tower kernel: </TASK> Jul 28 18:56:18 Tower kernel: ---[ end trace 0000000000000000 ]--- Jul 28 18:56:18 Tower kernel: ------------[ cut here ]------------ Jul 28 18:56:18 Tower kernel: RPM wakelock ref not held during HW access Jul 28 18:56:18 Tower kernel: WARNING: CPU: 0 PID: 2817 at drivers/gpu/drm/i915/intel_runtime_pm.h:135 assert_rpm_wakelock_held+0x50/0x58 [i915] Jul 28 18:56:18 Tower kernel: Modules linked in: kvmgt(+) kvm mdev i915 drm_buddy i2c_algo_bit ttm drm_display_helper drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops ip6table_filter ip6_tables iptable_filter ip_tables x_tables af_packet 8021q garp mrp bridge stp llc bonding tls intel_rapl_msr intel_rapl_common iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 aesni_intel crypto_simd cryptd rapl nvme intel_cstate mei_hdcp mei_pxp wmi_bmof intel_wmi_thunderbolt i2c_i801 i2c_smbus intel_uncore i2c_core nvme_core mei_me e1000e video ahci mei libahci tpm_tis tpm_tis_core tpm thermal fan wmi backlight intel_pmc_core acpi_pad button unix Jul 28 18:56:18 Tower kernel: CPU: 0 PID: 2817 Comm: modprobe Tainted: G U W 6.1.38-Unraid #2 Jul 28 18:56:18 Tower kernel: Hardware name: LENOVO INVALID /30D0, BIOS FWKTBFA 06/23/2022 Jul 28 18:56:18 Tower kernel: RIP: 0010:assert_rpm_wakelock_held+0x50/0x58 [i915] Jul 28 18:56:18 Tower kernel: Code: 00 01 e8 ab fb 9f e0 0f 0b c1 eb 10 75 1e 80 3d 42 e3 1e 00 00 75 15 48 c7 c7 9a 12 7c a0 c6 05 32 e3 1e 00 01 e8 88 fb 9f e0 <0f> 0b 5b c3 cc cc cc cc 0f 1f 44 00 00 41 54 41 89 d4 55 89 f5 53 Jul 28 18:56:18 Tower kernel: RSP: 0018:ffffc9000042bcd8 EFLAGS: 00010282 Jul 28 18:56:18 Tower kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000027 Jul 28 18:56:18 Tower kernel: RDX: 0000000000000002 RSI: ffffffff82090ebc RDI: 00000000ffffffff Jul 28 18:56:18 Tower kernel: RBP: 00000000000020a8 R08: 0000000000000000 R09: ffffffff82245ed0 Jul 28 18:56:18 Tower kernel: R10: 00007fffffffffff R11: 0000000000000000 R12: ffffc9000042bd80 Jul 28 18:56:18 Tower kernel: R13: 0000000000000000 R14: ffff88813dce8000 R15: ffff88813dce9c40 Jul 28 18:56:18 Tower kernel: FS: 000014fe2a988740(0000) GS:ffff88881dc00000(0000) knlGS:0000000000000000 Jul 28 18:56:18 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 28 18:56:18 Tower kernel: CR2: 00000000006bff58 CR3: 0000000104b32006 CR4: 00000000003706f0 Jul 28 18:56:18 Tower kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jul 28 18:56:18 Tower kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jul 28 18:56:18 Tower kernel: Call Trace: Jul 28 18:56:18 Tower kernel: <TASK> Jul 28 18:56:18 Tower kernel: ? __warn+0xab/0x122 Jul 28 18:56:18 Tower kernel: ? report_bug+0x109/0x17e Jul 28 18:56:18 Tower kernel: ? assert_rpm_wakelock_held+0x50/0x58 [i915] Jul 28 18:56:18 Tower kernel: ? handle_bug+0x41/0x6f Jul 28 18:56:18 Tower kernel: ? exc_invalid_op+0x13/0x60 Jul 28 18:56:18 Tower kernel: ? asm_exc_invalid_op+0x16/0x20 Jul 28 18:56:18 Tower kernel: ? assert_rpm_wakelock_held+0x50/0x58 [i915] Jul 28 18:56:18 Tower kernel: ? assert_rpm_wakelock_held+0x50/0x58 [i915] Jul 28 18:56:18 Tower kernel: fwtable_read32+0x24/0xb8 [i915] Jul 28 18:56:18 Tower kernel: handle_mmio+0x4d/0x65 [i915] Jul 28 18:56:18 Tower kernel: iterate_generic_mmio+0x1d/0x5ae9 [i915] Jul 28 18:56:18 Tower kernel: intel_gvt_iterate_mmio_table+0x12/0x194e [i915] Jul 28 18:56:18 Tower kernel: intel_gvt_init_device+0x170/0x23a [i915] Jul 28 18:56:18 Tower kernel: ? intel_gvt_clean_device+0x53/0x53 [i915] Jul 28 18:56:18 Tower kernel: intel_gvt_set_ops+0x5e/0x82 [i915] Jul 28 18:56:18 Tower kernel: ? 0xffffffffa062f000 Jul 28 18:56:18 Tower kernel: kvmgt_init+0x12/0x1000 [kvmgt] Jul 28 18:56:18 Tower kernel: do_one_initcall+0x82/0x19f Jul 28 18:56:18 Tower kernel: ? kmalloc_trace+0x43/0x52 Jul 28 18:56:18 Tower kernel: do_init_module+0x4b/0x1d4 Jul 28 18:56:18 Tower kernel: __do_sys_init_module+0xb6/0xf9 Jul 28 18:56:18 Tower kernel: do_syscall_64+0x68/0x81 Jul 28 18:56:18 Tower kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd Jul 28 18:56:18 Tower kernel: RIP: 0033:0x14fe2aaacdfa Jul 28 18:56:18 Tower kernel: Code: 48 8b 0d 21 20 0d 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d ee 1f 0d 00 f7 d8 64 89 01 48 Jul 28 18:56:18 Tower kernel: RSP: 002b:00007ffe747a90b8 EFLAGS: 00000246 ORIG_RAX: 00000000000000af Jul 28 18:56:18 Tower kernel: RAX: ffffffffffffffda RBX: 0000000000429480 RCX: 000014fe2aaacdfa Jul 28 18:56:18 Tower kernel: RDX: 000000000041d480 RSI: 0000000000087428 RDI: 0000000000638b30 Jul 28 18:56:18 Tower kernel: RBP: 000000000041d480 R08: 0000000000000007 R09: 00000000004290a0 Jul 28 18:56:18 Tower kernel: R10: 0000000000000005 R11: 0000000000000246 R12: 0000000000638b30 Jul 28 18:56:18 Tower kernel: R13: 0000000000000000 R14: 0000000000429590 R15: 0000000000000000 Jul 28 18:56:18 Tower kernel: </TASK> Jul 28 18:56:18 Tower kernel: ---[ end trace 0000000000000000 ]--- Jul 28 18:56:18 Tower kernel: i915 0000:00:02.0: Direct firmware load for i915/gvt/vid_0x8086_did_0x1912_rid_0x06.golden_hw_state failed with error -2 Jul 28 18:56:18 Tower kernel: i915 0000:00:02.0: MDEV: Registered

tower-diagnostics-20230731-1712.zip

[itimpi]

Your flash drive is not showing up in the SMART information which makes me think it has dropped offline.   That would explain the server name reverting to the default.

[Asmithcompute]

the flash drive dropped offline? so should i shut the server off and try to replug it?

[itimpi]

5 minutes ago, Asmithcompute said:

the flash drive dropped offline? so should i shut the server off and try to replug it?

Probably rebooting the server is enough, but a full power cycle would not hurt.   You could also consider trying a different USB port (preferably USB2 if you have one).

[Asmithcompute]

unfortunetly I only have usb 3.0 ports, im using a usb 2.0 drive though. I will try that now.

[Asmithcompute]

19 minutes ago, itimpi said:

Probably rebooting the server is enough, but a full power cycle would not hurt.   You could also consider trying a different USB port (preferably USB2 if you have one).

so far its not good. tried shutting it off and back on, and moving it. my little lenovo m900 is beeping twice before start up. ugh. 

[fallenfederation]

Does it still beep if you boot without the flashdrive? Also try plugging the flashdrive into the front/top usb ports (not into the motherboard).

Edited July 31, 2023 by fallenfederation

[Asmithcompute]

54 minutes ago, fallenfederation said:

Does it still beep if you boot without the flashdrive? Also try plugging the flashdrive into the front/top usb ports (not into the motherboard).

it does still beep without flashdrive. and i tried plugging it into the front port as well. hmmmmmm

[Asmithcompute]

On 7/31/2023 at 7:04 PM, fallenfederation said:

Does it still beep if you boot without the flashdrive? Also try plugging the flashdrive into the front/top usb ports (not into the motherboard).

okay ive plugged a monitor into it, and when it posts, it says " machine type or serial number is invalid"

[Frank1940]

I would suggest googling the expression----      machine type or serial number is invalid

[Asmithcompute]

44 minutes ago, Frank1940 said:

I would suggest googling the expression----      machine type or serial number is invalid

yeah doing that now. I have no idea how my computer could have just randomly forgotten its serial number...ive been using this pc as my server for months now slowly upgrading it