SGAShepp

Just putting in my request for this feature too. By default, the ONLY way to do this is to set specific disks for shares, but it's extremely limiting and depends on the size\amount of disks

Hey guys, odd issue here, searched the forums didn't find this. When I go to start any VM, windows, or linux, it will look like its starting, and the monitor will even wake from sleep, but then nothing happens. I then have to force stop the VM, then start it again. The second time it always works. Not sure it's related to the issue but this is what the log looks like. -device '{"driver":"vfio-pci","host":"0000:01:00.0","id":"hostdev0","bus":"pci.0","addr":"0x6"}' \ -device '{"driver":"vfio-pci","host":"0000:01:00.1","id":"hostdev1","bus":"pci.0","addr":"0x8"}' \ -device '{"driver":"vfio-pci","host":"0000:0a:00.0","id":"hostdev2","bootindex":1,"bus":"pci.0","addr":"0x9"}' \ -device '{"driver":"usb-host","hostdevice":"/dev/bus/usb/001/005","id":"hostdev3","bus":"usb.0","port":"1"}' \ -device '{"driver":"usb-host","hostdevice":"/dev/bus/usb/001/006","id":"hostdev4","bus":"usb.0","port":"2"}' \ -device '{"driver":"usb-host","hostdevice":"/dev/bus/usb/001/011","id":"hostdev5","bus":"usb.0","port":"3"}' \ -device '{"driver":"usb-host","hostdevice":"/dev/bus/usb/001/002","id":"hostdev6","bus":"usb.0","port":"4"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) 2023-07-17T00:20:00.898201Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:00.898229Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380000000000, 0x10000000, 0x149737600000) = -2 (No such file or directory) 2023-07-17T00:20:00.898318Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:00.898322Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380010000000, 0x2000000, 0x149735600000) = -22 (Invalid argument) 2023-07-17T00:20:01.027918Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:01.027927Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380000000000, 0x10000000, 0x149737600000) = -22 (Invalid argument) 2023-07-17T00:20:01.028041Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:01.028044Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380010000000, 0x2000000, 0x149735600000) = -22 (Invalid argument) 2023-07-17T00:20:01.029736Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:01.029744Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380012010000, 0x3000, 0x149b534ba000) = -22 (Invalid argument) 2023-07-17T00:20:01.034355Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:01.034362Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380000000000, 0x10000000, 0x149737600000) = -22 (Invalid argument) 2023-07-17T00:20:01.034517Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:01.034521Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380010000000, 0x2000000, 0x149735600000) = -22 (Invalid argument) 2023-07-17T00:20:01.035525Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:01.035530Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380012010000, 0x3000, 0x149b534ba000) = -22 (Invalid argument) 2023-07-17T00:20:01.088036Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:01.088046Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380000000000, 0x10000000, 0x149737600000) = -22 (Invalid argument) 2023-07-17T00:20:01.088145Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:01.088149Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380010000000, 0x2000000, 0x149735600000) = -22 (Invalid argument) 2023-07-17T00:20:01.097516Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:01.097526Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380012010000, 0x3000, 0x149b534ba000) = -22 (Invalid argument) 2023-07-17T00:20:03.440186Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:03.440207Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380000000000, 0x10000000, 0x149737600000) = -22 (Invalid argument) 2023-07-17T00:20:03.440480Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:03.440486Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380010000000, 0x2000000, 0x149735600000) = -22 (Invalid argument) 2023-07-17T00:20:03.444127Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:03.444135Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380012010000, 0x3000, 0x149b534ba000) = -22 (Invalid argument) 2023-07-17T00:20:03.456513Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:03.456525Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380000000000, 0x10000000, 0x149737600000) = -22 (Invalid argument) 2023-07-17T00:20:03.456679Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:03.456683Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380010000000, 0x2000000, 0x149735600000) = -22 (Invalid argument) 2023-07-17T00:20:03.462508Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:03.462517Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380012010000, 0x3000, 0x149b534ba000) = -22 (Invalid argument) 2023-07-17T00:20:03.558306Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:03.558324Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380012010000, 0x3000, 0x149b534ba000) = -22 (Invalid argument) 2023-07-17T00:20:06.350973Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:06.350988Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380000000000, 0x10000000, 0x149737600000) = -22 (Invalid argument) 2023-07-17T00:20:06.351323Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:20:06.351328Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380010000000, 0x2000000, 0x149735600000) = -22 (Invalid argument) 2023-07-17T00:29:19.371208Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:19.371219Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380000000000, 0x10000000, 0x149737600000) = -22 (Invalid argument) 2023-07-17T00:29:19.371319Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:19.371322Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380010000000, 0x2000000, 0x149735600000) = -22 (Invalid argument) 2023-07-17T00:29:19.438119Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:19.438127Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380000000000, 0x10000000, 0x149737600000) = -22 (Invalid argument) 2023-07-17T00:29:19.438241Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:19.438244Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380010000000, 0x2000000, 0x149735600000) = -22 (Invalid argument) 2023-07-17T00:29:19.440297Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:19.440303Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380012010000, 0x3000, 0x149b534ba000) = -22 (Invalid argument) 2023-07-17T00:29:19.445170Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:19.445177Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380000000000, 0x10000000, 0x149737600000) = -22 (Invalid argument) 2023-07-17T00:29:19.445285Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:19.445288Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380010000000, 0x2000000, 0x149735600000) = -22 (Invalid argument) 2023-07-17T00:29:19.445893Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:19.445899Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380012010000, 0x3000, 0x149b534ba000) = -22 (Invalid argument) 2023-07-17T00:29:19.501951Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:19.501962Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380000000000, 0x10000000, 0x149737600000) = -22 (Invalid argument) 2023-07-17T00:29:19.502070Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:19.502074Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380010000000, 0x2000000, 0x149735600000) = -22 (Invalid argument) 2023-07-17T00:29:19.511302Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:19.511311Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380012010000, 0x3000, 0x149b534ba000) = -22 (Invalid argument) 2023-07-17T00:29:22.983007Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:22.983022Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380000000000, 0x10000000, 0x149737600000) = -22 (Invalid argument) 2023-07-17T00:29:22.983299Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:22.983304Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380010000000, 0x2000000, 0x149735600000) = -22 (Invalid argument) 2023-07-17T00:29:22.987452Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:22.987462Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380012010000, 0x3000, 0x149b534ba000) = -22 (Invalid argument) 2023-07-17T00:29:23.000647Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:23.000660Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380000000000, 0x10000000, 0x149737600000) = -22 (Invalid argument) 2023-07-17T00:29:23.000937Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:23.000942Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380010000000, 0x2000000, 0x149735600000) = -22 (Invalid argument) 2023-07-17T00:29:23.007172Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:23.007182Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380012010000, 0x3000, 0x149b534ba000) = -22 (Invalid argument) 2023-07-17T00:29:23.079003Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:23.079019Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380012010000, 0x3000, 0x149b534ba000) = -22 (Invalid argument) 2023-07-17T00:29:23.866768Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:23.866786Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380000000000, 0x10000000, 0x149737600000) = -22 (Invalid argument) 2023-07-17T00:29:23.867041Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument 2023-07-17T00:29:23.867045Z qemu-system-x86_64: vfio_dma_map(0x1497493ec200, 0x380010000000, 0x2000000, 0x149735600000) = -22 (Invalid argument) I've searched around and tried a few fixes for the VFIO thing but nothing helped, but also it seems to work fine even with these errors. I am passing through a 1080Ti, if that matters, and otherwise the VM's work fine, once they start. Thanks and regards,

