JonathanM

That's par for the course. Wifi advertises huge throughput but real world conditions mean you almost never get there.

That won't do anything. https://wiki.lime-technology.com/Troubleshooting#Re-enable_the_drive

Weird. I wonder if the three pack has something to do with the three identical GUID's. I've always bought single drives, albeit 4 at a time. Strangely, it's cheaper that way for me. Multi packs always seem to be overpriced.

That is very strange. Where did you purchase them? One of two things is going on, either they very recently quit programming unique GUID's, or what you purchased is counterfeit. A little over a month ago I got 4 more, and they all have unique (and none the same as your) GUID's. Do they have unique serial numbers laser etched on the narrow edge? All mine have a large outline CE, and two lines of text with DTSE9H/16GB 05655-315.A00LF, OS XXXXXXX, 5V, and TAIWAN on them. The XXXXXXX are unique on all my different drives.

Are you sure? The default I believe for raw is sparse, unless you copied the vdisk file using something that un-sparsified it. You should be able to use cp --sparse=always to make the file sparse again.

Why? Pre-clear is just a testing routine, you can add it to the array without a valid preclear.

Depends. You won't know until you try. Some USB interfaces pass the drive through intact, others remap the drive sector locations. Worst case the drive will be cleared when you add it, meaning another pass and several hours, but not the end of the world. Clearing to add an array drive is much quicker than a pre-clear cycle.

If you are too impatient to wait for the stable linuxserver build, you can do it yourself following the directions ich777 posted. Asking for beta builds when they are coming out back to back is a little presumptuous.

You realize that beta 25 is out, right?

XFS added some file system features recently which likely account for the space. Think of the file system like the physical filing cabinets that hold folders and pieces of paper. The drawers and folders all need labels to help you find the specific piece of paper you are after. By keeping the content organization scheme robust and complete, it's quicker to access the needed content, and should some papers get scrambled or misplaced, it's easier to recover if the drawers and folders have more information about what should be where. By reserving the majority of space that could be needed ahead of time, you can ensure a lot of the meta-data is in the quicker portions at the beginning of the drive and doesn't get fragmented across the platters.

If your signature is accurate you may be having issues with your SAS2LP.

This is wrong on so many levels. I wouldn't trust a scan tool that can't correctly identify the product. Unraid is based on slackware.

Read the recommended post at the top of every page in this topic.

Why? From the FAQ johnnie.black linked, you should have run it on /dev/md3 assuming we are still talking about disk3.

Have you copied enough data to get past the high water level to use a different disk?

Yep, wrong sector size.

Diagnostics zip file missing, crystal ball broken, my best guess would be wrong sector size.

Sure. I'm still not sure what you are gaining by doing it this way, it definitely takes much longer than just building parity with the new config, and you are basically writing the full capacity of the parity drive X times (where X is the number of drives to remove) vs. just once.

Do you have a way to verify that not all boards use the same GUID? I suspect given the string of 6 repeated characters that it's not unique, and can't be licensed.

That's normal when the router isn't set to reflect outside addresses accessed from the inside to the appropriate internal resources. Search for your router model plus the terms "nat loopback reflection hairpinning"

any repeats or series?

Unraid will use all resources available to it. Any resources that you dedicate to a VM will be unavailable to Unraid. The more resources you leave for Unraid, the faster it can serve the emulated resources to the VM. Think of Unraid as the motherboard for your VM's. If you restrict the speed of the motherboard, it doesn't matter much how fast your CPU is or how much RAM you have, the computer isn't going to run very well. 3 VM's running concurrently on 16GB of RAM is going to be extremely tight.

Yes, but it will be slower, and usage will extend the rebuild time.