jmshrtn

Thanks @JorgeB

Hi folks. This morning I started seeing these errors in my logs: Mar 1 16:32:39 Arthur kernel: btrfs_print_data_csum_error: 102 callbacks suppressed Mar 1 16:32:39 Arthur kernel: BTRFS warning (device nvme0n1p1): csum failed root 5 ino 19531461 off 512389120 csum 0x8941f998 expected csum 0x7d7fa01c mirror 2 Mar 1 16:32:39 Arthur kernel: btrfs_dev_stat_inc_and_print: 102 callbacks suppressed Mar 1 16:32:39 Arthur kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 69890, rd 10037, flush 3987, corrupt 17789, gen 0 Mar 1 16:32:39 Arthur kernel: repair_io_failure: 102 callbacks suppressed Mar 1 16:32:39 Arthur kernel: BTRFS info (device nvme0n1p1): read error corrected: ino 19531461 off 512389120 (dev /dev/nvme0n1p1 sector 1959275848) The output of `btrfs dev stats /mnt/cache` is: [/dev/nvme0n1p1].write_io_errs 69890 [/dev/nvme0n1p1].read_io_errs 10037 [/dev/nvme0n1p1].flush_io_errs 3987 [/dev/nvme0n1p1].corruption_errs 17911 [/dev/nvme0n1p1].generation_errs 0 [/dev/nvme1n1p1].write_io_errs 0 [/dev/nvme1n1p1].read_io_errs 0 [/dev/nvme1n1p1].flush_io_errs 0 [/dev/nvme1n1p1].corruption_errs 0 [/dev/nvme1n1p1].generation_errs 0 However the UI shows no errors or alerts. I have ordered a new SSD to replace the obviously failing one but I think this must be a bug that it's not detected my unraid.

Hi folks. I have a machine running unRAID 6.12.6 with a 9 device array with a single parity. The machine isn't terribly fast (i7-3770, 32GB of DDR3 and only PCIe 3.0 slots) but has enough IO to do the job for me. The motherboard (Intel Q77 based) has three SATA3 6Gbps connectors, and 2 SATA 3 3Gbps connectors, and I am using an LSI SAS2008 HBA to connect 8 drives (including the parity) and one of the on-board 6Gbps ports to connect the ninth. I'm wondering if I should leave the parity drive connected to the HBA (on the assumption that it performs better than the on-board controllers) or connect it to the on-board controller (on the assumption that there is not enough bandwidth in and out of the HBA). Does anyone have any reckons?

Thanks, will do.

