Jump to content

Froberg

Members
  • Content Count

    118
  • Joined

  • Last visited

Community Reputation

4 Neutral

About Froberg

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I've used Resilio way back to sync my data from my primary box to a secondary NAS. I've recently purchased a SOC motherboard and set up another home NAS to replicate this. Unfortunately, resilio seems content to sit at around 120mb/s. If I disable tracker options and set it to use LAN only, it does nothing. I've tried fiddling with the power user settings, encryption to see if that was the overhead and whatever else I can think of. Any ideas? Both boxes have dual gigabit NICs and should be able to at least get gigabit for the transfers. It will get there.. eventually.. of course, but the idea was to turn on the backup box for a few days a month to get synced and to run a parity check and otherwise keep it spun down. Any suggestions as to where I might be wise to look? They're both set to bridge on the respective docker containers, would host maybe have an impact? Solved it myself; Setting the share on the receiving box to forced LAN and changing the docker containers on both sides to host mode proved to drastically increase speed.
  2. NVME without active cooling would be a concern and could be the cause of instability. Those bastards can get toasty really quickly.
  3. Are there any differences in bridgemode/host network configuration for the dockers? i.e.:
  4. Not sure why you'd mix a spinning disk and a 500GB SSD and expect speed... but what's the file system on there? Sounds like you didn't set it up for RAID1 maybe, if all data is inaccessible?
  5. I have not messed with this, so take it with a grain of salt, but one option would be to split up your shares so that the normal file-shares only use spinning disks and your SSD's only encompass the VM shares. It's a bit more manual, but should allow you to make sure where the VM data is located. Again I say should because I don't think this would be considered best practice.
  6. Sounds like my origin story, too, almost all of it. My computer was far shittier though and came with Windows ME. I remember one time fiddling with screen refresh rates, not knowing how they worked, and being unable to use the computer. My mom was NOT happy, lmao. Figured it out, because that's how you learn, but man was I worried because it was so expensive. My second one was an Athlon XP 1800 I believe. Massive upgrade!
  7. Your age is showing! My first system was a 443mhz! (To be fair, did start with windows 3.1 in school, but yeah) In Denmark we call laptops that are heavy for "luggables". This seems to fall in to that category.
  8. Even during my time in IT it's incredible to witness. I remember saving stuff to floppy drives, even splitting up .zip's if they were over capacity. Zip drives! When a 700MB CD was groundbreaking. I am getting old.
  9. It's probably going to happen eventually. Hoping transfer speeds go up too in that case.
  10. Now you just need to get the rest to 14 TB and you'll be on your way to .5!
  11. Doesn't the PSU come with the case, as in, 45Drives made sure of this?
  12. Actually to be fair, one of the best bits of mass was in the third one. That DLC where you were running around the citadel with your entire party and fighting your own clone. That had real bioware magic. (and Boo!) Personally Baldurs Gate series trumps ME for sheer storytelling. Isometric is so underrated. I haven't even bothered with Andromeda just out of sheer disappointment.
  13. I believe he mentioned using Storinators. Clearly falcon, other than a good taste in games (at least the two out of three) has seen too much Linus Tech Tips. https://www.45drives.com/products/storage/
  14. If I may suggest something; try running it trough WD Lifeguard and do an erase and then a full extended test. Try it again after that. I've had success in repurposing "failed" drives for my backup box this way. One has been running another few years since 'failing' originally. I just don't take any chances with my production server. I dunno, it's just worked for me a lot, and it's only like 12-14 hours to run it through in an external dock.
  15. Try reseating them first. Usually if you buy memory you buy a pair. I'd recommend getting a new pair in this case. Otherwise, test them one at a time if you can live with half capacity. I would not recommend buying "similar" memory and dropping it in, as that has been known to cause weird issues.