b3lc

Lost 4TB+ of files, new drive to be used with xfs_undelete already in its way here... a question though: As my data is/was spread along the data array, should I run this program for every drive on the array separately? do I need to run it separately for every /dev/sd#1? or perhaps for every /dev/md#p1? it doesn't seem it would work that way but I guess I got that information wrong.. Thank you and sorry if I'm highjacking this post. It's just that I've seen people redirecting other posts to this one and didn't want to create a new one so results are consolidated.

Hello all, Two days ago I have changed my server, going from an old intel 4770k to a shiny new AMD 5600G. All went well instalation-wise and, after identifying a faulty ram, sooner than later I had my unraid server running. The problem is: it runs, even for a few minutes or half an hour, without a problem. All is there, docker, containers, vms... Then, after that it just goes unresponsive: no SSH, no Web UI, no SMB shares, no docker access, nothing. Oh, and attaching a screen to the server.. when shit hits the fan it goes to black screen. I thought the problem could be with nvidia driver, as I have a Quadro P400 to do transcoding (as the 5600G has graphics). It was not as it happened again without it. I was able to get the diagnostics, as well as logs up to the time it goes frozen using tail -f /var/logs/syslog. I don't know what else to do. The problem, at least in the syslogs, appear to start here (snipped whatever came before as it was the mover): Oct 17 01:26:30 Tank emhttpd: shcmd (288): /usr/local/sbin/mover &> /dev/null & Oct 17 01:27:01 Tank emhttpd: Starting services... Oct 17 01:27:01 Tank emhttpd: shcmd (294): /etc/rc.d/rc.samba restart Oct 17 01:27:01 Tank nmbd[3338]: [2021/10/17 01:27:01.619134, 0] ../../source3/nmbd/nmbd.c:59(terminate) Oct 17 01:27:01 Tank winbindd[3348]: [2021/10/17 01:27:01.619143, 0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler) Oct 17 01:27:01 Tank nmbd[3338]: Got SIGTERM: going down... Oct 17 01:27:01 Tank winbindd[3348]: Got sig[15] terminate (is_parent=1) Oct 17 01:27:01 Tank winbindd[3350]: [2021/10/17 01:27:01.619160, 0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler) Oct 17 01:27:01 Tank winbindd[3350]: Got sig[15] terminate (is_parent=0) Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank winbindd[3667]: [2021/10/17 01:27:01.619521, 0] ../../source3/winbindd/winbindd.c:244(winbindd_sig_term_handler) Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank winbindd[3667]: Got sig[15] terminate (is_parent=0) Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: udp_send: Failed to send udp packet with No such device Oct 17 01:27:01 Tank wsdd[3345]: Failed to send bye with No such device Oct 17 01:27:06 Tank root: Starting Samba: /usr/sbin/smbd -D Oct 17 01:27:06 Tank root: /usr/sbin/nmbd -D Oct 17 01:27:06 Tank smbd[10082]: [2021/10/17 01:27:06.741635, 0] ../../lib/util/become_daemon.c:135(daemon_ready) Oct 17 01:27:06 Tank smbd[10082]: daemon_ready: daemon 'smbd' finished starting up and ready to serve connections Oct 17 01:27:06 Tank root: /usr/sbin/wsdd Oct 17 01:27:06 Tank nmbd[10087]: [2021/10/17 01:27:06.750436, 0] ../../lib/util/become_daemon.c:135(daemon_ready) Oct 17 01:27:06 Tank nmbd[10087]: daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections Oct 17 01:27:06 Tank root: /usr/sbin/winbindd -D Oct 17 01:27:06 Tank winbindd[10097]: [2021/10/17 01:27:06.791637, 0] ../../source3/winbindd/winbindd_cache.c:3203(initialize_winbindd_cache) Oct 17 01:27:06 Tank winbindd[10097]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Oct 17 01:27:06 Tank winbindd[10097]: [2021/10/17 01:27:06.792149, 0] ../../lib/util/become_daemon.c:135(daemon_ready) Oct 17 01:27:06 Tank winbindd[10097]: daemon_ready: daemon 'winbindd' finished starting up and ready to serve connections Oct 17 01:27:29 Tank nmbd[10087]: [2021/10/17 01:27:29.782646, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Oct 17 01:27:29 Tank nmbd[10087]: ***** Oct 17 01:27:29 Tank nmbd[10087]: Oct 17 01:27:29 Tank nmbd[10087]: Samba name server TANK is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1 Oct 17 01:27:29 Tank nmbd[10087]: Oct 17 01:27:29 Tank nmbd[10087]: ***** Oct 17 01:27:29 Tank nmbd[10087]: [2021/10/17 01:27:29.782705, 0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Oct 17 01:27:29 Tank nmbd[10087]: ***** Oct 17 01:27:29 Tank nmbd[10087]: Oct 17 01:27:29 Tank nmbd[10087]: Samba name server TANK is now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1 Oct 17 01:27:29 Tank nmbd[10087]: Oct 17 01:27:29 Tank nmbd[10087]: ***** Oct 17 01:56:12 Tank CA Backup/Restore: Backup Complete Oct 17 01:56:12 Tank CA Backup/Restore: Verifying backup Oct 17 01:56:12 Tank CA Backup/Restore: Using command: cd '/mnt/cache/appdata/' && /usr/bin/tar --diff -C '/mnt/cache/appdata/' -af '/mnt/user/backups/appdatabackup/[email protected]/CA_backup.tar.gz' > /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log & echo $! > /tmp/ca.backup2/tempFiles/verifyInProgress Must be noted that the logs and the diagnostics are not from the same try; Diagnostics may include nvidia drivers being loaded which is no longer the case as I have taken the GPU out for now. The only problem I can think of is something related to the CPU, whether being something I have to delete from the system as being intel or something new I need to do as I changed to AMD. Honestly, I don't know. Please help. Thank you tank-diagnostics-20211016-2020.zip

