enJOyIT

I ran in this... so yes even if you excluded the container-folder the stopping of the container isn't effected by this! So the container stopps and starts as every other container.

Hi, is it still an issue that the whole backup-file gets marked as failed if there are changed files while the backup process? Can we just ignore this error (as an option)? Because it's not an error for me if there are files (e.g. temp files within nzbget) which changed while backing up... AND Why points the support-link to nowhere: https://forums.lime-technology.com/topic/61211-plugin-ca-appdata-backup-restore-v2/ 😁

one question: I have two accounts... one for unraid.net and one for the forum here... Is there any chance that i can "connect" these accounts so I don't lose my forum history?

I did the filesystem check and reinstalled from a backup. But the same error is still there. Are there any other options? Edit: It's working now... I switched to direct IP access and changed the docker settings from maclan to iplan (don't know if this is necessary... i read it in another post) Thanks 🙂

Ok, will try that tomorrow! Will the docker configs be lost?

I installled some docker apps. Do you can recommend a software for checking the usb filesystem? And do I have to shutdown the server or can it still run from RAM without the stick?

Does it work if i'm backing my settings now and restore it from that? My last backup is from 6th january... Can I pull the usb stick out while it's running?

sadly this didn't work.

The same share is working on my laptop without issues. Here is the diagnostic: unraid-diagnostics-20230212-1708.zip I see other messages: Feb 12 17:15:25 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118.local' 2>&1) took longer than 10s! Feb 12 17:15:30 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118' 2>&1) took longer than 10s! Feb 12 17:15:40 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118.local' 2>&1) took longer than 10s! Feb 12 17:15:44 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118' 2>&1) took longer than 10s! Feb 12 17:15:54 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118.local' 2>&1) took longer than 10s! Feb 12 17:16:00 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118' 2>&1) took longer than 10s! Feb 12 17:16:10 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118.local' 2>&1) took longer than 10s! Feb 12 17:16:15 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118' 2>&1) took longer than 10s! Feb 12 17:16:25 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118.local' 2>&1) took longer than 10s! Feb 12 17:16:30 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118' 2>&1) took longer than 10s!

From today I'm not able to mount my SMB share on synology... I had a unclean shutdown this morning, I'm not sure if it is related to that? If yes, why isn't it working?! unraid 6.11.3 Feb 12 16:17:28 unraid unassigned.devices: Mounting Remote Share '//DS118/Datenbackup'... Feb 12 16:17:28 unraid unassigned.devices: Mount SMB share '//DS118/Datenbackup' using SMB default protocol. Feb 12 16:17:28 unraid unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_Datenbackup' '//DS118/Datenbackup' '/mnt/remotes/DS118_Datenbackup' Feb 12 16:17:38 unraid unassigned.devices: Warning: shell_exec(/sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_Datenbackup' '//DS118/Datenbackup' '/mnt/remotes/DS118_Datenbackup' 2>&1) took longer than 10s! Feb 12 16:17:38 unraid unassigned.devices: SMB default protocol mount failed: 'command timed out'. Feb 12 16:17:38 unraid unassigned.devices: Mount SMB share '//DS118/Datenbackup' using SMB 3.1.1 protocol. Feb 12 16:17:38 unraid unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.1.1,credentials='/tmp/unassigned.devices/credentials_Datenbackup' '//DS118/Datenbackup' '/mnt/remotes/DS118_Datenbackup' Feb 12 16:17:39 unraid unassigned.devices: Warning: shell_exec(/sbin/arp -a 'DS118' 2>&1) took longer than 10s! I deleted the mount and recreated it, even with a new smb user... no success Any thoughts?

Yes, I don't care about the files being changed because these are mostly cached files etc... Maybe you can add an option to ignore these errors, so it's possible the foldername will be without "-errors"? 🙂

Hi, used the old plugin without issues and updated to the new one. It doesn't create tar files since then: [22.12.2022 06:29:08] Backing Up /usr/bin/tar: ./unifi-controller/data/db/diagnostic.data: file changed as we read it /usr/bin/tar: ./unifi-controller/data/db: file changed as we read it /usr/bin/tar: ./unifi-controller/run/mongodb-27117.sock: socket ignored /usr/bin/tar: ./lidarr: file changed as we read it /usr/bin/tar: ./syslog-ng/syslog-ng.ctl: socket ignored [22.12.2022 07:12:51] tar creation failed! disabled tar verifiying. containers are set to "don't stop" Can I use this tar file nonetheless? Just rename it from "-error" to the usual folder name? Any thoughts?

May it's usefull to just shut down VM's which are using the array. Apps like unifi controller, don't really need the array to work.

+1

I'm just looking for a way to see the SAS-SMART status.

+999999 Please implement the feature to run VMs/Docker without having a Array started. No joke... I would pay 100 € instant to get this feature. Let's do a kickstarter campaign? @limetech Are there any plans or did you ever discussed this feature internally? What can we do to push this? Currently I'm running unraid as a proxmox vm and the only reason for me not to upgrade, is that missing feature. But I want to run unraid on bare metal so hard...

UP

Angenommen ich habe jetzt zwei 14 TB Parity-Drives... Ich möchte ein Drive durch 18 TB ersetzen und die andere erstmal auf 14 TB lassen. Geht das ohne Probleme? Mir ist bewusst, dass die maximale Größe des Arrays von den 14 TB Parity Drive abhängt. Zu einem späteren Zeitpunkt würde ich dann die zweite Platte ebenfalls durch ein 18 TB Drive ersetzen.

There is a problem showing the right disk order and showing the right assignment: Any suggestions? Thank you!

I can say that the Transcend JetFlash 600 USB-Stick is a reliable (MLC chips) option aswell. UK: https://www.amazon.co.uk/Transcend-JetFlash-Flash-USB2-0-connector/dp/B002QCAN9S US: out of amazon stock DE: https://www.amazon.de/Transcend-JetFlash-Extreme-Speed-32GB-USB-Stick/dp/B002QCAN9S

Hi, ich konnte mittlerweile das Problem mit Hilfe von dlandon lösen. Es lag daran, dass beim Verbinden des shares die inodes vom Server verwaltet worden und da diese sich beim Verschieben durch den mover verändern ist dann der Client durcheinander gekommen, weil er noch die alten falschen inodes im Zugriff hatte. Durch den "noserverino"-Parameter der beim mounten gesetzt wird, verwaltet der Client nun die inodes und das Problem tritt nicht mehr auf. So ähnlich habe ich es verstanden und es funktioniert auch!

Ok, I will have a look and maybe upgrading to the RC (depends on the release date of the final version 🙂) Thank you very much so far!!!

Ja, das MC-Fenster ist von dem Linux Client.

I am using 6.9.2

Als funktionierenden Workaround (danke an @dlandon) kann ich den Mount mit dem "noserverino"-Parameter verbinden (siehe das englische Forum). Anscheinend ist jetzt dadurch meine CPU-usage auf dem unraid server nach oben gegangen und steht dauerhaft bei 20%. Warum auch immer das ist. Vielleicht hat noch jemand eine Idee?