downloadedskill

I have a W11 VM that crashing every few days and when it does it pins all the cores it's assigned to 100%. It just started happening like 2 weeks ago. It's running important automation software for our business and to be up as much as possible. Please let me know what I have to upload like logs or something. XML for the VM is attached. Unraid 7.2 SwitchServer.txt

Gotcha. TY

SMH...That fixes it. So you can expand after creation but not shrink after creation is the idea?

Diagnostics attachedhal-9000-diagnostics-20260306-1426.zip

I just added hot swap bays to my server with an HBA card and 3 x 4tb IronWolf drives. I added them to a pool and when I go to format them formatting pops up for a second and nothing happens. What should I do now?

That did it. I didn't realize I needed the whole location like that. Thank you for correcting my stupidity!

Looking to delete the PSserver-deleteme NAME USED AVAIL REFER MOUNTPOINT working 1.62T 1.08T 209K /mnt/working working/Backups 140K 1.08T 140K /mnt/working/Backups working/appdata 286M 1.08T 186K /mnt/working/appdata working/appdata@2026-02-20-154435 55.1M - 141M - working/appdata@autosnap_2026-02-23_07:13:29_monthly 0B - 105M - working/appdata@autosnap_2026-02-23_07:13:29_weekly 0B - 105M - working/appdata@autosnap_2026-02-23_07:13:29_daily 0B - 105M - working/appdata@syncoid_HAL-9000_2026-02-23:07:21:08-GMT-05:00 279K - 843K - working/appdata/DiskSpeed 140K 1.08T 140K /mnt/working/appdata/DiskSpeed working/appdata/DiskSpeed@syncoid_HAL-9000_2026-02-23:07:21:09-GMT-05:00 0B - 140K - working/appdata/binhex-krusader 125M 1.08T 106M /mnt/working/appdata/binhex-krusader working/appdata/binhex-krusader@syncoid_HAL-9000_2026-02-23:07:21:09-GMT-05:00 19.3M - 106M - working/appdata/duckdns 145K 1.08T 145K /mnt/working/appdata/duckdns working/appdata/duckdns@syncoid_HAL-9000_2026-02-23:07:21:09-GMT-05:00 0B - 145K - working/domains 1.61T 1.08T 174K /mnt/working/domains working/domains@2026-02-19-090904 1.25G - 590G - working/domains@2026-02-19-093442 903M - 590G - working/domains@2026-02-19-132641 93K - 588G - working/domains@2026-02-19-135548 7.29G - 743G - working/domains@2026-02-19-144634 301M - 743G - working/domains@2026-02-19-150029 354M - 743G - working/domains@autosnap_2026-02-23_07:18:09_monthly 0B - 301G - working/domains@autosnap_2026-02-23_07:18:09_weekly 0B - 301G - working/domains@autosnap_2026-02-23_07:18:09_daily 0B - 301G - working/domains@syncoid_HAL-9000_2026-02-23:07:23:50-GMT-05:00 81.4K - 174K - working/domains/PS Server - Fresh 33.8G 1.08T 32.0G /mnt/working/domains/PS Server - Fresh working/domains/PS Server - Fresh@autosnap_2026-02-23_07:18:09_monthly 0B - 32.7G - working/domains/PS Server - Fresh@autosnap_2026-02-23_07:18:09_weekly 0B - 32.7G - working/domains/PS Server - Fresh@autosnap_2026-02-23_07:18:09_daily 0B - 32.7G - working/domains/PS Server - Fresh@syncoid_HAL-9000_2026-02-23:07:35:29-GMT-05:00 0B - 32.7G - working/domains/PSserver-deleteme 458G 1.08T 140K /mnt/working/domains/PSserver-deleteme working/domains/PSserver-deleteme@2026-02-19-145953 0B - 456G - working/domains/PSserver-deleteme@2026-02-19-150029 0B - 456G - working/domains/PSserver-deleteme@autosnap_2026-02-23_07:18:09_monthly 0B - 445G - working/domains/PSserver-deleteme@autosnap_2026-02-23_07:18:09_weekly 0B - 445G - working/domains/PSserver-deleteme@autosnap_2026-02-23_07:18:09_daily 0B - 445G - working/domains/PSserver-deleteme@syncoid_HAL-9000_2026-02-23:07:36:00-GMT-05:00 11.6K - 140K - working/domains/Switch 1023K 1.08T 140K /mnt/working/domains/Switch working/domains/Switch@2026-02-19-093442 116K - 407K - working/domains/Switch@2026-02-19-101712 384K - 698K - working/domains/Switch@2026-02-19-102259 93K - 407K - working/domains/Switch@2026-02-19-135548 0B - 140K - working/domains/Switch@2026-02-19-144634 0B - 140K - working/domains/Switch@2026-02-19-144704 0B - 140K - working/domains/Switch@2026-02-19-144716 0B - 140K - working/domains/Switch@2026-02-19-150029 0B - 140K - working/domains/Switch@autosnap_2026-02-23_07:18:09_monthly 0B - 140K - working/domains/Switch@autosnap_2026-02-23_07:18:09_weekly 0B - 140K - working/domains/Switch@autosnap_2026-02-23_07:18:09_daily 0B - 140K - working/domains/SwitchServer 343G 1.08T 149G /mnt/working/domains/SwitchServer working/domains/SwitchServer@2026-02-19-150344 5.72G - 316G - working/domains/SwitchServer@2026-02-20-102439 3.82G - 316G - working/domains/SwitchServer@autosnap_2026-02-23_07:18:09_monthly 0B - 307G - working/domains/SwitchServer@autosnap_2026-02-23_07:18:09_weekly 0B - 307G - working/domains/SwitchServer@autosnap_2026-02-23_07:18:09_daily 0B - 307G - working/isos 753M 1.08T 753M /mnt/working/isos working/public 9.81G 1.08T 9.81G /mnt/working/public working/system 4.64G 1.08T 4.64G /mnt/working/system working/zfs 267M 1.08T 140K /mnt/working/zfs working/zfs/working_appdata 267M 1.08T 163K /mnt/working/zfs/working_appdata working/zfs/working_appdata@2026-02-20-154435 55.1M - 141M - working/zfs/working_appdata@autosnap_2026-02-23_07:13:29_monthly 0B - 105M - working/zfs/working_appdata@autosnap_2026-02-23_07:13:29_weekly 0B - 105M - working/zfs/working_appdata@autosnap_2026-02-23_07:13:29_daily 0B - 105M - working/zfs/working_appdata@syncoid_HAL-9000_2026-02-23:07:21:08-GMT-05:00 326K - 843K - working/zfs/working_appdata/DiskSpeed 221K 1.08T 140K /mnt/working/zfs/working_appdata/DiskSpeed working/zfs/working_appdata/DiskSpeed@syncoid_HAL-9000_2026-02-23:07:21:09-GMT-05:00 81.4K - 140K - working/zfs/working_appdata/binhex-krusader 106M 1.08T 174K /mnt/working/zfs/working_appdata/binhex-krusader working/zfs/working_appdata/binhex-krusader@syncoid_HAL-9000_2026-02-23:07:21:09-GMT-05:00 106M - 106M - working/zfs/working_appdata/duckdns 238K 1.08T 140K /mnt/working/zfs/working_appdata/duckdns working/zfs/working_appdata/duckdns@syncoid_HAL-9000_2026-02-23:07:21:09-GMT-05:00 98.8K - 145K -

Pretend you didn't see that. It says the dataset doesn't exist but I see it in ZFS Master. I double checked the spelling! When I go to the folder though it's empty. I then tried to delete the folder and nothing happened.

This is what I get when using the destroy command. root@HAL-9000:~# zfs destory working/PSserver-deleteme unrecognized command 'destory' usage: zfs command args ... where 'command' is one of the following: version [-j] create [-Pnpuv] [-o property=value] ... <filesystem> create [-Pnpsv] [-b blocksize] [-o property=value] ... -V <size> <volume> destroy [-fnpRrv] <filesystem|volume> destroy [-dnpRrv] <filesystem|volume>@<snap>[%<snap>][,...] destroy <filesystem|volume>#<bookmark> snapshot [-r] [-o property=value] ... <filesystem|volume>@<snap> ... rollback [-rRf] <snapshot> clone [-p] [-o property=value] ... <snapshot> <filesystem|volume> promote <clone-filesystem> rename [-f] <filesystem|volume|snapshot> <filesystem|volume|snapshot> rename -p [-f] <filesystem|volume> <filesystem|volume> rename -u [-f] <filesystem> <filesystem> rename -r <snapshot> <snapshot> bookmark <snapshot|bookmark> <newbookmark> diff [-FHth] <snapshot> [snapshot|filesystem] list [-Hp] [-j [--json-int]] [-r|-d max] [-o property[,...]] [-s property]... [-S property]... [-t type[,...]] [filesystem|volume|snapshot] ... set [-u] <property=value> ... <filesystem|volume|snapshot> ... get [-rHp] [-j [--json-int]] [-d max] [-o "all" | field[,...]] [-t type[,...]] [-s source[,...]] <"all" | property[,...]> [filesystem|volume|snapshot|bookmark] ... inherit [-rS] <property> <filesystem|volume|snapshot> ... upgrade [-v] upgrade [-r] [-V version] <-a | filesystem ...> userspace [-Hinp] [-o field[,...]] [-s field] ... [-S field] ... [-t type[,...]] <filesystem|snapshot|path> groupspace [-Hinp] [-o field[,...]] [-s field] ... [-S field] ... [-t type[,...]] <filesystem|snapshot|path> projectspace [-Hp] [-o field[,...]] [-s field] ... [-S field] ... <filesystem|snapshot|path> project [-d|-r] <directory|file ...> project -c [-0] [-d|-r] [-p id] <directory|file ...> project -C [-k] [-r] <directory ...> project [-p id] [-r] [-s] <directory ...> mount [-j] mount [-flvO] [-o opts] <-a|-R filesystem|filesystem> unmount [-fu] <-a | filesystem|mountpoint> share [-l] <-a [nfs|smb] | filesystem> unshare <-a [nfs|smb] | filesystem|mountpoint> send [-DLPbcehnpsVvw] [-i|-I snapshot] [-R [-X dataset[,dataset]...]] <snapshot> send [-DnVvPLecw] [-i snapshot|bookmark] <filesystem|volume|snapshot> send [-DnPpVvLec] [-i bookmark|snapshot] --redact <bookmark> <snapshot> send [-nVvPe] -t <receive_resume_token> send [-PnVv] --saved filesystem receive [-vMnsFhu] [-o <property>=<value>] ... [-x <property>] ... <filesystem|volume|snapshot> receive [-vMnsFhu] [-o <property>=<value>] ... [-x <property>] ... [-d | -e] <filesystem> receive -A <filesystem|volume> redact <snapshot> <bookmark> <redaction_snapshot> ... allow <filesystem|volume> allow [-ldug] <"everyone"|user|group>[,...] <perm|@setname>[,...] <filesystem|volume> allow [-ld] -e <perm|@setname>[,...] <filesystem|volume> allow -c <perm|@setname>[,...] <filesystem|volume> allow -s @setname <perm|@setname>[,...] <filesystem|volume> unallow [-rldug] <"everyone"|user|group>[,...] [<perm|@setname>[,...]] <filesystem|volume> unallow [-rld] -e [<perm|@setname>[,...]] <filesystem|volume> unallow [-r] -c [<perm|@setname>[,...]] <filesystem|volume> unallow [-r] -s @setname [<perm|@setname>[,...]] <filesystem|volume> hold [-r] <tag> <snapshot> ... holds [-rHp] <snapshot> ... release [-r] <tag> <snapshot> ... load-key [-rn] [-L <keylocation>] <-a | filesystem|volume> unload-key [-r] <-a | filesystem|volume> change-key [-l] [-o keyformat=<value>] [-o keylocation=<value>] [-o pbkdf2iters=<value>] <filesystem|volume> change-key -i [-l] <filesystem|volume> program [-jn] [-t <instruction limit>] [-m <memory limit (b)>] <pool> <program file> [lua args...] rewrite [-rvx] [-o <offset>] [-l <length>] <directory|file ...> wait [-t <activity>] <filesystem> zone <nsfile> <filesystem> unzone <nsfile> <filesystem> Each dataset is of the form: pool/[dataset/]*dataset[@name] For the property list, run: zfs set|get For the delegated permission list, run: zfs allow|unallow For further help on a command or topic, run: zfs help [<topic>]

