zeyoner

February 4, 2020

I was having some issues with the unifi-controller container. So I removed it and starting having issue with recreating the container. Reboot now the cache pool claims the following:

SATA cables to both SSDs have been re-seated.

Version 6.7.2 2019-06-25

My appdata appears to be gone. WTF is going on?

December 22, 2019

I resolved it.

December 22, 2019

Moved my install to new hardware with the same hard drives. Boot up and see that the cache appear off.. When I assign the SSDs it's seeing them as a "New Device"

I am afraid to start the array. Not sure why the SSDs are being detected as new devices.

Version 6.7.2 2019-06-25

November 13, 2019

Thank you all. Yes I agree it appears I have misunderstood a lot. Lesson has been learnt!

November 13, 2019

I see.

November 13, 2019

I meant to ask. What did I do wrong? After the "New Config" when I re-added the parity drive and disk1 (disk2) and checked the box that states that the parity is good. Shouldn't it have rebuild disk1 (disk2)?

November 13, 2019

2 minutes ago, johnnie.black said:

Yes, just make sure you don't assigned old disk1 to parity slot, and don't check parity is already valid, only the disk assigned to the parity slot will be overwritten.

Unraid will ask for a new passphrase but just enter old one.

Thank the data hoarding gods! I will execute this once I get home. Thanks a lot Jorge!

November 13, 2019

9 minutes ago, johnnie.black said:

Should be.

Yes, as long as disk1 is healthy.

Disk1 has been kicking back an error although it rebuilds and functions for days then kicks an error causing me to have to rebuild. Man I can't wait to get home and rebuild that parity. So moving forward how should I go about doing this?

Stop array
Power off
Remove disk1 (disk2)
Insert disk1
Power on
Here's where I get a bit confused
New Config (Preserving Cache)
Add same parity
Add disk1
Start Array with correct passphase
Allowing Unraid to rebuild parity

Will it rebuild parity and leave disk1 as is?

November 13, 2019

3 minutes ago, johnnie.black said:

Format is never part of a rebuild, also if you removed disks from the array, parity wouldn't be valid anymore, even if those disks were empty.

I assumed it had to seeing that I was now in theory moving disk2 to disk1's slot.

November 13, 2019

Would the current keyfile still be valid for disk1? Would I be able to put back disk1 and recreate the parity?

November 13, 2019

Here's my situation..

Unraid 6.7.2

4x10TB - Data

2x512GB - Cache

Drives are encrypted

As of late I've been receiving errors on two (Disk 1 & 3) of the 4 hard drives. I've had to rebuild four times already. Disk1 is the only drive with data. I decided to remove the two drives in question and re-use disk2 as disk1. I did a new config preserving the cache. Powered down and removed disk1 & 3. Booted up checked the box stating the parity drive is good. Disk2 now being used as disk1 was then added to the array as disk1 which then needed to be formatted and rebuilt. I used the same passphase to unlock the drive. After 14 hours of rebuild all of my docker containers are gone and so is my data. I have one folder which I assume was moved from cache.

I still have the original disk1 untouched however I do not have a keyfile even though I know the passphase. Please tell me there's light at the end of this forsaken tunnel!

September 24, 2017

2 hours ago, Squid said:

IDK I've got no problems. Try Dolphin instead.. TBQH, I wouldn't expect any updates to this container.

Squid,

As always thanks for the assistance. I'll check out Dolphin..

September 24, 2017

On 9/23/2017 at 10:03 AM, zeyoner said:

I am also experiencing this issue. I would need to completely remove the docker and it's appdata. Re-install and it'll work for the first day. Then back to it just hanging at the XRDP login prompt. I can't for the life of me figure out what the hell is the issue. Would love to have it fixed.

September 24, 2017

1 minute ago, Squid said:

Your best bet if any problems with this container is to remove the app, delete the appdata for it, and then reinstall.

We've already done this and it keeps happening. Once I remove and install it'll work for a one time use. After that it's broken all over again.

September 24, 2017

On 12/19/2014 at 5:14 AM, sparklyballs said:

Tapatalk users: This post is best viewed as a web page

Using squid's php script to keep this more updated.

http://i.imgur.com/uf0NDSm.png[/img]KrusaderKrusader is a fully featured file manager, highly configurable. Full gui in a RDP container accessible via browser.Support

So the developer of the container is on here. Maybe he can shine some light on our issues.

September 23, 2017

18 minutes ago, tillkrueger said:

I feel your pain. And while we’re at it, if there was a menu function to get the transfer progress window back after clicking anywhere outside of it, that would make data operations soooo much easier too.

so close, and yet so far, this Docker.

Wow, dude I can't agree more. I've done this countless times and have spent a lot of time looking for an option some where..

September 23, 2017

I am also experiencing this issue. I would need to completely remove the docker and it's appdata. Re-install and it'll work for the first day. Then back to it just hanging at the XRDP login prompt. I can't for the life of me figure out what the hell is the issue. Would love to have it fixed.

