blakeslade

Members
  • Posts

    29
  • Joined

  • Last visited

Posts posted by blakeslade

  1. Hello!

     

    I'm getting an Unable to Connect error and then an Internal Server Error when I try again to connect to my Nextcloud docker.

     

    Had some major PSU issues recently resulting is false HDD failures and errors. Replaced PSU, MB, CPU and RAM and rebuilt the server and the array. IP address has changed as well, perhaps this has something to do with it?

     

    Initially none of my dockers worked, but after a couple of reboots they are all working except for NC and Transmission.

     

    Thanks for your help!

  2. Hello!

     

    I'm getting an "Unable to Connect" error to my Transmission docker. Tried both FF and Edge same error. While waiting for a reply I went ahead and removed the docker and then reinstalled it. Still having the same issue.

     

    How do I resolve an unable to connect error via web browser for transmission? And while we're at it, is it usually the same solution for all dockers?

     

    Secondly, how do I connect via consol?

     

    Had some major PSU issues recently resulting is false HDD failures and errors. Replaced PSU, MB, CPU and RAM and rebuilt the server and the array. IP address has changed as well, perhaps this has something to do with it?

     

    Initially none of my dockers worked, but a couple of reboots later and a HDD xfs_repair only Transmission and NC are refusing to work.

     

    Thanks for your help!

  3. Initially none of them worked at all using the GUI. I am not familiar with how to connect via console.

     

    I am now only having issues with two dockers: Nextcloud (unable to connect initially then internal server error) and Transmission client (unable to connect).

     

    How to connect via console?

  4. Thank you JorgeB.

     

    And now I have a question about the dockers, I am unable to connect to any of them. Is this as simple as redoing the settings files?

     

    When I upgraded the MB, CPU, RAM and PSU the server got a new ip address. Should I tell the router to set the old one?

     

    Thanks!

  5. Here is the xfs_repair -n result:

     

    Quote

    Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... agf_freeblks 205949954, counted 205949590 in ag 3 agf_longest 205932767, counted 205934435 in ag 3 agi_freecount 1226, counted 1258 in ag 3 agf_freeblks 170272000, counted 170277590 in ag 4 agf_longest 170236487, counted 170233465 in ag 4 agf_freeblks 138193913, counted 143248099 in ag 1 agf_longest 138049324, counted 143132200 in ag 1 agi_freecount 1342, counted 1447 in ag 1 agf_freeblks 164830396, counted 164843628 in ag 2 agf_longest 164786646, counted 164788526 in ag 2 agf_freeblks 123306136, counted 127540887 in ag 0 agf_longest 121943290, counted 127191054 in ag 0 agi_freecount 1195, counted 1320 in ag 2 agf_freeblks 23442946, counted 23447163 in ag 5 agf_longest 23432351, counted 23436698 in ag 5 agi_freecount 1253, counted 1323 in ag 5 agi_freecount 1395, counted 1483 in ag 4 sb_ifree 7760, counted 8180 sb_fdblocks 825995421, counted 835307033 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 imap claims a free inode 2098448 is in use, would correct imap and clear inode imap claims a free inode 2099020 is in use, would correct imap and clear inode imap claims a free inode 16051712 is in use, would correct imap and clear inode imap claims a free inode 16052347 is in use, would correct imap and clear inode imap claims a free inode 16052417 is in use, would correct imap and clear inode imap claims a free inode 16053297 is in use, would correct imap and clear inode imap claims a free inode 16053307 is in use, would correct imap and clear inode imap claims a free inode 16053553 is in use, would correct imap and clear inode imap claims a free inode 16053683 is in use, would correct imap and clear inode imap claims a free inode 16053685 is in use, would correct imap and clear inode imap claims a free inode 16072524 is in use, would correct imap and clear inode imap claims a free inode 16075264 is in use, would correct imap and clear inode imap claims a free inode 16075280 is in use, would correct imap and clear inode imap claims a free inode 16075298 is in use, would correct imap and clear inode imap claims a free inode 16075315 is in use, would correct imap and clear inode imap claims a free inode 16075332 is in use, would correct imap and clear inode imap claims a free inode 16077061 is in use, would correct imap and clear inode imap claims a free inode 16077067 is in use, would correct imap and clear inode imap claims a free inode 16077068 is in use, would correct imap and clear inode imap claims a free inode 16077069 is in use, would correct imap and clear inode imap claims a free inode 16077070 is in use, would correct imap and clear inode imap claims a free inode 16077071 is in use, would correct imap and clear inode imap claims a free inode 16077072 is in use, would correct imap and clear inode imap claims a free inode 16077073 is in use, would correct imap and clear inode imap claims a free inode 16077074 is in use, would correct imap and clear inode imap claims a free inode 16077075 is in use, would correct imap and clear inode imap claims a free inode 16077076 is in use, would correct imap and clear inode imap claims a free inode 16077077 is in use, would correct imap and clear inode imap claims a free inode 16077080 is in use, would correct imap and clear inode imap claims a free inode 16077081 is in use, would correct imap and clear inode imap claims a free inode 16077083 is in use, would correct imap and clear inode imap claims a free inode 16077108 is in use, would correct imap and clear inode imap claims a free inode 16077116 is in use, would correct imap and clear inode imap claims a free inode 16077187 is in use, would correct imap and clear inode imap claims a free inode 16077195 is in use, would correct imap and clear inode imap claims a free inode 16077894 is in use, would correct imap and clear inode imap claims a free inode 16077903 is in use, would correct imap and clear inode imap claims a free inode 16077904 is in use, would correct imap and clear inode imap claims a free inode 16077905 is in use, would correct imap and clear inode imap claims a free inode 16077906 is in use, would correct imap and clear inode imap claims a free inode 16077907 is in use, would correct imap and clear inode imap claims a free inode 16077913 is in use, would correct imap and clear inode imap claims a free inode 16077919 is in use, would correct imap and clear inode imap claims a free inode 16077922 is in use, would correct imap and clear inode imap claims a free inode 16077923 is in use, would correct imap and clear inode imap claims a free inode 16077945 is in use, would correct imap and clear inode imap claims a free inode 16078016 is in use, would correct imap and clear inode imap claims a free inode 16078018 is in use, would correct imap and clear inode imap claims a free inode 16078034 is in use, would correct imap and clear inode imap claims a free inode 16078036 is in use, would correct imap and clear inode imap claims a free inode 16078043 is in use, would correct imap and clear inode imap claims a free inode 16078044 is in use, would correct imap and clear inode imap claims a free inode 16078066 is in use, would correct imap and clear inode imap claims a free inode 16078068 is in use, would correct imap and clear inode imap claims a free inode 16078069 is in use, would correct imap and clear inode imap claims a free inode 16337485 is in use, would correct imap and clear inode imap claims a free inode 16339328 is in use, would correct imap and clear inode imap claims a free inode 16339382 is in use, would correct imap and clear inode imap claims a free inode 16344633 is in use, would correct imap and clear inode imap claims a free inode 16344635 is in use, would correct imap and clear inode imap claims a free inode 16344636 is in use, would correct imap and clear inode imap claims a free inode 16344639 is in use, would correct imap and clear inode imap claims a free inode 16350482 is in use, would correct imap and clear inode imap claims a free inode 16772427 is in use, would correct imap and clear inode imap claims a free inode 16772428 is in use, would correct imap and clear inode imap claims a free inode 16772429 is in use, would correct imap and clear inode imap claims a free inode 16772430 is in use, would correct imap and clear inode imap claims a free inode 16772444 is in use, would correct imap and clear inode imap claims a free inode 16782277 is in use, would correct imap and clear inode imap claims a free inode 16793899 is in use, would correct imap and clear inode imap claims a free inode 16795088 is in use, would correct imap and clear inode imap claims a free inode 16795089 is in use, would correct imap and clear inode imap claims a free inode 16795090 is in use, would correct imap and clear inode imap claims a free inode 16795091 is in use, would correct imap and clear inode imap claims a free inode 16795092 is in use, would correct imap and clear inode imap claims a free inode 16795093 is in use, would correct imap and clear inode imap claims a free inode 16795094 is in use, would correct imap and clear inode imap claims a free inode 16795095 is in use, would correct imap and clear inode imap claims a free inode 16795096 is in use, would correct imap and clear inode imap claims a free inode 16795098 is in use, would correct imap and clear inode imap claims a free inode 16795100 is in use, would correct imap and clear inode imap claims a free inode 16795126 is in use, would correct imap and clear inode imap claims a free inode 16795127 is in use, would correct imap and clear inode imap claims a free inode 16799166 is in use, would correct imap and clear inode imap claims a free inode 16799167 is in use, would correct imap and clear inode - agno = 1 - agno = 2 - agno = 3 data fork in ino 6446624915 claims free block 826511721 - agno = 4 data fork in ino 8589935586 claims free block 1073743179 imap claims in-use inode 8589935586 is free, would correct imap data fork in ino 8589935648 claims free block 1073747565 data fork in ino 8589935654 claims free block 1073771920 data fork in ino 8589935663 claims free block 1073769938 data fork in ino 8589935670 claims free block 1073769000 data fork in ino 8589935676 claims free block 1089399469 imap claims a free inode 8589936110 is in use, would correct imap and clear inode - agno = 5 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... free space (4,1700-1701) only seen by one free space btree - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 2 - agno = 4 - agno = 5 - agno = 1 entry "ab85caaf60cf88419b9ee0e186964d62b8555915.jpg" at block 0 offset 96 in directory inode 152 references free inode 16077068 would clear inode number in entry at offset 96... entry "ab40142fee35c21a40c06c295ce520d0ff834c59.jpg" at block 0 offset 2600 in directory inode 152 references free inode 16077083 would clear inode number in entry at offset 2600... entry "0ea283db8e6159d20f7b0d132795fd2c7aeaafc0.jpg" at block 0 offset 1480 in directory inode 154 references free inode 16053685 would clear inode number in entry at offset 1480... entry "0e3ed499d60c1076079398dafafd63553c1c21ad.jpg" at block 0 offset 1640 in directory inode 154 references free inode 16077067 would clear inode number in entry at offset 1640... entry "d85e09e88e80aefb1d8db1beedbfeb1ff602d509.jpg" at block 0 offset 1008 in directory inode 162 references free inode 16077072 would clear inode number in entry at offset 1008... entry "d832b71fe3d94c45ff77cabb70060ace72487519.jpg" at block 0 offset 1168 in directory inode 162 references free inode 16077919 would clear inode number in entry at offset 1168... entry "d8e8e1c8c41870e670c0cba2381e7d83b9b08e8c.jpg" at block 0 offset 1328 in directory inode 162 references free inode 16072524 would clear inode number in entry at offset 1328... entry "d86c31a996a1069f7d5fab174b601b19bb52bb46.jpg" at block 0 offset 1488 in directory inode 162 references free inode 16078069 would clear inode number in entry at offset 1488... entry "bf3a85ff86cd9418b505ddd8d081cb5406ac0d49.jpg" at block 0 offset 200 in directory inode 164 references free inode 16077922 would clear inode number in entry at offset 200... entry "1483362e6c55544f07434795e203458c182b4739.jpg" at block 0 offset 1272 in directory inode 168 references free inode 16077894 would clear inode number in entry at offset 1272... entry "14cba337c807d0920c3ae20f8aeca9f0e393c5f2.jpg" at block 0 offset 1432 in directory inode 168 references free inode 16077923 would clear inode number in entry at offset 1432... entry "bc913203d55aaec203c5b26f9aaccc7da2b0c419.jpg" at block 0 offset 360 in directory inode 170 references free inode 16077906 would clear inode number in entry at offset 360... entry "b68e061138fbf8b7ee4a20dc853f4c5fca3359b4.jpg" at block 0 offset 1216 in directory inode 172 references free inode 16077071 would clear inode number in entry at offset 1216... entry "b692af99fcf4c38cee822a7ca8522405ee9346a4.jpg" at block 0 offset 1376 in directory inode 172 references free inode 16077116 would clear inode number in entry at offset 1376... entry "b6d23bd199ec5bbc5e0ce2e1d0f3ed8aec584dad.jpg" at block 0 offset 1536 in directory inode 172 references free inode 16078034 would clear inode number in entry at offset 1536... entry "7f2a38fb22e677bb5126216c49e36f29f97fa469.jpg" at block 0 offset 1696 in directory inode 174 references free inode 16077069 would clear inode number in entry at offset 1696... entry "7f7d3ce62f301f8318327d000633a5dec5f06414.jpg" at block 0 offset 1856 in directory inode 174 references free inode 16077073 would clear inode number in entry at offset 1856... entry "297c4ef8b8cc413ea720652112b1ced0b802b14c.jpg" at block 0 offset 1480 in directory inode 176 references free inode 16077108 would clear inode number in entry at offset 1480... entry "dbc19db6486a6d91980bc061fa21a8d729b68744.jpg" at block 0 offset 520 in directory inode 180 references free inode 16075264 would clear inode number in entry at offset 520... entry "db8c2402eee5053fb7b61d38f49a7e4f8fecd59c.jpg" at block 0 offset 680 in directory inode 180 references free inode 16078016 would clear inode number in entry at offset 680... entry "db2ef792dc74372a49a6c5380e8d183558befdd5.jpg" at block 0 offset 840 in directory inode 180 references free inode 16078018 would clear inode number in entry at offset 840... entry "9afc7958d465a732da528e46e8870dfa1c1e5dbd.jpg" at block 0 offset 416 in directory inode 182 references free inode 16075280 would clear inode number in entry at offset 416... entry "9ae2ff9f80888b89751a070b74a65b7c63cb654d.jpg" at block 0 offset 576 in directory inode 182 references free inode 16078036 would clear inode number in entry at offset 576... entry "75f97cb41375527482ce73d3397b918b1604a25d.jpg" at block 0 offset 2072 in directory inode 184 references free inode 16077904 would clear inode number in entry at offset 2072... entry "86508a98a89e28df4bcb78ff7c13cc990988c5dc.png" in shortform directory 191 references free inode 16078068 would have junked entry "86508a98a89e28df4bcb78ff7c13cc990988c5dc.png" in directory inode 191 entry "md.log" in shortform directory 8589935659 references free inode 8589954248 would have junked entry "md.log" in directory inode 8589935659 entry "frame159.xtc" in shortform directory 8589935659 references free inode 8589954252 would have junked entry "frame159.xtc" in directory inode 8589935659 entry "checkpt.crc" in shortform directory 8589935659 references free inode 8589954255 would have junked entry "checkpt.crc" in directory inode 8589935659 entry "state_prev.cpt" in shortform directory 8589935659 references free inode 8589942499 would have junked entry "state_prev.cpt" in directory inode 8589935659 would have corrected i8 count in directory 8589935659 from 10 to 6 setting reflink flag on inode 6446624915 setting reflink flag on inode 8589935238 setting reflink flag on inode 8589935266 setting reflink flag on inode 8589935321 setting reflink flag on inode 8589935550 setting reflink flag on inode 8589935558 setting reflink flag on inode 8589935650 setting reflink flag on inode 6446884318 Missing reference count record for (4/146) len 1 count 2 setting reflink flag on inode 8589935658 setting reflink flag on inode 8589935661 Missing reference count record for (3/21205309) len 44 count 2 setting reflink flag on inode 8589935662 Missing reference count record for (4/154) len 1 count 2 Missing reference count record for (4/179) len 1 count 2 Missing reference count record for (4/536) len 1 count 2 Missing reference count record for (4/561) len 1 count 2 Missing reference count record for (4/2092) len 5 count 2 setting reflink flag on inode 8589935664 setting reflink flag on inode 8589935670 setting reflink flag on inode 8589935671 Missing reference count record for (4/27175) len 1 count 2 setting reflink flag on inode 8589938573 setting reflink flag on inode 8589939264 No modify flag set, skipping phase 5 Inode allocation btrees are too corrupted, skipping phases 6 and 7 No modify flag set, skipping filesystem flush and exiting.

     

    and then again with xfs_repair -v:

    Quote

    Phase 1 - find and verify superblock... - block cache size set to 715704 entries Phase 2 - using internal log - zero log... zero_log: head block 4131029 tail block 4131017 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.

     

    When array is started the drive is mounted but I cannot browse the content. How do I replay the log? Or do I use xfs_repair -L to destroy the log?

  6. Hello!

     

    I'm a basic Unraid user and have run into some trouble with my server. As the title reads, I have a data disk (with data on it) that is being reported as unmountable and another disk with errors reported when building a new config. I have attached the tower diagnostics the downloaded smart report for sdh and sdf and a screen shot of Tower Main.

     

    What I have done:

    - Ran a full smart diagnostic which passes on the unmountable disk (sdh)

    - Mounted array in Maintenance Mode and ran xfs_repair (through GUI) with arguments removed on both disks (sdh and sdf)

     

    I don't know what steps to take next?

     

    A little back story for some context:

     

    A Defective PSU has been giving random HDD errors off and on over the past year. I didn't realize it was the PSU and kept changing SATA cables, SATA headders and PCIe slots for the LSI SATA card, and SATA brake out cables. This would work for a little while then errors would appear again. Only this past week did I make the connection, but not before I went to Tools and selected "New Config" and all hell broke loose. HDD's were disappearing with every boot and errors in parity. In hind sight I should have made a post here in the forums and saved myself a whole lot of trouble.

     

    I really appreciate your help!

    Tower_Main_March_20.jpg

    tower-diagnostics-20220320-1536.zip tower-smart-20220319-2009.zip xfs_repair_output.txt tower-smart-20220320-1739-sdf.zip

  7. On 1/14/2021 at 7:23 AM, skois said:

    I was able to reproduce, something after the install is messing up the trusted domains.
    So lets do it all over again.
    go to 

    - /mnt/user/appdata/nextcloud  - delete everything there.

    - /mnt/user/appdata/mariadb - delete everything there.

    - /mnt/user/nextcloud - delete everything there *if you have DATA there, back them up first*(this is the /data folder, i suggest cleaning because i saw before you created a bunch of admins and there will be a lot of files assosiated with them there that you wont need.)

     

    Ok, now delete both dockers 

    - mariadb

    - nextcloud

     

    * Go to Apps.
    * Install mariadb (check that is on bridge network for now)

    * Open console

     

    
    mysql -uroot -p
    password
    
    create user 'dbusernextcloud' identified by 'mypassword';
    
    create database if not exists nextclouddb;
    
    grant all privileges on nextclouddb.* to 'dbusernextcloud' identified by 'mypassword';

    * Close console.

    * Go to Apps

    * Install nextcloud (check that is on bridge network for now)
    * Open WebUI (if it opens, do the initial setup)

    - database user: dbusernextcloud

    - database password: mypassword

    - database name: nextclouddb

    - localhost: unraidip:portofmariadb

    fill also username and password for admin.
    *Click Finish Setup. (DONT CLOSE PAGE on 504 error)

    *With the page still displaying 504 error, go to /mnt/user/appdata/nextcloud/www/nextcloud/config/ and edit the config.php

    truested_domain section should look like this (dont forget the comma after each entry). ofc change the ips according to yours.
    You should only need to add the line 1, 0 should be there.


      'trusted_domains' => 
      array (
        0 => '10.0.0.72:444',
        1 => '10.0.0.*',
      ),


    *After saving the config.php. Go back to your browser and refresh the page. It should now ask you to log in. 

    In case still shows 504 error. Try restarting docker WITHOUT CLOSING the page. and when docker restarts, refresh the page once more.


    Hopefully this will get you started!

     

    Thank you skois! I now have nc up and running!

     

    I'm amazed that you were able to recreate my issue and state the work around so easily. Thank you for taking the time to help me out. I really appreciate it.

     

    I'm going to continue the setup process here, with letsencrypt (after I get letsencrypt installed using spaceinvaderone's instructions).

     

    Is there another resource that will be helpful to me?

  8. 4 hours ago, skois said:

    I was able to reproduce, something after the install is messing up the trusted domains.
    So lets do it all over again.
    go to 

    - /mnt/user/appdata/nextcloud  - delete everything there.

    - /mnt/user/appdata/mariadb - delete everything there.

    - /mnt/user/nextcloud - delete everything there *if you have DATA there, back them up first*(this is the /data folder, i suggest cleaning because i saw before you created a bunch of admins and there will be a lot of files assosiated with them there that you wont need.)

     

    Ok, now delete both dockers 

    - mariadb

    - nextcloud

     

    * Go to Apps.
    * Install mariadb (check that is on bridge network for now)

    * Open console

     

    
    mysql -uroot -p
    password
    
    create user 'dbusernextcloud' identified by 'mypassword';
    
    create database if not exists nextclouddb;
    
    grant all privileges on nextclouddb.* to 'dbusernextcloud' identified by 'mypassword';

    * Close console.

    * Go to Apps

    * Install nextcloud (check that is on bridge network for now)
    * Open WebUI (if it opens, do the initial setup)

    - database user: dbusernextcloud

    - database password: mypassword

    - database name: nextclouddb

    - localhost: unraidip:portofmariadb

    fill also username and password for admin.
    *Click Finish Setup. (DONT CLOSE PAGE on 504 error)

    *With the page still displaying 504 error, go to /mnt/user/appdata/nextcloud/www/nextcloud/config/ and edit the config.php

    truested_domain section should look like this (dont forget the comma after each entry). ofc change the ips according to yours.
    You should only need to add the line 1, 0 should be there.


      'trusted_domains' => 
      array (
        0 => '10.0.0.72:444',
        1 => '10.0.0.*',
      ),


    *After saving the config.php. Go back to your browser and refresh the page. It should now ask you to log in. 

    In case still shows 504 error. Try restarting docker WITHOUT CLOSING the page. and when docker restarts, refresh the page once more.


    Hopefully this will get you started!

     

    I say hot damn! I am floored by your steps. Thank you so much skois! I will get on this later today, and report my results.

  9. 22 minutes ago, skois said:

    Correct!
    Actually /mnt/user contains both data cache and array, depending on the share configuration

    Sent from my Mi 10 Pro using Tapatalk
     

    Getting a 504 Gateway time out error now. I feel like this is a comedy of errors on my end.

     

    Here are the commands I entered for mariadb:

     

    mysql -uroot -p
    password

    create user 'nextcloud' identified by 'mypassword';

    create database if not exists nextcloud;

    grant all privileges on nextcloud.* to 'nextcloud' identified by 'mypassword';

     

    I used nano for the config.php file, which looked like this before opening the nc webui:

     

    <?php
    $CONFIG = array (
      'memcache.local' => '\\OC\\Memcache\\APCu',
      'datadirectory' => '/data',
      'trusted_domains' =>
      array (
        0 => '10.0.0.72:444',
        1 => '10.0.0.*',
      ),
      );

     

    Now the config.php looks like this (after the 504 timeout):

     

    <?php
    $CONFIG = array (
      'memcache.local' => '\\OC\\Memcache\\APCu',
      'datadirectory' => '/data',
      'trusted_domains' =>
      array (
        0 => '10.0.0.72:444',
      ),
      'instanceid' => 'ocj51yowyofq',
      'passwordsalt' => 'MrmUOLhtq7TnzskZxDQePo8gChclH+',
      'secret' => 'Ee5QoOEXhdGDvIzD61ogzdx4g53tXVsCe6RB2eddED4DnWzI',
      'dbtype' => 'mysql',
      'version' => '20.0.4.0',
      'overwrite.cli.url' => 'https://10.0.0.72:444',
      'dbname' => 'nextcloud',
      'dbhost' => '10.0.0.72:444',
      'dbport' => '',
      'dbtableprefix' => 'oc_',
    );

     

    I've attached an updated nextcloud.log from the /data folder (on my array /mnt/user/Nextcloud) and docker page logs.

     

    Ideas?

     

    nextcloud.log Nextcloud_Log_2021.01.13.txt Mariadb_log_2021.01.13.txt

  10. 16 minutes ago, skois said:

    If this is a new installation and you don't have any data, i would suggest delete appdata from both database and nextcloud and force update both dockers (open advanced view on docker tab). and start fresh.
    That means you have to recreate the databases (check spaceinvaders video for the commands).
    Something wasn't completed correctly on the 1st install and now it seems to fail every time.
    Also before starting the initial setup (after wiping appdata and forcing update the dockers) 
    Add the trusted domain.
      'trusted_domains' => 
      array (
        0 => '10.0.0.72:444',
        1 => '10.0.0.*',
      ),

    Thanks ton skois, I'll give that a go this afternoon.

     

    I'm not currently using a cache drive, so my appdata is located at: /mnt/user/appdata

     

    That's the only place I need to delete the data?

  11. 22 minutes ago, John Graham said:

    The Answer is yes use nano or

    this worked on my system

    open up the shell for nexcloud

    cd /config/www/nextcloud

    pwd

    should show ":/config/www/nextcloud#"

    copy and paste

    occ config:system:set trusted_domains 1 --value=192.168.1.*

    change your ip to the one you need ... Did this from memory hope it works and helps you out

     

    So nextcloud is still stuck in the inital setup phase. It's stuck there. Every time I open the WebGUI it's asking me for an admin user and pw along with db options.

     

    When I open a shell to "/config/www/nextcloud" this is what I get:

     

    occ config:system:set trusted_domains 1 --value=10.0.0.*


    Nextcloud is not installed - only a limited number of commands are available

    There are no commands defined in the "config:system" namespace.
     

    At this point I've tried a few times and am running out of user names since it seems to save the ones I've tried in the past (lots of admin variations)?

     

    Thanks again!

  12. On 1/12/2021 at 3:21 AM, skois said:

    If we assume your lan pc is on the same subnet and your subnet is 10.0.0.0/24, then on your config.php on nc add this on the trusted domains.
    It should work now



      'trusted_domains' => 
      array (
        0 => '10.0.0.72:444',
        1 => '10.0.0.*',
      ),

     

    Thanks for your help! Gave this a shot but no go. I stopped the nc docker, updated the config.php file using krusader and confirmed that I had the changes saved. Then started up the nc container which brought me back to the initial set up page. I entered all the details as before and ended up back at the Internal server error page. Looking at the config.php file I see that my entry has been removed and it's back the way it was now.

     

    Should I be using nano or a command line based editor instead? I've attached a new log file and the config.php as it was edited, before being reset.

     

    Thank your for your time skois! I'm sure you're very busy and I appreciate your help.

     

    Edit: I've got wireguard installed, is that causing a problem?

    nextcloud.log config.php

  13. 1 hour ago, ainuke said:

    When you "remove and reinstall" the plugin (docker container?), did you delete the "deluge" folder in /appdata?
    If not, your config is still there and the new container install will see it and perpetuate the problem.

    Rookie mistake. Thank you for pointing that out.

     

    You are correct, I did not delete the "deluge" foler in /appdata.

     

    Would explain why some other docker containers are also having some issues due to old configs remaining.

     

    Will report back of the issue is not resolved.

     

    Thank you!

  14. Morning!

     

    Just installed Deluge 2.0.3-2-201906121747 on Unraid 6.8.3 and I'm unable to log in. I'm getting stuck in an endless loop at the login prompt. The default password, "deluge", is accepted, but then the prompt reappears. In the background I can see a prompt asking me to change my password, but I can't select it.

     

    I've tried to remove and install the plugin again, but I get the same result.

     

    Ideas now I can get past this?


    Thanks so much!

    deluge.png

    deluge_setup.png

  15. Did some reading (oh oh) here, https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive

     

    All SMART tests have passed (took the liberty of doing parity and Disk 1).

    - Reallocated_Sector_Ct, Current_Pending_Sector, and UDMA_CRC_Error_Count Raw_Values are '0'

     

    So, I've followed the safe instructions to rebuild the array and am waiting for the process to complete.

     

    Thanks for your help JorgeB!

    tower-diagnostics-20201208-1532.zip

  16. Cables replaced on disk 2 and 3!

     

    Issues with disk 3 now appear to be resolved.

     

    disk 2 is still being reported as "disabled", see screen below.

     

    I am running the Extended SMART scan on disks 2 and 3.

     

    What additional diagnostics should I run for disk 2?

     

    My new HDD's arrive this week, what steps do I follow to upgrade from my current setup? What would be an optimal set up for 4 x 6TB drives and 3 x 3TB drives (assuming disk 2 is finished)?

     

    Thanks!

    Array_updated.jpg

    • Like 1
  17. Hello all!

     

    I've got some HDD problems and would like guidance on how to proceed. I've attached syslog and diagnostics from this morning.

     

    The situation:

     

    I have 2 drives with errors.  I discovered these errors while attempting to set up Nextcloud using spaceinvaderone's YT instructions when I couldn't get nextcloud to start. I know it's unrelated to the drive failing.

     

    I have a 9TB array: 1 x 3TB parity and 3 x 3TB drives (screen: 'Array_drives').

     

    I took the array offline and remounted in maintenance mode and am currently running Read-check which is 4.1% complete. I also have the extended SMART check running on both drives.

     

    I have ordered replacement drives (4 x 6TB WDC WD6002FRYZ) so I will replace and upgrade at the same time once they arrive next week.

     

    I'd like to know how to proceed from here?

    1) Until the drives arrive, what steps do I take in preparation?

    2) What steps do I take to replace and upgrade the drives?

     

    My plan is to have 2 x 6TB parity and then 12TB array (2 x 6TB) and a 2 x 3TB cash pool

     

    Thank you so much for your advice and I appreciate all you help!

    Array_drives.jpg

    tower-diagnostics-20201204-0759.zip tower-syslog-20201204-1258.zip

  18. 4 hours ago, saarg said:

    There isn't really a need to do it this way anymore.

    If the usb card have its own ID (4 digits:4 digits) then you can stub the card in the syslinux.conf file and then choose the card in the other PCI devices part in the VM template.

    If the usb card shares an ID with a USB controller on the motherboard, you have to use the new method of stubbing the card using a config file and the PCI number.

    Thank you for replying! I continued to research and read last night an managed to pass the card through using the VFIO-PCI Config plugin.

     

    I did give the syslinux.conf method a try by clicking on the flash drive in the GUI, and added the USB controller ID after the "append". With that method the USB controller appeared in the PCI devices section in the VM settings, but then I had the same "guest" error starting up the VM.

     

    After removing that line from the syslinux.conf and using the VFIO plugin instead it works!

     

    USB PnP is now functional in my W10 VM and so does the Oculus Rift.

  19. Good day all!

     

    First of all, thank you very much for this guide! It was very helpful, though I am experiencing an error when I add the hostdev lines of code to the XML file:

     

    Quote

    Execution error
    internal error: Non-endpoint PCI devices cannot be assigned to guests

     

    I just installed a PCIe USB3.0 card in my unraid system since the onboard ports have not been playing nicely with anything I plug into them. I've got a W10 VM set up and running nicely that I want to game with. There's a GTX1070 already passed through and I am able to run Dirt Rally 2.0 on my tv and a G27 wheel.

     

    Since we're social distancing now, I picked up an Oculus Rift and am having trouble getting it detected in the VM.

     

    If I use the VM settings GUI to set up the USB passthrough for all devices (KB, mouse, wheel, Rift headset and Rift sensor), only the Rift headset is not detected within the VM W10 guest (KB, mouse, wheel and Rift sensor all detect fine).

     

    I was hoping to pass the USB PCIe card to benefit from USB PnP which would then solve my Rift issue.

     

    Here are the results of the steps I followed in the OP:

     

    ls | grep USB

    Quote


    00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
    00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
    00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
    04:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10)
    05:00.0 USB controller: VIA Technologies, Inc. VL80x xHCI USB 3.0 Controller (rev 03)

     

     

    lsusb

    Quote

    Bus 006 Device 005: ID 0781:558b SanDisk Corp. Extreme **my test USB key in 1st slot**
    Bus 006 Device 006: ID 0781:558b SanDisk Corp. Extreme **my test USB key in 2nd slot**
    Bus 005 Device 003: ID 046d:c294 Logitech, Inc. Driving Force **in 3rd**
    Bus 005 Device 005: ID 413c:2003 Dell Keyboard **4th**
    Bus 005 Device 004: ID 1532:0001 Razer Diamondback **5th**


    readlink /sys/bus/usb/devices/usb5

    Quote

    ../../../devices/pci0000:00/0000:00:1c.1/0000:04:00.0/usb5

    readlink /sys/bus/usb/devices/usb6

    Quote

    ../../../devices/pci0000:00/0000:00:1c.1/0000:04:00.0/usb6

     

    PCIe ACS override is ENABLED

    Quote

    IOMMU group 8:    [8086:1e12] 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)

     

    The lines I added to my XML file:

    Quote

        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x00' slot='0x1c' function='0x1'/>
          </source>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x00' slot='0x1c' function='0x4'/>
          </source>
        </hostdev>

     

    Without those two hostdev entries (or even just one) I get the error above. Here is my XML file in whole:

    Quote

    <?xml version='1.0' encoding='UTF-8'?>
    <domain type='kvm'>
      <name>Player2</name>
      <uuid>bc7b1d2e-b6e2-bf90-72d2-dd34d956efae</uuid>
      <description>Prodigal son returns</description>
      <metadata>
        <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
      </metadata>
      <memory unit='KiB'>8912896</memory>
      <currentMemory unit='KiB'>8912896</currentMemory>
      <memoryBacking>
        <nosharepages/>
      </memoryBacking>
      <vcpu placement='static'>6</vcpu>
      <cputune>
        <vcpupin vcpu='0' cpuset='1'/>
        <vcpupin vcpu='1' cpuset='5'/>
        <vcpupin vcpu='2' cpuset='2'/>
        <vcpupin vcpu='3' cpuset='6'/>
        <vcpupin vcpu='4' cpuset='3'/>
        <vcpupin vcpu='5' cpuset='7'/>
      </cputune>
      <os>
        <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type>
        <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
        <nvram>/etc/libvirt/qemu/nvram/bc7b1d2e-b6e2-bf90-72d2-dd34d956efae_VARS-pure-efi.fd</nvram>
      </os>
      <features>
        <acpi/>
        <apic/>
        <hyperv>
          <relaxed state='on'/>
          <vapic state='on'/>
          <spinlocks state='on' retries='8191'/>
          <vendor_id state='on' value='none'/>
        </hyperv>
      </features>
      <cpu mode='host-passthrough' check='none'>
        <topology sockets='1' cores='3' threads='2'/>
      </cpu>
      <clock offset='localtime'>
        <timer name='hypervclock' present='yes'/>
        <timer name='hpet' present='no'/>
      </clock>
      <on_poweroff>destroy</on_poweroff>
      <on_reboot>restart</on_reboot>
      <on_crash>restart</on_crash>
      <devices>
        <emulator>/usr/local/sbin/qemu</emulator>
        <disk type='file' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source file='/mnt/user/domains/Player2/vdisk1.img'/>
          <target dev='hdc' bus='virtio'/>
          <boot order='1'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
        </disk>
        <disk type='file' device='cdrom'>
          <driver name='qemu' type='raw'/>
          <source file='/mnt/user/isos/Windows10.iso'/>
          <target dev='hda' bus='ide'/>
          <readonly/>
          <boot order='2'/>
          <address type='drive' controller='0' bus='0' target='0' unit='0'/>
        </disk>
        <disk type='file' device='cdrom'>
          <driver name='qemu' type='raw'/>
          <source file='/mnt/user/isos/virtio-win-0.1.173-2.iso'/>
          <target dev='hdb' bus='ide'/>
          <readonly/>
          <address type='drive' controller='0' bus='0' target='0' unit='1'/>
        </disk>
        <controller type='ide' index='0'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
        </controller>
        <controller type='virtio-serial' index='0'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
        </controller>
        <controller type='pci' index='0' model='pci-root'/>
        <controller type='usb' index='0' model='qemu-xhci' ports='15'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
        </controller>
        <interface type='bridge'>
          <mac address='52:54:00:8a:23:d9'/>
          <source bridge='br0'/>
          <model type='virtio'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
        </interface>
        <serial type='pty'>
          <target type='isa-serial' port='0'>
            <model name='isa-serial'/>
          </target>
        </serial>
        <console type='pty'>
          <target type='serial' port='0'/>
        </console>
        <channel type='unix'>
          <target type='virtio' name='org.qemu.guest_agent.0'/>
          <address type='virtio-serial' controller='0' bus='0' port='1'/>
        </channel>
        <input type='tablet' bus='usb'>
          <address type='usb' bus='0' port='3'/>
        </input>
        <input type='mouse' bus='ps2'/>
        <input type='keyboard' bus='ps2'/>
        <sound model='ich9'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
        </sound>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
        </hostdev>

        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x00' slot='0x1c' function='0x1'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x00' slot='0x1c' function='0x4'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/>
        </hostdev>

        <memballoon model='none'/>
      </devices>
    </domain>

     

    I appreciate all ideas! Thanks

  20. *I had this posted in VM Engine (KVM) but didn't get any responses so I've deleted that one and posted here in General.*

     

    Good day!

     

    I've got a Win10 VM running on my Unraid server v6.8.2. and a couple of days ago one of my children turned the computer off by accident. When I realized it was off and rebooted (noticed a load optimized defaults BIOS message) and once Unraid was up and running again, the VM was gone.

     

    After some duckducking around I realized that hardware virtualisation had been turned off (I was getting KVM errors). So I rebooted to the BIOS and made sure those settings were enabled, which fixed the KVM errors.

     

    Back in Unraid I've tried turning the VM off and back on again. Checked that the Domains folder contains the image for my machine, and that the Unraid VM Manager is pointing to libvirt.img.

     

    I've attached the diagnostics and some screen shots.

     

    I'm not sure which direction to go from here. I'm a novice Unraid user so help will be greatly appreciated! Thanks very much!

    Libvert.info.jpg

    VM_manager.jpg

    VM_list.jpg

    tower-diagnostics-20200223-0802.zip