bitphire

Seems I had fixed it and did not even know it since docker and vms were turned off ><

I'm in Settings -> Network Settings. for eth0 IPv4 default gateway is set. eth1 has same gateway as etho but is inactive, eth2 and eth3 are inactive with no gateway listed. Interface Extra br0 br1 are Current listening interfaces, include listening interface virbr0. Interface Rules just shows eth0-3 mac addresses. Routing table, see screenshot link in previous post. I see at the bottom "Interface - Ethernet Port 1 is down. Check cable!" however, I only have 1 ethernet cable going to the server and it's on eth0. I believe wireguard setup the eth1. I just don't know why my internet settings were changed during the upgrade. It's been working for a couple of years now with no issues. ifconfig: 192.168.1.8 is the static ip of the server. 192.168.1.254 is the router/gateway. bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500 ether 24:6e:96:1d:4d:64 txqueuelen 1000 (Ethernet) RX packets 868292 bytes 83284768 (79.4 MiB) RX errors 0 dropped 30642 overruns 0 frame 0 TX packets 116332 bytes 88937151 (84.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.8 netmask 255.255.255.0 broadcast 0.0.0.0 ether 24:6e:96:1d:4d:64 txqueuelen 1000 (Ethernet) RX packets 836716 bytes 69457429 (66.2 MiB) RX errors 0 dropped 3327 overruns 0 frame 0 TX packets 69795 bytes 86384026 (82.3 MiB) TX errors 0 dropped 2 overruns 0 carrier 0 collisions 0 br-1851d5d79b78: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.21.0.1 netmask 255.255.0.0 broadcast 172.21.255.255 inet6 fe80::42:4aff:feb1:9570 prefixlen 64 scopeid 0x20<link> ether 02:42:4a:b1:95:70 txqueuelen 0 (Ethernet) RX packets 199 bytes 11906 (11.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 404 bytes 125001 (122.0 KiB) TX errors 0 dropped 56 overruns 0 carrier 0 collisions 0 br-7092b668af83: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.20.0.1 netmask 255.255.0.0 broadcast 172.20.255.255 ether 02:42:23:dd:4d:54 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 295 overruns 0 carrier 0 collisions 0 br-859cc085c417: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.19.0.1 netmask 255.255.0.0 broadcast 172.19.255.255 inet6 fe80::42:9eff:fe66:20bd prefixlen 64 scopeid 0x20<link> ether 02:42:9e:66:20:bd txqueuelen 0 (Ethernet) RX packets 7725 bytes 1069677 (1.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3494 bytes 573148 (559.7 KiB) TX errors 0 dropped 127 overruns 0 carrier 0 collisions 0 br-b70b924d0f34: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.31.200.1 netmask 255.255.255.0 broadcast 172.31.200.255 ether 02:42:62:51:26:96 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 295 overruns 0 carrier 0 collisions 0 br-c4e2ba15c192: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.31.201.1 netmask 255.255.255.0 broadcast 172.31.201.255 ether 02:42:3c:90:ba:6a txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 287 overruns 0 carrier 0 collisions 0 br-ed301ccddf5b: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255 ether 02:42:4b:13:4d:61 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 278 overruns 0 carrier 0 collisions 0 eth0: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 24:6e:96:1d:4d:64 txqueuelen 1000 (Ethernet) RX packets 868292 bytes 83284768 (79.4 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 116332 bytes 88937151 (84.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device memory 0xda680000-da6fffff eth1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 24:6e:96:1d:4d:65 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 22 overruns 0 carrier 0 collisions 0 device memory 0xda700000-da77ffff lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 3522 bytes 381900 (372.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3522 bytes 381900 (372.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vhost1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 02:15:b9:0d:da:81 txqueuelen 500 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

I am a beginner in a lot of this but after turning off VMs, Docker, and Wireguard I have this and still not working. Is there somewhere else I am supposed to make the change? Network Settings - Routing Table

Upgrade to 7.2.1 from 7.0. Everything seemed to go smooth. Server just sat doing it's thing until I wanted to watch a show on my Emby. Normal I access it with a domain with rever proxy and all that. Has worked for over a year no issues. Could not access it. Tried to just run it with the local ip to the docker and worked fine. Jumped on server and noticed that APPS can't access the WWW either. It is looking like Everything works fine locally but the server itself can't access outside. Fiber Modem/Router (AT&T) - Ethernet to Server. I use Cloudflare/Reverse Proxy to access my services. Again, haven't had any issues until after upgrading. I turned off Docker and VMs to see if it would make a difference; nothing. Attached is Diag. I am not sure where to go from here on fixing this issue beside maybe downgrading back to 7.0. cuddles-diagnostics-20251206-0043.zip

I ran sg_format --format --fmtpinfo=0 /dev/sdX on all 3 new drives and still had same issues. They are seagate drives and I read about SED drives but have no way of mounting sas on my Windows machine at the momment to use SeaTools and see if they are protected that way. I cannot find where you see they are write protected either, just wanted to know where so if I order future drives from this location I know what to look for. However, I did move the drives physically to another bay and got 2 out of 3 to format. Got one to mount and is now parity and seems to be fine. The 2nd drive I added to the array and it shows 1025 errors and never cleared. The 3rd drive no change. attached another diagnostics from this morning. Drives: sde (New Parity and seems to be working fine), sdf (new disk in array but not working and shows 1025 errors on MAIN page), sdg (Has a button to format but fails every time). cuddles-diagnostics-20230408-0925.zip

Here you go! Thank you cuddles-diagnostics-20230405-0820.zip

Hello! I purchased 3 drives that are larger than my parity. I want to make current parity a data disk and one of the new disks parity then add the other 2 new disks as data disks as well. I tried Stopping Array and swapping the parity with one of the larger disks thinking it would then rebuild but it does not. Under "Unassigned Devices" I show all 3 new drives and they say "Format" but that fails every time on all drives. Log: Apr 4 18:24:52 Cuddles unassigned.devices: Format device '/dev/sdg'. Apr 4 18:24:52 Cuddles unassigned.devices: Device '/dev/sdg' block size: 11721045168. Apr 4 18:24:52 Cuddles unassigned.devices: Clearing partition table of disk '/dev/sdg'. Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#910 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#910 Sense Key : 0x4 [current] [descriptor] Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#910 <<vendor>>ASC=0x81 ASCQ=0x0 Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#910 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 00 00 00 00 04 00 00 00 Apr 4 18:24:52 Cuddles kernel: critical target error, dev sdg, sector 0 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0 Apr 4 18:24:52 Cuddles kernel: buffer_io_error: 523 callbacks suppressed Apr 4 18:24:52 Cuddles kernel: Buffer I/O error on dev sdg, logical block 0, lost async page write Apr 4 18:24:52 Cuddles kernel: Buffer I/O error on dev sdg, logical block 1, lost async page write Apr 4 18:24:52 Cuddles kernel: Buffer I/O error on dev sdg, logical block 2, lost async page write Apr 4 18:24:52 Cuddles kernel: Buffer I/O error on dev sdg, logical block 3, lost async page write Apr 4 18:24:52 Cuddles kernel: Buffer I/O error on dev sdg, logical block 4, lost async page write Apr 4 18:24:52 Cuddles kernel: Buffer I/O error on dev sdg, logical block 5, lost async page write Apr 4 18:24:52 Cuddles kernel: Buffer I/O error on dev sdg, logical block 6, lost async page write Apr 4 18:24:52 Cuddles kernel: Buffer I/O error on dev sdg, logical block 7, lost async page write Apr 4 18:24:52 Cuddles kernel: Buffer I/O error on dev sdg, logical block 8, lost async page write Apr 4 18:24:52 Cuddles kernel: Buffer I/O error on dev sdg, logical block 9, lost async page write Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#911 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#911 Sense Key : 0x4 [current] [descriptor] Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#911 <<vendor>>ASC=0x81 ASCQ=0x0 Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#911 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 04 00 00 00 04 00 00 00 Apr 4 18:24:52 Cuddles kernel: critical target error, dev sdg, sector 1024 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0 Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#912 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#912 Sense Key : 0x4 [current] [descriptor] Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#912 <<vendor>>ASC=0x81 ASCQ=0x0 Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#912 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 08 00 00 00 04 00 00 00 Apr 4 18:24:52 Cuddles kernel: critical target error, dev sdg, sector 2048 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0 Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#913 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#913 Sense Key : 0x4 [current] [descriptor] Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#913 <<vendor>>ASC=0x81 ASCQ=0x0 Apr 4 18:24:52 Cuddles kernel: sd 3:0:3:0: [sdg] tag#913 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 0c 00 00 00 04 00 00 00 Apr 4 18:24:52 Cuddles kernel: critical target error, dev sdg, sector 3072 op 0x1:(WRITE) flags 0x800 phys_seg 128 prio class 0 Apr 4 18:24:52 Cuddles unassigned.devices: Clear partition result: 1+0 records in 1+0 records out 2097152 bytes (2.1 MB, 2.0 MiB) copied, 0.332216 s, 6.3 MB/s Apr 4 18:24:54 Cuddles unassigned.devices: Reloading disk '/dev/sdg' partition table. Apr 4 18:24:54 Cuddles unassigned.devices: Reload partition table result: /dev/sdg: re-reading partition table Apr 4 18:24:54 Cuddles unassigned.devices: Creating Unraid compatible gpt partition on disk '/dev/sdg'. Apr 4 18:24:54 Cuddles kernel: sd 3:0:3:0: [sdg] tag#2401 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 4 18:24:54 Cuddles kernel: sd 3:0:3:0: [sdg] tag#2401 Sense Key : 0x4 [current] [descriptor] Apr 4 18:24:54 Cuddles kernel: sd 3:0:3:0: [sdg] tag#2401 <<vendor>>ASC=0x81 ASCQ=0x0 Apr 4 18:24:54 Cuddles kernel: sd 3:0:3:0: [sdg] tag#2401 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 00 00 00 00 00 28 00 00 Apr 4 18:24:54 Cuddles kernel: critical target error, dev sdg, sector 0 op 0x1:(WRITE) flags 0x0 phys_seg 5 prio class 0 Apr 4 18:24:54 Cuddles kernel: sd 3:0:3:0: [sdg] tag#2400 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 4 18:24:54 Cuddles kernel: sd 3:0:3:0: [sdg] tag#2400 Sense Key : 0x4 [current] [descriptor] Apr 4 18:24:54 Cuddles kernel: sd 3:0:3:0: [sdg] tag#2400 <<vendor>>ASC=0x81 ASCQ=0x0 Apr 4 18:24:54 Cuddles kernel: sd 3:0:3:0: [sdg] tag#2400 CDB: opcode=0x8a 8a 00 00 00 00 02 ba a0 f4 88 00 00 00 28 00 00 Apr 4 18:24:54 Cuddles kernel: critical target error, dev sdg, sector 11721045128 op 0x1:(WRITE) flags 0x0 phys_seg 5 prio class 0 Apr 4 18:24:55 Cuddles kernel: sd 3:0:3:0: [sdg] tag#2008 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 4 18:24:55 Cuddles kernel: sd 3:0:3:0: [sdg] tag#2008 Sense Key : 0x4 [current] [descriptor] Apr 4 18:24:55 Cuddles kernel: sd 3:0:3:0: [sdg] tag#2008 <<vendor>>ASC=0x81 ASCQ=0x0 Apr 4 18:24:55 Cuddles kernel: sd 3:0:3:0: [sdg] tag#2008 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Apr 4 18:24:55 Cuddles kernel: critical target error, dev sdg, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Apr 4 18:24:56 Cuddles kernel: sd 3:0:3:0: [sdg] tag#540 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 4 18:24:56 Cuddles kernel: sd 3:0:3:0: [sdg] tag#540 Sense Key : 0x4 [current] [descriptor] Apr 4 18:24:56 Cuddles kernel: sd 3:0:3:0: [sdg] tag#540 <<vendor>>ASC=0x81 ASCQ=0x0 Apr 4 18:24:56 Cuddles kernel: sd 3:0:3:0: [sdg] tag#540 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 00 00 00 00 00 28 00 00 Apr 4 18:24:56 Cuddles kernel: critical target error, dev sdg, sector 0 op 0x1:(WRITE) flags 0x0 phys_seg 5 prio class 0 Apr 4 18:24:56 Cuddles kernel: sd 3:0:3:0: [sdg] tag#539 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 4 18:24:56 Cuddles kernel: sd 3:0:3:0: [sdg] tag#539 Sense Key : 0x4 [current] [descriptor] Apr 4 18:24:56 Cuddles kernel: sd 3:0:3:0: [sdg] tag#539 <<vendor>>ASC=0x81 ASCQ=0x0 Apr 4 18:24:56 Cuddles kernel: sd 3:0:3:0: [sdg] tag#539 CDB: opcode=0x8a 8a 00 00 00 00 02 ba a0 f4 88 00 00 00 28 00 00 Apr 4 18:24:56 Cuddles kernel: critical target error, dev sdg, sector 11721045128 op 0x1:(WRITE) flags 0x0 phys_seg 5 prio class 0 Apr 4 18:24:57 Cuddles unassigned.devices: Create gpt partition table result: Creating new GPT entries in memory. The operation has completed successfully. Apr 4 18:24:59 Cuddles unassigned.devices: Reloading disk '/dev/sdg' partition table. Apr 4 18:24:59 Cuddles unassigned.devices: Reload partition table result: /dev/sdg: re-reading partition table Apr 4 18:24:59 Cuddles unassigned.devices: Formatting disk '/dev/sdg' with 'xfs' filesystem. Apr 4 18:24:59 Cuddles unassigned.devices: Format drive command: /sbin/mkfs.xfs -f '/dev/sdg1' 2>&1 Apr 4 18:25:00 Cuddles unassigned.devices: Format disk '/dev/sdg' with 'zfs' filesystem failed: Error accessing specified device /dev/sdg1: No such file or directory Usage: mkfs.xfs /* blocksize */#011#011[-b size=num] /* config file */#011[-c options=xxx] /* metadata */#011#011[-m crc=0|1,finobt=0|1,uuid=xxx,rmapbt=0|1,reflink=0|1, #011#011#011 inobtcount=0|1,bigtime=0|1] /* data subvol */#011[-d agcount=n,agsize=n,file,name=xxx,size=num, #011#011#011 (sunit=value,swidth=value|su=num,sw=num|noalign), #011#011#011 sectsize=num /* force overwrite */#011[-f] /* inode size */#011[-i perblock=n|size=num,maxpct=n,attr=0|1|2, #011#011#011 projid32bit=0|1,sparse=0|1] /* no discard */#011[-K] /* log subvol */#011[-l agnum=n,internal,size=num,logdev=xxx,version=n #011#011#011 sunit=value|su=num,sectsize=num,lazy-count=0|1] /* label */#011#011[-L label (maximum 12 characters)] /* naming */#011#011[-n size=num,version=2|ci,ftype=0|1] /* no-op info only */#011[-N] /* prototype file */#011[-p fname] /* quiet */#011#011[-q] /* realtime subvol */#011[-r extsize=num,size=num,rtdev=xxx] /* sectorsize */#011[-s size=num] /* version */#011#011[-V] #011#011#011devicename <d

Hello all, Unraid 6.11.5 VM: Ubuntu 22.04 I tried to follow SpaceInvader's Tutorial however I am getting: After connecting the vdisk image using: qemu-nbd --format=raw --connect=/dev/nbd0 /mnt/user/domains/Ubuntu-Web22.04/vdisk1.img I run fdisk /dev/nbd0 -l Result fdisk: cannot open /dev/nbd0: Input/output error That tutorial is fairly old so was wondering if there is another way to accomplish this?

I setup unraid on my current PC and recently purchased an older PowerEdge R720XD server. Is there a guide or best way to move everything over to the new server without losing data? My only 2 externals are setup as a pool with all my media on it at the moment and I rather not have to redownload everything. From what I understand, all individual files are stored completly on a single hard drive in the raid and not split across multiple drives. I am hoping that if I move all the hard drive's over minus my nvme drive that in theory it should just work. I will find a way to back up any files that I really don't want to lose before I do anything but just curious if this is would work or should I just get another copy of UnRaid and setup the new server then transfer the files over? Thanks for any advice.

Thank you for the response. I bought the H310 as it is already flashed and vendor claimed the 710 wasn’t the best to flash. I’m not too concerned on power consumption yet. The noise I am hoping to solve by replacing fans with quieter ones if needed. My work area is pretty secluded from where people hangout though. Rack, rails, pfsense router/firewall, 310 card, and server should all hopefully be here by Friday. This will be my first “real server”. I’m sure I’ll be back with more beginner questions.

Just wanted to add that I also purchased a Dell H310 mini monolithic K09CJ with LSI 9211-8i P20 IT Mode ZFS FreeNAS unRAID off of EBay after vendor recommendation.

Greetings, I just ordered a Dell PowerEdge R720XD Server | 2x E5-2680v2 2.8Ghz 20 Cores | 128GB | H710 | 2x 3TB SAS . I currently have UnRaid running on what was my gaming rig. I would like to have my gaming rig back for gaming. (For the most part the Windows 10 VM games OK). I assume this is way overkill but seemed like a good price compared to what I was looking at spending to build another machine. This UnRaid is currently running Emby/Radarr/Sonarr ect, Windows 10 VM, and Ubuntu Server 22.04 VM. I would like to move everything except the Windows 10 VM over to this new server if possible. Just wondering if these type of servers have any know issues or are even supported by UnRaid.

For now I have it working with DuckDNS and Swag with my own domain. Not 100% if this is the way to go for the webserver when I get that going but for now this gets my media back up and going for me.

Hello, I have 5 static ip's from my ISP that face the outside world. I don't want to use a service like no-ip anymore if I can help it. At the moment everything is set as DHCP with 192.168.1.xxx addresses. Eventually I would like: EmbyServer - Public/WAN Static IP (108.xxx.xxx.xxx) Webserver - Public/WAN Static IP (108.xxx.xxx.xxx) (and use vhosts for different sites I host, my ISP allows webservers) I don't think I can assign the 108 addresses to these containers while the server is set to dhcp with 192.168.1.xxx address. I plan on having more than 5 dockers and vm's and not sure how they will get an ip address since I only have access to 5 and they are all public. Server has 2 onboard NICs gigabit (active-backup for now). They are currently both connected to the ISP supplied modem/router. I have 0 extra PCI ports on my server (it's a mini-itx with only one for a gpu). I was going to try pfSense but not sure it's possible with what I have. I am fairly new to all this so if you explain something just pretend I have no clue because I most likely don't. Edit: Looking into Wireguard as a possible solution.

Hello All, Just install Unraid this morning and it's just about done with parity sync. I have the official EmbyServer docker installed and I can access it. On Windows 10, I had my 8TB and 12TB external drives made to look as one 20TB drive. I was having issues with Radarr not being able to monitor both drives and it kept downloading duplicate files and this was the solution I found that worked great. I am not concerned about data loss on these. Question: Is it possible to have them appear as one single drive to multiple dockers? (EmbyServer, Radarr, Sonarr, Lidar, ect...)