cyberspectre

Members
  • Posts

    111
  • Joined

  • Last visited

Posts 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.

     

     

    Screenshot 2022-08-11 172320.png

  3. 1 hour ago, Outer_Zevin said:

     

    Thank you for reaching out! My cache drive is a Samsung 970 EVO and when I reformatted the drive earlier in the thread I kept it as XFS just to see what how things went. It definitely lasted longer between problems. How did you go about diagnosing that problem? If memtest gets me no where I will definitely be interested in following up with that.

     

    My current RAM is 2x sticks of 16gb Crucial DDR4 unbuffered ECC RAM though. Same brand as your junked SSD. No idea if that means anything.

     

    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. On 1/2/2022 at 6:38 AM, Outer_Zevin said:

    Okay, I had another problem this morning, the server didn't hang up, I was able to log into the gui and managed to shut down the server from there. All Docker containers showed as stopped with generic icons and no container names. I attached the logs from today below, it seems there was an error with my cache drive or possibly my memory? I'm no expert at reading these things yet, but I did find this thread while googling.

     


    If anyone has any input, it is greatly appreciated. If I have to reformat my NVME drive, I'm fine, the only things on there I'd be broken up about losing is backed up on the array and elsewhere.

     

     

    syslogs01022022.txt 56.53 kB · 3 downloads

     

    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. 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!

  6. 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)

    • Like 1
  7. 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?

  8. 5 hours ago, cyberspectre said:

     

    Which version of Q35 let you successfully install the Radeon software? I'm getting incompatibility messages from the installer on Q35 5.1.

     

    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

     

  9. On 1/30/2021 at 4:04 PM, zeus83 said:

    I've decided to put it here because just spent several hours trying to figure out AMD Radeon 6800XT passthrough to my Win 10 VM.

    Previously I've only worked with Nvidia gpus and experienced zero issues with them. Radeon a bit different story.

     

    I'm running unraid on Ryzen 5950X Asus Crosshair VIII Hero. The GPU is Gigabyte Radeon 6800XT (ref). So not all tips may be relevant to your hardware/software.

     

    So the hints are:

    1. BIOS: disable CSM compatibility mode and leave only UEFI. I couldn't get GPU passed through in Legacy mode.
    2. Only use Q35 virtual machine. i440fx didn't worked for me. Couldn't install a driver.
    3. Don't install amdgpu host drivers. Couldn't pass through the GPU to VM in that case.
    4. Passthrough didn't work on unRAID 6.8 for me (got error 43 always). So I had to switch to unRAID 6.9rc2 on 5.10 kernel.
    5. For 6800XT passthrough four devices:187035181_.thumb.PNG.f73ab2e588f91dc4ddf074364e75f030.PNG
    6. Enabling the AMD Smart Access Memory (SAM) didn't work for me. Got error 43 in windows vm immediately (seems like it's not yet implemented and exposed in vfio https://github.com/qemu/qemu/commit/3412d8ec9810b819f8b79e8e0c6b87217c876e32).
    7. Encoding delay in Parsec is awful > 20 ms (h.265, 1440p). Something wrong with driver/encoder I think. Didn't figure out what's wrong yet, but saw someone complains on reddit about it as well.

     

    Which version of Q35 let you successfully install the Radeon software? I'm getting incompatibility messages from the installer on Q35 5.1.

  10. On 1/30/2021 at 4:04 PM, zeus83 said:

    I've decided to put it here because just spent several hours trying to figure out AMD Radeon 6800XT passthrough to my Win 10 VM.

    Previously I've only worked with Nvidia gpus and experienced zero issues with them. Radeon a bit different story.

     

    I'm running unraid on Ryzen 5950X Asus Crosshair VIII Hero. The GPU is Gigabyte Radeon 6800XT (ref). So not all tips may be relevant to your hardware/software.

     

    So the hints are:

    1. BIOS: disable CSM compatibility mode and leave only UEFI. I couldn't get GPU passed through in Legacy mode.
    2. Only use Q35 virtual machine. i440fx didn't worked for me. Couldn't install a driver.
    3. Don't install amdgpu host drivers. Couldn't pass through the GPU to VM in that case.
    4. Passthrough didn't work on unRAID 6.8 for me (got error 43 always). So I had to switch to unRAID 6.9rc2 on 5.10 kernel.
    5. For 6800XT passthrough four devices:187035181_.thumb.PNG.f73ab2e588f91dc4ddf074364e75f030.PNG
    6. Enabling the AMD Smart Access Memory (SAM) didn't work for me. Got error 43 in windows vm immediately.
    7. Encoding delay in Parsec is awful > 20 ms (h.265, 1440p). Something wrong with driver/encoder I think. Didn't figure out what's wrong yet, but saw someone complains on reddit about it as well.

     

    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.

  11. On 1/4/2021 at 1:17 PM, Mihai said:

    I'm kind of late to the party, but to me it seems the main issue is the lack of ssl certificate on port 443 and it seems lately invoiceninja enforces https.

    I got it working by generating a self signed certificate.

    I didn't have time to create another Unraid app, but until then if anyone wants to try it out:

    Hit Edit on the container and change Repository field to this: maihai/invoiceninja and then hit Apply.

    EDIT: The way this works is that it generates a SSL certificate on the first container run which is self signed. Of course don't forget to import this certificate in your browser otherwise you will be at risk of MITM.

     

    image.thumb.png.a489af023b121b183a9c0ec85cc8e345.png

     

     

    If you're paranoid like me, you can find the code here: https://github.com/mihai-cindea/invoiceninja

    Feel free to tell me if you have any issues or requests. I also want to add the possibility of feeding custom certificates and generate the certificate CN based on the APP_URL. Currently this is a PoC.

    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.

    • Like 1
  12. 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. 

    • Like 1
  13. 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.

  14. On 5/28/2020 at 1:14 AM, johnnie.black said:

    Look for a bios update or try a different NVMe device. 

    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.

  15. On 7/24/2019 at 10:31 AM, CyberMew said:

    Thanks, pretty sure it's already screwed down tight a couple months ago, but will still double check the screw in case it somehow came loose. 

     

    So far it's been running for 24 hours and all seems to be fine 🤞Let's see what happens during the next parity check next month..that's when the read/drive errors will usually appear again

    Did you ever discover what was wrong? I'm having the same issue as we speak.

  16. 19 hours ago, johnnie.black said:

    This can sometimes help with those NVMe errors:

     

    Some NVMe devices have issues with power states on Linux, try this, on the main GUI page click on flash, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (on the top right) and add this to your default boot option, after "append"

     

    
    nvme_core.default_ps_max_latency_us=0

     

    Reboot and see if it makes a difference.

    Thanks, I've done so. Seems to be working normally now. I'll report back if I have more issues.