DivideBy0

That's bummer, not in UnRaid control. Where could I escalate this issue?

With or without blacklist statement, it doesn't make any difference, it does not work. What the heck man, it worked just fine before 6.12? I now have to downgrade to ?? to keep this working? What changed? Kernel? Really frustrating

No display, is a headless server.

O maaannnn. I have to take everything apart just for a jumper It worked fine before, what the heck changed? I will look at the BIOS first I guess

I have not changed any hardware. Everything was working perfect before 6.12.6 I believe. I tried the new line in i915.conf but no difference after reboot. Same errors. I did an upgrade to 6.12.8, rebooted and same errors. See attached Diagnostic again please. nas-unraid-2-diagnostics-20240229-1023.zip

Still not working and here is the "Diagnostic" file. Appreciate it. nas-unraid-2-diagnostics-20240229-0916.zip

Looks like is the 915 is blacklisted in \config\modprobe.d\i915.conf? Take that line off?

My apology, is attached now.

Didn't pay attention after the upgrade but I look at my gTOP and I get nothing. Something happened during the 6.12.6 upgrade with the kernel or my plugins got screwed up? It was working fine. root@NAS-UNRAID-2:~# dmesg | grep i915 [ 56.640642] i915 0000:00:02.0: [drm] VT-d active for gfx access [ 56.651966] i915_driver_probe+0x83f/0xc19 [i915] [ 56.659757] i915_init+0x1f/0x7f [i915] [ 56.668112] Modules linked in: x86_pkg_temp_thermal intel_powerclamp coretemp i915(+) kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 ast sha256_ssse3 iosf_mbi sha1_ssse3 drm_vram_helper drm_buddy i2c_algo_bit aesni_intel drm_ttm_helper crypto_simd drm_display_helper ttm cryptd drm_kms_helper rapl ipmi_ssif intel_cstate drm mei_pxp mei_hdcp wmi_bmof i2c_i801 intel_gtt intel_uncore i2c_smbus nvme agpgart video mei_me tpm_crb mpt3sas(+) cdc_ether syscopyarea tpm_tis raid_class sysfillrect ahci acpi_ipmi tpm_tis_core usbnet sr_mod sysimgblt input_leds i2c_core igc mei nvme_core joydev led_class libahci cdrom mii scsi_transport_sas vmd thermal fb_sys_fops fan ipmi_si tpm backlight wmi intel_pmc_core acpi_tad acpi_pad button unix root@NAS-UNRAID-2:~# lspci -nn | grep VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation AlderLake-S GT1 [8086:4680] (rev 0c) 09:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 52) root@NAS-UNRAID-2:~# ls -la /dev/dri total 0 drwxrwxrwx 3 root root 80 Feb 29 07:35 ./ drwxr-xr-x 16 root root 4220 Feb 29 07:37 ../ drwxrwxrwx 2 root root 60 Feb 29 07:35 by-path/ crwxrwxrwx 1 root video 226, 0 Feb 29 07:36 card0 DMESG Output: [ 56.640783] BUG: kernel NULL pointer dereference, address: 0000000000000008 [ 56.640803] #PF: supervisor read access in kernel mode [ 56.640816] #PF: error_code(0x0000) - not-present page [ 56.640829] PGD 105afe067 P4D 105afe067 PUD 105aff067 PMD 0 [ 56.640846] Oops: 0000 [#1] PREEMPT SMP NOPTI [ 56.640857] CPU: 12 PID: 1017 Comm: udevd Not tainted 6.1.64-Unraid #1 [ 56.640875] Hardware name: ASUSTeK COMPUTER INC. System Product Name/Pro WS W680M-ACE SE, BIOS 2703 08/11/2023 [ 56.640902] RIP: 0010:kernfs_root+0x0/0x14 [ 56.640916] Code: 89 cb 44 8b 6c 24 30 e8 24 32 fb ff 48 8b bd 58 02 00 00 48 89 da 5b 48 89 c6 5d 4c 89 e1 45 89 e8 41 5c 41 5d e9 66 ff ff ff <48> 8b 47 08 48 85 c0 48 0f 45 f8 48 8b 47 50 c3 cc cc cc cc 0f 1f [ 56.640970] RSP: 0018:ffffc90000c27a88 EFLAGS: 00010286 [ 56.640984] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00000000ffffffff [ 56.641003] RDX: 0000000000000000 RSI: ffffffff81e987e8 RDI: 0000000000000000 [ 56.641022] RBP: ffffffff81e986a0 R08: 0000000000000000 R09: 00000000000001d8 [ 56.641040] R10: 8080808080808080 R11: fefefefefefefeff R12: ffffffff82335da0 [ 56.641059] R13: ffff8881020de000 R14: ffff8881123f1b50 R15: ffff8881020de0d0 [ 56.641078] FS: 000014d5f4a11240(0000) GS:ffff88903f700000(0000) knlGS:0000000000000000 [ 56.641100] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 56.641115] CR2: 0000000000000008 CR3: 0000000105a6e000 CR4: 0000000000750ee0 [ 56.641134] PKRU: 55555554 [ 56.641769] Call Trace: [ 56.642394] <TASK> [ 56.643011] ? __die_body+0x1a/0x5c [ 56.643626] ? page_fault_oops+0x329/0x376 [ 56.644233] ? do_user_addr_fault+0x12e/0x48d [ 56.644835] ? exc_page_fault+0xfb/0x11d [ 56.645432] ? asm_exc_page_fault+0x22/0x30 [ 56.646036] ? kernfs_vfs_xattr_set+0x41/0x41 [ 56.646648] ? notifier_call_chain+0x35/0x5a [ 56.647266] kernfs_find_and_get_ns+0x1c/0x5c [ 56.647874] sysfs_unmerge_group+0x16/0x4d [ 56.648473] dpm_sysfs_remove+0x1e/0x52 [ 56.649075] device_del+0xa4/0x31d [ 56.649663] platform_device_del+0x21/0x70 [ 56.650241] platform_device_unregister+0xf/0x19 [ 56.650814] sysfb_disable+0x2b/0x54 [ 56.651385] aperture_remove_conflicting_pci_devices+0x1e/0x82 [ 56.651966] i915_driver_probe+0x83f/0xc19 [i915] [ 56.652597] ? slab_free_freelist_hook.constprop.0+0x3b/0xaf [ 56.653173] local_pci_probe+0x3d/0x81 [ 56.653741] pci_device_probe+0x197/0x1eb [ 56.654314] ? sysfs_do_create_link_sd+0x71/0xb7 [ 56.654887] really_probe+0x115/0x282 [ 56.655451] __driver_probe_device+0xc0/0xf2 [ 56.656009] driver_probe_device+0x1f/0x77 [ 56.656561] ? __device_attach_driver+0x97/0x97 [ 56.657108] __driver_attach+0xd7/0xee [ 56.657648] ? __device_attach_driver+0x97/0x97 [ 56.658184] bus_for_each_dev+0x6e/0xa7 [ 56.658713] bus_add_driver+0xd8/0x1d0 [ 56.659238] driver_register+0x99/0xd7 [ 56.659757] i915_init+0x1f/0x7f [i915] [ 56.660325] ? 0xffffffffa14f7000 [ 56.660831] do_one_initcall+0x82/0x19f [ 56.661323] ? kmalloc_trace+0x43/0x52 [ 56.661797] do_init_module+0x4b/0x1d4 [ 56.662251] __do_sys_init_module+0xb6/0xf9 [ 56.662692] do_syscall_64+0x68/0x81 [ 56.663121] entry_SYSCALL_64_after_hwframe+0x64/0xce [ 56.663552] RIP: 0033:0x14d5f4f23dfa [ 56.663981] 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 [ 56.664916] RSP: 002b:00007ffdd5362838 EFLAGS: 00000246 ORIG_RAX: 00000000000000af [ 56.665388] RAX: ffffffffffffffda RBX: 0000000000468c20 RCX: 000014d5f4f23dfa [ 56.665856] RDX: 000014d5f5018aad RSI: 00000000004b1868 RDI: 000014d5f42b6010 [ 56.666317] RBP: 000014d5f5018aad R08: 0000000000000007 R09: 0000000000464e30 [ 56.666771] R10: 0000000000000005 R11: 0000000000000246 R12: 000014d5f42b6010 [ 56.667217] R13: 0000000000000000 R14: 000000000044b7e0 R15: 0000000000000000 [ 56.667666] </TASK> [ 56.668112] Modules linked in: x86_pkg_temp_thermal intel_powerclamp coretemp i915(+) kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 ast sha256_ssse3 iosf_mbi sha1_ssse3 drm_vram_helper drm_buddy i2c_algo_bit aesni_intel drm_ttm_helper crypto_simd drm_display_helper ttm cryptd drm_kms_helper rapl ipmi_ssif intel_cstate drm mei_pxp mei_hdcp wmi_bmof i2c_i801 intel_gtt intel_uncore i2c_smbus nvme agpgart video mei_me tpm_crb mpt3sas(+) cdc_ether syscopyarea tpm_tis raid_class sysfillrect ahci acpi_ipmi tpm_tis_core usbnet sr_mod sysimgblt input_leds i2c_core igc mei nvme_core joydev led_class libahci cdrom mii scsi_transport_sas vmd thermal fb_sys_fops fan ipmi_si tpm backlight wmi intel_pmc_core acpi_tad acpi_pad button unix [ 56.671499] CR2: 0000000000000008 [ 56.672111] ---[ end trace 0000000000000000 ]--- [ 59.050150] RIP: 0010:kernfs_root+0x0/0x14 [ 59.050780] Code: 89 cb 44 8b 6c 24 30 e8 24 32 fb ff 48 8b bd 58 02 00 00 48 89 da 5b 48 89 c6 5d 4c 89 e1 45 89 e8 41 5c 41 5d e9 66 ff ff ff <48> 8b 47 08 48 85 c0 48 0f 45 f8 48 8b 47 50 c3 cc cc cc cc 0f 1f [ 59.052041] RSP: 0018:ffffc90000c27a88 EFLAGS: 00010286 [ 59.052667] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00000000ffffffff [ 59.053294] RDX: 0000000000000000 RSI: ffffffff81e987e8 RDI: 0000000000000000 [ 59.053927] RBP: ffffffff81e986a0 R08: 0000000000000000 R09: 00000000000001d8 [ 59.054555] R10: 8080808080808080 R11: fefefefefefefeff R12: ffffffff82335da0 [ 59.055181] R13: ffff8881020de000 R14: ffff8881123f1b50 R15: ffff8881020de0d0 [ 59.055811] FS: 000014d5f4a11240(0000) GS:ffff88903f700000(0000) knlGS:0000000000000000 [ 59.056445] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 59.057083] CR2: 0000000000000008 CR3: 0000000105a6e000 CR4: 0000000000750ee0 [ 59.057731] PKRU: 55555554 [ 59.058368] note: udevd[1017] exited with irqs disabled [ 59.064587] udevd[961]: worker [1017] failed while handling '/devices/pci0000:00/0000:00:02.0' nas-unraid-2-diagnostics-20240229-0824.zip

