Hi

this is my first post and I am relatively new to Unraid so please be patient

I added a second hdd to my array. I use high water and automatic split for each share (this is what I found in the forums what solved problems for others).

Then i added a lot of data from my Qnap NAS.

As you can see in the screenshot disk1 is running out of space and disk 2 won't be used.

At last I tried to transfer a single file but it stopped at 47% because disk 1 is full. Disk 2 won't even wake up (but it does when clicked).

Hope someone can help me please...

best regards

Jens

Attach Diagnostics ZIP to your NEXT post in this thread.

OK forgot it - here it is, thanks

homeserver-diagnostics-20260124-1735.zip

1 hour ago, Jens1973 said:

hen i added a lot of data from my Qnap NAS

How exactly are you doing this?

47 minutes ago, trurl said:

How exactly are you doing this?

I mounted the Qnap share as SMB share and copied/moved via unraids filemanager to the unraid share..

Could not spot anything obviously wrong, but it might help if you mentioned the Unraid share name so we can check.

There are some anomalies you should correct.

• The share starting with I appears to not exist. You can remove any configuration files for non-existent shares by clicking the Tidy button on the Shares tab

• You have several shares with files on the cache that are not configured to store files there. This implies you manually created top level folders on the’ cache’ pool which then automatically become User Shares, albeit with default settings.

I----h                            shareUseCache="no"      # Share does not exist
P-------s                         shareUseCache="no"      # Share exists on cache
a-----a                           shareUseCache="no"      # Share exists on cache
d-----s                           shareUseCache="no"      # Share exists on cache
s----m                            shareUseCache="no"      # Share exists on cache

Post a screenshot of Global Share Settings

OK here are the shares and the global share settings.

Anything strange there?

12 minutes ago, itimpi said:

it might help if you mentioned the Unraid share name

What user share are you writing to?

24 minutes ago, trurl said:

What user share are you writing to?

to "Mov"...

I checked the disk informations and I saw that under "Partitionsformat" there is

• disk 2 (the empty one)"GPT 4KiB-Ausrichtung"

• disk 1 "no partitions"

can that be a problem?

12 hours ago, Jens1973 said:

can that be a problem?

Not related toi this, are you sure you are copying to the share and not disk1? What is the full path you are using for the destination?

1 hour ago, JorgeB said:

Not related toi this, are you sure you are copying to the share and not disk1? What is the full path you are using for the destination?

hm that's a good point, I copy to mnt/disk1/Mov. There are morelocations for "Mov" here: mnt/user/Mov, mnt/user0/Mov and mnt/cache/Mov. Which one is would be correct? I read that you shouldn't copy from share to user so the only place is mnt/disk1/Mov.

I have to say that all shares have been created when there was only disk1. I added disk2 later but disk1 has been <50% full when I started copiing.

If you explicitly copy to disk1 that is the only place files will go so that explains your symptoms.

2 minutes ago, Jens1973 said:

I read that you shouldn't copy from share to user so the only place is mnt/disk1/Mov.

That is true if copying internally within Unraid in that you must not mix a disk share and a user share in the same command. However in this case you are copying from an external device to Unraid storage. If using Uranid's built in file manager it will protect you from this issue as it will not allow a combination of source and target that can cause this issue.

What you want to be doing is copying to the 'Mov' user share (which appears at the Linux level as /mnt/user/Mov) as that is a share that spans all drives and pools. That will then obey whatever rules you have set up for that share as to where files should go. The /mnt/user0/Mov path is a variant that only includes array drives having files for the 'Mov' User share omitting any files on pools.

You may want to manually move some files from /mnt/disk/Mov to /mnt/disk2/Mov to free up space on disk1 as Unraid will not automatically move any existing files.

Ok thanks for your explanation, understood.

it works as you said! when copiing to /user the files end up on the cache. when copping to /user0, it uses disk2 as it should.

Only for my understanding: "Mov" is set to use array only. Why is the cache used?

Can I solve it somehow that as mentioned above disk1 has "no partitions"? will it be a problem sometimes later?

32 minutes ago, Jens1973 said:

Can I solve it somehow that as mentioned above disk1 has "no partitions"? will it be a problem sometimes later?

It should not be a problem while the disk is assigned to the array, but it would not mount outside it; you can correct the issue by creating a standard Unraid partition layout (it won't delete the data)

With the array stopped, type:

sgdisk -o -a 8 -n 1:32K:0 /dev/sdX

Replace X with the correct identifier for disk1, after refreshing the GUI it should now show a partition for that disk

22 minutes ago, JorgeB said:

It should not be a problem while the disk is assigned to the array, but it would not mount outside it; you can correct the issue by creating a standard Unraid partition layout (it won't delete the data)

With the array stopped, type:

sgdisk -o -a 8 -n 1:32K:0 /dev/sdX

Replace X with the correct identifier for disk1, after refreshing the GUI it should now show a partition for that disk

Thank you, works like a charme!

Thank you all !

3 hours ago, Jens1973 said:

Only for my understanding: "Mov" is set to use array only. Why is the cache used?

No idea - it should not with the settings you have.

4 hours ago, Jens1973 said:

when copiing to /user the files end up on the cache. when copping to /user0, it uses disk2 as it should.

Only for my understanding: "Mov" is set to use array only. Why is the cache used?

Reboot in SAFE mode and repeat that test