[Support] binhex - Krusader

[Linguafoeda]

Okay...it started working again. Seems like it works ~1 hour after i reboot. Does anyone know why this happens and what causes it?

[binhex]

11 hours ago, Linguafoeda said:

Okay...it started working again. Seems like it works ~1 hour after i reboot. Does anyone know why this happens and what causes it?

most probably cookie related, try clearing cookies in your browser next time.

[westcoastbias]

Looking for a little advice here.

I had a 6 TB drive that I replaced with an 18 GB drive.  However, because the 6 TB was formatted as reiserfs, when I swapped them, I got a bug with the 18 GB.  Reading on here, indicated that it was because reiserfs didnt work with 18 GB.  So I changed it to xfs.

 

I still have the old 6 GB as an unassigned device and I want to copy all of the data over to the 18 GB so parity is good and I can continue with my changes.

My question is how exactly to setup the paths within the docker container to get them to work right.  I watched a video and got the unassigned devices up with this:

 

 

But I am unsure how to configure the new disk.  I know the Host Path is /mnt/disk2/, but what about the access mode?

 

 

I also assume once its all configured right, it should be pretty simple just to copy all contents from the 6 TB to the 18 TB?

 

After that, I want to do a parity check and then move over a different 6 TB that is still part of the array onto the 18 TB.  How should that be configured? 

 

THanks.

 

 

 

 

 

 

 

 

Edited December 20, 2023 by westcoastbias

[binhex]

8 hours ago, westcoastbias said:

But I am unsure how to configure the new disk.  I know the Host Path is /mnt/disk2/, but what about the access mode?

leave it on the default mode for an array disk, so 'Read/Write' it's only UD drives that you have to mess with the mode.

 

8 hours ago, westcoastbias said:

I also assume once its all configured right, it should be pretty simple just to copy all contents from the 6 TB to the 18 TB?

simple but lengthy of course, expect a long wait, just ensure you obey the rule (see last paragraph).

 

8 hours ago, westcoastbias said:

After that, I want to do a parity check and then move over a different 6 TB that is still part of the array onto the 18 TB.  How should that be configured? 

you can do a parity check, but it shouldn't be necessary unless you suspect parity is not in sync with what is written to the array, the choice is yours. If you want to move data off another array drive (i assume the 6tb is part of the array right?), then it should be as simple as selecting everything on /mnt/diskX and copying to /mnt/diskY, where diskX = 6TB and diskY=18TB.

 

One VERY important thing to mention here, NEVER copy data from a disk share to a user share, or vice-versa, you must always copy from a user share to a user share, or from a disk share to a disk share, if you do not obey this rule then you may experience data loss.

[VladoB]

Dears,

 

I am not sure what is wrong - I am trying to access remote folder from Krusader and answer is Cannot open remote folder. Remote folder is NFS and it is old synology NAS. Strange is that when I go to Unraid web GUI and click on mounted NFS share, it shows me all the files, folders etc.

 

Can you please advice?

 

V.

Edited December 22, 2023 by VladoB

[tunablenormal]

On 12/5/2023 at 5:38 PM, Linguafoeda said:

Okay...it started working again. Seems like it works ~1 hour after i reboot. Does anyone know why this happens and what causes it?

 

I seem to be having a similar issue. I never had krusader set to auto start, so I am use to being able to access the WebUI immediately after starting the Docker. Since I updated to 6.12.6 last week, I've noticed that I cannot access the WebUI for krusader immediately. It is definitely less than an hour in my case though. I think 20min or less. So, it seems to be a slow start issue and not really a show stopper, but it is interesting that it only started after upgrading to 6.12.6.

[wobblewoo]

Hello, Happy new Year

 

I've just installed and run Appdata backup and have noticed my Krusader backup is 46Gb which seems very large.

Do i need to remove some temp files or suchlike?

[wobblewoo]

Got it. In Krusader you have to go tools >Empty Trash. The backup is now 5.08 Mb instead of 46.2 Gb.

[Nicon4454]

for some reason sftp is no longer a supported option? is this going to be this way for the future or will sftp come back? the ver i am on is 2.8.0 "a new day" according to the about section

[wirenut]

Got notification docker auto updated overnight during regular schedule for this action.

Then received fix common problems notice this morning there was a docker update available, checked docker tab and sure enough said there was.

Manually updated, finished successfully. Still shows update available.

 

 

any idea why?

[wirenut]

On 3/7/2024 at 1:47 PM, wirenut said:

Got notification docker auto updated overnight during regular schedule for this action.

Then received fix common problems notice this morning there was a docker update available, checked docker tab and sure enough said there was.

Manually updated, finished successfully. Still shows update available.

 

 

any idea why?

Same issue for the last two days.

Is this an issue on my end or the update side? I am not sure how to troubleshoot this.

[binhex]

43 minutes ago, wirenut said:

Is this an issue on my end or the update side?

 

On 3/7/2024 at 7:47 PM, wirenut said:

Manually updated, finished successfully. Still shows update available.

