Watever

For me, that worked fine ! I have some question regarding how the folders must be organize and how can you integrate with klipper or something like that for tracking filaments since there is a UI part for this.

Have you been able to solve this ? I am in the same boat for a while and didn't get much into it to fix it. But it's driving me crazy with no idea what to do. I created a new container as dashy2 and get the same issue. I don't know what's the problem.

Thank you ! This fixed my issue !

Have you lose all the data on the database ? That's what I am worry now. I updated Immich and it started doing connection problem. But I don't want to lose the data either...

I got it working using the ip, without domains. Might depends on how your server is setup. Buy I suppose if on the same domain, it's not required. Also remove the last \ in the path. ip\path

I have the same issue but with a new mfc-4535dw. But didn't try to much yet. Have you tested using IP instead of server name for path ? Changing the authentification mode to kerberos?

If someone have the same issue, you can check your restore file with the XML. You should have an admin token there. Then you can enter it and after remember to replace it. If it's older, you will have a warning to create a stronger one, with Argon2id probably. Just try to remember that one

I have an issue, my cache device failed and I loss my appdata dockers. So I installed a new one, did a backup restore. Now when I go to the web gui of Vaultwarden, I am asked for an API key. I see there is one in the container config file but I don't remember to have filled this as I usually note theses elsewhere in case. Now I can't find that. Is there a default one or a way to recover ? (I still have local data since it's just not syncing across device since it failed). Thank you

I installed another older nvme and it get recognized as unsassigned. I reinstalled the nvme that is faulty and I don't even see it in unraid.

I did. I turned off, removed the ssd and put it back. turning back on, when in the bios and I can't even see it there.

I formated the nvme drive and unraid failed. I had no gui and couldn't ssh. I waited but nothing happened. So I turned the server off and rebooted. Now the nvme isn't listed. I don't even see it on my bios. Not sure if there is a fall back or if it's the drive that is faulty. I might try another nvme to see if it's the drive or the motherboard or something else.

I will reformat and use the backup, there shouldn't be much change. What I am wondering is why and mostly how it happened. Don't want that to happen again :s.

I don't think I understand the sfisk command and it's use. Created a new DOS disklabel with disk identifier 0x1e332f7b. Created a new partition 1 of type 'Linux' and of size 1.8 TiB. /dev/nvme0n1p1 : 64 3907029167 (1.8T) Linux /dev/nvme0n1p2:

Created a new DOS disklabel with disk identifier 0x664956a5. Created a new partition 1 of type 'Linux' and of size 1.8 TiB. /dev/nvme0n1p1 : 2048 3907029167 (1.8T) Linux /dev/nvme0n1p2:

Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: SPCC M.2 PCIe SSD Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes From my understanding, there is no more partition. How would that be possible ?