zeyoner
-
Posts
31 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by zeyoner
-
-
I resolved it.
-
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 -
Thank you all. Yes I agree it appears I have misunderstood a lot. Lesson has been learnt!
-
I see.
-
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)?
-
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!
-
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?
-
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.
-
Would the current keyfile still be valid for disk1? Would I be able to put back disk1 and recreate the parity?
-
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!
-
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..
-
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.
-
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.
-
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.
-
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..
-
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
Cache after reboot unmountable
in General Support
Posted · Edited by zeyoner
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?