gubbgnutten

Members
  • Posts

    369
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • Location
    Storskogen
  • Personal Text
    Romulan ale should be illegal!

Recent Profile Visitors

1214 profile views

gubbgnutten's Achievements

Contributor

Contributor (5/14)

19

Reputation

  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"?