In the future, will the grandfathered and subscription versions of UnRaid be identical, encompassing not only patches and updates but also capabilities and development? There are no plans to establish two separate tiers for UnRaid, correct? I inquire because I previously experienced a situation with an automation software, Indigo, which transitioned from a license model to a subscription model. Following this transition, the new app version was excluded from the grandfathered option, leading to the creation of two tiers where the grandfathered tier ceased to receive further developments or enhancements.

Upgraded 2 systems, smooth and no problem at all

This is a *unix system after all so at least it should mimic same basic security principles I don't think that's asking for too much. After all is *unix that invented the security principles and not Al Gore

So far stable after these changes. Lets hope it stays that way. Will keep reporting

LOL I think you're ready for your CISSP now. Monkey see, Monkey do

LOL, keep talking, keep digging, and get a troll mirror and take a look at it. Since you din't get the hint the nice way, let me try another way. Your rubbish is just bunch of rambling non-sense and please stop polluting everyones time and availability. MOVE ON mate, please. Get TrueNAS, get BSDI or SCO or Solaris for what I care, get even KALI on a CD if it makes you happy.

Sorry mate but you're a child. I would be scared to hire you in this filed even as an intern. That being said I disengage from your nonsense ranting. I politely asked, show me the money and you kept on ranting. Unless you have objective proof take the backseat and you may learn something.

