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 ?

Of course. I don't have the logs has it was on the cache. But here is the diagnostics. Is the simplest way to remove the cache, create a new ones (with a new name), format the nvme and add it to it and do a backup restaure with the app-backup tools ? servername-diagnostics-20230829-0825.zip

My cache is listed as "CacheSPCC_M.2_PCIe_SSD_AA230619NV02KG00385 - 2 TB (nvme0n1)47 C000autoUnmountable: Unsupported or no file system". There is a walkaround from 2018, is it still good ? I have a backup of my 2-3 days older of my appdata. So I could do a restore if I wipe the device. Is that the best and simplest way ? Will the issue be back eventually ? I don't know what happened, I was away for the weekend and at some point my apps on my phone were not working and when I looked remotely, the server was on but there was no docker running, only the VMs. Back home, I tought there was an issue with the docker service, may be due to an update. I update the my plugins and containers on sunday to monday night, because I am usually home at that time and in case there is an issue I can resolve the next day. I only came back on monday evening. Also, my syslog was on the cache, so I don't know when or why it happened. Based on another topic : cache-become-unmountable-after-reboot I might have a similar issue. In the past, I had two smaller device that I replaced with a single larger one (the one I have issue with). But creating a new cache pool and assigned it to it didn't work. This is part of the log of the device. Aug 28 22:08:09 MyServer emhttpd: SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 (nvme0n1) 512 3907029168 Aug 28 22:08:09 MyServer emhttpd: import 30 cache device: (nvme0n1) SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 Aug 28 22:08:09 MyServer emhttpd: read SMART /dev/nvme0n1 Aug 28 22:08:23 MyServer emhttpd: shcmd (512): mount -t xfs -o noatime,nouuid /dev/nvme0n1p1 /mnt/cache Aug 28 22:08:23 MyServer root: mount: /mnt/cache: special device /dev/nvme0n1p1 does not exist. Aug 28 22:08:23 MyServer kernel: /dev/nvme0n1p1: Can't open blockdev Aug 28 22:08:24 MyServer emhttpd: /mnt/cache: no btrfs or device /dev/nvme0n1p1 is not single Aug 28 22:08:24 MyServer emhttpd: /usr/sbin/zpool import -d /dev/nvme0n1p1 2>&1 Aug 28 22:08:24 MyServer emhttpd: shcmd (513): mount -t reiserfs -o noatime,user_xattr,acl /dev/nvme0n1p1 /mnt/cache Aug 28 22:08:24 MyServer root: mount: /mnt/cache: special device /dev/nvme0n1p1 does not exist. Aug 28 22:09:23 MyServer emhttpd: read SMART /dev/nvme0n1 Aug 28 22:09:32 MyServer emhttpd: SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 (nvme0n1) 512 3907029168 Aug 28 22:09:32 MyServer emhttpd: import 30 cache device: (nvme0n1) SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 Aug 28 22:09:32 MyServer emhttpd: read SMART /dev/nvme0n1 Aug 28 22:09:39 MyServer emhttpd: SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 (nvme0n1) 512 3907029168 Aug 28 22:09:39 MyServer emhttpd: read SMART /dev/nvme0n1 Aug 28 22:10:27 MyServer emhttpd: SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 (nvme0n1) 512 3907029168 Aug 28 22:10:27 MyServer emhttpd: read SMART /dev/nvme0n1 Aug 28 22:10:33 MyServer emhttpd: SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 (nvme0n1) 512 3907029168 Aug 28 22:10:33 MyServer emhttpd: import 33 cache device: (nvme0n1) SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 Aug 28 22:10:33 MyServer emhttpd: read SMART /dev/nvme0n1 Aug 28 22:10:51 MyServer emhttpd: shcmd (787): mount -t xfs -o noatime,nouuid /dev/nvme0n1p1 /mnt/v2_cache Aug 28 22:10:51 MyServer root: mount: /mnt/v2_cache: special device /dev/nvme0n1p1 does not exist. Aug 28 22:10:51 MyServer kernel: /dev/nvme0n1p1: Can't open blockdev Aug 28 22:10:51 MyServer emhttpd: /mnt/v2_cache: no btrfs or device /dev/nvme0n1p1 is not single Aug 28 22:10:51 MyServer emhttpd: /usr/sbin/zpool import -d /dev/nvme0n1p1 2>&1 Aug 28 22:10:51 MyServer emhttpd: shcmd (788): mount -t reiserfs -o noatime,user_xattr,acl /dev/nvme0n1p1 /mnt/v2_cache Aug 28 22:10:51 MyServer root: mount: /mnt/v2_cache: special device /dev/nvme0n1p1 does not exist. Aug 28 22:11:19 MyServer emhttpd: read SMART /dev/nvme0n1 Aug 28 22:11:29 MyServer emhttpd: SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 (nvme0n1) 512 3907029168 Aug 28 22:11:29 MyServer emhttpd: import 33 cache device: (nvme0n1) SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 Aug 28 22:11:29 MyServer emhttpd: read SMART /dev/nvme0n1 Aug 28 22:11:54 MyServer emhttpd: SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 (nvme0n1) 512 3907029168 Aug 28 22:11:54 MyServer emhttpd: read SMART /dev/nvme0n1 Aug 28 22:11:58 MyServer emhttpd: SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 (nvme0n1) 512 3907029168 Aug 28 22:11:58 MyServer emhttpd: import 30 cache device: (nvme0n1) SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 Aug 28 22:11:58 MyServer emhttpd: read SMART /dev/nvme0n1 Aug 28 22:12:12 MyServer emhttpd: shcmd (1005): mount -t xfs -o noatime,nouuid /dev/nvme0n1p1 /mnt/cache Aug 28 22:12:12 MyServer root: mount: /mnt/cache: special device /dev/nvme0n1p1 does not exist. Aug 28 22:12:12 MyServer kernel: /dev/nvme0n1p1: Can't open blockdev Aug 28 22:12:12 MyServer emhttpd: /mnt/cache: no btrfs or device /dev/nvme0n1p1 is not single Aug 28 22:12:12 MyServer emhttpd: /usr/sbin/zpool import -d /dev/nvme0n1p1 2>&1 Aug 28 22:12:12 MyServer emhttpd: shcmd (1006): mount -t reiserfs -o noatime,user_xattr,acl /dev/nvme0n1p1 /mnt/cache Aug 28 22:12:12 MyServer root: mount: /mnt/cache: special device /dev/nvme0n1p1 does not exist. Aug 28 22:17:02 MyServer emhttpd: read SMART /dev/nvme0n1 Aug 28 22:17:12 MyServer emhttpd: SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 (nvme0n1) 512 3907029168 Aug 28 22:17:12 MyServer emhttpd: import 30 cache device: (nvme0n1) SPCC_M.2_PCIe_SSD_AA230619NV02KG00385 Aug 28 22:17:12 MyServer emhttpd: read SMART /dev/nvme0n1

I just want to say a big "Thank You" for your work on this ! It's appreciated by lot of people ! I was searching for how to reorganize my folder (not inside) and realize there is now a "lock" on the unraid display page to reorder items. In case someone is searching for it.

Actually, i loss the docker system cause I didn't stop the docker in setting but didn't lose the appdata. So I moved back all files to the cache, then I enable docker and went to the ca app (plugin was working) and reinstalled all the apps/containers. It's easy when they are all listed in the "previously installed" section. Thank you for trying to help me

Hi, I might have screwed-up, not sure how to recover. I had a 128gb nvme and 1 sata ssd (500gb) that was showing sign of errors so I went to replace them for 1x2tb nvme. I stopped my containers, moved all my cache to disk. Then shutdown, replaced and rebooted. On reboot, I assigned the 2tb as the single cache, but then I have no docker container running, and nothing in showing up. I wanted to do a restore back-up, so I went to CA Backup Appdata v2.5, to realize it was replaced by Backup/Restore Appdata on 6.12. Meaning, it was not working and backing up my container after the os update. So my last backup is on july 17th. So I taught I would add back my 128gb nvme and do a backup with it, then put the new drive and do a restore. But it's when I assign the drive to the cache, it says it's "unmountable". I still have my appdata folder but there might be some files that were not moved from system/docker. Any help on how I should handle it without reinstalling everything ?

For the proxy, the logs said couldn't renew the certificate. I renew the certificate throw nginx gui (the date was august 30th so should still be good) and it worked. Not sure why. I don't think that's the problem, but I will check if it comes back, since I rebooted. Unless someone see something in the diagnostic file. Could a parity check cause some problems too ?

This is the diagnostic after doing a reboot to make it work. But the problem is not there. But my web gui isn't available with the proxy (nginx), getting 502 bad gateway, but all other dockers are fine. unraid-diagnostics-20230801-2109.zip

I didn't get the issue right after reboot. I also sometimes get a "bad gateway 502" on some page.

I don't know if it's related to the update from 6.11 to 6.12, I did a few days/1 week ago or so. But part of the dashboard will not show, the table, borders will show but not the data, I only have an unraid logo waiting forever. The server is still running, the dockers are running, etc.. just that the gui is not useful. After a reboot, everything looks good (at least when I did). It can be the docker page, the main page, the share pages, sometimes one can work but not the others. I don't think it's the same as this topic : I am already on IPv4 only and the gui is partially working in my case. I am trying to get the diagnostic, but when I download, it also seems unresponsive (or just take a lot of time), but the tools and setting pages were working.