Axanar

I'm still having trouble copying a large file to the NAS. The last time I tried it was either a 1 TB or 1.5 TB file. The share is set to use only disk 9 and 10. Disk 9 has 2 TB free and disk 10 has 4 TB free. The copy failed. Perhaps the problem is my Windows system. I am considering backing off all the data, resetting Unraid to the initial state, and starting over.

yes. I removed the cache drive as it was only 500GB in size and not big enough to handle files 1.5TB in size. Do I need to do something more to remove the cache?

Thank you everyone for your help.

I just tried again with Beyond Compare and it failed again. I've tried both drag and drop with file explorer and beyond compare to copy the file. I'm getting the diagnostics.zip now. godzilla-diagnostics-20240723-0812.zip

disk 9. I changed the share to go only to disks 9 and 10 instead of all disks. disk 9 has 4 TB of free space and disk 10 has 6 TB of free space. both are 6 TB drives. During the copy I watched on the main page and it was doing writes to disk 9 as it should. The attempted copy of a 476 GB took hours before it failed.

I checked all the drives. No file with the same name, neither partial or complete.

I still am unable to copy that file. I have the share set to use only drives 9 and 10. Both of which have plenty of space (4 TB and 6 TB). I then tried a smaller 476 GB file. That also failed. So then instead of using Windows drag and drop of the file I used Beyond Compare to copy the file. That also failed. godzilla-diagnostics-20240722-1445.zip

Thanks.

Thank you for your help! I've been stuck with this for quite a while - copying files back and forth, de-fraging disks, changing settings and trying again. One question though. Does the size of the cache drive have to be larger than the biggest file you will ever copy?

Currently, I changed the share to specifically use two disk that have over 5TB of free space. I expect that will succeed. What would be your recommendation for me to do now? I would hate to have to manually set a specific disk to use for transfers and keep changing it as needed. What would be your recommendation for me to do now? I can set it back to High Water and increase the minimum free space. Would going back to a single "data" share help, hurt, or make no difference? This all started happening when it was set to High Water and all shares were set to use all drives. I believe this all started when a large file wouldn't copy to the "data" share. I replaced a 6 TB drive with a 12 TB drive and it still wouldn't copy saying there wasn't enough free space.

It was set to High Water when the problem first started happening. Later I changed it to Fill Up hoping that would help. It didn't.

the share was "game images". all shares can use all drives. I previously had everything in one big share called "data". I had the same problem of not being able to copy large files was happening back then too. I made a few more shares and moved a bunch of files from the data share to the new shares hoping that would defrag the drives a bit. it didn't help. In fact I was getting the same problem trying to move files from the data share to one of the others. So then I moved a bunch of files from the NAS to an external drive. when I tried to move the files back it said there wasn't enough free space. I hadn't written any other files to the NAS in between. I was only able to move back small files. Now I how a bunch of directories where some of the files are on the NAS and others are on external storage and I can't move them back to the NAS even though it has 35 TB of free space.. I had a 500 GB SSD as a cache drive. Thinking it could be part of the problem I changed the cache drive to "no device" yesterday. it didn't help. I just removed the mover plugin.

godzilla-diagnostics-20240721-1216.zip

As the file is copying I see that only three drives are being written to. The 2 parity drives and disk2 which only has 304 GB of free space instead of one of the drives that have 6 TB of free space.

thanks. I will start the drag and drop of the file again and get a fresh log.