But of course you had a rebuttal So that leaves my UnRaid vulnerable / flying blind at SSL mercy. Enlighten me now what's the worse can and will happen with my UnRaid over SSL. Keep the facts objective, quantitative and not what you read or what you heard I have no need to hear what could potentially happen. Hard facts strictly related to UnRaid which you claim is unsecure but have no data or evidence to offer. By the way Nessus will use the same scanning engines / plugins as the nmap ones, which really tells me how well versed you're in the world of cybersecurity if you don't know the difference. And I don't believe you're grasping the concept of defense in depth. What the hell is "vulnerability and hardening in the host is also defense in depth."

My stuff is behind the firewall and in a DMZ. Nothing is allowed inbound including the UnRaid cloud plugin. My IPS/IDS can and will see and block anything inbound/outbound. Is called defense in depth, multiple layers of defense. That being said I am to lazy to do this but have at it and report back: nmap -sV --script=vulscan/vulscan.nse www.example.com nmap --script nmap-vulners/ -sV www.example.com https://securitytrails.com/blog/nmap-vulnerability-scan

This argument is dead in the water from the beginning Says who that UnRaid is not secure nor stable? I would start with that first Nothing to see and nothing to debate here, end of story.

I changed my setting to this so we will see if it makes a difference? My setup has: NFS Disable and Tunable (support Hard Links): 0

My shares are gone AGAIN this morning. Not cool as I am getting annoyed by this bug. How can we troubleshoot? What do you guys need besides the diagnostic file? nas-unraid-2-diagnostics-20231006-0758.zip

I guess I need to write a script and when the shares are no longer available do a reboot

Thanks Jorge, indeed the reboot fixed. Will this permanently be fixed or is one of these things?

Version: 6.12.4 , all my shares are gone from GUI or CLI. I haven't done a reboot yet but I do have a recent backup for my flash and my dockers so I am good there. Here is my diagnostics file. Should I just reboot and hopefully they comeback? Can't explain it nas-unraid-2-diagnostics-20231004-1639.zip

Nobody?