John4559

I just noticed that Unraid says my parity drive is "invalid," but it's still doing the parity sync so far as I can tell. Is that normal? Is there something I should do?

So far so good! Thank you all sooooooo much. I am so relieved. Do we think it's safe to use now or should I wait until the parity-sync finishes just to be sure?

Sorry. I didn't understand to do this, but I've now done it and it mounted using my passphrase for the older drive. What next?? I'm hopeful.....

When I change parity to unassigned and assign the old parity drive to be Disk1, it's says it's "Wrong". I'm not exactly sure what that means, but it won't let me start the array. It says it's an invalid configuration.

/dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="2732-64F5" BLOCK_SIZE="512" TYPE="vfat" /dev/loop1: TYPE="squashfs" /dev/sdd1: UUID="b2aa9d32-c183-4326-aacf-5e08acb1d737" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="c19cae91-3a78-48e4-abd4-3bd5f4230135" /dev/sdb1: UUID="521c4bfc-01d0-4c32-a5a7-812a532cf80a" UUID_SUB="3f9e0276-c0a3-4e32-9590-fbcd0ce996b5" BLOCK_SIZE="4096" TYPE="btrfs" /dev/loop0: TYPE="squashfs" /dev/sdc1: UUID="3765e3e1-c1fc-466e-9b29-43ac5cf7bdd8" TYPE="crypto_LUKS" PARTUUID="25a605ed-bcaf-4dbd-a1e0-e3509b9d0854"

Thanks so much itimpi. I'm attaching my diagnostics file. I wish I had used the other repair utility, but now I'm hoping there's a way to get back on track! elitedesk-diagnostics-20231206-1027.zip

I'm running Unraid 6.12.3, with two 12 TB drives - one used for shares and the other for parity. I've been having a lot of random freezeups/crashes and coudln't figure out what was causing it. I thought it was faulty RAM, but when I replaced that the problem persisted. I changed the Docker custom network setting from "macvlan" to "ipvlan," but then I couldn't start or remove one of the containers. Ultimately, I noticed a bunch of errors and log entries suggesting I do an xfs_repair, which I attempted "xfs_repair -v /dev/sdd1" but it gave me an error about a log problem. Following another thread, I repeated the command with an additional parameter "-L" which appear to complete successfully. BUT then my drive shows up as unmountable and the space where I'd normally put in my passphrase to decrypt the drive was asking for a new passphrase. Now, I'm concerned I won't be able to recover the data on my drive or restore my server setup. I'm so hoping someone here can point me in the right direction. I've been using Unraid for years and have never had this kind of problem.

Folks, I can't figure out why I'm getting the following error for my config: [2022-11-30 09:16:34] frigate.app INFO : Starting Frigate (0.11.1-2eada21) ************************************************************* ************************************************************* *** Your config file is not valid! *** *** Please check the docs at *** *** https://docs.frigate.video/configuration/index *** ************************************************************* ************************************************************* *** Config Validation Errors *** ************************************************************* 'ffmpeg' Traceback (most recent call last): File "/opt/frigate/frigate/app.py", line 332, in start self.init_config() File "/opt/frigate/frigate/app.py", line 82, in init_config user_config = FrigateConfig.parse_file(config_file) File "/opt/frigate/frigate/config.py", line 942, in parse_file return cls.parse_obj(config) File "pydantic/main.py", line 521, in pydantic.main.BaseModel.parse_obj File "pydantic/main.py", line 339, in pydantic.main.BaseModel.__init__ File "pydantic/main.py", line 1056, in pydantic.main.validate_model File "pydantic/fields.py", line 859, in pydantic.fields.ModelField.validate File "pydantic/fields.py", line 994, in pydantic.fields.ModelField._validate_mapping_like File "pydantic/fields.py", line 1067, in pydantic.fields.ModelField._validate_singleton File "pydantic/fields.py", line 857, in pydantic.fields.ModelField.validate File "pydantic/fields.py", line 1074, in pydantic.fields.ModelField._validate_singleton File "pydantic/fields.py", line 1121, in pydantic.fields.ModelField._apply_validators File "pydantic/class_validators.py", line 313, in pydantic.class_validators._generic_validator_basic.lambda12 File "pydantic/main.py", line 704, in pydantic.main.BaseModel.validate File "/opt/frigate/frigate/config.py", line 584, in __init__ if len(config["ffmpeg"]["inputs"]) == 1: KeyError: 'ffmpeg' ************************************************************* *** End Config Validation Errors *** ************************************************************* This is the configuration on a clean install: mqtt: host: [ip address] user: mqtt password: password detectors: coral: type: edgetpu device: usb cameras: backyard: # ffmpeg: # input_args: # - -avoid_negative_ts # - make_zero # - fflags # - +genpts+discardcorrupt # - -flags # - low_delay # - -strict # - experimental # - -analyzeduration # - 1000M # - -probesize # - 1000M # - -rw_timeout # - "5000000" inputs: - path: rtsp://admin:[email protected]:554/h264Preview_01_main roles: - record - path: rtsp://admin:[email protected]:554/h264Preview_01_sub roles: - detect detect: width: 640 height: 480 fps: 7 # rtmp: # enabled: False snapshots: enabled: True bounding_box: True For the life of me, I can't figure out what the "ffmpeg" problem is.