I'm trying to delete some datasets that are no longer needed. I'm very short on space and I can't delete them. I have no idea what is using them still because the VM's aren't on anymore. I've tried renaming to delete them but that didn't work.

I'm just testing on an Unraid Trial to move a physical W11 machine to a VM. Planning on moving our work server to Unraid and a few physical machines to VMs to consolidate down to 1 machine. Also eventually get rid of our Synology and use another Unraid app for that. Anyway I did a W11 backup on the test system then used V2V converter to make the vhdx to a raw image. I moved it onto the array and pointed the VM settings to it and went by the Unraid documentation but the system won't boot. It keeps saying no bootable media and goes into the Unraid VM bios. Am I doing something wrong with the backups and conversions? Also is there a way to make the backups smaller? Like the size of the actual used space and not the HDD capacity? My machines have 500gb SSD's but only use like 100gb. I'd rather not have to have multiple 500gb images that are not doing anything.

This no longer works for me and the background just shows an X when hovering over it.

Since it got updated the other day neither can I.

I hate the the built in file manager but that makes sense I always 'move' stuff instead of copying. I'm going to test that and see what happens. Thank you for that. I'll see how that works.

The path just shortcuts to /mnt/user/ and my TV share and Movie shares are there which is where I dumb the files.

The only thing it could have been was Krusader manually moving files into the share. I keep having to use unbalance to move stuff back onto the right disks and they still come back.

