Doing this:
mv /sbin/start-stop-daemon.REAL /sbin/start-stop-daemonin SSH did nothing
Doing this:
mv /sbin/start-stop-daemon.REAL /sbin/start-stop-daemonin SSH did nothing
I can re-install again. Only takes about 15 min. Let it sit a while after installing to see if it reboots
Did you restart after that? Don't reinstall yet. If you can get the install log that might be useful.
ok...how to get the install log?
Did sharing start working?
Well I guess it is a directory.
ls -las /var/log/installer
total 344
4 drwxr-xr-x 3 root root 4096 Jun 18 10:43 .
4 drwxr-xr-x 13 root root 4096 Oct 21 07:35 ..
4 drwxr-xr-x 2 root root 4096 Jun 18 10:43 cdebconf
16 -rw-r--r-- 1 root root 16282 Jun 18 10:43 hardware-summary
4 -rw-r--r-- 1 root root 161 Jun 18 10:43 lsb-release
80 -rw------- 1 root root 79544 Jun 18 10:43 partman
60 -rw-r--r-- 1 root root 57551 Jun 18 10:43 status
172 -rw------- 1 root root 172901 Jun 18 10:43 syslog
Not sure what to look at there. If you want to post them I can look but no guaranty I can tell whats wrong. Also look at them and be sure there is no confidential info.
ls -las /var/log/installer
ls: cannot access /var/log/installer: No such file or directory
So...looks like I reinstall and let it sit a while when finished
Did sharing start working??????
I guess that only confirms it didn't finish. They were probable still in ram. If it was mine I would reinstall and leave it for quite a while hoping it finished. You could also try alt-controle-F1 to F8 and see if you can find the console that is doing the install. Might be able to see what hangs there.
No sharing. same as all installs before. I am reinstalling. will try the alt-ctrl thing.
Good luck
donh' signature: If you make it idiot proof, somebody will build a better idiot.
better idiot ---> innovator1
After re-installing for the eleventy-first time (I think it was 5 total), it seems to be working.
I simply had to let it sit after the install.
OMV does state that it is finished and it is going to reboot and to remove the install media for boot up.
It seems that after a minute or so of it sitting, I just pushed the reboot button on the computer.
BIG MISTAKE! HUGE!!! (Julia Roberts, Pretty Woman, 1990)
My infinite wisdom tells me that when it said it was done, it was done. Not so.
It seems there are still scripts running that need to finish before it reboots.
Anyway, If you would like to keep your idiot from shining, JUST LET IT SIT! It will reboot on its own!
I didn't get the shares on windows right away after finishing the setup.
Soooo....I was discouraged and went and watched television, then went to bed!
The next morning....the magic network fairies had come along and sprinkled magic network share dust on my systems.
And....the shares - including the OMV machine itself - were all present in windows explorer.
I hope this helps some other impatient OMV installers in the future!
Thanks for updating us. Glad you got it going. Don't take the idiot saying personally.
Not sure why it would take overnight for the network to start working. Also not sure how to add that to the first post. LOL
I created a bug at http://bugtracker.openmediavault.org/view.php?id=1835 . Other contributions welcome.
I have just the same problem. I broke all head already to myself. the latest version of OMV 3 on the virtual machine in proxmox is set, nextcloud 12 is set nearby. everything worked on the previous servers well.
I do not understand your question.
it is not question. i have problem with not work samba too. the problem is not unique.
it is not question. i have problem with not work samba too. the problem is not unique.
Please start a thread and provide as much detail as you can. I assume you have done the steps in the first post of this thread. If you don't understand a step ask here. We have no idea what version of omv you are using or what you are trying to connect from.
The better question you ask the better answer you might get.
Not sure if relevant but here goes anyways:
For Windows 10 users - Microsoft silently disabled SMB 1.0 in latest Win 10 patches (because of previous cryptolocking crap spreading that way)...
I find it somewhat weird that Win 10 machine needs several attempts to "get it to work" when using only SMB 3.X (RDMA or Samba Direct).
Which Samba is OMV 3.X using?
When I reenable SMB 1.X support it works right away...
P.S. (All of the previous instructions were applied)
To see your version of samba or any other package for that matter. dpkg -l |grep samba
I assume debian would patch this if it didn't work with 10. I don't have win10 to test with.
If you find a solution I will reference it in the first post.
Thanks
@donh would you like to create a document of this for the new omv wiki?
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!