This is what I'm getting in the logs for the docker

ErrorWarningSystemArrayLogin


Fatal server error:

Server is already active for display 1
If this server is no longer running, remove /tmp/.X1-lock
and start again.

ddxGiveUp:
Error: Can't open display: :1

Openbox-Message: Failed to open the display from the DISPLAY environment variable.


Fatal server error:

Server is already active for display 1
If this server is no longer running, remove /tmp/.X1-lock
and start again.

ddxGiveUp:
Error: Can't open display: :1

Openbox-Message: Failed to open the display from the DISPLAY environment variable.


Fatal server error:

Server is already active for display 1
If this server is no longer running, remove /tmp/.X1-lock
and start again.

ddxGiveUp:
Error: Can't open display: :1

Openbox-Message: Failed to open the display from the DISPLAY environment variable.


Fatal server error:

Server is already active for display 1
If this server is no longer running, remove /tmp/.X1-lock
and start again.

ddxGiveUp:
Error: Can't open display: :1

Openbox-Message: Failed to open the display from the DISPLAY environment variable.


Fatal server error:

Server is already active for display 1
If this server is no longer running, remove /tmp/.X1-lock
and start again.

ddxGiveUp:
Error: Can't open display: :1

Openbox-Message: Failed to open the display from the DISPLAY environment variable.


Fatal server error:

Server is already active for display 1
If this server is no longer running, remove /tmp/.X1-lock
and start again.

ddxGiveUp:
Error: Can't open display: :1

Openbox-Message: Failed to open the display from the DISPLAY environment variable.


Fatal server error:

Server is already active for display 1
If this server is no longer running, remove /tmp/.X1-lock
and start again.

ddxGiveUp:
Error: Can't open display: :1

Openbox-Message: Failed to open the display from the DISPLAY environment variable.


Fatal server error:

Server is already active for display 1
If this server is no longer running, remove /tmp/.X1-lock
and start again.

ddxGiveUp:
Error: Can't open display: :1

Openbox-Message: Failed to open the display from the DISPLAY environment variable.


Fatal server error:

Server is already active for display 1
If this server is no longer running, remove /tmp/.X1-lock
and start again.

ddxGiveUp:
Error: Can't open display: :1

Openbox-Message: Failed to open the display from the DISPLAY environment variable.


Fatal server error:

Server is already active for display 1
If this server is no longer running, remove /tmp/.X1-lock
and start again.

ddxGiveUp:
Error: Can't open display: :1

Openbox-Message: Failed to open the display from the DISPLAY environment variable.


Fatal server error:

Server is already active for display 1
If this server is no longer running, remove /tmp/.X1-lock
and start again.

ddxGiveUp:
Error: Can't open display: :1

Openbox-Message: Failed to open the display from the DISPLAY environment variable.


Fatal server error:

Server is already active for display 1
If this server is no longer running, remove /tmp/.X1-lock
and start again.

ddxGiveUp:
Error: Can't open display: :1

guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
guacd[164]: INFO:	Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 guacd[164]: Using fallback PATBLT (server is ignoring negotiated client capabilities)
Sep 23 10:06:07 d50ab8452f52 XRDP[167]: (167)(47195364642816)[INFO ] An established connection closed to endpoint: NULL:NULL - socket: 11
Openbox-Message: Failed to open the display from the DISPLAY environment variable.

Sep 23 10:06:07 d50ab8452f52 XRDP[167]: (167)(47195364642816)[INFO ] An established connection closed to endpoint: NULL:NULL - socket: 11

September 9, 2017

So I finally decided to reboot the server and this is what I'm getting.

September 9, 2017

1 hour ago, Squid said:

Crashplan is a pig memory wise. Perhaps limit its memory either within its settings somewhere or via the docker template.

I've noticed it is a memory hog. I'm only restoring my backups so that I can move it away from Crashplan since they've done away with the consumer plan.

September 9, 2017

2 hours ago, Squid said:

That's an understatement!

What you had was a bunch of page allocation stalls (computer brain farts while it tried to figure out how to allocate some memory for various processes).

Then came a single Out Of Memory issued which killed off part of the KVM system. Then it all went downhill from there. A reboot will fix you up at least temporarily. How much memory have you allocated to your various VMs? Are you running preclears or any plugin particularly memory intensive?

Not sure where you're seeing this (maybe I'm missing something), beyond the NIC seemingly having a heart attack at one point trying to figure out if its up or down and what speed that its running at.

At the time I was running Emby, Crashplan (restoring), streaming a video via SMB share, and my one VM. I do have preclear plugin installed but it wasn't clearing any disk.

The VM is using 8GB and the server has 32GB. Memory usage is usually at 42%.

2 hours ago, Squid said:

ok. Missed that. I gave up after looking at the first 100 traces....

I'm no expert, but syslog 101: Start at the top.

To be quite honest, I checked out the diagnostics because I figured the answer was going to be easy due to the reference in the OP's snippet to fuse.c issuing the trace (I figured it was going to be drive filesystem corrupt). After the OOM and seeing hundreds of traces right after it, I think it may be safe to ignore everything at the end as you've got to look at the root cause.