I don't think anything was originally. I just had them as shares to separate my media. Handbrake uses my "working" pool along with dropping downloads from some dockers. skynet-diagnostics-20250303-1141.zip

I'm only using krusader to manually move files into the shares and they end up where they shouldn't.

The issue I'm having is that files keep ending up out of designated drives and pools. For instance in my one TV share my "Working" ssd pool shows up which is shouldn't be attached to that share and also Disk 1 which shouldn't either. I'm getting this with my "Working" ssd pool and some other shares as well. What am I missing? How do I stop this from happening?

@binhex Any thoughts on this one?

binhex-official-windows question. I'm trying to add my shares to windows as native drives, is that possible? If so how can I do it or do something similar?

My main issue with Unraid is the performance hit. If that wasn't an issue I'd be stilling with it but because of that I'm considering switching to zfs/pools. Not sure when I might make the jump.

You did that on another windows machine?

Finally realized where the logs are so I attached a few. Star Trek Lower Decks - S05E01 2025-01-25 10-02-48.log Star Trek Discovery - S04E10 2025-01-25 10-02-45.log Star Trek Discovery - S05E10 2025-01-25 10-02-48.log Star Trek Strange New Worlds - S02E08 2025-01-25 10-02-44.log Star Trek Strange New Worlds - S02E10 2025-01-25 10-02-45.log

Files attached. Let me know if that is correct. Binhex-delugevpn-CommandEx.txt supervisord.log