CurlyBen
-
Posts
23 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by CurlyBen
-
-
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!
-
1
-
-
1 hour ago, JorgeB said:
Find it interesting that the board BIOS checks for that, you should be able to correct that with gdisk, e.g.:
gdisk /dev/sdb GPT fdisk (gdisk) version 1.0.5 Caution: invalid main GPT header, but valid backup; regenerating main header from backup! Warning: Invalid CRC on main header data; loaded backup partition table. Warning! One or more CRCs don't match. You should repair the disk! Main header: ERROR Backup header: OK Main partition table: OK Backup partition table: OK Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged **************************************************************************** Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. **************************************************************************** Command (? for help): w Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!! Do you want to proceed? (Y/N): y OK; writing new GUID partition table (GPT) to /dev/sdb. The operation has completed successfully.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.
-
1
-
-
12 hours ago, JorgeB said:
The syslog is showing a similar error:
Oct 2 16:19:58 Tower kernel: Alternate GPT is invalid, using primary GPT.But like mentioned not clear which device is the problem, check the output of:
fdisk -l /dev/sdXfor all the devices, it should indicate the culprit
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.
-
On 5/25/2022 at 9:48 AM, JorgeB said:
The part were the emulated disk had filesystem corruption, likely the result of parity not being 100% in sync.
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
On 5/25/2022 at 9:48 AM, JorgeB said:Like mentioned this is usually a RAM problem, unfortunately memtest is only definite if errors are found, not the other way, but like mentioned it could also be for example a disk issue, those are much more difficult to diagnose since basically you need to remove/replace one disk from the array at a time and run a coupe of parity checks to see if it helped or not, that's why I suggested:
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!
-
18 hours ago, AndrewZ said:
Is there now a Lost & Found directory on the rebuilt drive?
There is, but there's also about 2TB more free space than there was previously on the drive
17 hours ago, JorgeB said:This was expected from what you wrote above:
Sorry, which bit? I'm not really clear why data loss was expected
17 hours ago, JorgeB said:That's why I asked if you copied everything you needed from the actual disk1 before rebuilding on top, if yes you just need to copy the data over, though you still need to find what's making parity go out of sync and/or possibly corrupting data.
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.
-
1 hour ago, itimpi said:
In that case you should be following this process to try and repair the file system on the emulated disk.
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... -
17 minutes ago, itimpi said:
If disk1 is being emulated then you should be able to see it’s contents just as if it was physically present. What does the Main tab show for disk1?
It says "Disk 1 Not installed xfs unmountable:not mounted"
-
38 minutes ago, JorgeB said:
OK, assuming the data is the same if you do a new config and keep old disk1 intact you won't lose any data, of course the array will be unprotected until the sync is done, also disk1 won't be parity protected initially, then if no more sync errors you could do another new config this time including disk1 and re-sync parity again.
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?
-
9 minutes ago, JorgeB said:
First please confirm if the actual disk1 has the same data as the emulated disk1, from what I understood it has, correct?
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!
-
3 minutes ago, JorgeB said:
Yes, but the emulated disk1 should have the same data as the actual disk1, assuming the parity check was correct and there's no new data added/changed since you unassigned it.
Alternatively, and if you have one, rebuild to a spare, then do a couple of parity checks to look for sync errors.
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!
-
43 minutes ago, JorgeB said:
Main suspect is usually the RAM, but it can also be a disk, from your description looks like all corrupt files you found were on disk1?
Yes, although with the caveat that I didn't check many files and it may have been coincidence (all the files were copied to the array at the same time and haven't been accessed since). I assume that whenever they were corrupted was prior to the last successful parity check, as the emulated files match the ones copied from the array before disk1 was removed. I'll do a little more digging and see if the errors are limited to disk1. It's perhaps also relevant to say that disk1 shouldn't have seen much write activity for the last few months, as my array was at about 90% capacity until I added another drive a few months ago. I didn't rebalance but files have slowly been removed from disk1 (and disk2) as I've moved stuff around.
43 minutes ago, JorgeB said:If that's correct I would start by doing a new config without it, then sync parity and run a couple of parity checks, of course if there's any new data on the emulated disk1 vs the actual disk you need to copy that first, if there are no errors do another new config with disk1 back and re-sync parity, if errors return you found the problem.
My concern with this - and it might be an issue with my understanding - is that, assuming disk1 is failing in some way which is causing the parity errors, those errors are potentially limited to disk1. At the moment, I can rebuild disk1 using the remaining disks in the array, but if I rebuild parity then I lose this ability. Is that correct?
-
I'm having some problems with my server! I posted a couple of weeks ago about errors that occurred when running a parity check, but the situation has evolved a bit since then. Apologies for the bullet points, but I wanted to try and keep things clear and as brief as possible. I've attached the latest logs, although the server has been shut down since the last parity check.
- Probably irrelevant, but in the few days prior to the problems being detected I have moved a lot of relatively large (1-3gb) files around, mostly using MC through the terminal
- About two weeks ago a parity check ran after I shut down my server to remove two drives (unassigned devices)
- The check found lots of parity errors (about 650,000) The previous parity check (February) found no errors
- All drives passed extended SMART checks with no errors. 2 drives have CRC errors from several months ago, none since changing cables/HBA
- Unraid’s memtest wouldn’t run (when selected the machine restarted), but I downloaded memtest86 (free version, limited to 4 passes) to a different USB stick and it completed 4 passes with no errors
- No power loss or crash induced hard shutdowns since the last successful parity check, although I now realise Unraid’s ‘clean’ shutdown may not have been clean due to issues stopping the array - but it seems unlikely that a hard shutdown would cause so many parity issues
- I copied the most important data off the array when parity check started showing errors
- I used FreeFileSync to compare the copied data to partial backups – mostly identical. Some large (GoPro) video files were different, with the copy on the array corrupted. I looked at a few files on the array to see which disk they were on, and all I checked were on disk 1
- Removed disk 1, started array with disk 1 emulated, copied off some of the files that were identified in the last step – ran a file comparison and they were identical to the files copied off after the parity errors started, which I assume means they were corrupt before the parity issues started (from a quick binary comparison it looks as though the files go blank about halfway through)
- Reinstalled disk 1 but it didn’t come back into the array – I can assign it to the array, but it appears as a new disk, i.e. needs to be initialised
- I didn’t make any changes to the array while I had disk 1 removed, but docker was running and may have made changes (although I have a cache disk and I think all shares on the array use it)
- I’ve mounted disk 1 as an unassigned device and I’m copying all the data off it to a spare hard drive
Questions:
- What could have caused the parity errors? How can I prevent this occurring in the future?
- Why is disk 1 seen as new? Is it because data was written to the array while it was simulated, or just because the array was started while it was missing?
- Do I have any other sensible options other than assigning disk 1 to the array again then rebuilding?
Hardware
- Intel i5-3570K
- Gigabyte Z77-D3H
- 9gb RAM (Odd, I know, but I had a 1gb stick of ECC RAM which I installed last year to see if the motherboard supports ECC and I never got round to removing it!)
- 4x 8tb Western Digital HDs for the array (1x parity)
- 1x 500gb Samsung Evo SSD (cache drive)
- 2x Blu Ray drives
- 1x Marvell HBA. I understand this can cause problems, but the array drives are all connected to the motherboard SATA controller. The Blu Ray drives and an unassigned drive (now removed) are connected to the HBA
- I think that's everything!
-
Thanks Jorge. I'm currently running extended SMART tests and I'll do a filesystem check too, assuming they all come back clean I'll do as you advised in your first post.
-
54 minutes ago, JorgeB said:
Run memtest, if no errors are found after a couple of passes run a correcting check followed by a non correcting one, if there are errors on the 2nd run post new diags without rebooting.
Thanks Jorge. I'm assuming that if the errors are on a data drive, rather than the parity drive, this will solidify the errors - so if that's what you're suggesting then there's no way to correct anyway?
-
Hi everyone,
I've got a bit of a problem! I recently shut down my server (using the GUI) to remove two unassigned drives, and when I booted up again a parity check started. I think there may be an intermittent issue when booting which then triggers the parity check, I've not got to the bottom of it. Anyway, parity check, no problem... except it immediately started showing errors. It's still running (non-correcting mode) but, with over half a million sync errors by 30%, I clearly have a problem.
There's nothing obviously wrong - to me anyway - in the SMART data and I'm not aware of an unclean shutdown since the last successful parity check (late February), and what I've read so far suggests an unclean shutdown wouldn't cause this massive number of errors. Are there any other likely culprits? Or do I have a disk that is failing in a way SMART doesn't detect?
I don't know if it's relevant, but most of the recent file changes on the array have been adding/moving media around. Is it likely the errors will be in this data (which is easily replaceable) or spread throughout the array?
I think I have good copies of all my most important data - but I'm not so confident I want to test it!
Logs are attached but, as mentioned above, the parity check is still running so I don't know if anything will be included yet. The array is 4x8tb drives, 1x parity and 3x data.
-
I got it working! To cut a long story short, I found a post on a MakeMKV forum which said that, by default, Windows does not allow access to removable storage when using Remote Desktop. I followed this instruction:
In the local Group Policy editor (run gpedit.msc), go into Computer Configuration/Administrative Templates/System/Removable Storage Access
Enable the policy "All Removable Storage: Allow direct access in remote sessions"and now I can access the drive. The code in my XML is the same as in my original post. I'm running Unraid 6.9.0 (the beta). I did notice that when looking in the system devices tab on 6.8.3 it listed the blu ray drive but had no size listed next to it. When looking at the same tab in 6.9.0 it did list the size of the CD in the drive. No idea if it's relevant!
-
Oh that's a bummer. Possibly a dealbreaker for me. I'm still in my trial period but I don't know if I'll have enough time to figure out how to get my data off before the end of the trial! Still at least I know now, thanks
-
Hi everyone, I hope this is the right place to post this!
I'm trying to pass a blu ray drive through to a Windows virtual machine. I edited the XML to add the following code (acquired from here, modified for my drive's address)
<hostdev mode='subsystem' type='scsi' managed='no'> <source> <adapter name='scsi_host5'/> <address bus='0' target='0' unit='0'/> </source> <readonly/> <alias name='hostdev0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </hostdev>
and the drive shows up in the VM. It correctly shows the audio CD in the drive. However, I can't access any data on the drive. I've tried a couple of different discs and have the same problem with each. Every file shows a file size of 1kb, and attempting to open them will launch Windows Media Player but it can't play the track (no error message is shown). I can't copy the files off and iTunes won't even recognise a CD in the drive. I even swapped out the drive with another and still no joy.
Could this be because my computer doesn't support IOMMU? I have a 3570k and apparently Intel decided buyers of the 'k' variant wouldn't want all the features of the processor enabled! If not, are there any obvious culprits?
Bonus questions:
1) One of my BR drives is a write. Is enabling this functionality as simple as removing the readonly flag in the code above?
2) When using USB passthrough, is there any way to disable the passthrough if the device is no longer connected? I was using a USB hard drive with pass through. I disconnected it without disabling the passthrough, and the next time I tried to start the VM it failed because the drive wasn't there - but nor was the option to remove if from pass through. I had to reconnect the drive and remove it from pass through before I could load the VM.
[Support] A75G Repo
in Docker Containers
Posted
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: