Remote Mount will not mount

Vk27 · 17. Juni 2018

It just will not mount from one OMV to the Next all setting are correct (I think ) just will not mount.

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mount '/srv/a5f52b92-c76f-4caa-9d81-a0e932642505' 2>&1' with exit code '32': mount error(115): Operation now in progress Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Code

Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mount '/srv/a5f52b92-c76f-4caa-9d81-a0e932642505' 2>&1' with exit code '32': mount error(115): Operation now in progress
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) in /usr/share/php/openmediavault/system/process.inc:175
Stack trace:
#0 /usr/share/php/openmediavault/system/filesystem/remote.inc(427): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/module/fstab.inc(72): OMV\System\Filesystem\Remote->mount()
#2 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleFsTab->startService()
#3 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusqz...', '/tmp/bgoutputhk...')
#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#8 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#9 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
#10 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#11 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#12 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#13 {main}

Alles anzeigen

ryecoaaron · 17. Juni 2018

It might not make a difference but the share name should not have the leading slash. if it still fails, it is likely a permissions issue. is the remote host a Windows 10 Home system?

Vk27 · 17. Juni 2018

ive had a go without the slash with one before and after none all the same.

And no the host is OMV also i know the share works fine as its in use with many other devices.
Thanks

ryecoaaron · 17. Juni 2018

Zitat von DarkVodka34

And no the host is OMV also i know the share works fine as its in use with many other devices.

Both systems are OMV?

Vk27 · 17. Juni 2018

Zitat von ryecoaaron

Both systems are OMV?

Correct, Host is omv 2.0. and im trying to mount on OMV4

ryecoaaron · 17. Juni 2018

Zitat von DarkVodka34

Correct, Host is omv 2.0. and im trying to mount on OMV4

Then the username should be a local user on the OMV 2.x host with permissions to the share not darkvodka34@outlook.com.

Vk27 · 17. Juni 2018

Zitat von ryecoaaron

Then the username should be a local user on the OMV 2.x host with permissions to the share not darkvodka34@outlook.com.

That is my username under 2.0 the share works fine and it in use with other devices. just will not mount in 4.0

edit = made a use called remote still does not work with all the correct permissions

ryecoaaron · 17. Juni 2018

Zitat von DarkVodka34

That is my username under 2.0 the share works fine and it in use with other devices. just will not mount in 4.0

I am surprised that even works. It is a terrible idea. The @outlook.com is overriding the hostname. I assume you added it because that is your windows login name but you should use Windows 10 credential manager instead. This will never work in remotemount because the fstab entry appends the hostname in the fstab string. So, you end up with two @ symbols which won't work. Create another user with the same permissions to use with remote mount.

Vk27 · 17. Juni 2018

Zitat von ryecoaaron

I am surprised that even works. It is a terrible idea. The @outlook.com is overriding the hostname. I assume you added it because that is your windows login name but you should use Windows 10 credential manager instead. This will never work in remotemount because the fstab entry appends the hostname in the fstab string. So, you end up with two @ symbols which won't work. Create another user with the same permissions to use with remote mount.

I did same problem works fine on 2.0 must be something in 4.0

Vk27 · 17. Juni 2018

Getting this now even tho the host defo NOT down. this is with user "remote"

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mount '/srv/e692c910-4494-47c6-b23f-4bb56e0e4945' 2>&1' with exit code '32': mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Code

Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mount '/srv/e692c910-4494-47c6-b23f-4bb56e0e4945' 2>&1' with exit code '32': mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) in /usr/share/php/openmediavault/system/process.inc:175
Stack trace:
#0 /usr/share/php/openmediavault/system/filesystem/remote.inc(427): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/module/fstab.inc(72): OMV\System\Filesystem\Remote->mount()
#2 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleFsTab->startService()
#3 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusNg...', '/tmp/bgoutputYz...')
#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#8 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#9 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
#10 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#11 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#12 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#13 {main}

Alles anzeigen

ryecoaaron · 17. Juni 2018

Zitat von DarkVodka34

I did same problem works fine on 2.0 must be something in 4.0

Yep, the remotemount plugin didn't exist in 2.0. The remoteshare plugin did things much differently. I wrote both of them. OMV 2.x also used samba 3.6 vs 4.5 for OMV 4.x. Regardless, I still wouldn't use a user with a domain appended.

Vk27 · 17. Juni 2018

Zitat von ryecoaaron

Yep, the remotemount plugin didn't exist in 2.0. The remoteshare plugin did things much differently. I wrote both of them. OMV 2.x also used samba 3.6 vs 4.5 for OMV 4.x. Regardless, I still wouldn't use a user with a domain appended.

Yup remoteshare that worked fine. ive used the username "remote" now and tells me host is down when its indeed not.

Think its a problem coming from samba 3.6 to the 4.5 from omv4.0?

ryecoaaron · 17. Juni 2018

Zitat von DarkVodka34

Getting this now even tho the host defo NOT down. this is with user "remote"

Sounds like a samba protocol version mismatch.

Vk27 · 17. Juni 2018

Zitat von ryecoaaron

Sounds like a samba protocol version mismatch.

No fix than other than upgrade my 2.0 box?

ryecoaaron · 17. Juni 2018

Zitat von DarkVodka34

No fix than other than upgrade my 2.0 box?

While that is a good idea (actually a fresh install is better), it is possible to specify the smb protocol version of a mount in the mount options.

Vk27 · 17. Juni 2018

Zitat von ryecoaaron

While that is a good idea (actually a fresh install is better), it is possible to specify the smb protocol version of a mount in the mount options.

Updating to 4.0 right now lets see cheers Ryecoaaron (fresh install that is:)

Vk27 · 17. Juni 2018

Works fine when upgrade to 4.0

Thanks again

Jetzt mitmachen!