dedi

Members
  • Posts

    34
  • Joined

  • Last visited

Posts posted by dedi

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

  2. 9 minutes ago, flyize said:

    Shouldn't it just say: 

    Warning: All files within /mnt/user/backups/appdata backup/ will be overwritten / deleted during a backup process!

    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.

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

  4. 2 minutes ago, KluthR said:

    Okay. As said, I will look into this later this day. Stay tuned!

     

    Maybe I can get the file selector to also offer subfolders (in an even newer release in the future).

    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.

    • Like 1
  5. 40 minutes ago, KluthR said:

     It seems, that you manually typed in deeper levels of exclusion, is that right? And yes, that case is currently ignored. I never thought someone will use it that way (just because, the UI does not offer it directly). 😁

    However, if this confirms to be the case, I will - of course - fix this behavior! (later today)

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

    • Upvote 1
  6. 19 minutes ago, Hawkins said:

    Try changing the exclude paths from /mnt/user/appdata/foo/bar/ to /mnt/cache/appdata/foo/bar/.

    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.

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

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

  9. 23 hours ago, DogeKitteh007 said:

    Hello,

     

    It is I.. again. 😄

     

    Issue: https://github.com/nzbget/nzbget/issues/784#issuecomment-931609658

     

    Is it necessary to update the container? I've fixed mine.

     

    edit: I have not fixed mine. 😛

     

    Just putting this out there in case an update is needed. nzbget could no longer connect to news server today because of this issue with certificate.


    Same here. Will wait for an update :)

    Edit: Thanks, all working now :)

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

    • Like 1
  11. On 9/9/2020 at 4:31 AM, David Puziol Prata said:

     

    I have the same problem. Have you found a solution? I was reading about fake CSR and that it was necessary to recompile the Linux source code module. I can't give an UP on hci0 and it just stays on DOWN with the error Can't init device hci0: Operation not supported (95)

    Didn't found any solution, gave up :)

  12. Suddenly can't make changes to the docker configuration via UI anymore:
     

    Quote

    Stopping container: Nextcloud

    Successfully stopped container 'Nextcloud'

     

    Removing container: Nextcloud

    Successfully removed container 'Nextcloud'

     

    Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='Nextcloud' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -p '4337:80/tcp' -v '/mnt/user/appdata/nextcloud/nextcloud':'/var/www/html':'rw' -v '/mnt/user/appdata/nextcloud/apps':'/var/www/html/custom_apps':'rw' -v '/mnt/user/appdata/nextcloud/config':'/var/www/html/config':'rw' -v '/mnt/user/Cloud/':'/var/www/html/data':'rw' -v '/mnt/user/Share':'/mnt/Share':'rw' --user 99:100 --sysctl net.ipv4.ip_unprivileged_port_start=0 'nextcloud:latest' && docker exec -u 0 NAME_OF_THIS_CONTAINER /bin/sh -c 'echo "umask 000" >> /etc/apache2/envvars'

    b13d8a585c9ae8eb4874432d969b17491174ea1fab00071b1ac60dd4245e7a2f
    Error: No such container: NAME_OF_THIS_CONTAINER

    The command failed.

    Was running fine before. Can still start/stop. Does it have something to do with NC 19 beeing released?

  13. 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?

  14. Thanks, I'll keep that in mind :)

    I'm still curious, why can I connect to an IP that isn't up?
    My config:
    eth0: 192.168.0.20, after the problem I shut it down with (ifconfig eth0 down). eth1 takes over and network starts working again.
    eth1: 192.168.0.21
    On other devices on the network, I still can connect to 192.168.0.20

  15. Since a few weeks (about since 6.6.0) I'm repeatedly loosing my network connection after a uptime from one to a few days. From that moment on I get "r8169 0000:0f:00.0 eth0: link up" spamed in the syslog.
    I can manually put eth0 down and up with no success, also plugin in to another switch doesn't help. I can shut down eth0 and start using eth1, I currently have no bridging or bonding active. (A side note: isn't it strange that I can still connect to the IP of eth0 even it is down?).
    The same thing happens when I switch eth0 with eth1.

    Hardware:
    Mainboard Z68 Professional Gen3, I2500k with 2 onboard NICs (r8169),
    16 GB RAM
    Unraid 6.6.2

     

    dednas-diagnostics-20181019-1624.zip

  16. I thought I share my rsync config. I still feel like Unraid as a Storage Server should provide a build in method to backup or sync its data to an other location, but configuring rsync gives you a lot of power, and once set up, it's just great.

    I based my config and setup on the tutorial found here: https://lime-technology.com/forums/topic/52830-syncronize-servers-using-rsync-over-ssh-next-door-or-across-the-world/
    And I made some adjustments, specially the option to watch the sync going on, and the notification that works with the build in unraid notification. So on "errors" you will get a E-Mail notification if your unraid is setup for that.

    The above tutorial covers the SSH setup and connect via key instead of login, and the basic rsync setup.

    You can continue after that guide. What you need is the NerdPack Plugin, and there install "screen". It is used to run rsync in it own screen, giving you the option to pull the progress up in a console at any time.

    The second one is optional but recommended, its the "User Scripts" plugin. It allows you to add own scripts and execute it via cron in your unraid GUI.

     


    I created 2 scripts for my rsync:

    The first one I called "rsync" and does the rsync job, and depending on its exit code, it gives the notification to the Unraid Notification Service.

    #!/bin/bash
    rsync -avu --bwlimit=4000 --numeric-ids --log-file=/mnt/user/Backup/rsync-logs/log.`date '+%Y_%m_%d__%H_%M_%S'`.log --progress --exclude 'C Sys' --timeout=600 -e "ssh -p 4222 -i /root/.ssh/DSStoDMS-key  -T  -o Compression=no -x " /mnt/user/Backup/Devices/ [email protected]:/volume2/Backup/Unraid_rsync
    
    if [ $? -eq 0 ]
    then
    /usr/local/emhttp/webGui/scripts/notify -s "`hostname` to DMS Rsync Backup complete" -d "Sync compled. `date` `tail /mnt/user/Backup/rsync-logs/last.log`"
    else
    /usr/local/emhttp/webGui/scripts/notify -s "`hostname` to DMS Rsync Backup FAILED" -i "alert" -d "Sync compled. `date` `tail /mnt/user/Backup/rsync-logs/last.log`"
    fi
    

    Of course, the rsync command would need some adjustments.
    If your Unraid server is setup to send you a E-Mail on errors, it will do that too if rsync fails!


    The second one is for calling that script in a "screen" session.
     

    #!/bin/bash
    export SCREENDIR=/root/.screen
    screen -dmS rsyncdms /boot/config/plugins/user.scripts/scripts/rsync/script

    You can pull it up as long as it is running with

    screen -r

    from a console. You can  just use the build in one from the WebGUI.
    Attention, if you name the first script different than "rsync", you have to adjust this location.

     

    Now just set a schedule for the second script. Watch its progress with "rsync -r"
     


    I hope this can help somebody. Im not a rsync expert, so if anyone is around with more experience has some input, its very welcome.

    And I have a questions myself:

    I have large files to transfer, sometimes a lot of new data comes up at once. So if I have to transfer >400GB, it needs more than 24h, and the rsync backup script (which is scheduled to run daily) is started again. It starts with the files that is currently transfering in the first instance of rsync. It works, but it will transfer that big file twice. Should I check when running the script if rsync is already running? Or does running rsync with --partial do any good or bad here?

    • Like 1