cyberspectre

Members
  • Posts

    111
  • Joined

  • Last visited

Everything posted by cyberspectre

  1. Hi Unraid community, I recently signed on with Zoho One because it makes sense for my small business, especially since it includes a decent amount of storage space that my customers can access, too. My question is, how can I sync my UnRaid shares with Workdrive? Rclone has a connector for it, but for all intents and purposes, it isn't functional, because it hits the rate limit after just 4-6 files. Zoho support tells me this is because Rclone doesn't use the right API calls. That leaves just Zoho's own app, which is a desktop client with no CLI options. Any ideas for how to automate backup / sync from my UnRaid server?
  2. My 8-month-old 870 Evo has suddenly started reallocating sectors on a daily basis. 39 reallocated so far. Is this something I should get warrantied by Samsung? Or is this normal behavior? The 850 Evo and 860 Evo in my system are older with more reads, writes, and uptime, but both have 0 reallocated sectors.
  3. You've got a 970 Evo formatted XFS and you're still getting that issue? I don't have much to add, then. Controller thermals could still be part of the issue, possibly. You can keep an eye on it in your terminal with: watch -n 0.1 nvme smart-log /dev/nvme0 The reading for the NAND itself is different from the controller's, which is where the drive gets hottest. Look at temperature sensor 2. Mine goes to 65-70 C pretty regularly, but still doesn't cause problems. It usually doesn't even throttle. With regard to your memory, I doubt the brand makes a difference. But if memtest picks up a fault, start pulling one DIMM at a time and re-running memtest until no faults appear.
  4. I'm the OP in that thread. There was another thread after that, in which I determined the lockups were occurring when the temperature of the NVME SSD's onboard controller exceeded about 60 degrees celcius. The SSD was a Crucial P1. I threw it in the garbage and replaced it with a Samsung 970 Evo, haven't had a single problem since. I'm also using XFS on the cache drive now, not BTRFS.
  5. Very, very cool. I love the desk PC idea. Sadly, it wouldn't work for me. I like to sit really close to the desk.
  6. Here's something I discovered recently that may help you decide what not to do. Steam Link (both the physical device and the app) somehow ties to the NIC itself. So, if you're running multiple VMs with a bridge, it won't be able to tell them apart. I have to exit Steam on one VM in order to use Steam Link with the other.
  7. Mine always starts in the wrong time zone, and I have a task scheduler entry to sync with NTP to fix this. But I've never heard of the clock actually losing time.
  8. I'm almost finished with my newest PC build, a 2-gamers-1-pc + NAS powered by UnRaid. As a nice touch, I had wanted to put two Raspberry Pi displays inside the case to monitor the system metrics — mainly the GPU temps, but also memory usage and more — of each Windows VM. Two softwares exist for this purpose: ModBros MoBro Monitor and Trigone System Monitor. But after a few minutes running either one, my entire server crashes hard. I suspect they're probing for some sensor or device that isn't emulated by KVM. Not sure if this is specific to my hardware or common to all KVM virtual machines. Does anyone have a possible solution? Thanks!
  9. You guys, this is the weirdest thing. My UnRaid server has a 6800 and a 6800XT. Both have been working perfectly since February. Yesterday, I installed water blocks on both cards. Since I did that, now, reset doesn't work anymore. If I reboot the VM, the display doesn't come back, and one CPU thread assigned to the VM gets stuck at around 87%. Changing the cooler on these cards couldn't possibly cause this, right? The only other thing I did was install an NVME SSD in the M.2 slot. Do you think that could cause reset to fail for both cards? Edit: False alarm. It was because the new SSD changed the IOMMU groups and for some reason, UnRaid stopped stubbing the serial bus controller for each card. This was causing reset to not work. Just in case anyone needs to know, or in case I forget this again (lol), these are the devices that need to be passed through for an AMD reference card. Obviously, your PCIe IDs will be different. AMD Radeon RX 6800/6800 XT / 6900 XT (0a:00.0) AMD Device (0a:00.1) <--- sound card AMD Device | USB controller (0a:00.2) AMD Device | Serial bus controller (0a:00.3)
  10. Looks like a good plan. You know, I've got a 970 and two matching water blocks for it. If you decide to water-cool your build, DM me. I'd gladly give you these things for cheap so you could have two 970s in there.
  11. Awesome rig, man! Now that you're on UnRaid, I can promise you'll never go back to not using it. It makes so much sense to put your machine's extra muscle to work for you instead of letting it go unused in Windows. Your build actually looks similar to my last one, though with much better hardware. That 5950X is making me feel kinda jelly, I passed on that and did a 3900X in my new rig. Mine's got soft black tubing, too, not to mention purple lighting. We have similar tastes. Which flow meter is that?
  12. Months after replacing the Crucial drive with a Samsung 970 Evo, I'm pleased to say this issue has not happened since. Not even once. The Samsung doesn't miss a beat.
  13. Nevermind, got it working on Q35 5.0. Very pleased so far. For posterity, let me say this. It required all of the things the OP mentioned + an extra kernel argument to make my GTX-970 work again after switching to UEFI mode. That kernel argument is... video=efifb:off
  14. Which version of Q35 let you successfully install the Radeon software? I'm getting incompatibility messages from the installer on Q35 5.1.
  15. Thanks for this. I happen to be doing the same thing right now, so your post has great timing. I'll try the things you suggested and see if I get anywhere. Should have known it wouldn't be easy... but the card came highly recommended by Level 1 Techs, so I was hopeful.
  16. I just get "Whoops, looks like something went wrong."
  17. Unfortunately, this doesn't work for me. In case anyone's interested, I found a different free invoice software that can be used in a Docker container. It's called Crater. There isn't a pre-made image for it on DockerHub, though, so, despite messing with it for an hour or two, I have no idea how to install it... They provide instructions but I'm nervous about following them instead of using the UnRaid UI.
  18. Very cool! Now, if only we could have auto checkout. 🤩
  19. Unfortunately, the issue has resurfaced. It is certainly connected to the temperature of the controller. Moving the SSD away from the graphics cards and installing a heat sink did help, but ultimately did not eliminate the problem. Certain activities can cause the temperature of the controller to spike suddenly, and when it does, it's lights out. To anyone who reads this in the future, do not buy a Crucial P1 NVME SSD for UnRaid, or for a gaming PC for that matter. It cannot tolerate even moderate heat.
  20. For posterity, I'd like to report that I solved the problem. Using the smartctl / nvme, I discovered that even though the disk's main temperature was within the acceptable range, one of the disk's secondary temperature sensors (labeled Temperature Sensor 5) was reading 60-64c at idle and 70c or higher under load. This is most likely the temperature of the controller. Apparently, most nvme controllers begin throttling at 70c, so the I/O errors make sense. I moved the disk from the M.2 slot to a PCI-e adapter and installed a metal heatsink. The controller now runs 20 degrees cooler on average, and I haven't experienced any more issues. When it's right behind a graphics card, an M.2 slot is apparently not an ideal thermal environment for an SSD.
  21. Thanks johnnie.black. Updating the firmware seemed promising at first, but ultimately made no difference. Since it's clear to me now that this is an issue with the disk itself, I'm going to make a new thread in hardware to get some more opinions.
  22. Did you ever discover what was wrong? I'm having the same issue as we speak.
  23. Nope, it's still happening. Seems to be that whenever it seems stable with a VM running, all I need to do is start a few docker containers and that will cause it to fail. Basically, heavier I/O causes it.
  24. Thanks, I've done so. Seems to be working normally now. I'll report back if I have more issues.