YoHoNoMo

Oh my ... *facepalm* Now it worked, thank you!

I do have backups on my array, so recovery is not a must. It's probably no good with some of it being unreadable and starting fresh would be best.

mount -v -o rescue=all,ro /dev/nvme0n1p1 /x mount: /x: /dev/nvme0n1p1 already mounted on /temp. dmesg(1) may have more information after failed mount system call. I mounted the NVMe to /temp yesterday working through the Unraid forums and manual. There were a few occassions where Midnight Command was unable to copy some files (msg: Stalling ....). That's why I stopped bothering with the drives and went nuclear on the pool/drives trying to format everything. 😁

Because of the backups I "recklessly" did try formatting the pool, that did not work. Than removed the drive and tried formatting the SN570. Didn't succeed either. Thank you very much for looking into my mess! root@UNRAID-NAS:~# btrfs fi show Label: none uuid: d1776af5-1bda-45f7-a369-70e42d89cf09 Total devices 2 FS bytes used 153.51GiB devid 1 size 931.51GiB used 215.06GiB path /dev/nvme0n1p1 devid 2 size 931.51GiB used 82.03GiB path /dev/nvme1n1p1

Yesterday 1 of 2 Cache Pool SSDs died (SMART shows failure), but both SSDs show up as "unmountable: unsupported or no file system" (it was btrfs, with a mirrored backup drive - non-technical term, because I don't really remember 😅 I'm pretty sure I set it up after watching a SpaceinvaderOne Tutorial video). I have the appdata and nextcloud folders that are/were on these drives backed up, so I am quite calm. But nonetheless I am at a loss on how to proceed from here. I thought I would be able to use the other drive when one would eventually fail, but ... here I am with both being unmountable. The diagnostics unfortunately were taken after a reboot (because of course ... sorry). But since the Samsung 970 EVO Plus shows a SMART failure and I have the data backed up to the array that probably does not matter? Either way, I'll now know better in the future. 😅 My Cache Pool consisted of these drives: Cache 1: Samsung 970 EVO Plus Cache 2: WD Blue SN570 I have since removed the Samsung SSD from the pool and tried just the WD SN570. I even tried formatting the drive through Unraid but that would start and stop immediately. Any help from a kind stranger to get the probably okay WD SN570 working again would be much appreciated. unraid-nas-diagnostics-20240415-1406.zip

I checked again today after updating my binhex containers. Latest updates changed binhex/arch-radarr to version 5.6.1. It is now affected as well.

Unraid 6.12.9 is also unaffected with version 5.4.1. Popular docker containers with 5.6(.1) I found: - binhex/arch-prowlarr - binhex/arch-sabnzbd - binhex/arch-sonarr It seems binhex/arch-radarr is unaffected with version 5.4.5.

Thank you for the way you are handling the change and keep honouring the lifetime licenses in a user-friendly way! My server has six drives and while I initially bought the Plus license I soon upgraded to the Pro license even though I will probably never need it –– Just because I have been so happy with my purchase. I'm planning to build an Unraid server as a gift for my father this year and had to snatch another lifetime license after reading the announcement. I don't want another subscription in my life, I'm sorry. 🥺 😁 Thank you for allowing users to still buy the old license type, store them for later use and keeping an upgrade path open!

Thank you. It is working for now after updating to 6.12.3, but the server has only been running for 3.5 hours, so I will have to wait and see. Should be fixed if it lasts more than 24 hours. I will update the topic tomorrow.

A few weeks back I received a notification through Unraid GUI that it is recommended to change docker network type from macvlan to ipvlan because of stability issues with macvlan. I tried changing it, had an unclean shutdown in the process, and since then I have been in a world of pain... All docker containers were suddenly gone, well all Community Applications. The manual caddy docker installation survived, but reinstalling CAs was easy and with the ipvlan setting everything was fine for a few hours. Then the server started losing internet access (network timeout). Trying to fix this I ended up changing back to macvlan. Again, at first everything worked fine (besides having to reinstall all CAs again). But after some time the server randomly vanished from my network and wasn't accessible anymore. Forcing a hard shutdown per long button press was the only thing I could think of to access it again. (I tried restarting the router and temporarily removed the network cable to no avail). My next try to fix this was trying to delete the docker directory (I switched from image to folder when I set up the server ~ 18 months ago). That somehow first failed, but a few more reboots through GUI and reported unclean shutdowns later 😄 the directory was empty and then regenerated. With ipvlan docker network setting I was briefly able to reinstall my caddy container and a few minutes later the server's internet access is gone again. I went to the network settings, didn't see anything out of the ordinary (but enabled IPV4+IPV6 instead of IPV4 only as a wild guess to reset the network somehow - didn't help though). I hope I have summarized everything correctly, as I said it's been going on for a few weeks now and I am still a newbie. It's been a while since I set up everything and didn't have any serious problems before. Any help or guidance would be much appreciated! Edit: I didn't even notice the release of Unraid 6.12.3 because of the network issues. I was on 6.12.0rc06 and I just upgraded to 12.6.3 - now setting everything up again. I'll update the post when done, maybe this will help. ===== Updating to 6.12.3 solved all issues I had. syslog.txt

I'm experiencing this problem with Unraid 6.11.5.

Same here! I added some HDDs 9 days ago and the problem did not reoccur until today.

I'm also having this issue for two weeks now. *sigh*

code-server könnte dir da weiterhelfen. Ich hatte vor kurzem ein Tutorial zur Einrichtung auf Unraid gesehen, in dem der Content Creator code-server für die Bearbeitung seiner docker-configs genutzt hat. Dann sollten die Berechtigungen eigentlich kein Problem sein, da du ja lokal auf dem Server auf die Dateien zugreifst?

Der Stromverbrauch der AEG Protect NAS USV hat mich doch so gewurmt, dass ich mir noch die kleine Cyberpower C550EPFCLCD bestellt habe. Ich kann bestätigen, die hat tatsächlich nur einen sehr geringen Leistungsbedarf von 4 bis 5 Watt. Ich kann nicht sagen, ob die AEG USV ein Montagsgerät ist, aber die Cyberpower USV kann ich uneingeschränkt empfehlen.