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

I spoke too soon. [emoji37] Still have false overtemp warnings. Sent from my iPhone using Tapatalk

Just putting this out there..... it may be too early to get excited however, I've just updated to 6.7.1 and upon checking my event logs to do my daily clearing of overtemp warnings,... THERE ARE NONE!! Just getting "There are no event log entries present at this time." I would normally have about 6 overtemp warnings by this stage, anyone else checked their event logs recently after 6.7.1?? M/B: ASRock EP2C602-4L/D16 Version BIOS: American Megatrends Inc. Version P1.90. Dated: 04/11/2018 CPU: 2 x Intel® Xeon® CPU E5-2670 0 @ 2.60GHz

You Legend!!! This solves my "Marvell" problem. 6.7 updates perfectly! For info, I wasn't using any of the marvell based ports on my motherboard however, my PCI card ended up having a marvell controller on it as well. I've ordered a Dell H310 6Gbps SAS HBA card from eBay which should solve any future problems. Thanks so much for your help on this. Regards, Kev tower-diagnostics-20190514-0612.zip

No change for me. I amended my syslinux.cfg file under 6.6.7 and rebooted... all good. I then updated to 6.7 and I still have disk 4 and 5 showing as missing. So no change. tower-diagnostics-20190514-0226.zip

I have also suffered from having 2 of my HDD not being found after upgrading to 6.7. This is a repeatable fault. I have upgraded to 6.7 and reset to 6.6.7 twice now with similar results. I include both diagnostic files from 6.6.7 and 6.7 versions. Any help would be appreciated. tower-diagnostics-20190513-0426.ziptower-diagnostics-20190513-1304.zip

Just adding myself to this thread. Exact same problem with exact same hardware. Sent from my iPhone using Tapatalk

Whoops... rookie mistake. Thanks Squid. All done via the console and vim. The logs look good after a restart. Thanks for everyones input 👍

OK, Now I have the problem that my system doesn't have an /acpi folder in the /etc directory and when I search for *.sh files there isn't an acpi_handler.sh file in my system???

OK... I'll do this I just assumed because you continued to post queries on the thread that the script route didn't work out. Thanks for clarifying

Hi BRit, Did you finally resolve this dilemma? I have exactly the same hardware and log file output as you and would like to clean this up. Any help would be appreciated.