Kevlar75

Thanks for the input. I have rebooted and it appears the rebuild was successful. I did move the new 18TB replacement drive to a different drive bay in case it was a cabling issue. I plan on doing a parity check to confirm the rebuild. I will include my diagnostic file but all appears fine now. Thanks again for your support. tower-diagnostics-20240422-1655.zip

Replaced an older 2TB HDD with a fresh 18TB HDD. I formatted the 18TB as xfs prior to adding it to the array but I didn't preclear it. The rebuild process appeared to be operating normally however, it has stopped at 33.5% completed. Data-Rebuild in progress. Total size: 18 TB Elapsed time: 1 day, 6 hours, 29 minutes Current position: 6.03 TB (33.5 %) Estimated speed: 191.2 MB/sec Estimated finish: 17 hours, 23 minutes Sync errors corrected: 0 I am unable to download a diagnostic report... it hangs at the step "df -h 2>/dev/null|todos >'/tower-diagnostics-20240422-0816/system/df.txt'" I will include my System/Enhanced System logs. I still have the old 2TB HDD. I am on the verge of attempting a shutdown and rebuild using the original 2TB HDD but thought it wise to seek expert advice first. 🙏 Kev Smith Unraid server Pro, version 6.12.10 Motherboard: ASRock EP2C602-4L/D16 Processor: Intel® Xeon® CPU E5-2670 0 @ 2.60GHz Memory: 128 GiB DDR3 Multi-bit ECC Kernel: Linux 6.1.79-Unraid x86_64 tower-syslog-20240422-0041.zip tower-syslog-20240422-0841.zip

Hi, I've been successfully using the original paperless (P) docker for some time and have quite a few correspondents, tags and documents. I have installed paperless-ng (P-ng) and I'm trying to use the importer to setup P-ng with the backup I exported from P. I use the document_importer but because the P json file doesn't include any "file_type" information, I get an exception and nothing imports. root@7669a69ac285:/usr/src/paperless/src# python3.7 manage.py document_importer /usr/src/paperless/export/ Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/django/db/models/options.py", line 575, in get_field return self.fields_map[field_name] KeyError: 'file_type' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/django/core/serializers/json.py", line 70, in Deserializer yield from PythonDeserializer(objects, **options) File "/usr/local/lib/python3.7/site-packages/django/core/serializers/python.py", line 117, in Deserializer field = Model._meta.get_field(field_name) File "/usr/local/lib/python3.7/site-packages/django/db/models/options.py", line 577, in get_field raise FieldDoesNotExist("%s has no field named '%s'" % (self.object_name, field_name)) django.core.exceptions.FieldDoesNotExist: Document has no field named 'file_type' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "manage.py", line 11, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line utility.execute() File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 395, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 330, in run_from_argv self.execute(*args, **cmd_options) File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 371, in execute output = self.handle(*args, **options) File "/usr/src/paperless/src/documents/management/commands/document_importer.py", line 71, in handle call_command("loaddata", manifest_path) File "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", line 168, in call_command return command.execute(*args, **defaults) File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 371, in execute output = self.handle(*args, **options) File "/usr/local/lib/python3.7/site-packages/django/core/management/commands/loaddata.py", line 72, in handle self.loaddata(fixture_labels) File "/usr/local/lib/python3.7/site-packages/django/core/management/commands/loaddata.py", line 114, in loaddata self.load_label(fixture_label) File "/usr/local/lib/python3.7/site-packages/django/core/management/commands/loaddata.py", line 172, in load_label for obj in objects: File "/usr/local/lib/python3.7/site-packages/django/core/serializers/json.py", line 74, in Deserializer raise DeserializationError() from exc django.core.serializers.base.DeserializationError: Problem installing fixture '/usr/src/paperless/export/manifest.json': root@7669a69ac285:/usr/src/paperless/src# Any help in migrating all my documents and correspondents from Paperless to Paperless-ng would be greatly appreciated.

Ok, thanks for the response AgentXXL and itimpi. I did find this... might try some CLI. Cheers

Hi, I'm having problems getting an external SSD to mount using UD and UD+. The drive is formatted using Apple's APFS file system. The EFI partition mounts however, the APFS partition will not. I've played with UD settings selecting Legacy Mount Point Compatibility? to on and off with no help. I've also checked my Docker settings for binhex-krusader and RW/slave is selected. Having said all that, I can see from my web GUI that the APFS volume is not mounted. I've spent a fair bit of time googling for a fix to no avail, any help appreciated. tower-diagnostics-20210109-1104.zip drives.pdf

This solved my problem!!! Thanks Squid.

Hey Squid, At the risk of hijacking this thread... Thank you, you are correct. The problem was within Sabnzbd settings. However, I still can't seem to get sonarr to automatically import the downloaded file. I can manually import it so the location is accessible from within the sonarr docker. Here's the log output: I've even tried mapping a remote path for the download client in sonarr settings: I'm sure its just something simple I've overlooked. Thanks again.

Hey Squid, Thanks for the reply. I'm not so sure that is my problem. I use SabNZBD as my download client and specify the downloads to go to it's /data location... That's the same /data location I map for sonarr, so I effectively have in place already what you suggest (unless I'm missing something) Kev

Hey Binhex, Kudos for the Sonarr docker. I've just transitioned from Sickbeard to Sickrage and now to Sonarr. Not sure if I've set Sonarr up correctly but I think it's looking for downloaded files in my /config directory not my /data directory. Here's my config setup for the docker file: As you can see, I've specified my docker as per the instructions: Configuration /config This is where sonarr will store it's configuration file, database and logs. /data This path is used retrieve the downloaded files by your downloader application. /media This is where sonarr will scan for media files. Unfortunately, the docker appears to be looking in the /config directory for downloaded files: Here's a screenshot of the System Page on the Sonarr GUI: I have to carry out a manual import after each show completes its download, not ideal. Here's a screenshot of my log file: Any help would be appreciated. Cheers