ssh with public key - bad ownership or modes for directory

For information, I had the same problem with OMV_4_Odroid_C2.img.xz dated 2018-06-03

chmod 755 / seems to have fixed this.

Thanks once again for the work on OMV and supporting these little boxes.

Same issue with current build OMV_4_Odroid_XU4_HC1_HC2.img.xz as of 2018-06-03 (SHA1: 447d21d503e6ae81574943c2dac51485950ac4d2).

chmod 755 / seems to have fixed this.

Don't know if new builds will be uploaded to Sourceforge, but maybe it is worth mentioning in Readme? @ryecoaaron @tkaiser

Quote from PWSteal

Don't know if new builds will be uploaded to Sourceforge, but maybe it is worth mentioning in Readme?

The images I have built in the last couple of days are correct. I was just doing some more testing before uploading them.

I had the same problem with an image downloaded in mid-August, and the solution in this thread worked for me.

FYI the images on Sourceforge still aren't updated (dated 2018-06-03), at least for the SBCs like the Odroid HC2: https://sourceforge.net/projec…ngle%20Board%20Computers/

Quote from grokov

FYI the images on Sourceforge still aren't updated (dated 2018-06-03), at least for the SBCs like the Odroid HC2

Yep. I haven't had time to work on this.

Just had this same problem with a fresh install of OMV5 in a VMware virtual machine using openmediavault_5.3.9-amd64.iso although I had installed openmediavault-omvextrasorg_latest_all5.deb before I noticed the problem

Quote from sw25481

Just had this same problem with a fresh install of OMV5 in a VMware virtual machine using openmediavault_5.3.9-amd64.iso although I had installed openmediavault-omvextrasorg_latest_all5.deb before I noticed the problem

You may fix that by running salt-call --local state.orchestrate omv.stage.setup.fixmode.

Worked great.

When I installed openmediavault_5.5.11-amd64.iso from scratch the same thing happened again. This time to fix I needed to do

sudo salt-call --local state.orchestrate omv.setup.fixmode

I assume the "stage" in the previous one was because it was something you were working on that has now been promoted

Thank you

I had the same problem and the solution worked for me too. Thanks for always being so helpful in this forum