So I've been using this container for more than a year, but last week I've seen some weird behaviour from the notification system I have in place, which would not detect qbittorrent every few minutes. Inspecting the problem I found kind of what is happening, which is the following process: - container loads fine, with normal speeds, no warnings from it about wireguard or anything else - after one or two minutes speeds start to diminish, soon reaching 0 - after a few more seconds with all downloads stale, qbittorrentvpn logs read: What should I do to start troubleshooting this? Thanks. EDIT: it is happening to other containers so I believe it's something to do with the VPN itself. I will check and report back EDIT2: Can confirm that this is happening with whatever personal VPN I (as in VPS-turned-VPN-server) I try. Can someone think of anything I might be missing here? EDIT3: apparently openvpn works with the very same provider so I don't really know what the problem might be. For the time being I'll stick to it.

Hello, First and foremost, thanks for this container. It has been great. So great that.. it is so cutting edge that is currently using qBittorrent v4.3.0, which not all sites whitelist just yet. Would it be possible to retain an older version, perhaps as a tag in the container DockerHub?

Did it, and the pool was successfully imported and shows fine on FreeNAS. The only thing is.. it is empty. Before this (yesterday, before even creating the topic) I tried 'recreating' the pool in Unraid as a part of rebuilding the pool inside. Using the same name. Is it possible that I may have fucked up the data inside the drive, even if only recreating the zpool this way? It should be noted that I got it to work earlier this week. I could see my files in unraid. The only thing is.. I didn't have the drive to transfer all my data by then.

Of course I am doing that hehe sorry if it looked as I literally pasted the command I think I may have fucked up somehow I just don't know how or why

Doing so gives me It there any other way to mount that drive? This is the UD menu, with its pools showed when expanded.

Hello, I am running into a simple problem, yet I won't be trying anything that might damage the disk I am trying to get data from. I have backups, but recovering data would take me weeks with my current connection. I am coming from FreeNAS, with a 4TB ZFS formatted drive. I got a new 4TB drive, which is already formatted in XFS and ready to get that data. Problem is: I forgot to 'export' my zpool on the FreeNAS system before, well, formatting it to install unRaid. As so, the 'zpool import' command does not work, and I am unsure on how to properly mount the ZFS drive to retrieve the data. That HDD will be properly formatted and added to the array when the transfer is done. I got this far, but pressing 'mount' won't properly mount the drive. What should I do to retrieve that data?