firstly this is an unraid issue it is not image related, check that you are not using a specific tagged version, this can sometimes confuse the unraid webui into thinking there is an update, to do this left click krusader, select edit, the toggle 'advanced view' and check the repository, it should be 'binhex/arch-krusader', if this is ok then please post the issue at https://forums.unraid.net/forum/58-docker-engine/

[Nicon4454]

On 3/7/2024 at 12:42 PM, Nicon4454 said:

for some reason sftp is no longer a supported option? is this going to be this way for the future or will sftp come back? the ver i am on is 2.8.0 "a new day" according to the about section

@binhex is there any information about this?

[binhex]

On 3/11/2024 at 4:53 PM, Nicon4454 said:

@binhex is there any information about this?

i didn't knowingly include or remove sftp, there has been no alterations to the code, it was simply a re-triggered build from a upstream change.

 

Can you detail how you previously used sftp in this container, that way i can then investigate why it got removed and how to add it back in.

[Shesakillatwo]

On 3/9/2024 at 11:08 AM, binhex said:

 

firstly this is an unraid issue it is not image related, check that you are not using a specific tagged version, this can sometimes confuse the unraid webui into thinking there is an update, to do this left click krusader, select edit, the toggle 'advanced view' and check the repository, it should be 'binhex/arch-krusader', if this is ok then please post the issue at https://forums.unraid.net/forum/58-docker-engine/

I experienced this issue the other day as well.  So I did nothing for a few days and tried the update again last night and it worked.  Ii appeared to me that when this issue occurs that one of the larger components/files does not actually reach the "Pull Complete" stage after which I still have the indicator that an update is available.   I have also seen this before....  Could it be an Unraid Timeout issue???

[wirenut]

2 hours ago, Shesakillatwo said:

I experienced this issue the other day as well.  So I did nothing for a few days and tried the update again last night and it worked.  Ii appeared to me that when this issue occurs that one of the larger components/files does not actually reach the "Pull Complete" stage after which I still have the indicator that an update is available.   I have also seen this before....  Could it be an Unraid Timeout issue???

Interesting, I have been away a few days and was looking to address this today based on binhex last response to me and saw your post. I tried manually again to see if i had same issue you describe, and it appears I do. @binhex my repository is correct as you directed to check, should I still post the issue at https://forums.unraid.net/forum/58-docker-engine/ ??

 

Pulling image: binhex/arch-krusader:latest

IMAGE ID [1269367198]: Pulling from binhex/arch-krusader.
IMAGE ID [ba79b0a00404]: Already exists.
IMAGE ID [014829145dc4]: Already exists.
IMAGE ID [8981650a5ede]: Already exists.
IMAGE ID [3e6f6e9c14bc]: Already exists.
IMAGE ID [21c1cc086e6b]: Already exists.
IMAGE ID [d61b27411559]: Already exists.
IMAGE ID [6bed959144b4]: Already exists.
IMAGE ID [867955bafe2a]: Already exists.
IMAGE ID [af760b31737e]: Already exists.
IMAGE ID [b91d01ffc1e9]: Already exists.
IMAGE ID [b8db4f2655a2]: Pulling fs layer.Downloading 100% of 3 KB.Verifying Checksum.Download complete.Extracting.Pull complete.
IMAGE ID [5f904db18c50]: Pulling fs layer.Downloading 100% of 1 KB.Verifying Checksum.Download complete.Extracting.Pull complete.
IMAGE ID [c6b8e095478d]: Pulling fs layer.Downloading 100% of 684 MB.Verifying Checksum.Download complete.Extracting.

TOTAL DATA PULLED: 684 MB

 

Stopping container: binhex-krusader

Error:

 

Removing container: binhex-krusader

Successfully removed container: binhex-krusader

 

Command executiondocker run
  -d
  --name='binhex-krusader'
  --net='bridge'
  --privileged=true
  -e TZ="America/Chicago"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="binhex-krusader"
  -e 'TEMP_FOLDER'='/config/home/.config/krusader/tmp'
  -e 'WEBPAGE_TITLE'='Krusader'
  -e 'VNC_PASSWORD'=''
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:6080]/vnc.html?resize=remote&host=[IP]&port=[PORT:6080]&autoconnect=1'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/krusader-icon.png'
  -p '6080:6080/tcp'
  -v '/mnt/user':'/media':'rw'
  -v '/mnt/cache/appdata/binhex-krusader':'/config':'rw' 'binhex/arch-krusader'

bf494d6710cd0ba84e94b716483ae787bbb08c3aead77f316918569d68ccf692

The command finished successfully!

 

[binhex]

5 hours ago, wirenut said:

my repository is correct as you directed to check, should I still post the issue at https://forums.unraid.net/forum/58-docker-engine/ ??

i am confident the image is fine as other people have pulled it down with no issue (including myself) so the issue you are seeing is either specific to your network in some way or it's an unraid bug that you are seeing, so i think it's worth a post there and see what people say.

[wirenut]

1 hour ago, binhex said:

i am confident the image is fine as other people have pulled it down with no issue (including myself) so the issue you are seeing is either specific to your network in some way or it's an unraid bug that you are seeing, so i think it's worth a post there and see what people say.

ok Done. Thank You binhex

[Miralthor]

