armhf is working reasonably well with Raspbian on RPi/Cubieboard and Debian Wheezy armhf on Pandaboard ES. The charting did not seem to be working but the few other items (update, samba, ssh) seemed to work.
OMV (Fedaykin) on RPi with armhf/armel
-
-
Hi there,
Thanks for the work done on the RPi. Complete noob so please excuse any stupid questions! I've followed the instructions to get OMV on the Pi and everything seems to be fine. I can log in to OMV but if I click on the Plugins link I get the following error:Error #4000:
exception 'OMVException' with message 'Failed to execute command 'export LANG=C;sudo dpkg-query --list openmediavault-*': ' in /var/www/openmediavault/rpc/plugin.inc:186
Stack trace:
#0 [internal function]: PluginRpc->getList(Array)
#1 /usr/share/php/openmediavault/rpc.inc(265): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(98): OMVRpc::exec('Plugin', 'getList', Array)
#3 /var/www/openmediavault/rpc.php(44): OMVJsonRpcServer->handle()
#4 {main}
Any ideas??Thanks,
-
Hello everyone,
I have the same issue with my Raspberry Pi on armhf.
I followed this how to :
http://www.element14.com/commu…i-nas-with-openmediavault
And I had to do the same as jevy_b posted as a comment with success.
All works well but, as I wanted to install an Upnp or DLNA plugin, I encounter this message when I clicked on 'plugins' in the OMV interface :Erreur #4000:
exception 'OMVException' with message 'Failed to execute command 'export LANG=C;sudo dpkg-query --list openmediavault-*': ' in /var/www/openmediavault/rpc/plugin.inc:186
Stack trace:
#0 [internal function]: PluginRpc->getList(Array)
#1 /usr/share/php/openmediavault/rpc.inc(265): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(98): OMVRpc::exec('Plugin', 'getList', Array)
#3 /var/www/openmediavault/rpc.php(44): OMVJsonRpcServer->handle()
#4 {main}I saw 2 existing threads about this error :
http://forums.openmediavault.o…c.php?f=12&t=481&start=20
http://forums.openmediavault.org/viewtopic.php?f=12&t=1359But no solution for now...
I am using OMV 0.4.17 on RPI armhf.
Help would be very appriciated.
-
-
I'm sorry, i'm so a noob !
I went to :
http://omv-plugins.org/
I downloaded the .deb file by clicking "OMV-Plugins.org Plugin Download for OMV 0.4 (Fedaykin)"
I sent this on my rpi by ssh and installed it there.
Then, as asked in the installation, I opened the OMV interface, clicked on "plugins" in "system" section and after a moment, voilà, a beautiful list of omv plugins appeared.Hope this helps.
Thanks. -
RPI users, I have a new problem. OMV list 2 devices :
mmcblk01
mmcblk02
The first one is mounted automatically.
The second one, even if it is in the fstab is not mounted.
See the picture :
https://docs.google.com/file/d…pbGNQYjQ/edit?usp=sharing
So, I click on "mount" and the system is mounted :
https://docs.google.com/file/d…wRENBdlU/edit?usp=sharing
BUT, when I reboot, it fails.
I can not start my rpi on omv anymore.
Can someone help me ? -
I assume you have Raspbian installed? What is it installed on? Is there any error message when you plug in a display?
-
-
Yes, I am on Raspbian, OMV 0.4.17.
I Installed OMV-Plugins deb and miniDLNA from them, but the problem was there before, right after the first install of OMV.My fstab before mounting via OMV is like that :
Codeproc /proc proc defaults 0 0 /dev/mmcblk0p1 /boot vfat defaults 0 2 /dev/mmcblk0p2 / ext4 defaults,noatime 0 1
When I am connected to my PI with SSH, I can browse to every directories but OMV just can't see anything. When I want to add a share folder, OMV doesn't see any volume so I can not configure my shared folders.
Then, I click on "mount" and I can see the mmcblk0p2 volume in the combobox.
My fstab then change to this :
Codeproc /proc proc defaults 0 0 /dev/mmcblk0p1 /boot vfat defaults 0 2 /dev/mmcblk0p2 / ext4 defaults,noatime 0 1 # a swapfile is not a swap partition, so no using swapon|off from here on, use dphys-swapfile swap[on|off] for that # >>> [openmediavault] UUID=b7b5ddff-ddb4-48dd-84d2-dd47bf00564a /media/b7b5ddff-ddb4-48dd-84d2-dd47bf00564a ext4 defaults,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 0 2 # <<< [openmediavault]
Here is a picture of the screen after that :
docs.google.com/file/d/0B0gXWwO7AoZNSEQ4eGtqNHpidGs/edit?usp=sharing -
fsck is failing which means your sd card is having issues.
1 - Put the card in another machine and change init=/sbin/init to init=/bin/sh in cmdline.txt
2 - Put the card back in rpi and boot. This will boot into single user mode.
3 - Run fsck.ext4 -f /dev/mmcblk0p2
4 - Change line from step 1 back to original and reboot rpi. -
Thanks for this quick answer.
I am login as root on my PI and connected to my TV so I suppose I can do these instructions directly on my PI, right ?
Where is cmdline.txt ? Do I have to create one ? -
-
cmdline.txt is either in the root directory or boot (don't have my rpi setup now). It is already created. And yes, you could do it directly on the rpi.
-
I looked for it in all the PI without success. I don't have this file. Maybe, since the last raspbian version, there is no more cmdline.txt ?
The result of command :
$ cd /
$ find . -type f -name "cmdline.txt"
returns no result. -
Sorry, you can't find it because it is in the unmounted partition of your sd card. Can you put the sd card in a desktop computer? It is in the root directory when inserted into a Windows system.
-
-
No problem. (I use Ubuntu).
I found the cmdline.txt, its content is :dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
I tried to add " init=/bin/sh" at the end of this line but the PI seems not giving me the keyboard to type anything.
-
Add single to the end instead.
By the way, I have this on mine:
boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 ssh quiet
-
I tried with " single" instead of " init=/bin/sh" at the end of the line but it was like I didn't change the cmdline.txt at all from the original one.
I tried to simply copy your content of cmdline.txt but it reaches a "kernel panic - not syncing (...)"
I tried your cmdlin.txt with " init=/bin/sh" at the end => kernel panic.
...
If it helps, I noticed that commenting the openmediavault line in /etc/fstab restores my PI to before I clicked on mount on the mmcblk0p2 in the omv interface.Of course I tried fsck.ext4 -f /dev/mmcblk0p2 when possible but I always have a message like : "mmcblk02 is mounted - fsck can not continue".
I understand that the aim of init=/bin/sh is to avoid this. -
-
I should've read your previous post a little better. If you are using Ubuntu, you can run the fsck command from there.
-
OK but I can't find the mmcblk0p2 when the sdcard is inserted in my PC.
The sdcard is /dev/sdb
Partitions are mounted as :
/dev/sdb1 (59MB FAT) => /media/3312-932F
/dev/sdb2 (15GB EXT4) => /media/b7b5ddff-ddb4-48dd-84d2-dd47bf00564a
I unmounted these two partitions and ran this :
$ fsck.ext4 -f /dev/sdb2Here is the result (sorry it's in french) :
e2fsck 1.42 (29-Nov-2011)
Passe 1 : vérification des i-noeuds, des blocs et des tailles
Passe 2 : vérification de la structure des répertoires
Passe 3 : vérification de la connectivité des répertoires
Passe 4 : vérification des compteurs de référence
Passe 5 : vérification de l'information du sommaire de groupe
/dev/sdb2 : 75004/983040 fichiers (0.2% non contigüs), 547026/3922688 blocsThen, inserted in the PI, I have the same problem as in the screen picture...
-
I guess the sd card has some corrupt file (but not filesystem). I would try reinstalling Raspbian.
-
-
Ok. Too bad.
Ubuntu says that the two partitions are clean. I don't understan'd. Isn't Fsck detect corrupt files ?
And, uncommenting the OMV line in /etc/fstab makes the PI rebooting normally.
Are you sure corrupted files can be the cause ?
Couldn't a bad fstab configuration with other config files be responsible for this ?
...
the installation is soooooooooo lonnnnnnnnnnnnnnnnnnnnnng... -
You could try uninstalling the OMV package and reinstalling it instead of reinstalling all of it
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!