Everything posted by RomRedel
-
Log full
Hi, I just updated my unraid server to the version 6.10.0-rc3. Since then my /var/log is getting 100% full by one minute after boot. I just looked at the syslog and found this warning spamming over and over: Mar 11 08:24:01 Tower kernel: DMAR: ERROR: DMA PTE for vPFN 0xb5e3a already set (to b5e3a003 not 20d52d803) Mar 11 08:24:01 Tower kernel: ------------[ cut here ]------------ Mar 11 08:24:01 Tower kernel: WARNING: CPU: 0 PID: 101 at drivers/iommu/intel/iommu.c:2387 __domain_mapping+0x2e5/0x390 Mar 11 08:24:01 Tower kernel: Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap xt_nat xt_tcpudp veth xt_conntrack nf_conntrack_netlink nfnetlink xt_addrtype br_netfilter xfs md_mod drm backlight iptable_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 wireguard curve25519_x86_64 libcurve25519_generic libchacha20poly1305 chacha_x86_64 poly1305_x86_64 ip6_udp_tunnel udp_tunnel libblake2s blake2s_x86_64 libblake2s_generic libchacha ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding tg3 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ipmi_ssif i2c_core crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl intel_cstate intel_uncore acpi_ipmi ahci libahci ipmi_si thermal acpi_power_meter button [last unloaded: tg3] Mar 11 08:24:01 Tower kernel: CPU: 0 PID: 101 Comm: kworker/u128:1 Tainted: P W IO 5.15.27-Unraid #1 Mar 11 08:24:01 Tower kernel: Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 11/02/2015 Mar 11 08:24:01 Tower kernel: Workqueue: loop2 loop_workfn Mar 11 08:24:01 Tower kernel: RIP: 0010:__domain_mapping+0x2e5/0x390 Mar 11 08:24:01 Tower kernel: Code: 2b 48 8b 4c 24 08 48 89 c2 4c 89 e6 48 c7 c7 d4 c7 ef 81 e8 b7 95 2c 00 8b 05 de 3c c3 00 85 c0 74 08 ff c8 89 05 d2 3c c3 00 <0f> 0b 8b 74 24 38 b8 34 00 00 00 8d 0c f6 83 e9 09 39 c1 0f 4f c8 Mar 11 08:24:01 Tower kernel: RSP: 0018:ffffc9000055f3a8 EFLAGS: 00010046 Mar 11 08:24:01 Tower kernel: RAX: 0000000000000000 RBX: ffff88810775b1d0 RCX: 0000000000000027 Mar 11 08:24:01 Tower kernel: RDX: 0000000000000000 RSI: ffffc9000055f238 RDI: ffff888436e1c550 Mar 11 08:24:01 Tower kernel: RBP: ffff888107518000 R08: ffff888447f59470 R09: 0000000000000000 Mar 11 08:24:01 Tower kernel: R10: 0000000000000002 R11: ffff888447fd628e R12: 00000000000b5e3a Mar 11 08:24:01 Tower kernel: R13: ffff88810775b000 R14: 0000000000001000 R15: 00000000b5e00000 Mar 11 08:24:01 Tower kernel: FS: 0000000000000000(0000) GS:ffff888436e00000(0000) knlGS:0000000000000000 Mar 11 08:24:01 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 11 08:24:01 Tower kernel: CR2: 000014de38d3f024 CR3: 00000001b20b6005 CR4: 00000000001706f0 Mar 11 08:24:01 Tower kernel: Call Trace: Mar 11 08:24:01 Tower kernel: <TASK> Mar 11 08:24:01 Tower kernel: intel_iommu_map_pages+0xf3/0x102 Mar 11 08:24:01 Tower kernel: __iommu_map+0x138/0x211 Mar 11 08:24:01 Tower kernel: __iommu_map_sg+0x8c/0x110 Mar 11 08:24:01 Tower kernel: iommu_dma_map_sg+0x245/0x3e3 Mar 11 08:24:01 Tower kernel: __dma_map_sg_attrs+0x63/0x95 Mar 11 08:24:01 Tower kernel: dma_map_sg_attrs+0xa/0x12 Mar 11 08:24:01 Tower kernel: ata_qc_issue+0xec/0x1ab Mar 11 08:24:01 Tower kernel: __ata_scsi_queuecmd+0x1f2/0x1fd Mar 11 08:24:01 Tower kernel: ata_scsi_queuecmd+0x41/0x7a Mar 11 08:24:01 Tower kernel: scsi_queue_rq+0x57d/0x6db Mar 11 08:24:01 Tower kernel: blk_mq_dispatch_rq_list+0x2a7/0x4da Mar 11 08:24:01 Tower kernel: __blk_mq_do_dispatch_sched+0x23d/0x281 Mar 11 08:24:01 Tower kernel: ? setup_object.isra.0+0x18/0x4f Mar 11 08:24:01 Tower kernel: __blk_mq_sched_dispatch_requests+0xd5/0x129 Mar 11 08:24:01 Tower kernel: blk_mq_sched_dispatch_requests+0x2f/0x52 Mar 11 08:24:01 Tower kernel: __blk_mq_run_hw_queue+0x50/0x76 Mar 11 08:24:01 Tower kernel: __blk_mq_delay_run_hw_queue+0x4d/0x108 Mar 11 08:24:01 Tower kernel: blk_mq_sched_insert_requests+0xa2/0xd9 Mar 11 08:24:01 Tower kernel: blk_mq_flush_plug_list+0xfb/0x12c Mar 11 08:24:01 Tower kernel: blk_mq_submit_bio+0x2e6/0x406 Mar 11 08:24:01 Tower kernel: submit_bio_noacct+0x9d/0x203 Mar 11 08:24:01 Tower kernel: ? blkg_tryget+0x22/0x55 Mar 11 08:24:01 Tower kernel: ? bio_associate_blkg_from_css+0x11f/0x169 Mar 11 08:24:01 Tower kernel: btrfs_map_bio+0x2e7/0x31f Mar 11 08:24:01 Tower kernel: btrfs_submit_direct+0x3b5/0x42e Mar 11 08:24:01 Tower kernel: iomap_dio_submit_bio+0x66/0x75 Mar 11 08:24:01 Tower kernel: iomap_dio_bio_iter+0x306/0x373 Mar 11 08:24:01 Tower kernel: __iomap_dio_rw+0x309/0x61b Mar 11 08:24:01 Tower kernel: iomap_dio_rw+0xa/0x25 Mar 11 08:24:01 Tower kernel: btrfs_file_read_iter+0xb9/0x10a Mar 11 08:24:01 Tower kernel: lo_rw_aio.isra.0+0x1e7/0x234 Mar 11 08:24:01 Tower kernel: loop_process_work+0x58e/0x7f4 Mar 11 08:24:01 Tower kernel: ? __raw_spin_unlock+0x5/0x6 Mar 11 08:24:01 Tower kernel: ? finish_task_switch.isra.0+0x12f/0x207 Mar 11 08:24:01 Tower kernel: process_one_work+0x198/0x27a Mar 11 08:24:01 Tower kernel: worker_thread+0x19c/0x240 Mar 11 08:24:01 Tower kernel: ? rescuer_thread+0x28b/0x28b Mar 11 08:24:01 Tower kernel: kthread+0xde/0xe3 Mar 11 08:24:01 Tower kernel: ? set_kthread_struct+0x32/0x32 Mar 11 08:24:01 Tower kernel: ret_from_fork+0x22/0x30 Mar 11 08:24:01 Tower kernel: </TASK> Mar 11 08:24:01 Tower kernel: ---[ end trace b215edd86a51fffe ]--- I can't figured it out what to do with that. Is there someone who understand this warning that can help me ? Thank's RomRedel tower-diagnostics-20220311-0827.zip
-
Add a 2 new drives as data and parity
Hi, I have an array with 2 drives, 2To each. 1 as data drive and one as parity. I would like to extend my server by adding 2 new 4To drives 1 as parity and the other as data drive. So 1x2To + 1x 4To as parity and the same as data. But when I'm trying to add the data drive unraid says the parity drive is too small. I tried to swap the 4To drives but, same problem. Any idea of what could be the problem?