Greygoose

Members
  • Posts

    462
  • Joined

  • Last visited

Everything posted by Greygoose

  1. hey, so my docker filled up today, i located the issue to immich. ive checked my mapings in docker and they all seem fine, any ideas?
  2. Thanks Kilrah, I have jumped the gun slightly and installed a second instance of nextcloud. The current nextcloud was installed and running/used dialy by multiple people since 2019 (time flys).
  3. Is it worth me installing nextcloud from scratch if im having these errors.
  4. Hey itimpi, Spot on, removed it and now working. Thank you
  5. hey, Got a strange issue. I cant restart ANY dockers, it shows the restart button but it doesnt work. I click it any literally nothing happens...
  6. This solved my issue, thank you.
  7. This and the Dynamix file manager plugin solved the update issue for me. When using the dynamix plug click the nextcloud folder in appdata, goto the options at the bottom and change ownership to nobody. Then it updates fine as per above.
  8. Just found this plugin, must have midded it Very happy with it, great work.
  9. im trying to resolve this issue aswell as most others., I get this error when i try to do the upgrade Nextcloud or one of the apps require upgrade - only a limited number of commands are available You may use your browser or the occ upgrade command to do the upgrade Cannot write into "apps" directory. This can usually be fixed by giving the web server write access to the apps directory or disabling the App Store in the config file. An unhandled exception has been thrown: Exception: Environment not properly prepared. in /config/www/nextcloud/lib/private/Console/Application.php:167 Stack trace: #0 /config/www/nextcloud/console.php(99): OC\Console\Application->loadCommands() #1 /config/www/nextcloud/occ(11): require_once('...') #2 {main}root@62ccda3b9b50:/config/www/nextcloud# Id appreciate some advice how to resolve, a small step by step if possible please.
  10. im trying to get paperless-ngx to work but i keep getting an error. the paperless login comes up, when ienter username and password i get the following error my conf file server { listen 443 ssl; listen [::]:443 ssl; server_name paperless-ngx.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; # enable for Authelia include /config/nginx/authelia-server.conf; #Organizr ServerAuth #include /config/nginx/proxy-confs/organizr-auth.subfolder.conf; #auth_request /auth-0; location / { # enable the next two lines for http auth # auth_basic "Restricted"; # auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth # auth_request /auth; # error_page 401 =200 /ldaplogin; # enable for Authelia # include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app 192.168.10.221; set $upstream_port 8000; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; # REMOVE THIS LINE BEFORE SUBMITTING: Additional proxy settings such as headers go below this line, leave the blank line above. } } EDIT: this post helped fix the issue https://github.com/paperless-ngx/paperless-ngx/issues/712
  11. RESOLVED the issue I can now get the paperless-ngx login page to show. but i get this error (image) this is my swag proxy conf file server { listen 443 ssl; listen [::]:443 ssl; server_name paperless-ngx.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; # enable for Authelia include /config/nginx/authelia-server.conf; #Organizr ServerAuth #include /config/nginx/proxy-confs/organizr-auth.subfolder.conf; #auth_request /auth-0; location / { # enable the next two lines for http auth # auth_basic "Restricted"; # auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth # auth_request /auth; # error_page 401 =200 /ldaplogin; # enable for Authelia # include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app 192.168.10.220; set $upstream_port 8000; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; # REMOVE THIS LINE BEFORE SUBMITTING: Additional proxy settings such as headers go below this line, leave the blank line above. } } EDIT Found the answer here https://github.com/paperless-ngx/paperless-ngx/issues/712
  12. is this the default borgmatic repo As i have had this popup in my log
  13. I just checked my reliable backup methods... Or at least i thought so. I dont have a recent appdata backup, only 6mths prior to this issue. I am moving back the data from the cache to the array as I have a replacement drive to install. I will post the diagnostics once this has completed, as hopefully then we can see what files wont copy onto the array.
  14. Hi everyone, I've checked the files not copied to array. I see the issue being the new files created and now mover is unable to overwrite the files. I moved everything back to the cache. So mostly everything is back on the cache drive. But some of the dockers have lost the configs, such as Plex not showing my server to claim. Immich not allowing login of existing accounts and wanting a new account created. Is there a way to resolve this issue.
  15. Hi Jorge, Thanks again. I have narrowed down my issue... hopefully the last one. I have files from my dockers showing on cache and array where the move process stopped, either from me restsrting from a paused system or the docker still running during the move of the appdata from cache to array. How do i sort this, how do i get the rest of the data off the cache to array, move doesnt do anything.
  16. Hi Jorge, I had to restart the server. I put it in maintance mode as i wanted to move everyhting off the cache drive to the array and now im getting errors and it wont move the appdata folder and whatever else is on that drive. Another issue Apr 25 17:00:57 mediaserver kernel: CIFS: VFS: \\192.168.30.201\media Close cancelled mid failed rc:-9 Apr 25 17:03:34 mediaserver kernel: CIFS: VFS: \\192.168.30.201\media Close unmatched open for MID:61222186 Apr 25 17:04:36 mediaserver kernel: CIFS: VFS: \\192.168.30.201\media Close unmatched open for MID:61271094 Apr 25 17:05:07 mediaserver kernel: CIFS: VFS: \\192.168.30.201\media Close unmatched open for MID:61296616 Apr 25 17:05:48 mediaserver emhttpd: shcmd (8373): /usr/local/sbin/mover &> /dev/null & mediaserver-syslog-20230425-1607.zip
  17. Im back again Jorge I tried to stop the array and now its constantly retrying to stop the array. I have no idea whats causing it. I checked the syslog but unable to find a solution. mediaserver-syslog-20230424-1638.zip
  18. Thanks jorge Where did you see these warnings in the logs? just for future refrence.
  19. This looks like it being my cache drive. Is this a drive issue or could it be cable.
  20. This is ongoing for the past week, once i reboot it works for a short period then locks up or docker crashes, Apr 23 05:02:48 mediaserver kernel: CIFS: VFS: \\192.168.30.201\media Close cancelled mid failed rc:-9 Apr 23 05:02:51 mediaserver kernel: I/O error, dev loop2, sector 11430744 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Apr 23 05:02:51 mediaserver kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 1, rd 34070, flush 0, corrupt 6, gen 0 Apr 23 05:03:01 mediaserver kernel: I/O error, dev loop2, sector 11430744 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Apr 23 05:03:01 mediaserver kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 1, rd 34071, flush 0, corrupt 6, gen 0 Apr 23 05:03:11 mediaserver kernel: I/O error, dev loop2, sector 11430744 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Apr 23 05:03:11 mediaserver kernel: BTRFS error (device loop2: state EA): bdev /dev/loop2 errs: wr 1, rd 34072, flush 0, corrupt 6, gen 0 mediaserver-diagnostics-20230422-0821.zip
  21. I had a warning on my unraid machine along with multiple crashes. The following drive is used as the Cache drive. The diagnostics log is below smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.23-Unraid] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Samsung based SSDs Device Model: Samsung SSD 860 PRO 1TB Serial Number: S42NNX0R702113D LU WWN Device Id: 5 002538 e41713dae Firmware Version: RVM02B6Q User Capacity: 1,024,209,543,168 bytes [1.02 TB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Form Factor: 2.5 inches TRIM Command: Available, deterministic, zeroed Device is: In smartctl database 7.3/5440 ATA Version is: ACS-4 T13/BSR INCITS 529 revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sat Apr 22 08:20:06 2023 BST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled DSN feature is: Unavailable ATA Security is: Disabled, frozen [SEC2] Wt Cache Reorder: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x53) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 85) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 1 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0 9 Power_On_Hours -O--CK 097 097 000 - 14223 12 Power_Cycle_Count -O--CK 099 099 000 - 71 177 Wear_Leveling_Count PO--C- 097 097 000 - 65 179 Used_Rsvd_Blk_Cnt_Tot PO--C- 100 100 010 - 0 181 Program_Fail_Cnt_Total -O--CK 100 100 010 - 0 182 Erase_Fail_Count_Total -O--CK 100 100 010 - 0 183 Runtime_Bad_Block PO--C- 100 100 010 - 0 187 Uncorrectable_Error_Cnt -O--CK 100 100 000 - 0 190 Airflow_Temperature_Cel -O--CK 074 060 000 - 26 195 ECC_Error_Rate -O-RC- 200 200 000 - 0 199 CRC_Error_Count -OSRCK 099 099 000 - 13 235 POR_Recovery_Count -O--C- 099 099 000 - 40 241 Total_LBAs_Written -O--CK 099 099 000 - 48420193736 ||||||_ K auto-keep |||||__ C event count ||||___ R error rate |||____ S speed/performance ||_____ O updated online |______ P prefailure warning General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] Address Access R/W Size Description 0x00 GPL,SL R/O 1 Log Directory 0x01 SL R/O 1 Summary SMART error log 0x02 SL R/O 1 Comprehensive SMART error log 0x03 GPL R/O 1 Ext. Comprehensive SMART error log 0x04 GPL,SL R/O 8 Device Statistics log 0x06 SL R/O 1 SMART self-test log 0x07 GPL R/O 1 Extended self-test log 0x09 SL R/W 1 Selective self-test log 0x10 GPL R/O 1 NCQ Command Error log 0x11 GPL R/O 1 SATA Phy Event Counters log 0x13 GPL R/O 1 SATA NCQ Send and Receive log 0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log 0x80-0x9f GPL,SL R/W 16 Host vendor specific log 0xa1 SL VS 16 Device vendor specific log 0xa5 SL VS 16 Device vendor specific log 0xce-0xcf SL VS 16 Device vendor specific log 0xe0 GPL,SL R/W 1 SCT Command/Status 0xe1 GPL,SL R/W 1 SCT Data Transfer SMART Extended Comprehensive Error Log Version: 1 (1 sectors) No Errors Logged SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 2274 - # 2 Short offline Completed without error 00% 2272 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 256 (0x0100) Device State: Active (0) Current Temperature: 26 Celsius Power Cycle Min/Max Temperature: 19/34 Celsius Lifetime Min/Max Temperature: 15/40 Celsius Specified Max Operating Temperature: 70 Celsius Under/Over Temperature Limit Count: 0/0 SMART Status: 0xc24f (PASSED) SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 10 minutes Min/Max recommended Temperature: 0/70 Celsius Min/Max Temperature Limit: 0/70 Celsius Temperature History Size (Index): 128 (28) Index Estimated Time Temperature Celsius 29 2023-04-21 11:10 25 ****** 30 2023-04-21 11:20 24 ***** 31 2023-04-21 11:30 24 ***** 32 2023-04-21 11:40 25 ****** ... ..( 39 skipped). .. ****** 72 2023-04-21 18:20 25 ****** 73 2023-04-21 18:30 28 ********* 74 2023-04-21 18:40 29 ********** 75 2023-04-21 18:50 31 ************ 76 2023-04-21 19:00 29 ********** 77 2023-04-21 19:10 28 ********* 78 2023-04-21 19:20 26 ******* 79 2023-04-21 19:30 26 ******* 80 2023-04-21 19:40 25 ****** 81 2023-04-21 19:50 25 ****** 82 2023-04-21 20:00 25 ****** 83 2023-04-21 20:10 29 ********** 84 2023-04-21 20:20 32 ************* 85 2023-04-21 20:30 34 *************** 86 2023-04-21 20:40 31 ************ 87 2023-04-21 20:50 29 ********** 88 2023-04-21 21:00 32 ************* 89 2023-04-21 21:10 32 ************* 90 2023-04-21 21:20 32 ************* 91 2023-04-21 21:30 33 ************** 92 2023-04-21 21:40 33 ************** 93 2023-04-21 21:50 33 ************** 94 2023-04-21 22:00 29 ********** 95 2023-04-21 22:10 28 ********* 96 2023-04-21 22:20 27 ******** ... ..( 4 skipped). .. ******** 101 2023-04-21 23:10 27 ******** 102 2023-04-21 23:20 26 ******* ... ..( 3 skipped). .. ******* 106 2023-04-22 00:00 26 ******* 107 2023-04-22 00:10 27 ******** 108 2023-04-22 00:20 26 ******* 109 2023-04-22 00:30 27 ******** ... ..( 3 skipped). .. ******** 113 2023-04-22 01:10 27 ******** 114 2023-04-22 01:20 30 *********** 115 2023-04-22 01:30 31 ************ 116 2023-04-22 01:40 29 ********** 117 2023-04-22 01:50 30 *********** 118 2023-04-22 02:00 27 ******** ... ..( 3 skipped). .. ******** 122 2023-04-22 02:40 27 ******** 123 2023-04-22 02:50 26 ******* 124 2023-04-22 03:00 26 ******* 125 2023-04-22 03:10 27 ******** 126 2023-04-22 03:20 27 ******** 127 2023-04-22 03:30 27 ******** 0 2023-04-22 03:40 28 ********* 1 2023-04-22 03:50 26 ******* 2 2023-04-22 04:00 30 *********** 3 2023-04-22 04:10 27 ******** 4 2023-04-22 04:20 26 ******* ... ..( 21 skipped). .. ******* 26 2023-04-22 08:00 26 ******* 27 2023-04-22 08:10 25 ****** 28 2023-04-22 08:20 25 ****** SCT Error Recovery Control: Read: Disabled Write: Disabled Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description 0x01 ===== = = === == General Statistics (rev 1) == 0x01 0x008 4 71 --- Lifetime Power-On Resets 0x01 0x010 4 14223 --- Power-on Hours 0x01 0x018 6 48420193736 --- Logical Sectors Written 0x01 0x020 6 872604660 --- Number of Write Commands 0x01 0x028 6 122307369823 --- Logical Sectors Read 0x01 0x030 6 881469510 --- Number of Read Commands 0x01 0x038 6 2294000 --- Date and Time TimeStamp 0x04 ===== = = === == General Errors Statistics (rev 1) == 0x04 0x008 4 0 --- Number of Reported Uncorrectable Errors 0x04 0x010 4 1 --- Resets Between Cmd Acceptance and Completion 0x05 ===== = = === == Temperature Statistics (rev 1) == 0x05 0x008 1 26 --- Current Temperature 0x05 0x020 1 40 --- Highest Temperature 0x05 0x028 1 15 --- Lowest Temperature 0x05 0x058 1 70 --- Specified Maximum Operating Temperature 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 424 --- Number of Hardware Resets 0x06 0x010 4 0 --- Number of ASR Events 0x06 0x018 4 13 --- Number of Interface CRC Errors 0x07 ===== = = === == Solid State Device Statistics (rev 1) == 0x07 0x008 1 3 N-- Percentage Used Endurance Indicator |||_ C monitored condition met ||__ D supports DSN |___ N normalized value Pending Defects log (GP Log 0x0c) not supported SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 4 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x0008 2 0 Device-to-host non-data FIS retries 0x0009 2 47 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 47 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x000d 2 0 Non-CRC errors within host-to-device FIS 0x000f 2 0 R_ERR response for host-to-device data FIS, CRC 0x0010 2 0 R_ERR response for host-to-device data FIS, non-CRC 0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC 0x0013 2 0 R_ERR response for host-to-device non-data FIS, non-CRC
  22. Ive been having issues with borgmatic not running. What do these logs mean
  23. No gui needed, as sdub said once the configs are setup its leave alone and let it do its thing. The most i need to do is break-lock if i restart or stop the docker during the backup process.
  24. EDITED Ok i had multiple issues sorting this, most relating to firewall rules causing confusion. I also went on a circle edditing prefrences.xml, which i had to use krusader to change permissions so i could edit in windows. I dont think this was needed so just use the below instructions. --------------------------------------------- Log into Plex.tv. Then go to https://www.plex.tv/claim/. You get a code that is valid for 4 minutes, if you need more time than 4 minutes, just reload the page and use the new code. Leave this window open. Enter the following within unraid terminal (click icon on the main page) curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=CLAIM_CODE_HERE' If your Claim Code is claim-TxXXA3SYXX55XcXXjQt6, you enter the following in terminal/command prompt: curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=claim-TxXXA3SYXX55XcXXjQt6' Wait a little bit after entering, after 10 seconds or so you will see stuff appear on your screen. That's it, after this step you should see your Server visible again in Plex (just open it as you usually would, or via https://app.plex.tv/). Link to source ------------------------------------------- Use terminal within unraid (little icon main page). 5minute fix at most