dellorianes

I am also trying to delete them but I cant. Whatever rebooting the NAS, the ssh keys appears again. Also with known_host and authorized files. I try in maintenace mode and safe mode but I can´t.

HI, I found today several repeated errors about muy nvidia GPU. Jan 21 05:29:45 NASDiego kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Find attached diagnostics. Regards nasdiego-diagnostics-20240122-1707.zip

Some have suffer a crack in the docker? When I try to start it appears the following error message

ok, thank you very much. I will try.

I am suffering randomly disconnections from unraid in my network. Sometimes it resolves by itself in 1 or 2 hours, reconnecting, but other times unraid never connect again to the network and I have hard reset it. During the disconnection I cannot access unraid gui, nor docker, nor VM. I cannot also access it via ssh nor ping the server. Please, find attached the diagnostic file of my server after a lost and connecting again to network. Thank you in advance. Regards llorianes-diagnostics-20231220-1426.zip

No, only moving. one film, for example in disk 1, if renamed, is moved to disk 3 (this could be understandable if disk 3 is emptier than 1) ut it also happens in the film is in disk 3 and while ranaming it is moving also to disk 3 (I made trials). Anycase I rename a film it is moved + renamed. I want only to rename. Is that correct?

Hi, Is it possible to only rename a file and a folder? Anytime I try to do that, filebot renames it but it move the files. Is there a way to only rename them? An operation that can makes in a second spends 20 minutes for a single film (if I have to rename all the movies speds one week).

Absolutly true. Thank you very much. My apologues

Hi, I have been using luckybackup for some weeks but I have a problem with the schedule. I have two tasks scheduled and "cronIT" as per: Time (hour:min): 1:0 Day of week: Monday and another for Thursday month: any Day of Month: any I want a backup every monday and Thursday at 01:00 The problem is that no back is made. The only way I can get a backup is doing it manually. Someone can hel me? Thank you

Hi, I am transferring files (movies) from one share folder to another share folder. I am having very high loads in top window. Is that normal? I havnasdiego-diagnostics-20230822-1223.zipe a i7 9700 (8 cores) cpu. nasdiego-diagnostics-20230822-1223.zip

Hi, I have also the same problem. After have beeing moving the gpu I got this error: My vfio-pci.cfg shows: BIND=0000:01:00.0|10de:1402 0000:01:00.1|10de:0fba 0000:06:00.0|1b73:1100 0000:07:00.0|8086:2725 What I have to remove? Thank you Regardsnasdiego-diagnostics-20230729-1406.zip

some help?

I have connected my main Unraid server with a remote server via Wireguard, with a server to server peer. I can ping servers from both sides. What I want now is to make a backup of my main server onto my remote server using luckybackup but the container can not ping the remote server. (10.253.0.6). I think it is a setting up iptables network issue or something. Someone can give me a tuto, please?? Thank you Regards

After removing that, SMB server started to work again. Fix common problems also warned me to change macvlan to ipvlan in Docker settings. Thank you very much. Now, I also have this warning after reset. Should I do something with them? May 16 07:26:52 NASDiego kernel: Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA May 16 07:26:52 NASDiego kernel: ACPI: Early table checksum verification disabled May 16 07:26:52 NASDiego kernel: floppy0: no floppy controllers found May 16 07:26:52 NASDiego kernel: i915 0000:00:02.0: [drm] failed to retrieve link info, disabling eDP May 16 07:26:57 NASDiego mcelog: failed to prefill DIMM database from DMI data May 16 07:27:28 NASDiego kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20220331/utaddress-204) May 16 07:27:55 NASDiego rpc.statd[10765]: Failed to read /var/lib/nfs/state: Success May 16 07:28:05 NASDiego kernel: BTRFS info (device sdi1): using crc32c (crc32c-intel) checksum algorithm May 16 07:28:35 NASDiego kernel: BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm May 16 07:28:40 NASDiego kernel: BTRFS info (device loop3): using crc32c (crc32c-intel) checksum algorithm

