shanelovell

Members
  • Posts

    46
  • Joined

  • Last visited

Posts posted by shanelovell

  1. Good Morning all, 

    Krusader has become unresponsive using the GUI, so I have copied the repeating log section from Krusader and the Diagnostics for Unraid. 

    I have no idea how to change this as the log states.

     

    Error: Can't open display: :1
    Openbox-Message: Failed to open the display from the DISPLAY environment variable.
    _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
    _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

     

    I am at a loss and the array is useless right now

    Any help is greatly appreciated as always.

    "Update" Went to run "fstrim -v /mnt/cache" and noticed command line will not display either.


    Fatal server error:
    Couldn't add screen


    Backtrace:
    0: X11rdp (0x400000+0x1801f) [0x41801f]
    1: X11rdp (0x400000+0xcf39) [0x40cf39]
    2: /lib/x86_64-linux-gnu/libc.so.6 (0x2b334ef49000+0x36d40) [0x2b334ef7fd40]
    3: X11rdp (0x400000+0xd390) [0x40d390]
    4: X11rdp (0x400000+0x151e3) [0x4151e3]
    5: X11rdp (0x400000+0x15655) [0x415655]
    6: X11rdp (0x400000+0x6a0aa) [0x46a0aa]
    7: X11rdp (0x400000+0x8536) [0x408536]
    8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x2b334ef6aec5]
    9: X11rdp (0x400000+0x899e) [0x40899e]
    Segmentation fault at address (nil)

    FatalError re-entered, aborting
    Caught signal 11 (Segmentation fault). Server aborting

    Error: Can't open display: :1
    Openbox-Message: Failed to open the display from the DISPLAY environment variable.
    _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
    _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
    InitOutput:

    X11rdp, an X server for xrdp
    Version 0.9.0
    Copyright (C) 2005-2015 Jay Sorg
    See http://www.xrdp.org for information on xrdp.
    Underlying X server release 10903000, The X.Org Foundation
    Screen width 1420 height 720 depth 16 bpp 16
    dpix 100 dpiy 100
    buffer size 2044800
    rdpup_init: g_tcp_local_bind failed
    rdpScreenInit: rdpup_init failed
    pRRScrPriv 0x7efca0
    rdpScreenInit: ret 0

    Fatal server error:
    Couldn't add screen


    Backtrace:
    0: X11rdp (0x400000+0x1801f) [0x41801f]
    1: X11rdp (0x400000+0xcf39) [0x40cf39]
    2: /lib/x86_64-linux-gnu/libc.so.6 (0x2b6df60b1000+0x36d40) [0x2b6df60e7d40]
    3: X11rdp (0x400000+0xd390) [0x40d390]
    4: X11rdp (0x400000+0x151e3) [0x4151e3]
    5: X11rdp (0x400000+0x15655) [0x415655]
    6: X11rdp (0x400000+0x6a0aa) [0x46a0aa]
    7: X11rdp (0x400000+0x8536) [0x408536]
    8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x2b6df60d2ec5]
    9: X11rdp (0x400000+0x899e) [0x40899e]
    Segmentation fault at address (nil)

    FatalError re-entered, aborting
    Caught signal 11 (Segmentation fault). Server aborting

    Error: Can't open display: :1
    Openbox-Message: Failed to open the display from the DISPLAY environment variable.
    _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
    _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
    InitOutput:

    X11rdp, an X server for xrdp
    Version 0.9.0
    Copyright (C) 2005-2015 Jay Sorg
    See http://www.xrdp.org for information on xrdp.
    Underlying X server release 10903000, The X.Org Foundation
    Screen width 1420 height 720 depth 16 bpp 16
    dpix 100 dpiy 100
    buffer size 2044800
    rdpup_init: g_tcp_local_bind failed
    rdpScreenInit: rdpup_init failed
    pRRScrPriv 0x7efca0
    rdpScreenInit: ret 0

    tower-diagnostics-20170420-1714.zip

    tower-diagnostics-20170421-1049.zip

  2. I am not running a Ryzen processor but experiencing the same thing. Im am using an AMD 7860K. I pulled the Log file from the Krusader app  and copied the part that keeps repeating.

    Thanks in advance

    System diagnostics are attached as well.

     


    Fatal server error:
    Couldn't add screen


    Backtrace:
    0: X11rdp (0x400000+0x1801f) [0x41801f]
    1: X11rdp (0x400000+0xcf39) [0x40cf39]
    2: /lib/x86_64-linux-gnu/libc.so.6 (0x2b334ef49000+0x36d40) [0x2b334ef7fd40]
    3: X11rdp (0x400000+0xd390) [0x40d390]
    4: X11rdp (0x400000+0x151e3) [0x4151e3]
    5: X11rdp (0x400000+0x15655) [0x415655]
    6: X11rdp (0x400000+0x6a0aa) [0x46a0aa]
    7: X11rdp (0x400000+0x8536) [0x408536]
    8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x2b334ef6aec5]
    9: X11rdp (0x400000+0x899e) [0x40899e]
    Segmentation fault at address (nil)

    FatalError re-entered, aborting
    Caught signal 11 (Segmentation fault). Server aborting

    Error: Can't open display: :1
    Openbox-Message: Failed to open the display from the DISPLAY environment variable.
    _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
    _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
    InitOutput:

    X11rdp, an X server for xrdp
    Version 0.9.0
    Copyright (C) 2005-2015 Jay Sorg
    See http://www.xrdp.org for information on xrdp.
    Underlying X server release 10903000, The X.Org Foundation
    Screen width 1420 height 720 depth 16 bpp 16
    dpix 100 dpiy 100
    buffer size 2044800
    rdpup_init: g_tcp_local_bind failed
    rdpScreenInit: rdpup_init failed
    pRRScrPriv 0x7efca0
    rdpScreenInit: ret 0

    Fatal server error:
    Couldn't add screen


    Backtrace:
    0: X11rdp (0x400000+0x1801f) [0x41801f]
    1: X11rdp (0x400000+0xcf39) [0x40cf39]
    2: /lib/x86_64-linux-gnu/libc.so.6 (0x2b6df60b1000+0x36d40) [0x2b6df60e7d40]
    3: X11rdp (0x400000+0xd390) [0x40d390]
    4: X11rdp (0x400000+0x151e3) [0x4151e3]
    5: X11rdp (0x400000+0x15655) [0x415655]
    6: X11rdp (0x400000+0x6a0aa) [0x46a0aa]
    7: X11rdp (0x400000+0x8536) [0x408536]
    8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x2b6df60d2ec5]
    9: X11rdp (0x400000+0x899e) [0x40899e]
    Segmentation fault at address (nil)

    FatalError re-entered, aborting
    Caught signal 11 (Segmentation fault). Server aborting

    Error: Can't open display: :1
    Openbox-Message: Failed to open the display from the DISPLAY environment variable.
    _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
    _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
    InitOutput:

    X11rdp, an X server for xrdp
    Version 0.9.0
    Copyright (C) 2005-2015 Jay Sorg
    See http://www.xrdp.org for information on xrdp.
    Underlying X server release 10903000, The X.Org Foundation
    Screen width 1420 height 720 depth 16 bpp 16
    dpix 100 dpiy 100
    buffer size 2044800
    rdpup_init: g_tcp_local_bind failed
    rdpScreenInit: rdpup_init failed
    pRRScrPriv 0x7efca0
    rdpScreenInit: ret 0

     

    tower-diagnostics-20170420-1714.zip

  3. These forums are great, I just had a disk error as well but was unable to retrieve the log files as the server GUI became unresponsive which forced me to hard reboot.

    The unassign/reassign disk seems to have done the trick and rebuild is ongoing now. I will update as it progresses.

  4. 56 minutes ago, trurl said:

    Can you show us how you know the permissions?

     

    Can you show us the error you get with mover?

     

    Post diagnostics that include the timeframe of the issue.

    no error with the mover. it starts and stops as if there is nothing to move. I have been moving a lot of data and this is the only file I've had an issue with

    fix common problems shows the file in cache, which is why I'm looking to delete it in Dolphin.

  5. Probably something silly but, there is a movie file in my cache drive that I cannot move or delete with the Mover or Dolphin. Keeps giving me errno. 5

    I'm using unraid 6.3.3. tried using the help in Dolphin and I get "could not find service 'khelpcenter'"

    appreciate any suggestions. Permissions of the file are "can read and write"

     

     

  6. On 4/8/2017 at 9:16 AM, Squid said:

    One comment:

     

    When setting up the /UNASSIGNED folder mapped to /mnt/disks, the access mode should be set to Read/Write:Slave

     

    If you do not do this, then there are circumstances where Krusader (or any docker app) will display the /UNASSIGNED folder, but will always show it as empty.

     

    This should be done for all mounts done by unassigned devices

    How do I go in and change this? When I go into the installed apps and select setting it looks like it only allows me to add a new folder. Question being, do I need to delete the original and recreate the UNASSIGNED folder?

  7. 30 minutes ago, trurl said:

    I would say that "overview" section of the manual is trying to keep it simple (oversimplifying).

     

    In order to have redundancy, anything must exist on more than one disk. For example, I will use different numbers than you had to keep things clearer.

     

    If you have a 100 GB SSD and a 120 GB SSD in a cache pool, then you can have 100GB on one disk, and a copy of that 100GB on the other disk. But there is no way to use that other 20GB in such a way that it has a copy on another disk.

     

    As I said, things get more complicated with more than 2 disks since there are more than 2 disks to use for the redundancy.

     

    The calculator I linked gives the real numbers for any particular configuration, and the FAQ tells how to get other configurations, including raid0 which just adds the disks together.

    That makes sense.

  8. Well thank you for the clarification Trurl,

    As far as the Cache pool goes I am a bit confused now.

    The Unraid Manual states on page 11 

    "The unRAID cache pool is created through a unique twist on traditional RAID 1, using a BTRFS feature that provides both the data redundancy of RAID 1 plus the capacity expansion of RAID 0."

    Is that not what is really occurring?

     

  9. Keep in mind that one of the 8TB drives will need to be used as a parity drive. (Parity must be equal to or larger than other drives in the array.) This will give you 49TB of array data with 8TB parity.  Are you not going to have a Cache drive? If you decide to add multiple cache drives, keep in mind that the cache pool will sum the amount of memory and then divide by the number of drives. Example being: you have a 240GB and a 480GB SSDs as a Cache pool, it adds these (720GB) then divides by 2(for the 2 drives) Total cache memory is now 360GB.

    Just something to keep in mind of.

  10. Good Morning from NY everyone,

    I am wondering if any of you have used these services offered by Lime Tech?

    What was your experience and how much can be accomplished within an hour time slot? (ex. setting up a media server, a personal cloud, PVR, and maybe some other cool apps)

    Does the config services apply to the community apps? and how easy will it be for a new user?

    Looking forward to your replies and comments.

    Have a great rest of the day

  11. Thanks you guys for all the valuable information, I purchased the same card when doing my build, but do not have any drives going to it yet. Reason for buying this card over the other suggested cards was price. $48.00 usd open box item that was listed as a plug and play item at the time.  My goals is to use 4 of the 8 ports for 4 WD red array drives. What I do not understand is the varied differences from the first test which averaged 136MB/s across the HDDs, but then the second test shows

    sdc = 15.16 MiB/sec
    sdd = 60.61 MiB/sec
    sde = 37.64 MiB/sec
    sdf = 13.25 MiB/sec

    So is the first test, what the individual drive is capable of of through the card? and is the second test, Under maximum load what the card receives as bandwidth allocation?

    Edit:

    The test result itself (dskt_out_*.txt) looks pretty damn good; my only quibble would be the uneven (albeit, consistent) apportionment of bandwidth to the 4 devices (ie, 15 60 37 13 [vs (e.g.) 30 32 29 34]) during each run[**]. The 4 concurrent runs were nicely consistent with each other. And, the total combined bandwidth was about 505 MiB/s, which, in decimal terms [unRAID community's "preference"] is about 530 MB/s ... on that single 6Gbps connection (9235<=>9705). The consistency of the 4 runs with each other strongly suggests that they were running (essentially precisely) concurrently. If one had finished "late" (or started "early"), it would have had a different/unique result.

     

    The fact that DM_after.txt showed no (added) kernel messages indicates that, while the 9235/9705 may have been under duress, they never "cried uncle" [Zippi gets to learn some American slang :)]