I'm out of my element I don't know what I should be doing. I've rebooted the server. Based on what I'm understanding the issue may lie within the VM?

Here's the XML to the one VM I had running at the time.

<domain type='kvm' id='2'>
  <name>Server 10</name>
  <uuid>2ce10c02-6c90-0a96-a1f8-725725e8d5c7</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='4'/>
    <vcpupin vcpu='1' cpuset='5'/>
    <vcpupin vcpu='2' cpuset='6'/>
    <vcpupin vcpu='3' cpuset='7'/>
    <vcpupin vcpu='4' cpuset='12'/>
    <vcpupin vcpu='5' cpuset='13'/>
    <vcpupin vcpu='6' cpuset='14'/>
    <vcpupin vcpu='7' cpuset='15'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.7'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/2ce10c02-6c90-0a96-a1f8-725725e8d5c7_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'>
    <topology sockets='1' cores='4' 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/Server 10/vdisk1.img'/>
      <backingStore/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <alias name='virtio-disk2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/isos/Windows.iso'/>
      <backingStore/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='2'/>
      <alias name='ide0-0-0'/>
      <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.126-2.iso'/>
      <backingStore/>
      <target dev='hdb' bus='ide'/>
      <readonly/>
      <alias name='ide0-0-1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb'/>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <alias name='usb'/>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <alias name='usb'/>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    </controller>
    <controller type='ide' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:b6:0d:99'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/0'/>
      <target port='0'/>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/0'>
      <source path='/dev/pts/0'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-2-Server 10/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'>
      <alias name='input1'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input2'/>
    </input>
    <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
    </memballoon>
  </devices>
  <seclabel type='none' model='none'/>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
</domain>

September 8, 2017

Thanks 1812, title updated.

September 8, 2017

Hi everyone,

I'm experiencing an odd issue with my UnRaid 6.3.5 server. Due to the fact I do not have any idea on how to get it resolved. I'm reaching out and appreciate any assistance I receive. Now to what's going on.

Today is the second day I ran into the same issue. It started yesterday. While I'm downloading via Crashplan docker and my daughter is watching Daniel Tiger from an SMB share. I lose connectivity to the server. No webgui no share access. I can still ping the server however.

When I use iKVM (see attachment) It's as if there's an network issue. I tried reconnecting the cables and still same issue. The fact that I can still use iKVM to view the console proves networking is working because it's on the same NIC.

I tried to login via the console. But it just sits there and does nothing after I enter the login. After a long wait it seems to reset itself. Then I am able to login again. I do not like this at all because it seems to be rebooting all of my server's services.

dobby-diagnostics-20170908-1338.zip

Can this be relayed to the plugin I have installed (Tips and Tricks) I have the CPU Scaling Governor to Performance.

August 24, 2017

Updated still getting an error. Can you verify my settings for the docker image?

This is the error if it helps at all.

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="freeradius" --net="bridge" --privileged="true" -e TZ="America/New_York" -e HOST_OS="unRAID" -p 8088:\/tcp -v "/mnt/user/appdata/freeradius/":"\":rw marcelmaatkamp/freeradius

The command failed.

August 24, 2017

Enabling Docker Hub searches found FreeRadius however it didn't work. I tried doing it manually but kept getting errors. I may be doing something wrong. I'm not at all a linux person neither so I'm not sure if I were to get the docker working if whether I'd know what to do next. But I don't want to setup an entire VM with Windows Server just to play the role of a Radius server. It just seems silly.

August 24, 2017

I'd like to have a Radius Server as an app. I'm actually surprise not to see at least one when I search for it.

Found this: https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0ahUKEwjPr9metvDVAhUd3YMKHWkKDQcQFggmMAA&url=https%3A%2F%2Fhub.docker.com%2Fr%2Fmarcelmaatkamp%2Ffreeradius%2F&usg=AFQjCNHCiJADDwD-37q0Z_xnmFRsUAAqXw

However I am not well rounded in docker.

zeyoner

Posts

Joined

Last visited

Content Type

Profiles

Forums

Downloads

Store

Gallery

Bug Reports

Documentation

Landing

Posts posted by zeyoner

Cache after reboot unmountable

Cache come back.. (SOLVED)

Cache come back.. (SOLVED)

Rebuild nothing..

Rebuild nothing..

Rebuild nothing..

Rebuild nothing..

Rebuild nothing..

Rebuild nothing..

Rebuild nothing..

Rebuild nothing..

Krusader docker will start, but not the Web GUI

Krusader docker will start, but not the Web GUI

Krusader docker will start, but not the Web GUI

Krusader docker will start, but not the Web GUI

Krusader docker will start, but not the Web GUI

Krusader docker will start, but not the Web GUI

Got Call Traces!?

Got Call Traces!?

Got Call Traces!?

Got Call Traces!?

Got Call Traces!?

Radius Server

Radius Server

Radius Server