Maertuerer
Members
-
Joined
-
Last visited
-
Hey, me again. This month my gitlab got deleted AGAIN during the backup process, thank you!
-
So, during the last backup, my gitlab got deleted. How is this even possible? backup.log
-
1) install homarr as homepage 2) add tile with url (http://unraidip/Main) 3) click it Expected behaviour: main page loads Actual behaviour: login page loads This worked fine in all versions 6.x.x and just broke after updating to version 7.x.x I would assume that it has to do with the referrer policy. Homarr sets that to "no-referrer" and unraid then returns a 302 moved temporarily and redirects to login
-
Yeah, I had to use the SSD in the array... Might as well try to update to the most recent version, if I then can move the nvme from array to pool and keep using it. Is there a manual way to call trim on the ssd?
-
So, I tried to delete unused docker images and I am getting execution errors and the UI is Almost unusable now, CPU at 100% To me it feels like the SSD is dying right now nas-diagnostics-20250513-1755.zip
-
YES!!!! In there I got vaultwarden (didn't break) but also homarr and plex (which broke). Gitlab was not configured to backup external Data .... downloader was actually set to be skipped during backup .... Just gotta look into restoring the backup and reconfigure the missing backups correctly. No real data loss in gitlab, since I also have everything locally, but still sucks. THANK YOU VERY MUCH FOR YOUR SUPPORT, Ricky!
-
I am not completely understanding that question (noob), but is this what you are inquiring about? Both homarr settings, as well as gitlab data are gone Vaultwarden is still completely fine: /data/mnt/user/appdata/vaultwarden Data in /mnt/disk1/JDownloaderDownloads is fine, Data in /mnt/disk1/appdata/jdownloader2/ has been reset So it looks like only docker data in /mnt/disk1/appdata/ has been reset to the default values? Unfortunately, for homarr that would not explain the problem...
-
Is this someting useful? root@NAS:~# dmesg | grep -i error [ 0.422417] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [CAP1] at bit offset/length 64/32 exceeds size of target Buffer (64 bits) (20220331/dsopcode-198) [ 0.422428] ACPI Error: Aborting method \_SB._OSC due to previous error (AE_AML_BUFFER_LIMIT) (20220331/psparse-529)
-
18, of which only 6 were running all the time.
-
No idea, where would I configure the size? Maybe just precaution years ago?
-
Like I said, it looks like all changes in all of my containers (some running over 2 years) I did have been reverted after the high RAM problem and a subsequent restart.
-
The "crash" happened after multiple years of no problems...
-
nas-diagnostics-20250513-1633.zip
-
Don't think I enabled that, is it under the syslog server settings? *Local Syslog Server is disabled "Mirror to flash" was turned off. What now?
-
Hey everyone, todayI had a memory leak I guess, 75% of 64GB RAM used. I got many errors navigating the UI (especially on the docker and apps tabs). After a restart, all my docker containers have lost their data and can't start anymore. Seems like the data in disk1/appdata has been affected, just all configured data is gone, the rest is fine. Vaultwarden works fine, for Plex I had to regenerate all thumbnails, everything else seems to be working fine. Gitlab does not start anymore and it looks like all data has been lost Any tips?
