Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

harrisonmeister

Members
  • Joined

  • Last visited

  1. Take a look at this other post here - https://forums.unraid.net/topic/190705-windows-11-recent-update-kb5058499-disabled-vm-processor-unsupported/
  2. Is it possible from within unraid to move data off one of a 2-drive BTRFS pool to the other? One is an NVME SSD, the other a 2.5" Drive. I pooled them together but my VMs are running slowly on the spinny disk, so want to move back to a single drive pool with the NVME SSD for the VM data disk.
  3. Thanks for the detailed answer, and no I didnt blacklist anything. I starting looking at syslog when I had done a reboot and unraid didnt cleanly shutdown to reboot. I powered off the machine manually started it up again and then performed another reboot and it came back up fine but figured it was worth checking. I've attached the diagnostics file in case you have the time to check it out! zoidberg-diagnostics-20241115-1010.zip
  4. I noticed an error in syslog below. Is there a way to fix this, or is it safe to ignore it? Nov 14 15:23:11 Zoidberg kernel: WARNING: CPU: 16 PID: 1419 at drivers/gpu/drm/drm_probe_helper.c:838 drm_kms_helper_poll_disable+0x49/0x51 [drm_kms_helper] Nov 14 15:23:11 Zoidberg kernel: Modules linked in: cmac cifs asn1_decoder cifs_arc4 cifs_md4 dns_resolver xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vhost_net tun vhost vhost_iotlb tap xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc e1000e r8169 realtek amdgpu edac_mce_amd edac_core intel_rapl_msr intel_rapl_common iosf_mbi gpu_sched drm_buddy video i2c_algo_bit drm_ttm_helper ttm kvm_amd drm_display_helper drm_kms_helper kvm drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 backlight aesni_intel agpgart crypto_simd cryptd wmi_bmof rapl i2c_piix4 syscopyarea nvme ahci sysfillrect i2c_core Nov 14 15:23:11 Zoidberg kernel: k10temp ccp sysimgblt libahci fb_sys_fops nvme_core wmi tpm_crb tpm_tis tpm_tis_core tpm button acpi_cpufreq unix [last unloaded: e1000e] Nov 14 15:23:11 Zoidberg kernel: CPU: 16 PID: 1419 Comm: kworker/16:2 Tainted: P W O 6.1.106-Unraid #1 Nov 14 15:23:11 Zoidberg kernel: Hardware name: System manufacturer System Product Name/PRIME X570-P, BIOS 5013 03/22/2024 Nov 14 15:23:11 Zoidberg kernel: Workqueue: pm pm_runtime_work Nov 14 15:23:11 Zoidberg kernel: RIP: 0010:drm_kms_helper_poll_disable+0x49/0x51 [drm_kms_helper] Nov 14 15:23:11 Zoidberg kernel: Code: 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 ad 5f cc df 48 c7 c1 ef c6 8e a1 48 89 da 48 c7 c7 1d c6 8e a1 48 89 c6 e8 e0 88 79 df <0f> 0b 5b e9 40 9e 32 e0 0f 1f 44 00 00 41 55 41 54 55 53 48 8b 2f Nov 14 15:23:11 Zoidberg kernel: RSP: 0018:ffffc90000cf7d48 EFLAGS: 00010282 Nov 14 15:23:11 Zoidberg kernel: RAX: 0000000000000000 RBX: ffff88810176e180 RCX: 0000000000000027 Nov 14 15:23:11 Zoidberg kernel: RDX: 0000000000000002 RSI: ffffffff820d99e1 RDI: 00000000ffffffff Nov 14 15:23:11 Zoidberg kernel: RBP: ffff8881074a0000 R08: 0000000000000000 R09: ffffc90000cf7c00 Nov 14 15:23:11 Zoidberg kernel: R10: 00003fffffffffff R11: 000000002d2d2d2d R12: 0000000000000000 Nov 14 15:23:11 Zoidberg kernel: R13: ffffffffa0cb9440 R14: 0000000000000000 R15: 0000000000000000 Nov 14 15:23:11 Zoidberg kernel: FS: 0000000000000000(0000) GS:ffff889faec00000(0000) knlGS:0000000000000000 Nov 14 15:23:11 Zoidberg kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 14 15:23:11 Zoidberg kernel: CR2: ffff9d0129299000 CR3: 00000002270c8000 CR4: 0000000000350ee0 Nov 14 15:23:11 Zoidberg kernel: Call Trace: Nov 14 15:23:11 Zoidberg kernel: <TASK> Nov 14 15:23:11 Zoidberg kernel: ? __warn+0xab/0x122 Nov 14 15:23:11 Zoidberg kernel: ? report_bug+0x109/0x17e Nov 14 15:23:11 Zoidberg kernel: ? drm_kms_helper_poll_disable+0x49/0x51 [drm_kms_helper] Nov 14 15:23:11 Zoidberg kernel: ? handle_bug+0x41/0x6f Nov 14 15:23:11 Zoidberg kernel: ? exc_invalid_op+0x13/0x60 Nov 14 15:23:11 Zoidberg kernel: ? asm_exc_invalid_op+0x16/0x20 Nov 14 15:23:11 Zoidberg kernel: ? drm_kms_helper_poll_disable+0x49/0x51 [drm_kms_helper] Nov 14 15:23:11 Zoidberg kernel: ? drm_kms_helper_poll_disable+0x49/0x51 [drm_kms_helper] Nov 14 15:23:11 Zoidberg kernel: amdgpu_device_suspend+0x72/0xfd [amdgpu] Nov 14 15:23:11 Zoidberg kernel: amdgpu_pmops_runtime_suspend+0xbb/0x165 [amdgpu] Nov 14 15:23:11 Zoidberg kernel: ? pci_pm_default_resume+0x23/0x23 Nov 14 15:23:11 Zoidberg kernel: pci_pm_runtime_suspend+0x6d/0x155 Nov 14 15:23:11 Zoidberg kernel: ? pci_pm_default_resume+0x23/0x23 Nov 14 15:23:11 Zoidberg kernel: ? pci_pm_default_resume+0x23/0x23 Nov 14 15:23:11 Zoidberg kernel: __rpm_callback+0xce/0x13a Nov 14 15:23:11 Zoidberg kernel: ? pci_pm_default_resume+0x23/0x23 Nov 14 15:23:11 Zoidberg kernel: rpm_callback+0x4b/0x64 Nov 14 15:23:11 Zoidberg kernel: ? pci_pm_default_resume+0x23/0x23 Nov 14 15:23:11 Zoidberg kernel: rpm_suspend+0x2ae/0x4a8 Nov 14 15:23:11 Zoidberg kernel: ? srso_return_thunk+0x5/0x10 Nov 14 15:23:11 Zoidberg kernel: ? finish_task_switch.isra.0+0x140/0x218 Nov 14 15:23:11 Zoidberg kernel: pm_runtime_work+0x75/0x7f Nov 14 15:23:11 Zoidberg kernel: process_one_work+0x1ab/0x295 Nov 14 15:23:11 Zoidberg kernel: worker_thread+0x18b/0x244 Nov 14 15:23:11 Zoidberg kernel: ? rescuer_thread+0x281/0x281 Nov 14 15:23:11 Zoidberg kernel: kthread+0xe7/0xef Nov 14 15:23:11 Zoidberg kernel: ? kthread_complete_and_exit+0x1b/0x1b Nov 14 15:23:11 Zoidberg kernel: ret_from_fork+0x22/0x30 Nov 14 15:23:11 Zoidberg kernel: </TASK> Nov 14 15:23:11 Zoidberg kernel: ---[ end trace 0000000000000000 ]---
  5. Hi I'm UK based, and have 2 x used 2TB Western Digital Red Hard drives I'd be happy to donate to someone for free, would just want postage fee covered (in GBP currency). Although I could post abroad, due to customs and import fees, its probably easier for someone to get in the UK. Cost within the UK for tracked delivery by Royal Mail Tracked 24 is approximately ~ GBP £6 (with signature). I can accept PayPal payment for the delivery fee The 2 drives are about 4-5 years old, but are in working order. Details below: Drive 1 2TB WD20EFAX, serial number: WXU2A106UC6R, Manufacture Date: 20 March 2020 Drive 2 2TB WD20EFRX, serial number: WCC4M2EKLPPV, Manufacture Date: 14 April 2019 Both drives have been formatted. I don't need them anymore as I upgraded my drives to 16TB Seagate Ironwolf NAS drives. Please let me know if you have any questions
  6. > Also, you do not have to erase the disks first as the procedure overwrites every sector on the drives anyway. What about the drives I am removing? How can I ensure they have no data from my unraid device still left on them?
  7. Hi, I currently have 2 x WD RED 4TB drives in use for my array. 1 of the drives is parity, the other is used solely for the array. Not withstanding the fact there is only one drive in the array (I'm fine with this, and dont have any additional space in the physical tower for additional 3.5" drives) could someone outline the steps to erase the existing array disks and replace them with 2 new Seagate IronWolf NAS 16TB drives - I intend to have the same 1 x parity disk, and 1 x array disk. Stretch-goal: If I can do it without having to delete the data on the 1 x disk that is used for the array then so much the better but its not essential as I can migrate the data if needed. I have downloaded the pre-clear unraid unassigned devices plugin, so assume I could use this to erase the disks Thanks in advance
  8. Hey, I've been using unraid on a tower PC/Server successfully that functions as perfectly well as a Hypervisor and a NAS for work purposes. I have a parity drive on it, a data drive and an SSD cache pool that host my VMs. My employer recently paid for an ASRock Intel DeskMini to act as a Hypervisor. Since it's a small form factor PC which only has 2 drives (1 X 2TB SSD and 1 X 2 TB normal HDD) my question is really is unraid suitable for this PC setup? I'd like to use it for more VMs for work, and I love the unraid experience, just not sure how I would set the drives up. I assume the non-SSD drive could act as parity? And the SSD as the only drive in the array? To be clear I understand having only 2 drives leaves me with hardware failure risks. I'm fine with that and can backup the VM disks etc to either my other unraid server or another NAS I have. I have seen Proxmox too but was interested if anyone has suggestions on using unraid with only 2 drives and any tips?
  9. I got an error when running 3 scripts over the course of an hour: 2020-10-26 09:00 Simultaneous execution is disabled, and a script is already running. Exiting. Each of the configs have simultaneous execution enabled (set to Yes) Is there something obvious I'm missing?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.