kadajawi

Members
  • Posts

    6
  • Joined

  • Last visited

Recent Profile Visitors

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

kadajawi's Achievements

Noob

Noob (1/14)

0

Reputation

  1. For me besides the memory leak which I can live with if I must I also have the issue that just specific "drives" crash when Backblaze is trying to access too many files from it (it seems). Like, the drive gives me I/O errors. Any idea where that may come from? I'm using the rust version 1.7.0 (want to update to 1.8.0 when I find the time). Removing <memoryBacking> <nosharepages/> <source type='memfd'/> <access mode='shared'/> </memoryBacking> won't work as Unraid will complain then. I was able to fix this with updating the Virtio drivers and WinFSP.
  2. According to that Github page, "--inode-file-handles=mandatory" should work. I'd like to try, but I just don't know how to enter it in the XML...
  3. I have one that worked well for me for a couple of months. I had repasted the heatsink and had a 120mm fan in the side panel slowly blow air towards it. My system started to give me some trouble though (seems like a faulty HDMI cable was at least part of the problem), and while trying to figure out what was wrong I ran the system for a couple of minutes without heatsink. I got the buzzer, but not knowing what was happening I failed to turn it off immediately. This happened twice. Now the system boots fine, unless I have the card installed. Then I'm getting "Controller failed to load utility. Press any key to Exit." With drives connected I get a couple of error messages (BlockIO-Command Failed and LBA out of range), but I can't get into the BIOS for example where I could tell it to work in HBA mode. The system stops booting at this point. (Also without drives connected, just without the error messages). I can't enter the BIOS. Next up I'll try the card in another system, but I suppose it's gone. I can only say, keep it cool. And that means plenty of airflow. It gets really hot. (Any alternatives that support 16 drives or more and won't bankrupt me?)
  4. Thanks. I got it to work as you recommended, though I had to remove flock and posix_lock from the arguments. Will see if it crashes again or not. I hope those arguments aren't there for a good reason...?
  5. There is a memory leak (happening with the latest VirtioFS driver too, in combination with WinFSP 2022). Give it enough memory and reboot the VM once in a while before the memory is full, that should help until someone figures out a fix. The memory fills up as files are accessed it seems... I'm having worse issues though... VirtioFS just appears to be crashing. Used to work, but now after a short while the mounted drive just appears as empty. Any idea what could be wrong? Any fix? I tried installing WinFSP 2023, but that didn't help. https://github.com/virtio-win/kvm-guest-drivers-windows/issues/776 Someone seems to have the same problem. Can't get the solution to work though.
  6. I'd like 2 arrays because there's data that absolutely needs protection and resides on a couple of 18 TB drives, and data that I can do without if necessary (mostly 3-6 TB drives). Those smaller drives are older, they may not last forever (surely they won't). Now I do not feel comfortable having something like 14 drives with 1 parity drive, especially if some of the disks may very well die at a similar time. Even if I had two 18 TB drives for parity (which does cost a bit), I do not feel too comfortable. Two arrays would let me split those up. Maybe the smaller drives will also be parity protected by one of the smaller drives, but it's fewer drives, which should reduce the risk a bit...