Errors in OMV with raspberry pi image

ArrOShooter · 23. Mai 2015

Hi I am a total noob in CLI and OMV

I installed OMV on a raspberry pi as a tryout and for simple folder sharing and downloading torrents and newsgroups , when i like it on this pi i want to make a big server 16tb with all my multimedia and data on real hardware.

when i try to make a shared folder named Ronald i get this error

Code

error #6000:
exception 'OMVException' with message 'Failed to create the directory 


'/media/9ee8370a-a2e2-46f9-af68-fd0a6d7b1e31/Ronald/'' in 


/usr/share/openmediavault/engined/rpc/sharemgmt.inc:414
Stack trace:
#0 [internal function]: OMVRpcServiceShareMgmt->set(Array, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, 


Array)
#2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod


('set', Array, Array)
#3 /usr/sbin/omv-engined(500): OMVRpc::exec('ShareMgmt', 'set', Array, Array, 1)
#4 {main}]

Alles anzeigen

I see in windows OMV shared folder Ronald when i click

in windows 8.1 pro
0x80070043 cannot find network name

in android smb://192.168.178.47/Ronald/
The networkname cannot be found

I try my android tablet

in android smb://192.168.178.47/Ronald/
The networkname cannot be found

Then i fiddle with acl permissions i get

Code

failed to execute command 'export LANG=C; getfacl --no-effective --access -- 


'/media/9ee8370a-a2e2-46f9-af68-fd0a6d7b1e31/Ronald//' 2>&1': getfacl: 


/media/9ee8370a-a2e2-46f9-af68-fd0a6d7b1e31/Ronald//: No such file or directory

after OK

Code

Error #0:
exception 'UnexpectedValueException' with message 'DirectoryIterator::__construct


(/media/9ee8370a-a2e2-46f9-af68-fd0a6d7b1e31/Ronald//): failed to open dir: No such 


file or directory' in /usr/share/openmediavault/engined/rpc/folderbrowser.inc:99
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/folderbrowser.inc(99): DirectoryIterator-


>__construct('/media/9ee8370a...')
#1 [internal function]: OMVRpcServiceFolderBrowser->get(Array, Array)
#2 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, 


Array)
#3 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod


('get', Array, Array)
#4 /usr/sbin/omv-engined(500): OMVRpc::exec('FolderBrowser', 'get', Array, Array, 1)
#5 {main}

Alles anzeigen

Please help i spend almost 3 days and numerous re installs on a simple shared folder

Thanks

Ronald

tekkb · 23. Mai 2015

If you used ACL remove those settings and use privileges instead on the shared folder.

ArrOShooter · 23. Mai 2015

Thanks did that too and i keep getting errors

i cleared acl

and i get

Code

clearing ACLs ...
setfacl: /media/9ee8370a-a2e2-46f9-af68-fd0a6d7b1e31/Ronald/: No such file or directory
Done...

tekkb · 23. Mai 2015

It is weird. I don't understand why you get the message when you try to create the shared folder. one of the mods with an rpi will have to take a look.

ArrOShooter · 23. Mai 2015

Yes i know i tried 2 different sd cards already same errors the only folder i can see in omv is lost+found folder

tekkb · 23. Mai 2015

What model rpi is this?

ArrOShooter · 23. Mai 2015

Rpi 1 model b

ryecoaaron · 23. Mai 2015

I can't duplicate this problem on my RPi. What is the output of:

ls -al /media/9ee8370a-a2e2-46f9-af68-fd0a6d7b1e31/
blkid
mount

ArrOShooter · 23. Mai 2015

Code

root@OMV:~# ls -al /media/9ee8370a-a2e2-46f9-af68-fd0a6d7b1e31/
total 8
drwx------ 2 root root 4096 May 23 10:44 .
drwxr-xr-x 5 root root 4096 May 23 16:24 ..
root@OMV:~# blkid
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="boot" UUID="7D5C-A285" TYPE="vfat"
/dev/mmcblk0p2: UUID="5d18be51-3217-4679-9c72-a54e0fc53d6b" TYPE="ext4" LABEL="o
mv"
/dev/mmcblk0p3: LABEL="rrdcache" UUID="fa36508a-b3c4-4499-b30a-711dd5994225" TYP
E="ext4"
/dev/sda1: LABEL="Extern" UUID="9b57cf75-2c7a-4210-84f9-58f47b87d56f" TYPE="ext4
"
root@OMV:~# mount

Alles anzeigen

ryecoaaron · 23. Mai 2015

It isn't creating the directory when you create the shared folder. Was there really no output from the mount command? If so, that would explain why it doesn't create the folder.

ArrOShooter · 24. Mai 2015

No there was no output when i mounted te drive. Is there a possibility to mount the drive via cli , after the directory is created maybe i can proceed in omv because i realy like the layout.

ryecoaaron · 24. Mai 2015

OMV has to mount the drive otherwise you cannot create a shared folder. Can you take a screenshot of the filesystems screen?

ArrOShooter · 24. Mai 2015

Allright now i tried to use 1.17 kralizec

no update or upgrade via ssh i thought maybe that was the problem

and i still get when creating the shared folder 'Ronald'

Error
Failed to create the directory '/media/edae0d97-7db0-4215-a938-8f7704e13c71/Ronald/'

Code

Error #6000:
exception 'OMVException' with message 'Failed to create the directory '/media/edae0d97-7db0-4215-a938-8f7704e13c71/Ronald/'' in /usr/share/openmediavault/engined/rpc/sharemgmt.inc:414
Stack trace:
#0 [internal function]: OMVRpcServiceShareMgmt->set(Array, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('set', Array, Array)
#3 /usr/sbin/omv-engined(500): OMVRpc::exec('ShareMgmt', 'set', Array, Array, 1)
#4 {main}

next thing is to try different hdd?!

ryecoaaron · 24. Mai 2015

What about the screenshot of the filesystems tab not the output?

ArrOShooter · 24. Mai 2015

Ok put in a new but smaller hdd and presto everything is ok and working

I think i have to bin the extended lacie hdd (oh well)

because i have now version 1.17 kralizec is it safe to update via the gui or better through ssh ?

thanks for your help

ryecoaaron · 24. Mai 2015

Upgrade works the same either way but I recommend the gui. If you decide to use ssh, use omv-update instead of apt commands.

ArrOShooter · 24. Mai 2015

I checked the hdd , no problems i formatted to ntfs and everything ok , could it be that the controller inside the enclosure does not like ext4 ?

ryecoaaron · 24. Mai 2015

Hard to say. The controller driver may be buggy in the RPi kernel.

Errors in OMV with raspberry pi image

Jetzt mitmachen!

Tags