Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About Nischi

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. I haven't updated in a while, and it fixed the problem just as you suspected. thanks again!
  2. Would it be possible to give it a try to fix the previous problem with borg? qouting myself earlier in the thread to give a few details. I'm not sure where to start, but perhaps updating msgpack, setuptools and Python3 might help?
  3. And now 6.7.2 came out as well. Gonna wait to upgrade until this plugin is updated as well. great job by the way CHBMB!
  4. Having the same problem with "Bus 005 Device 002: ID 046d:08c9 Logitech, Inc. QuickCam Ultra Vision" Did you ever get it to work? My /dev/ does not seem to have any usb for this camera as well, can find it under /dev/bus/usb/ tho, but that's not working to passthrough to the docker.
  5. Sorry must have missed your reply, just noticed it now. Anyway, no I haven't been able to fix it. I tried manually installing the Slackware packages, but i never managed to get it fully working. I think we probably need to update some of the other 3 packages for it to run correctly.
  6. Could you please add FuseISO https://sourceforge.net/projects/fuseiso/ ?
  7. As mentioned earlier, you need msgpack, setuptools and Python3 However, that will lately result in the message "Using a pure-python msgpack! This will result in lower performance." when running backups. From what I can tell, it will only use 1 core, thus slowing down backups quite a lot.
  8. You need msgpack, setuptools and Python3 That was it, thanks!
  9. Hi again! Lately I'm having problems launching borg. I'm running Unraid 6.7.0-rc5, so I guess that could be the issue. Anyway, I get the following error when simply running "borg" root@unraid:~# borg Traceback (most recent call last): File "/usr/bin/borg", line 6, in <module> from pkg_resources import load_entry_point ModuleNotFoundError: No module named 'pkg_resources' Oh and thanks for adding fish shell earlier
  10. Thanks for the links to that thread, really insightful. My version info: modinfo mpt3sas filename: /lib/modules/4.19.24-Unraid/kernel/drivers/scsi/mpt3sas/mpt3sas.ko.xz alias: mpt2sas version: Also tried some commands from the mentioned thread. root@unraid:~# hdparm -I /dev/sdm | grep TRIM * Data Set Management TRIM supported (limit 8 blocks) * Deterministic read ZEROs after TRIM root@unraid:~# hdparm -I /dev/sdj | grep TRIM * Data Set Management TRIM supported (limit 1 block) * Deterministic read data after TRIM root@unraid:~# hdparm -I /dev/sdl | grep TRIM * Data Set Management TRIM supported (limit 8 blocks) root@unraid:~# hdparm -I /dev/sdk | grep TRIM * Data Set Management TRIM supported (limit 1 block) * Deterministic read data after TRIM root@unraid:~# fstrim -av /etc/libvirt: 926.5 MiB (971513856 bytes) trimmed on /dev/loop3 /var/lib/docker: 13.7 GiB (14724616192 bytes) trimmed on /dev/loop2 fstrim: /mnt/cache: FITRIM ioctl failed: Remote I/O error The reason I say only the intel doesn't work is because the unraid logs only mentions the intel one(sdj) as having problems. Feb 25 16:50:01 unraid kernel: print_req_error: critical target error, dev sdj, sector 232785982 Feb 25 16:50:01 unraid kernel: BTRFS warning (device sdj1): failed to trim 1 device(s), last error -121 I see that the /mnt/cache/ is mounted from /dev/sdj1. could that be why it complains about sdj above? Thought it would have said sdj1 on both errors. Seems like it's time to look for one of those 9300-8i soon. Thanks for your help.
  11. Got the same problem. And I get an email with the error "fstrim: /mnt/cache: FITRIM ioctl failed: Remote I/O error" from the server everytime the trim is scheduled to run. But the thing is that I have 4 SSDs on the same HBA, and 3 of them runs trim without a hatch. The faulty one is an INTEL SSDSC2BW120H6 120G drive. One note is that I did upgrade the firmware of my Logic SAS2308 PCI-Express Fusion-MPT SAS-2, and it was after that that the problems started occurring. I have no clue what to do about this, not to keen on flashing back to old firmware either >.> unraid-diagnostics-20190225-0007.zip
  12. This is still true, yes? I'm having issues manually specifying the VNC port to use. I followed these instructions https://www.reddit.com/r/unRAID/comments/44sftz/vnc_configuration/ This is my XML edit: <graphics type='vnc' port='5901' autoport='no' websocket='5901' listen='' keymap='sv'> <listen type='address' address=''/> </graphics> But always end up with the error "Execution error. internal error: Failed to reserve port 5901" when I try to start the VM.
  13. Ok I updated unrar booya! it's working. Thanks for your help, much appreciated.
  14. Try installing unrar Same error sadly. Working for you ?