The_Doctor

Members
  • Content Count

    20
  • Joined

  • Last visited

Posts posted by The_Doctor

  1. 15 hours ago, The_Doctor said:

    Thank you for looking into it. The only recent changes on the server was a chassis/hardware change. I can’t recall the last time I ran an extended test before that, more than a few months. Not sure if that would change anything with the working of the application. One would think that a uninstall, reinstall would correct that if there was? Everything else is working correctly that I can tell. I can try to swap back an test if you think it’s worth the effort.

    Good news, it took some time, but finally finished

     

    31-12-2019 02:32 Fix Common Problems Extended Tests Completed Errors Found warning

    29-12-2019 20:05 Fix Common Problems Extended Tests Beginning normal

    • Haha 1
  2. Thank you for looking into it. The only recent changes on the server was a chassis/hardware change. I can’t recall the last time I ran an extended test before that, more than a few months. Not sure if that would change anything with the working of the application. One would think that a uninstall, reinstall would correct that if there was? Everything else is working correctly that I can tell. I can try to swap back an test if you think it’s worth the effort.

  3. On 12/25/2019 at 10:36 AM, Squid said:

    Is it still running or did it crash abnormally?

    
    ps -aux | grep extendedTest

     

     

    requested output: after about 24 hours.

    ps -aux | grep extendedTest
    root      2874 18.7  0.0 100952 24420 ?        S    Dec25 286:18 /usr/bin/php /usr/local/emhttp/plugins/fix.common.problems/scripts/extendedTest.php
    root      3263  0.0  0.0   3912  2248 pts/1    S+   12:06   0:00 grep extendedTest

     

     

    Tail of log:

    /tmp/fix.common.problems# tail -f extendedLog
    <tt><b>The&nbsp;following&nbsp;user&nbsp;shares&nbsp;will&nbsp;be&nbsp;excluded&nbsp;from&nbsp;the&nbsp;permissions&nbsp;tests:</b><br><br></tt><tt>/mnt/user/appdata<br></tt><tt><br></tt><tt>Processing&nbsp;/mnt/user/appdata<br></tt>

     

     

     

    I did however notice if I stop the array, it will force finish the job, with the below results (removed some share names):

    The following user shares will be excluded from the permissions tests:

    /mnt/user/appdata

    Processing /mnt/user/appdata
    Processing /mnt/user/
    Processing /mnt/user/
    Processing /mnt/user/
    Processing /mnt/user/ISOs
    Processing /mnt/user/
    Processing /mnt/user/
    Processing /mnt/user/
    Processing /mnt/user/
    Processing /mnt/user/
    Processing /mnt/user/
    Processing /mnt/user/
    Processing /mnt/user/
    Processing /mnt/user/
    Processing /mnt/user/
    Processing /mnt/user/Programs
    Processing /mnt/user/Server_Backup
    Processing /mnt/user/
    Processing /mnt/user/
    Processing /mnt/user/system
    Processing /mnt/user/


    The following files / folders may not be accessible to the users allowed via each Share's SMB settings.  This is often caused by wrong permissions being used on new downloads / copies by CouchPotato, Sonarr, and the like:

    /mnt/user/BACKUP   root/root (/)  0
    /mnt/user/   root/root (/)  0
    /mnt/user/   root/root (/)  0
    /mnt/user/ISOs   root/root (/)  0
    /mnt/user/   root/root (/)  0
    /mnt/user/   root/root (/)  0
    /mnt/user/   root/root (/)  0
    /mnt/user/   root/root (/)  0
    /mnt/user/   root/root (/)  0
    /mnt/user/   root/root (/)  0
    /mnt/user/   root/root (/)  0
    /mnt/user/   root/root (/)  0
    /mnt/user/   root/root (/)  0
    /mnt/user/   root/root (/)  0
    /mnt/user/Programs   root/root (/)  0
    /mnt/user/Server_Backup   root/root (/)  0
    /mnt/user/   root/root (/)  0
    /mnt/user/   root/root (/)  0
    /mnt/user/system   root/root (/)  0
    /mnt/user/   root/root (/)  0

     

     

     

  4. Extended test not completing and stuck on appdata. I let it go for 24 hours before removing/reboot/re-installing and trying again today. Is there a way to force stop the test, and or get any more information on what it is doing? The tail and system log show no more than what the "status" shows on the GUI. TIA

     

     

    extendedLog:

    /tmp/fix.common.problems# tail -f extendedLog
    <tt><b>The&nbsp;following&nbsp;user&nbsp;shares&nbsp;will&nbsp;be&nbsp;excluded&nbsp;from&nbsp;the&nbsp;permissions&nbsp;tests:</b><br><br></tt><tt>/mnt/user/appdata<br></tt><tt><br></tt><tt>Processing&nbsp;/mnt/user/appdata<br></tt>

     

    System log:
    Dec 23 11:19:48 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 11:22:11 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 11:24:58 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 11:30:08 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 11:33:22 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 11:40:27 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 11:44:31 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 11:52:51 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 11:57:12 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 12:02:50 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 12:03:41 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 12:10:15 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 12:17:44 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 12:40:11 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 12:40:16 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 13:08:03 Tardis root: Fix Common Problems Version 2019.11.22
    Dec 23 15:17:29 Tardis root: Fix Common Problems Version 2019.11.22

     

     

     

  5. Master Version:

    Not sure what is going on, just updated, and now it crashes without much in the logs. Debug mask set to true or false comes up with same logs

    I will install and test dev, as I no longer see a master version, only 2 dev versions available.

    <

    ___. .__ .__
    \_ |__ |__| ____ | |__ ____ ___ ___
    | __ \| |/ \| | \_/ __ \\ \/ /
    | \_\ \ | | \ Y \ ___/ > <
    |___ /__|___| /___| /\___ >__/\_ \
    \/ \/ \/ \/ \/
    https://hub.docker.com/u/binhex/

    2019-12-04 17:03:37.527209 [info] System information Linux 642928f489f4 5.3.6-Unraid #2 SMP Wed Oct 16 14:28:06 PDT 2019 x86_64 GNU/Linux
    2019-12-04 17:03:37.565416 [info] PUID defined as '99'
    2019-12-04 17:03:37.760181 [info] PGID defined as '100'
    2019-12-04 17:03:38.047748 [info] UMASK defined as '000'
    2019-12-04 17:03:38.082860 [info] Permissions already set for volume mappings
    2019-12-04 17:03:38.125948 [info] DELUGE_DAEMON_LOG_LEVEL not defined,(via -e DELUGE_DAEMON_LOG_LEVEL), defaulting to 'info'
    2019-12-04 17:03:38.160930 [info] DELUGE_WEB_LOG_LEVEL not defined,(via -e DELUGE_WEB_LOG_LEVEL), defaulting to 'info'
    2019-12-04 17:03:38.197591 [info] VPN_ENABLED defined as 'yes'
    2019-12-04 17:03:38.245688 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/**

    >

    • Like 2
  6. 6 hours ago, binhex said:

    possible the old certificate from your vpn provider was using a weak cipher which is no longer permitted with the later version of openvpn, thus when you updated you couldnt connect, that would be my guess.

     

    - Looks like you might have solved an issue I brought up a few pages ago. Seems 2.4.7 openVPN is not playing nice with my vpn provider.

     

    Issue: when VPN set to

    write UDP: Operation not permitted (code=1)

     


    Not working Binhex DelugeVPN:
    Sun Sep 29 10:30:24 2019 OpenVPN 2.4.7 [git:makepkg/2b8aec62d5db2c17+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019

     

    Working Flexget delugeVPN:
    Sat Sep 21 15:27:14 2019 OpenVPN 2.4.0 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Dec 28 2016

     

    Also working OpenVPN client app:

    openvpnclient

    2019.02.09

    Update of OpenVPN packages to 2.4.6-2

     

     

     

  7. @binhex

     

    Having same issue has someone in this thread several pages back. The issue "write UDP: Operation not permitted (code=1)" that appears to be isolated to your dockers. I tried your:

    binhex delugevpn

    binhex qbittorrentvpn

     

    Both come out with write UDP: Operation not permitted (code=1)

     

    I tried delugevpn-flexget  from paulpoco/arch-delugevpn using the same openvpn file, and it works just fine.

     

    Please let me know what I can give you to help sort this out.

  8. 11 hours ago, binhex said:

     

    This sounds more like an issue with Deluge itself than the containerisation of Deluge, you're probably better off posting this on the Deluge forum, you will need to supply all traceback's (if there are any in the log, i have no idea how deluge deals with 300+ torrents, it could well not cope well with that quantity of torrents so another option is to try rtorrentvpn, this has a track record of being able to cope with a lot of torrents (1000+) and still be reasonably reactive to changes.

     

     

    I had a feeling this was more of a Deluge issue, but thought I would check with you first. Thanks for taking a look, ill bring it over to the other forum, and check out Rtorrentvpn.

  9. 5 minutes ago, The_Doctor said:

    @binhex apologies if this has been mentioned in this thread (wish there was a search within thread feature). Facing issue with Web UI constantly breaks connection, with about 300 Torrents running. If i use the web url, it will just break connection w/o doing anything "The connection to the web-server has been lost!". If i use a Thin client, the connection will stay up longer, unless I change something i.e. remove a torrent, then same results. When I open connection manager, it just shows a grey plug, if i hit refresh or connect again, it will show a red dot for some time, then it will go back green eventually, and I can connect again.


     

    
    The below example, came back on its own after abount a minute, but, no new connect message. 
    
    
    [INFO    ] 10:49:48 rpcserver:206 Deluge Client connection made from: *:61030 -- Thin client
    [INFO    ] 10:49:50 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. -- clicked remove torrent
    [INFO    ] 10:50:27 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:50:27 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:50:43 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:50:43 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 10:51:42 torrentmanager:635 Torrent * removed by user: * -- Finally removed torrent 
    [INFO    ] 10:51:42 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 10:51:42 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 10:52:51 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:52:51 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:52:55 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:52:55 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:54:17 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:54:17 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:54:43 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 10:55:49 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:55:49 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:56:04 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:56:04 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:56:44 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:56:44 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 10:57:51 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:57:52 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:58:02 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:58:02 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:58:03 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 10:59:04 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:59:04 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:59:05 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:59:05 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:59:14 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:59:14 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 11:00:02 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 11:00:02 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume

     

     

    Is this just me being impatient, or should I really be able to remove torrents, or make changes, with a quicker response time?

     

     

     

     

     

     

     

     

     

    \

     

     

     

     

    Here is another example from the thin client. Im trying to remove 8 seeders, and the connection from the thin client goes grey, but no connection drop in logs.

    Its almost like the connection drops until all the requested changes are completed, but taking over a minute to remove just one torrent?

     

     

    In this example the last part of the log is when the Thin client started to respond again. It seems once again, only after it completed the requested task.

     

    [INFO    ] 11:10:26 rpcserver:206 Deluge Client connection made from: *:64030
    [INFO    ] 11:11:06 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 11:11:06 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 11:11:23 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 11:12:25 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 11:12:25 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 11:13:56 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 11:13:56 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 11:14:58 torrentmanager:635 Torrent * removed by user: *
    [INFO    ] 11:14:58 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 11:14:58 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 11:16:00 torrentmanager:635 Torrent * removed by user: *
    [INFO    ] 11:16:00 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 11:16:00 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 11:16:58 torrentmanager:635 Torrent * removed by user: *
    [INFO    ] 11:16:58 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [WARNING ] 11:16:58 torrent:987 Unable to delete the torrent file: [Errno 2] No such file or directory: '/config/state/8c303f2bd419951f8f9c68678689a543860eebbc.torrent'
    [INFO    ] 11:16:58 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 11:18:01 torrentmanager:635 Torrent * removed by user: *
    [INFO    ] 11:18:01 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 11:18:01 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 11:19:03 torrentmanager:635 Torrent * removed by user: *
    [INFO    ] 11:19:03 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 11:19:03 torrentmanager:737 Saving the state at: /config/state/torrents.state

    INFO    ] 11:20:03 torrentmanager:635 Torrent * removed by user: *
    [INFO    ] 11:20:03 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 11:20:03 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 11:21:03 torrentmanager:635 Torrent * removed by user: *
    [INFO    ] 11:21:03 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 11:21:03 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 11:22:04 torrentmanager:635 Torrent * removed by user: *
    [INFO    ] 11:22:04 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 11:23:50 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 11:23:51 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 11:23:53 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 11:23:53 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume

     

     

     

     

     

     

     

     

    \

  10. @binhex apologies if this has been mentioned in this thread (wish there was a search within thread feature). Facing issue with Web UI constantly breaks connection, with about 300 Torrents running. If i use the web url, it will just break connection w/o doing anything "The connection to the web-server has been lost!". If i use a Thin client, the connection will stay up longer, unless I change something i.e. remove a torrent, then same results. When I open connection manager, it just shows a grey plug, if i hit refresh or connect again, it will show a red dot for some time, then it will go back green eventually, and I can connect again.


     

    The below example, came back on its own after abount a minute, but, no new connect message. 
    
    
    [INFO    ] 10:49:48 rpcserver:206 Deluge Client connection made from: *:61030 -- Thin client
    [INFO    ] 10:49:50 rpcserver:226 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. -- clicked remove torrent
    [INFO    ] 10:50:27 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:50:27 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:50:43 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:50:43 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 10:51:42 torrentmanager:635 Torrent * removed by user: * -- Finally removed torrent 
    [INFO    ] 10:51:42 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 10:51:42 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 10:52:51 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:52:51 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:52:55 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:52:55 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:54:17 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:54:17 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:54:43 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 10:55:49 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:55:49 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:56:04 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:56:04 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:56:44 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:56:44 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 10:57:51 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:57:52 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:58:02 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:58:02 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:58:03 torrentmanager:737 Saving the state at: /config/state/torrents.state
    [INFO    ] 10:59:04 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:59:04 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:59:05 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:59:05 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 10:59:14 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 10:59:14 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume
    [INFO    ] 11:00:02 torrentmanager:780 Successfully loaded fastresume file: /config/state/torrents.fastresume
    [INFO    ] 11:00:02 torrentmanager:826 Saving the fastresume at: /config/state/torrents.fastresume

     

     

    Is this just me being impatient, or should I really be able to remove torrents, or make changes, with a quicker response time?

     

     

     

     

     

     

     

     

     

    \

  11. 9 minutes ago, dlandon said:

    The 'Help' button is your friend.

    Just an FYI, the having to hit <return> is not listed under help info on the GUI. It is however, on your first post

     

    Help Info from GUI:

    "Additional options are available when you click on the device identification. When the disk is unmounted, the mount name of the device can be changed. A disk can be formatted and an fsck run to check the disk."

     

    From your first post:

    "There are different operations in various active areas (especially the disk serial number) based on whether or not the disk drive is mounted.  If the disk is not mounted, click on the '+ icon by the serial number, click on the partition name, then you can type a new mount point name.  Press Enter for the name change to be applied.  This will now become the mount point and the share name when the disk is shared."

     

    This is still on me, for missing something in your guide, but thought I would share in case this can be updated moving forward.

     

  12. 5 minutes ago, dlandon said:

    - Remove both disks and then delete them from the historical devices.

    - Verify the /mnt/disks/AMCC_9650SE_12M_DISK mount point is not there.  If it is unmount it and then rm -rf /mnt/disks/AMCC_9650SE_12M_DISK.  If you can't clear it up, reboot the server.

    - Install one disk and change the mount point.  Remember to hit <Return> to save the new mount point name.

    - Mount this disk and be sure the mount point is what you set.  If not the config file is probably corrupted.

    - If this works add the second disk and change the mount point.

     

    If this doesn't work, post your /flash/connfig/plugins/unassigned.devices/unassigned.devices.cfg file and let me see what it contains.

     

     

    I must have missed this part when reading over the guide. I never hit <return> When changing the mount point name. 

     

    Thank you for a quick reply, and fix!

  13. Having issue when mounting more than one disk. The 2nd disk takes over.

     

     

    unRAID server Pro, version 6.3.3

    Unassigned.devices 2017.05.04a

     

    Disk2: 9650SE-12M_DISK_9VK0FZTY000000000000

    Disk1: 9650SE-12M_DISK_A8346038000000000000

     

    If one or both are mounted, they show up as below, I think this might be the root of my problem. Could it be the 3ware controller I'm using in Jbod?

    /mnt/disks/AMCC_9650SE_12M_DISK

    This is even if i use the + and change the name, wi will always default back, and when I go to rename again, the name I changed it to is still there.

     

    	9650SE-12M_DISK_A8346038000000000000*	xfs	2 TB	0 	32.2 GB	1.97 TB
    		`->1/mnt/disks/AMCC_9650SE_12M_DISK

    I have a feeling I'm missing something stupid here, but any input is helpful.

     

     

     

     

     

  14. On 4/4/2017 at 5:30 AM, bonienl said:

     

    What particular new feature / functionality are you waiting for?

     

    The switch away from emhttp - to eliminate GUI lockups waiting on other process to finish.