gubbgnutten

Look at it as the perfect opportunity/excuse to get an external HDD for backup. 😁 Or if you are going the internal route, a disk to use as parity disk after the migration. Not the same as a backup, but it will cover for one failed disk.

Apologies in advance if this is not to your liking. Let’s just say that link aggregation is messy. I have it on my old server, a quad connection to a GS1900 or something like that. It took a lot of trial and error. I did it mostly for fun, I had the hardware, my homelab did not really benefit from it and I knew that beforehand. Please don’t take this the wrong way, but based on your questions it is not entirely obvious that you know if link aggregation will benefit you enough to warrant the trouble. Just switching to the Intel NIC from the Realtek NIC would be nice now that you have it. Why do you want link aggregation? Which problem/problems do you think it will solve? What will it improve? In the meantime, if you insist on going through with it — How about getting a free trial of some streaming service with content your partner is happy with to buy some time to tinker with the switch and your server? If you make a backup of the configuration you can go back to the current state of affairs with ease, no borking the whole thing for days. If you can’t get it working in 20 minutes, just revert to the previous configuration and use what you’ve learned to prepare for a new attempt some other time. If you can use GUI mode on the server things should go smoother during trial and error.

The Video Encode and Decode GPU Support Matrix is not listing decoding support for h.265 on GTX 970. https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new

There are NVMe drives that can sustain high speeds indefinitely and plenty that can handle four gigabyte. What size and model do you have?

Just keep in mind that this does virtually nothing to prevent the scenario described in the first post. Sure, the flash drive can’t be removed, but all the bad guy has to do is to bring a laptop and the passwords are toast.

Hey now, you’re not “so dumb on all this”. You’re learning, you’ve spotted a potential problem, you’re wise to ask about it, the question ended up in a very suitable place, and from the looks of it you correctly followed the given additional instruction. You’re going to do great! Unfortunately I’m not in front of a computer right now so I can’t take a closer look at the diagnostics. Hopefully someone else will get to it soon!

What motherboard/BIOS do you have? As for a workaround, can’t you just stick with UTC in the BIOS and adjust the wakeup time 8 hours instead?

That is not a problem with the file system, the disk needs to be rebuilt. I’m a bit rusty so I don’t dare provide instructions for that at the moment.

As @itimpi wrote better and more elaborated, the missing disk is emulated and the system continues to operate as if it were present. The system is indeed putting data on it, most likely you have high-water configured as the allocation method and that’s why writes are going to that disk. Move the data away from Disk 1 to the disk you want to keep (Disk 3) and follow the linked procedure to properly have Disk 1 (and why not Disk 2?) removed from the system. With the sizes of today’s drives, 3.02 GB is practically nothing. That amount of usage on an empty disk is typically just overhead related to the file system. If you don’t trust the drives, update them or retire them.

Never seen anyone go for a block size of 5G before, that’s literally orders of magnitude larger than commonly seen... How about a reasonable block size and increased count to match instead?

SMB is the way to go for modern Mac OS, yeah. Shouldn't really need any special configuration though. Have you created any shares via the unraid ui?

Perfectly normal. It is simply not mover's responsibility to manage your completed downloads. Need another tool for that.

Just Windows displaying TiB while calling it TB... 1 TB = 1 000 000 000 000 bytes 1 TiB = 1 099 511 627 776 bytes

For completeness - How fast are writes to the parity protected array (for a share not using cache)? When you do the write tests, what are you writing? (number of files, total size of data). I would expect all writes over the network to occur at line speed until the RAM buffer on the server is full, and you do have plenty of RAM.

For completeness - How fast are writes to the parity protected array (for a share not using cache)? When you do the write tests, what are you writing? (number of files, total size of data). I would expect all writes over the network to occur at line speed until the RAM buffer on the server is full, and you do have plenty of RAM.

Maybe, maybe not. Not entirely implausible. Wouldn't it be easy to test by just temporarily block outside access and see if it helps?

How did you move the files? Have you checked the size of the files after the move?

See Linux ate my RAM.

Are you logging in as root?

No worries Given the limited number of writes to the flash drive during normal use I don’t think SLC vs MLC will actually make a difference. That said, I would expect a better designed drive with quality components to be more reliable (and more expensive) than a really cheap one. So far I’ve use models recommended by Limetech and been lucky enough to not have one fail. Failure wouldn’t be a major inconvenience to me actually, thanks to the automated key replacement process. I would just grab a replacement drive (they’re cheap so I already have an extra), restore the most recent backup and be up and running within minutes.

The stick needs to have a unique GUID. Where did you read about "a individual serial number"?

...and B is not the same as b

670.71GiB is more or less 720GB. :-)

It does a clear, simple as that. The drive needs to be all zeros to be added to a parity protected array. The difference is that nowadays it is cleared in the background, while older versions kept the array offline until the clear was completed. A pre-cleared drive can be formatted and used really really soon after adding it (since it is already cleared).

Not saying you're wrong, just some thoughts about what I would do in a similar situation: :-) Is your old NAS fast or slow? If it is slow, I would have step 2 create a new array with parity. If it is fast, I would add the parity after step 4. For step 4, I would copy the files rather than move them, and when parity is in place verify that all files were written correctly. I usually have checksums for static files, so for me it is quite straightforward to verify files. Yes, I am quite paranoid...