Tryed safe mode and continued the same. Upgraded to 6.12-rc5 and the same again. Find diagnostics attached. May 15 22:47:17 NASDiego kernel: Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA May 15 22:47:17 NASDiego kernel: ACPI: Early table checksum verification disabled May 15 22:47:17 NASDiego kernel: floppy0: no floppy controllers found May 15 22:47:17 NASDiego kernel: Bluetooth: hci0: FW download error recovery failed (-19) May 15 22:47:17 NASDiego kernel: i915 0000:00:02.0: [drm] failed to retrieve link info, disabling eDP May 15 22:47:26 NASDiego mcelog: failed to prefill DIMM database from DMI data May 15 22:47:27 NASDiego smbd[1563]: tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record May 15 22:47:27 NASDiego smbd[1563]: Failed to open /var/lib/samba/private/secrets.tdb May 15 22:47:27 NASDiego smbd[1564]: tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record May 15 22:47:27 NASDiego smbd[1564]: Failed to open /var/lib/samba/private/secrets.tdb May 15 22:47:27 NASDiego smbd[1564]: exit_daemon: daemon failed to start: smbd can not open secrets.tdb, error code 13 May 15 22:47:27 NASDiego winbindd[1577]: tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record May 15 22:47:27 NASDiego winbindd[1577]: Failed to open /var/lib/samba/private/secrets.tdb May 15 22:47:59 NASDiego kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20220331/utaddress-204) nasdiego-diagnostics-20230515-2252.zip

Sorry, my English is not as well as I want but I undertooth in @dlandon post that someone (I didn't get alluded to due to I am not in v6.12-rc5) that posts 6.12-rc5 diagnostics to evaluate. I also understand that the problems of @OneMeanRabbit started when he upgraded to 6.12-rc5. So, being me in 6.11.5, are you recommending me to upgrade to 6.12-rc5? Thank you

Up

root@NASDiego:~# ls -la /var/lib/ total 16 drwxr-xr-x 14 root root 280 Nov 20 22:27 ./ drwxr-xr-x 15 root root 360 Dec 31 2019 ../ drwxr-xr-x 2 root root 40 Oct 6 2022 arpd/ drwxr-xr-x 2 messagebus root 60 May 11 15:24 dbus/ drwxr-x--- 2 root root 40 Aug 28 2022 dhcpcd/ drwx--x--- 1 root root 254 May 11 16:18 docker/ drwxr-xr-x 10 root root 220 Nov 20 22:26 libvirt/ drwxr-xr-x 6 rpc rpc 220 May 11 16:18 nfs/ drwx------ 7 root root 140 May 11 15:25 nginx/ drwxrwxr-x 2 ntp ntp 60 May 11 21:24 ntp/ drwxrwx--- 2 root apache 100 May 11 21:45 php/ drwxr-xr-x 6 root root 160 Nov 20 22:26 pkgtools/ drwxr-xr-x 4 root root 80 Nov 15 21:10 samba/ drwxr-xr-x 2 root root 40 May 1 2022 swtpm-localca/ root@NASDiego:~# ls -la /var/lib/samba/ total 0 drwxr-xr-x 4 root root 80 Nov 15 21:10 ./ drwxr-xr-x 14 root root 280 Nov 20 22:27 ../ drwxrwx--- 2 root root 40 Nov 15 21:10 bind-dns/ drwx------ 3 root root 100 May 11 16:18 private/ Thank you again

I proceed to delete smbpasswd and Reestart (I have to force the shootdown) the system. Once reestarted, smb continous not working. I checked that smbpasswd whas reseted (as you said without other users different than root). There are logs I am getting and the diagnostics file: nasdiego-diagnostics-20230511-1534.zip

The following shares are, between other, setup a smb shared: Andrea, Casa Regarding System Logs it a shows: In several periods of time Thank you again

Some days ago I found the array with all my disks unlocked. After rebooting the server all seems to be ok, but since then (I do not know if the problem existed before), I can not access my server via SMB from any device at home (Home Assistant OS, Android Mobile, Windows 11..) I tryed to stop the smb server, reestart the server and activate again but nothing changed. I have also tryed to make a share folder public but it cotinued not having access. Find attached my diagnostic file. Thank you very much nasdiego-diagnostics-20230511-1208.zip

The owner of the dms folder is root. I used the CA template, so no UID was defined. I applied "chmod 777 /mnt/user/appdata/dms" but the error continues. Thank you again

Hi, Trying to make first setup, when arriving to step "5. Try to connect to the server with an e-mail client.", I can add the account to my clients but when I try to send/receive an e-mail to my account it appears the following warnings in the log May 2 13:04:06 mail dovecot: [...] Error: Couldn't create mailbox list lock /var/mail/myaccount.com/diego/mailboxes.lock: file_create_locked(/var/mail/myaccount.com/diego/mailboxes.lock) failed: link(/var/mail/myaccount.com/diego/mailboxes.lockfacd1248548fb361, /var/mail/myaccount.com/diego/mailboxes.lock) failed: Function not implemented Any advise? Thank you in advance

What is the common speed for a single backup via sFTP? I always get 10 MB/S when doing that regardless of it is compressed or not. Is that a common speed? Thank you. Regards

any idea?