newhinton

I did try to write directly to /mnt/disk1. It seems to be far faster, the initial incremental file list takes only minutes instead of the better part of an hour. I assume when i directly use /mnt/diskX, i can only use empty directories, otherwise i would get into trouble with the array-aggretation wont i? Restarting from scratch is generally not a problem, so i will delete and resync to a single disk if i have to. But is there a way to high-speed write directly to all drives with rsync? If that isn't (relatively easily) possible i'll just start over. Thanks for your help either way!

Maybe! But i only have one pool of two disks in an array. Generally, my goal is to rsync all my data to the unraid system, preferably fast. If there is a different way, im open to suggestions!

I have a similar issue while migrating a disk with a lot of tiny files to my array. When writing to /mnt/user/share, i get abysmal performance with rsync. I have read that using "exclusive shares" bypasses the actual bottleneck, FUSE. Can i just enable exclusive shares, and add a new one to the share i want to transfer my files to? Do i have to worry about actual disks, eg. do they split the folders like they would with a "normal" share?

The short one fails aswell. The thing is that both fail basically immediately. The sector where it fails is also variable, so i dont quite understand the problem. Do you have a suggestion on how can i diagnose this issue and get more information? Is it possible to force-check the whole drive to get an overall health-overview? Regardless, i will contact the vendor for a replacement. It's sad to have a disk dead on arrival.

Hello! i just started my journey with unraid. Today i got a brand new drive, but a couple of hours after use i got smart errors. First, Current pending sector and Offline uncorrectable had some value greater than zero, but after a reboot they first were zero and then updated to 1 where they are now. Shortly after, Reallocated sector count also increased to 1. If i run smart self tests it fails: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 4 59208 # 2 Extended offline Completed: read failure 90% 3 59344 # 3 Extended offline Completed: read failure 90% 3 59344 # 4 Short offline Completed: read failure 90% 3 59208 # 5 Short offline Completed: read failure 90% 3 59256 # 6 Short offline Completed: read failure 90% 3 59208 # 7 Short offline Completed: read failure 90% 3 59208 # 8 Extended offline Completed: read failure 90% 3 59208 # 9 Short offline Completed without error 00% 0 - Is this truly already a dead disk and should be rma'ed? It reads and writes "fine" as far as i can tell. Unraid itself marks those smart values as warnings, but i usually have a really hard time interpreting smart-values. Thanks for your help!