If someone also has problems with SMB access then here is the command to install the package required for this:
 

sudo pacman -S kio5-extras

 

Simply minimize the Krusader window, right click on the desktop, open Xfce Terminal and run the command.

It would be nicer if SMB was included again in the next update, use it because it's easiest for me that way.

[binhex]

9 hours ago, Miralthor said:

If someone also has problems with SMB access then here is the command to install the package required for this:
 

sudo pacman -S kio5-extras

 

Simply minimize the Krusader window, right click on the desktop, open Xfce Terminal and run the command.

It would be nicer if SMB was included again in the next update, use it because it's easiest for me that way.

it will be included in the next build.

[draeh]

Is there a reason why the container has roughly doubled in size?

 

It may not have literally doubled in size, but its gotten significantly bigger in the last 2 updates.

 

Edited March 15 by draeh

[bombz]

would be awesome if unraid docker section implemented a link to the change logs for dockers... perhaps some day
https://github.com/KDE/krusader/blob/master/ChangeLog

I assume this is the most recent changelog ?

[draeh]

Doesn't seem like any of those changes would lead to such an increase in the container. Most likely its one of the other supporting images that changed.

 

This is what I hate about docker. The lack of traceability. I mean, yes, its traceable if I take each image that makes up the container and track them down manually one by one. Its tedious, but when I see a size increase like this I want to know why.

[binhex]

6 hours ago, draeh said:

Doesn't seem like any of those changes would lead to such an increase in the container. Most likely its one of the other supporting images that changed.

 

This is what I hate about docker. The lack of traceability. I mean, yes, its traceable if I take each image that makes up the container and track them down manually one by one. Its tedious, but when I see a size increase like this I want to know why.

the base os i use is arch linux, this is a rolling distro which means i need to update all packages if i want to pick up the latest versions of packages pushed to arch linux repository and because docker images are built in immutable layers this can lead to larger image sizes depending on when the base image was last built, so the size will vary somewhat, this is compounded for this image as it requires a lot of packages due to the fact its running a gui.

I have not built the base in a while due to an ongoing issue, so i will take a look at it and see if i can fix it up and then kick off a new build of this image which should result in a reduction in the image size (nothing to update).

[ph_]

Hi,

 

I just updated Krusader,

 

unfortunately the update seems to have introduced some problems, see below logs. The app does not work any more, the WebUI shows another error. Help would be appreciated. 

 

I am running Unraid 6.12.4.

 

text  error  warn  system  array  login  

int2: panel items: TSC

2024-03-18 01:28:15,361 DEBG 'start' stderr output:
tint2: Systray composited rendering on
tint2: nb monitors 1, nb monitors used 1, nb desktops 4
tint2: panel 1 uses scale 1 

2024-03-18 01:28:15,423 DEBG 'start' stderr output:
tint2: Kernel uevent interface initialized...

2024-03-18 01:28:15,424 DEBG 'start' stderr output:
tint2: systray window 8388621

2024-03-18 01:28:15,424 DEBG 'start' stderr output:
tint2: systray started

2024-03-18 01:28:15,666 DEBG 'start' stderr output:
MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)

2024-03-18 01:28:15,667 DEBG 'start' stderr output:
glx: failed to create drisw screen

2024-03-18 01:28:15,667 DEBG 'start' stderr output:
failed to load driver: zink

2024-03-18 01:28:16,020 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 434

2024-03-18 01:28:16,024 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 435
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 436
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 437
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 438

2024-03-18 01:28:16,029 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 439

2024-03-18 01:28:16,029 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 440

2024-03-18 01:28:16,030 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 441

2024-03-18 01:28:16,030 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 442

2024-03-18 01:28:16,031 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 443

2024-03-18 01:28:16,032 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 444

2024-03-18 01:28:16,032 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 445

2024-03-18 01:28:16,032 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 446

2024-03-18 01:28:16,032 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 447

2024-03-18 01:28:16,033 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 448

2024-03-18 01:28:16,033 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 449

2024-03-18 01:28:16,034 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 450

2024-03-18 01:28:16,034 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 451

2024-03-18 01:28:16,035 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 2 minor 0 serial 471
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 472

2024-03-18 01:32:13,289 WARN received SIGTERM indicating exit request
2024-03-18 01:32:13,290 DEBG killing start (pid 70) with signal SIGTERM
2024-03-18 01:32:13,295 INFO waiting for start to die
2024-03-18 01:32:13,303 DEBG 'start' stderr output:
Signal: 15
X connection to :0 broken (explicit kill or server shutdown).
Signal: 15
In exit

2024-03-18 01:32:13,305 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23117275914576 for <Subprocess at 23117276021584 with name start in state STOPPING> (stdout)>
2024-03-18 01:32:13,306 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23117275846800 for <Subprocess at 23117276021584 with name start in state STOPPING> (stderr)>
2024-03-18 01:32:13,307 WARN stopped: start (exit status 143)
2024-03-18 01:32:13,310 DEBG received SIGCHLD indicating a child quit

** Press ANY KEY to close this window ** 

 

 

Best,

ph

Edited March 18 by ph_
provide additional information