CurlyBen

Does the Wallabag container need an external database? This article says that it should work without requiring changes to the template, but I get an error saying the database connection can't be established. The log file from my Wallabag installation is below:

Just for completeness, I rebooted my server today and the BIOS error messages had all gone. It's definitely not something I've come across before but at least it was an easy fix!

Fantastic, thanks a lot for your help (again!). It was actually sdd (my parity drive), I misread which device the error message related to. All seems to be fixed now though - I haven't tried a reboot though as I'm working away this week and I'd rather be there in case I need to attach a keyboard and monitor. It's certainly interesting that the BIOS checks this, but also a bit frustrating - I wasted a lot of time removing sticks of memory etc. as I assumed it was a hardware issue that was preventing it from booting.

Thanks, I ran fdisk -l and under /dev/sdc1 there's a message saying "the backup GPT is corrupt, but the primary appears OK, so that will be used". Presumably there's some way to overwrite the backup with the primary? It's an array drive so I'd rather not mess it up!

Sorry, I wasn't very clear! It's a message from the BIOS, almost immediately after turning on. I can't post a photo at the moment but it's very similar to the one I linked to above - obviously the processor details are different, but it's at that same point just after POST. I haven't received any errors from Unraid.

Today I finally got round to upgrading my server! I've gone from a 3570k to a 12600k on an Asus Z690 motherboard. However, when I boot I get a message stating that GPT header corruption has been found, and to check SATA mode or attempt to repair the boot sector (this isn't my computer, but the wording here is the same or very similar). If I enter setup and immediately quit then my server will boot and Unraid seems to be operating with no issues. However, it's a bit of a pain as I normally run the server headless, and I have to attach monitor and keyboard to be able to boot at the moment. Is there any way to check the GPT headers using Unraid? I don't want to run a tool that 'fixes' the headers only to make the drives unreadable to Unraid. I don't think there's any useful info, but I've attached my diagnostics file. tower-diagnostics-20221002-1634.zip

I'm about 95% sure the filesystem corruption didn't occur immediately - I think I was able to load some files from the emulated disk1 when I first started the array with disk1 removed. I could be wrong but I'm fairly confident that was the case I've run one parity check with all four drives in the array, no errors, and I'm about 75% through a second check with no errors so far. Are there any other steps that can help in the meantime? I'm considering running the Dynamix File Integrity plugin, although I've not yet read enough to fully understand how it works. I may also bring forward my plans to upgrade my server's hardware. I don't really have the budget for it at the moment but I don't have time to be dealing with data loss either! Does ECC memory prevent issues like this? (Assuming it is the memory) Thanks for all your help!

There is, but there's also about 2TB more free space than there was previously on the drive Sorry, which bit? I'm not really clear why data loss was expected Yes, I copied everything off the actual disk1. At this stage I don't think I've suffered any real unrecoverable data loss, but my array has lost 2tb of data and possibly corrupted more without any indication as to a cause. A server I can't trust is more or less useless. Can you suggest next steps for identifying the cause?

I've rebuilt disk1 and I've now started a parity check. It looks as though approx. 2tb of data has been lost since disk1 was removed though, including some entire mounts. I think all that data is replicated elsewhere, but I'm more than a little nervous as I have absolutely no idea what's causing these problems!

I've now copied all the data off the physical disk1 (although comparing it with what I copied off the array when problems started there seem to be some discrepancies... joy...). Is there any reason not to re-assign it to the array and start a rebuild? It potentially gives me a little redundancy while I try and figure what data is good and what's bad. I'll potentially then run a file integrity plugin so at least that way if anything else goes bad I can see what it is, as I still don't have any good indication of where the problem is.

Thanks, I did that. Now I can see disk1 (emulated), but I have a new "lost+found" folder and some of the mount directories that are on the physical disk1 are missing on the emulated disk1. This is turning into a bit of a nightmare, I'm starting to regret having a parity drive! At least that way I wouldn't know there's anything wrong...

It says "Disk 1 Not installed xfs unmountable:not mounted"

Thanks. Is it possible to browse the emulated disk1? I've just opened up mc and I can see disk2, disk3, user etc. but I'd like to be able to take a copy of just the emulated disk1. Is there a way to do that or do I have to figure it out from what's in user but not disk2 or disk3?

I believe so, but I haven't done a full comparison. I'm in the process of making a full copy of the data from the actual disk1 and I can probably find enough space to copy the data from the emulated disk1, so I'll do that and compare - it'll take a while though!

I think I've misunderstood something - I thought your suggestion was to do a new config without disk1, i.e. parity, disk2, disk3, and rebuild parity - which would then lose the emulated disk1? Then add back disk1 after confirming there are no parity issues with those 3 disks? I don't have a spare disk at the moment, although I could buy one. I'm sure it will get filled at some point!