Good morning everyone, I was running a full backup of my main PC to my Unraid server and woke up this morning to a disabled device.  Looks like it has had a write error, but there's currently no SMART errors reported on the dashboard for it.  Could someone please take a look at my diagnostics and let me know what my next step should be?  The disk is full it seems from the backup and I'm not sure if I have a misconfiguration or some action I should take to free space, there's several other drives in the server that are open to use, but aren't I believe because of the way it's set to use them.

 

Thank you for reading, and any advice you could provide!

tower-diagnostics-20230126-0819.zip

SMART report for disabled disk1 looks fine. Diagnostics are after reboot so can't see anything that happened before.

 

Check connections, all disks, power and SATA, both ends, including splitters.

 

Emulated disk1 is mounted and completely full. After you rebuild you should try to make some free space on that disk.

 

You should set Minimum Free for each of your user shares to larger than the largest file you expect to write to the share. If you don't know what to do, 50G is a good place to start.

 

If a disk gets below Minimum, Unraid will choose another if allowed by other settings. You currently have zero Minimum, which means Unraid can choose the disk anytime allowed by other settings no matter how full it is.

 

Full disks don't perform as well. More importantly, filesystem repair needs some free space to work in if that becomes necessary.

 

 

 

 

13 minutes ago, Steiner49er said:

running a full backup of my main PC

Maybe the reason you filled disk1. How exactly were you doing the backup?

11 minutes ago, trurl said:

Maybe the reason you filled disk1. How exactly were you doing the backup?

I was actually trying to resolve a merge issue with Veeam Agent for Windows by running a full backup, and my drive on the main PC is right at 2TB used... so yikes, I have some definite configuration issue going on here.  I'll start the rebuild process (have to look up how to do that), and then it sounds like I need to set a minimum free space for my drives and then choose some different targets to overflow onto, if I'm using the right terminology?

6 minutes ago, Steiner49er said:

the rebuild process

https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

 

7 minutes ago, Steiner49er said:

set a minimum free space for my drives and then choose some different targets to overflow onto, if I'm using the right terminology?

Not exactly. There is no Minimum Free setting for array disks.

 

Each of your user shares has a Minimum Free Setting. When writing to a user share, if an array disk has less than Minimum, Unraid will choose another if allowed by other settings. Note that it does this choosing before knowing how large the file you are writing is, and in general, it can't know how large a file will become.

 

For example, a disk has 15G free, Minimum is 10G, you write a 10G file. Unraid can choose the disk since it has more than Minimum. After writing that 10G, disk will have 5G free and won't be chosen again.

 

Another example, a disk has 15G free, Minimum is 10G, you write a 20G file. Unraid can choose the disk since it has more than Minimum, and the write will fail when it runs out of space.

 

There is also Minimum Free setting for each of your pools (cache) that works in a similar manner. If a pool has less than Minimum, Unraid will choose an array disk instead (overflow), but only for cache:yes and cache:prefer shares.

 

 

On 1/26/2023 at 9:17 AM, trurl said:

https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

 

Not exactly. There is no Minimum Free setting for array disks.

 

Each of your user shares has a Minimum Free Setting. When writing to a user share, if an array disk has less than Minimum, Unraid will choose another if allowed by other settings. Note that it does this choosing before knowing how large the file you are writing is, and in general, it can't know how large a file will become.

 

For example, a disk has 15G free, Minimum is 10G, you write a 10G file. Unraid can choose the disk since it has more than Minimum. After writing that 10G, disk will have 5G free and won't be chosen again.

 

Another example, a disk has 15G free, Minimum is 10G, you write a 20G file. Unraid can choose the disk since it has more than Minimum, and the write will fail when it runs out of space.

 

There is also Minimum Free setting for each of your pools (cache) that works in a similar manner. If a pool has less than Minimum, Unraid will choose an array disk instead (overflow), but only for cache:yes and cache:prefer shares.

 

 

Thank you very much for your help!  I really appreciate the link you sent as well, that was exactly what I needed.  The drive is rebuilt and healthy now.  I've deleted some old 'stuff' from the drive/shares, and set minimum free space on the shares that get heavily used.

 

Thank you again!