dedi

Members
  • Posts

    34
  • Joined

  • Last visited

Everything posted by dedi

  1. Newly created cover and metadata files have read only permissions for root/root. -rw-r--r-- 1 root root cover.jpg -rw-r--r-- 1 root root metadata.json Can that be fixed somehow?
  2. Thanks, that was as issue for me too, and this fixed it. (appdata\plex\Library\Application Support\Plex Media Server\Codecs)
  3. It is really hard to find even after I googled to this thread and it feels misplaced
  4. Hi! A bit late to the topic but here is what I experienced: I have a WDC WD60EFRX-68MYMN1 hard drive that has been causing problems for 5 years (when I started using unraid). Although I've tried troubleshooting it a few times, I haven't found any solutions. Initially, I thought the drive might be failing or there was something wrong with my setup, so I started using it as an additional parity drive. However, it always starts to count errors after running for a while, although all parity checks and extended SMART tests have been successful over the years. I recently upgraded my unraid server and am now using a SAS card, but the drive continues to exhibit the same behavior. Additionally, it sometimes gets disabled after running for 1-3 weeks. Once, it happened exactly when I clicked on the spin-up/spin-down button, so I'm not sure if this is related to the spinning state. I've tried switching cables and controllers, but it hasn't made a difference. WDC WD60EFRX-68MYMN1 log.txt
  5. I had the same thought. Also it's not really true that all files within that location will be deleted. I have existing backups as well as custom folders and files there, they all stay fine. Only thing ever getting overwritten there are the contents of subfolders caBackupUSBStick and caBackupVM/libvirt.img when running a backup.
  6. The NICs for eth0 and eth1 are switching around on boots, making it sometimes unreachable from the network. I'm running Unraid on proxmox, when running correctly eth0 is on proxmox br0, eth1 is my 10G card with PCIe passtrough. I do not have any option in the network config to specifically assign the NICs. I also don't have a network-rules.cfg, if I create one it gets removed on reboot. diagnostics-20221205-1809.zip
  7. Can confirm, backing up subfolders works great now. Thank you!
  8. Thanks for all your effort! Just as a thought: adding single folder names in addition to full paths would be a nice solution too that would give a better overview (and maybe is not a lot more work to implement). A bigger/scaling input field is an other idea.
  9. Yes, that is the case. I use it a lot since there is a lot of diskspace hungry stuff that does not need to get backed up. (The UI isn't great to add these, that's why I edit it in notepad.)
  10. That is not working here, still creates full backups. (All data are on cache only). I tried to switch "Appdata Share (Source):" to /mnt/cache/appdata too but that also didn't help.
  11. Hi! Switched to the new fork, re-entered all config options, enabled "Create separate archives (one per folder)." It's now ignoring my list of excluded subfolders. Whole apps are still getting excluded, but I have a lot of cache/thumbnails/metadata folders that grow the backups way too big. (This was working before.)
  12. I switched today from another nzbget vpn docker. Whatever I configure for LAN_NETWORK makes exactly that network not working. Only when VPN is activated. I do have 2 IPs for my unraid. if I configure like that: 192.168.200.0/24,192.168.0.0/24, then I can't connect at all. If I only use one, the other one is working. If I enter something totally unrelated, then it works on both IPs. Also sonarr/radarr docker can't connect. Tried both wireguard and openvpn. If I disable VPN fully it works. And sonarr/radar are able to connect then. I also started a new docker from scratch with only minimal changes and it still happens. This does also happen with dyonr/jackettvpn. Other docker with vpn and similar network setting do work. Any clue what is wrong? log: https://pastebin.com/HTujsyhb
  13. Same here. Will wait for an update Edit: Thanks, all working now
  14. I was running the preview of v3 for some weeks without problems. Recently the preview tag got deprecated, so I removed it. Suddenly I was back to v2 and all settings gone. I changed the tag specifically to "latest" and with a force update I had v3 installed with all settings restored. Weird but it worked.
  15. Ohhh i totally forget that I added the post arguments and must have overlooked that.
  16. Suddenly can't make changes to the docker configuration via UI anymore: Was running fine before. Can still start/stop. Does it have something to do with NC 19 beeing released?
  17. I have a CSR Bluetooth dongle (Cambridge Silicon Radio Bluetooth Dongle) that I want to pass trough to a Home Assistant VM, I can select it in the VM config but hassos does not find the device there, Is that because firmware for CSR BT dongles are missing?
  18. After the reboot the names changed because I switched USB ports. I think it was sdm then.
  19. I did reseat it multiple times. But it would be a hell of a coincidence since nothing got touched, I only did the upgrade and the reboot. The disc is hosting my home assistant VM, so I would have noticed if there were problems anytime before bacause I use that daily. My windows machine shows the disc and the partition. The unraid does not even show a partition (no /dev/sdm1, only sdm). Update: on my osmc media box it got mounted without an issue.
  20. Nov 20 17:19:52 DedNAS kernel: blk_update_request: critical target error, dev sdc, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Nov 20 17:19:52 DedNAS kernel: Buffer I/O error on dev sdc, logical block 0, async page read I upgraded from 6.7.2 to 6.8.0 RC6 and my 120GB SSD - connected via USB-SATA adapter and running it as unassigned device - started to fail with the above error. It was running over a year without problems. I reverted back to 6.7.2 and the problem REMAINS. I tried reboots and different USB Ports. Maybe it's coincidence but since I saw some others reporting I/O errors I thought I report it. Diagnostics is done with 6.7.2 unraid-diagnostics-20191120-2057.zip
  21. I got the same problem with a VM running home assistant (hassio). Can't figure out if its a unraid or hassio problem. If its a VM with the dongle passed trough, it should not matter if unraid has drivers? I also tried the current beta of unraid. Any ideas?
  22. Another quick update: I had absolutely no problems anymore.
  23. I'm at 10d uptime on 6.6.3 and no problems so far.