Started a new Project and ive been looking at unraid to try (Proxmox, Turnkey, FreeNAS from past).

Got a GMKtec G9 (4x M.2 and 64gb emmc)

4x 4tb M.2 Gen4

USB 3.1 Samsung Drive Fit 64gb

Unraid 7.0.1 (Starter)

 

Installed, added 4x4tb to make the Array. Created a share "Media"

Minimum free space was set to 1TB

High Water

Auto Split any Directory as required

All 4 Disk included

0 Disk Expluded

SMB Share is public

 

From my Windows 19 Machine I have a mapped drive to my Proxmox 40tb share and to the 16tb Unraid "Media" Share.

I drag and drop from the Proxmox to the the Unraid and I get an error

1 Interrupted Action

There is not enough space on Media (NasG9-16tb Media Server)). You need an additional 116gb to copy these files.

 

Ive rebooted. I changed the "minimum free space" to a larger number (3.5tb) to 0kb to 500gb. Reading the forums ive attempted to copy smaller files and it works for a bit but then I hit a wall (Im down to single folders being transfered). Checked High Water, Checked Minimum free, checked included and excluded, no cache, format is XFS on all 4 drives, no parity, and ran te "New Permissions" tool.

 

That is 1 issue and my biggest. Docker Service failed to start was the other issue and when I click on Terminal I get a 502 error "Bad Gateway". Docker was not working before and I changed the "Docker data-root" to xfs vDisk and rebooted and it worked, but now it is not so something to do later.

 

 

Any help would be appreciated

 

nasg9-16tb-diagnostics-20250427-1224.zip

Just an update. Shutdown Unraid and removed the USB drive. deleted the trail file that was giving an error in the logs. reinserted and powered on. Docker started and the terminal is working. Still the error with not enough space

On 4/27/2025 at 3:13 PM, David61 said:

Minimum free space was set to 1TB

I don't think I have ever heard of anyone setting it that high. Does seem like it should work until free space gets below 1TB though.

 

Why did you choose such a high setting? The recommendation is to set it to larger than the largest file you expect to write to the share. Do you really expect to write a file as large as nearly 1TB?

 

There is something else you might reconsider about your current configuration though.

 

SSDs in the array cannot be trimmed. Usually those would be put in pools outside the array. Unraid v7 doesn't require an array.

Also, 500G docker.img is at least 10 times as large as should be needed.

https://docs.unraid.net/unraid-os/manual/shares/user-shares/#minimum-free-space

Killed the Array and moved all the 4x 4tb to a pool and created a pool from them. When I setup the share and look at the 4x nvme, 1 says btrfs and I get info the other 3 have nothing. no data, no info.

 

Is it something like Fill vs High Water?

2 hours ago, David61 said:

Is it something like Fill vs High Water?

Allocation methods only apply to the array.

 

2 hours ago, David61 said:

moved all the 4x 4tb to a pool and created a pool from them. When I setup the share and look at the 4x nvme, 1 says btrfs and I get info the other 3 have nothing. no data, no info.

If these are all in the same pool, then they are combined into one storage space. The info for the pool is displayed next to the first drive in the pool.

 

Post new diagnostics.