aniel

so u dont know a ETA and/or u just joking around?

when are we getting 6.13/ multi array support?

ok

i just need to see how this pools work because i have a feeling am gonna be disappointed in the end

when can i play around with this new version?

and why would i want unprotected pools ? that defeats the purpose of unraid or any sw raid for that matter.

so we are back to square 1. we cant go above 30+ devices in the main array which is the issue here.

am reading it but i cant comprehend how parity will work and/or if we are going to be able to go above 30+ hdds if we ever have that need

btrfs by itself cant protect u if there is not a hdd parity for it. so to make sure we are on the same page is unraid going to support 30+ hdds and/or multiple arrays?

so u can create pool with no data protection ?

i agree, and they fact that pp are requesting this on their "next version" release post gives you something to talk about.

xpenlogy wich is what am using right now supports unlimited hdds (aside from from the official limits/ and i havent test this)

so it ended up being a windows issue (most likely some kind of driver interference). after uninstalling a couple of sw that i had some suspicion, running a "windows repair tool" issue went away but after notice some performance loss i decided to go back to using two boxes. thank u to all of those that provided support and my apologies for pming some of you and getting frustrated for an "end user error" situation.

for the look of it they dont want to support 30+ drives

are we getting multi array option with this update ?

understood

ok thanks i will give that a try

ahh ok

that is what i meant, skip the checking when the disks is added. i as a user should have that option.

is it possible to add an option to skip pre check/ clear when adding new disks to the array ?

i agreed

I as the end user should decide and determine what is best for me.

more info (btw idk how to print): tower-syslog-20230104-2230.zip /sys/bus/pci/devices/0000:04:00.0/iommu_group/devices/0000:04:00.0 Binding... Successfully bound the device 1000:0072 at 0000:04:00.0 to vfio-pci --- Processing 0000:07:00.3 1022:149c Vendor:Device 1022:149c found at 0000:07:00.3 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:07:00.3/iommu_group/devices/0000:07:00.3 Binding... Unbound 0000:07:00.3 from xhci_hcd Successfully bound the device 1022:149c at 0000:07:00.3 to vfio-pci --- Processing 0000:08:00.0 1022:7901 Vendor:Device 1022:7901 found at 0000:08:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:08:00.0/iommu_group/devices/0000:08:00.0 Binding... Successfully bound the device 1022:7901 at 0000:08:00.0 to vfio-pci --- Processing 0000:09:00.0 1022:7901 Vendor:Device 1022:7901 found at 0000:09:00.0 IOMMU group members (sans bridges): /sys/bus/pci/devices/0000:09:00.0/iommu_group/devices/0000:09:00.0 Binding... Successfully bound the device 1022:7901 at 0000:09:00.0 to vfio-pci --- vfio-pci binding complete Devices listed in /sys/bus/pci/drivers/vfio-pci: lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:03:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:01.0/0000:03:00.0 lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:04:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:02.0/0000:04:00.0 lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:07:00.3 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:07:00.3 lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:08:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:09.0/0000:08:00.0 lrwxrwxrwx 1 root root 0 Jan 4 22:22 0000:09:00.0 -> ../../../../devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:0a.0/0000:09:00.0

please check your discord

yes