Hmm. Reading that output suggests the removal process did work. So, I tried to remove /dev/nvme3n1p1 from the pool again and it worked this time. The only difference is that I set it to "unassigned" first, started the array, it mounted properly. then went back and did the "new config", setting the total devices to 3. The first time I just went straight with new config. Not even sure if that was the reason or not. but nothing else makes sense. I 100% removed the correct device the first time. For future reverence, what IS the most recommended way to remove a device from a btrfs pool in unraid? Thanks!

Sure thing. :~# btrfs fi show Label: none uuid: e4beedf9-3a0d-4ff0-81ad-6f00dd4d38f5 Total devices 2 FS bytes used 1.57TiB devid 1 size 931.51GiB used 805.00GiB path /dev/sdd1 devid 2 size 931.51GiB used 804.06GiB path /dev/sdc1 Label: none uuid: acda611c-011e-41b8-98fd-dc6054483acb Total devices 3 FS bytes used 276.14GiB devid 1 size 931.51GiB used 184.03GiB path /dev/nvme0n1p1 devid 2 size 931.51GiB used 186.00GiB path /dev/nvme1n1p1 devid 3 size 931.51GiB used 185.03GiB path /dev/nvme2n1p1 Sorry for the delay, Miss your post last night and worked today. Thanks for the help!

So I put it in raid 1 mode, fully balanced, then stopped the array and removed it. When I started the array it said something like "unmounable or no file system". So I stopped again are added it back. Worked, back at square one. The next time I read to use the btrfs remove command. So I just tried to remove the one drive again, let it do it's thing for awhile til it completed, then again stopped the array and removed it from the pool. Again, "unmountable or no file system". Problem is, THIS time when I added it back, it's still unmountable. Looking through the logs I found two things that might me relevant. This: Jul 6 20:39:45 CyprusSrv kernel: BTRFS info (device nvme0n1p1): device deleted: /dev/nvme3n1p1 (when i used the command to delete that device from the pool). And this: Jul 6 20:40:55 CyprusSrv emhttpd: shcmd (2317): mount -t btrfs -o noatime,space_cache=v2 -U acda611c-011e-41b8-98fd-dc6054483acb /mnt/nvme_cache Jul 6 20:40:55 CyprusSrv root: mount: /mnt/nvme_cache: wrong fs type, bad option, bad superblock on /dev/nvme3n1p1, missing codepage or helper program, or other error. Maybe I'm actually going crazy but the docs seem spotty on exactly how to removing a drive, and I got different answers while searching. Thanks for any help guys. Edit: Edited title to be a little more clear, and added more information

Hey guys, Setting up went well. It properly detects my 1070ti, and I logged in with steam and downloaded some games. My question is. How to get better performance in a browser. The NoVNC client is running at about 0.2-0.5 Frames a second. Am I missing something? Thanks!

Wow, I restarted and it all popped up normally. I was afraid to restart.. or do anything- without confirming I wasn't going to make things worse. Thanks so much, you actually have no idea what a relief this is. Treating this as a wakeup call for backups. Regards,

I'm in full panic mode right now. I had an issue with a SATA cable, replaced it but when I tried to re-add the disk to the array it told me I needed to rebuild it so I did. It looks like it's rebuilding parity right now but all the disks are unmountable?? Please help.