Hi folks. When I got up this morning my unraid box was unresponsive on the network and plugging in a keyboard and monitor was ineffective, so I was forced to power cycle it (not something I'm that keen on doing too often). Can anyone give me some pointers of where to look to figure out why? Diagnostics attached.

I have a similar backtrace on my configuration also: Jul 18 09:36:01 Arthur kernel: ------------[ cut here ]------------ Jul 18 09:36:01 Arthur kernel: WARNING: CPU: 0 PID: 437 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 18 09:36:01 Arthur kernel: Modules linked in: udp_diag veth xt_nat xt_tcpudp macvlan xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs md_mod tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet 8021q garp mrp bridge stp llc bonding tls zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) intel_rapl_msr mei_hdcp mei_pxp wmi_bmof i915 intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 drm_kms_helper aesni_intel btusb btrtl btbcm btintel crypto_simd cryptd rapl intel_cstate e1000e intel_uncore drm bluetooth i2c_i801 i2c_smbus nvme mei_me intel_gtt video ecdh_generic ahci agpgart nvme_core i2c_core ecc mei intel_pch_thermal syscopyarea sysfillrect Jul 18 09:36:01 Arthur kernel: libahci sysimgblt fb_sys_fops thermal fan wmi backlight intel_pmc_core acpi_pad button unix Jul 18 09:36:01 Arthur kernel: CPU: 0 PID: 437 Comm: kworker/u12:6 Tainted: P O 6.1.38-Unraid #2 Jul 18 09:36:01 Arthur kernel: Hardware name: ASUSTeK COMPUTER INC. VC65-C1/VC65-C1, BIOS 0602 08/09/2018 Jul 18 09:36:01 Arthur kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan] Jul 18 09:36:01 Arthur kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 18 09:36:01 Arthur kernel: Code: 44 24 10 e8 e2 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 7e e6 ff ff 84 c0 75 a2 48 89 df e8 9b e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 18 dd ff ff e8 93 e3 ff ff e9 72 01 Jul 18 09:36:01 Arthur kernel: RSP: 0018:ffffc90000003d98 EFLAGS: 00010202 Jul 18 09:36:01 Arthur kernel: RAX: 0000000000000001 RBX: ffff8882138e9600 RCX: d35ba3b4373dc17c Jul 18 09:36:01 Arthur kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8882138e9600 Jul 18 09:36:01 Arthur kernel: RBP: 0000000000000001 R08: 87ace0eed9699699 R09: 175ed443f1bc65da Jul 18 09:36:01 Arthur kernel: R10: d490a8eaa63e3d03 R11: ffffc90000003d60 R12: ffffffff82a11d00 Jul 18 09:36:01 Arthur kernel: R13: 0000000000025735 R14: ffff8881035c9800 R15: 0000000000000000 Jul 18 09:36:01 Arthur kernel: FS: 0000000000000000(0000) GS:ffff88845dc00000(0000) knlGS:0000000000000000 Jul 18 09:36:01 Arthur kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 18 09:36:01 Arthur kernel: CR2: 000014e8890eeca0 CR3: 000000036e9b4002 CR4: 00000000003706f0 Jul 18 09:36:01 Arthur kernel: Call Trace: Jul 18 09:36:01 Arthur kernel: <IRQ> Jul 18 09:36:01 Arthur kernel: ? __warn+0xab/0x122 Jul 18 09:36:01 Arthur kernel: ? report_bug+0x109/0x17e Jul 18 09:36:01 Arthur kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 18 09:36:01 Arthur kernel: ? handle_bug+0x41/0x6f Jul 18 09:36:01 Arthur kernel: ? exc_invalid_op+0x13/0x60 Jul 18 09:36:01 Arthur kernel: ? asm_exc_invalid_op+0x16/0x20 Jul 18 09:36:01 Arthur kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack] Jul 18 09:36:01 Arthur kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack] Jul 18 09:36:01 Arthur kernel: ? nf_nat_inet_fn+0x60/0x1a8 [nf_nat] Jul 18 09:36:01 Arthur kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Jul 18 09:36:01 Arthur kernel: nf_hook_slow+0x3a/0x96 Jul 18 09:36:01 Arthur kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Jul 18 09:36:01 Arthur kernel: NF_HOOK.constprop.0+0x79/0xd9 Jul 18 09:36:01 Arthur kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Jul 18 09:36:01 Arthur kernel: __netif_receive_skb_one_core+0x77/0x9c Jul 18 09:36:01 Arthur kernel: process_backlog+0x8c/0x116 Jul 18 09:36:01 Arthur kernel: __napi_poll.constprop.0+0x28/0x124 Jul 18 09:36:01 Arthur kernel: net_rx_action+0x159/0x24f Jul 18 09:36:01 Arthur kernel: __do_softirq+0x126/0x288 Jul 18 09:36:01 Arthur kernel: do_softirq+0x7f/0xab Jul 18 09:36:01 Arthur kernel: </IRQ> Jul 18 09:36:01 Arthur kernel: <TASK> Jul 18 09:36:01 Arthur kernel: __local_bh_enable_ip+0x4c/0x6b Jul 18 09:36:01 Arthur kernel: netif_rx+0x52/0x5a Jul 18 09:36:01 Arthur kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Jul 18 09:36:01 Arthur kernel: ? _raw_spin_unlock+0x14/0x29 Jul 18 09:36:01 Arthur kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Jul 18 09:36:01 Arthur kernel: process_one_work+0x1a8/0x295 Jul 18 09:36:01 Arthur kernel: worker_thread+0x18b/0x244 Jul 18 09:36:01 Arthur kernel: ? rescuer_thread+0x281/0x281 Jul 18 09:36:01 Arthur kernel: kthread+0xe4/0xef Jul 18 09:36:01 Arthur kernel: ? kthread_complete_and_exit+0x1b/0x1b Jul 18 09:36:01 Arthur kernel: ret_from_fork+0x1f/0x30 Jul 18 09:36:01 Arthur kernel: </TASK> Jul 18 09:36:01 Arthur kernel: ---[ end trace 0000000000000000 ]--- I have a bunch of docker containers running in a separate VLAN from the main system, so I am using macvlan to support that.

Nope. The old one no longer boots

Hi there. My old USB drive started to fail, so I swapped it but I am getting an error when trying to replace the key. I guess in the mean time I'll put the dodgy one back in.

Yeah. I realise that they’re not recommended but needs must. Out of interest - why is it not possible for unraid to use the Linux block device UUID to identify drives?

Nevermind. I found the "New config" option in tools. Thanks anyway!

Hi folks. I have a home build which uses one of these 8 bay USB enclosures from Orico. I bought three new 8TB drives and stuffed the remaining ports full of whatever I had lying around. It's been running fine for several months. I decided to pull one of the older 1TB drives (it is empty anyway) to make room for adding a second parity drive (soon - I haven't ordered it yet) however it appears that the device ID's are based on the order that they're iterated and not the slot that they're in (which is annoying in and of itself). Is there any way to start the array having removed Disk 6 and pointed Disk 7 at the same device but with now a different device ID? To be clear, Disk 7 is in the same physical slot as before - I simply removed the drive from the slot next to it. In the mean time I'll put the 1TB drive back in the enclosure so that I can start the array. Thanks!