gubbgnutten

Members
  • Posts

    369
  • Joined

  • Last visited

Everything posted by gubbgnutten

  1. 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.
  2. 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?
  3. 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?
  4. Perfectly normal. It is simply not mover's responsibility to manage your completed downloads. Need another tool for that.
  5. Just Windows displaying TiB while calling it TB... 1 TB = 1 000 000 000 000 bytes 1 TiB = 1 099 511 627 776 bytes
  6. 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.
  7. 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.
  8. Maybe, maybe not. Not entirely implausible. Wouldn't it be easy to test by just temporarily block outside access and see if it helps?
  9. How did you move the files? Have you checked the size of the files after the move?
  10. 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.
  11. The stick needs to have a unique GUID. Where did you read about "a individual serial number"?
  12. 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).
  13. 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...
  14. Unfortunately only applies to expansion as far as I know.
  15. Yes, the two parity drives can be different sizes as long as both are at least as large as the largest data drive (as usual).
  16. If you add a pre-cleared drive it will be added to the array more or less instantaneously instead of cleared in the background and then added.
  17. Thank you, most appreciated. Will make sure to remember that when I get around to finishing my dual cpu server...
  18. That is only a summary of the current view, though, without taking contents of the folders into consideration.
  19. Not the same numbers of folders or files, check the circled numbers... Check the contents of the sub folders, maybe you accidentally copied everything twice or something?
  20. Start a new thread and attach your diagnostics zip as retrieved after writing to the array and we’ll have a look at it.
  21. The first part of the transfer is cached in RAM, you are not writing to the actual disks that fast.