Hello? Anyone? Can I get a little help here, please?
Posts by Marc
-
-
So... any clues here?
Still not sure how can I "stop" the update on 1.12, it goes straight to 1.9.
Thanks in advance!
-
So, confirming there is no way to install it without a modded kernel on the HMNDCE?
-
Exactly, that too.
-
Sorry, not meant to make you read all the threads, just the 1st one.
I should've been more clear.Anyway, as far as I know, standard kernel won't work properly with ARM processors. This NAS seems to require some specific steps, including boot sector strings, to install anything (as described here).
Then, the only way I could install it was installing this kernel-modded version of Wheezy, then installing OMV 0.4, then upgrading it. But it required A LOT of work and fixes, including some help of yours (davidh2k helped me a lot) but still had a lot of crashes and other issues --couldn't even copy large files to NAS without having it freezing up.
As David said, it was all related to the kernel issues...
Cheers!

EDIT: Here's a part of the tutorial for installing OMV on this NAS:
Quote from Stefan SeidelDisplay More
You will needdefinitely: a USB memory stick of at least 512MB (1GB is better if you need to recover the original firmware)
definitely: have your device updated to the latest firmware
definitely: a network router with DHCP enabled (it usually is) and the device connected to it (otherwise you won't be able to access the device)
highly recommended: access to the serial console of the device, although not strictly necessary, is helpful because otherwise you'll have no clue what's going on if it doesn't work (more information, but basically what you need is a 3.3V UART-USB adapter)
ideally: a copy of the first 32MB of the hard drive in your device (for last-resort recovery)
good to have: reasonable knowledge of Linux
Procedure
Download this ZIP file, extract the contents of the first folder in it onto the USB stick (so that the USB stick contains 4 files and one subfolder at its top level)
Power down the device
Plug the stick into one of the USB ports of the device
Power up the device and press and hold the "reset" button (small hole above the USB/Network ports, use needle) - if you have the device cover open for the serial console, you can just press the tiny white button by hand
wait until both white LEDs on the front start to blink - you can now release the reset button
wait (the installer will format the system portion of the HDD and copy the base system onto it)
the device will power down - you can safely pull the USB stick from the device
power up the device (e.g. by pressing the power button on top of the back side) - the LEDs might stay dark for a while, don't worry about that
the device will now boot the new system and install the OpenMediaVault packages
once you see the red LED lighting up, you can go and do something else.
-
Hello, KM0201!
Thanks for your reply.
I was using 1.9 before and had a lot of issues. But again, I installed a modded kernel-based version of Wheezy; never tried with original OMV ISO.
Maybe this topic can explain better than me the need of a modded kernel.
Thanks!

-
Greetings!
I'm thinking about give another try on OMV; I reallly enjoyed it.
However, it seems I cannot run OMV 1.9 on it, since I was running OMV on Debian Wheezy and several kernel resources were not available.
It seems the better version for my NAS is 1.12. I have some questions,though:
a) How do I install 1.12? Last time I did it, I installed 0.4x and ran 'apt-get update', ended up with 1.9.
b) Can I install it straight from ISO, without Debian Wheezy? I think it should be cleaner, am I right?
c) I'll need OwnCloud, DLNA and a Torrent client. Would love to make sure these are compatible with this version.
d) Where can I find OMV 1.12 files? The Sourceforge download page jumps from 0.5x to 1.9.
Thanks in advance.Cheers!
-
Hello willri,
I'm thinking about give it another try.
I ended up with OMV 1.9 running on Debian Wheezy. It was running, but I had a lot of issues that made me quit. However, it requires a modded kernel since the NAS is way too old (about 5 years old or even more).
I would love that someone could make an updated install tutorial, with the proper files and versions to use. I messed my install so much that I don't even remember what exactly I did to fix several of the issues.
It seems the OMV 1.12 is the better version for this NAS. Not sure I'll be able to install it tho. I remember installing 0.4 and running apt-get update, then it ended up with 1.9. Not sure how to stop on 1.12.
Cheers!
-
Hello!
Not solved, sorry.
And willri, can't install from ISO (as far as I know) because since it's a NAS, it requires an modded kernel. Processors, drivers, etc.
Cheers!
-
Hello David,
Thanks, but I'm giving up.
I can't upload the log, because it crashes. I can't move files to the HDD, because it freezes/crashes (I need to restart it to make it work again).
I do appreciate all your help, but it isn't worth the headache. I'll try to revert to the stock firmware and move on.
Cheers.
-
Alright, I rebooted the NAS and so far it's working fine, all settings remained.
I hope I can now enjoy my new super-improved NAS without more headaches.
Once again, thanks for all your support!
Cheers!

-
Yay, it worked!
Thanks a lot! You guys rock!
Just a question: can I rest assured that the configurations won't be lost again?
Cheers man!
-
Hello again!
Right, here's my actual fstab:
Code# UNCONFIGURED FSTAB FOR BASE SYSTEM tmpfs /tmp tmpfs defaults 0 0 UUID=b3343e94-52f3-4c18-9060-7ce0c436eb1b /media/b3343e94-52f3-4c18-9060-7ce0c436eb1b ext4 defaults,nofail,acl,user_xattr,noexec 0 2 #/dev/sda2 /mnt/Data ext4 defaults 0 0 # >>> [openmediavault] # <<< [openmediavault]config.xml (mntent section):
Then I try to unmount /dev/sda2 via webgui and get this:
CodeError #3003: exception 'OMVException' with message 'Failed to get configuration (xpath=//system/fstab/mntent[dir='/media/b3343e94-52f3-4c18-9060-7ce0c436eb1b'])' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:958 Stack trace: #0 [internal function]: OMVRpcServiceFileSystemMgmt->umount(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('umount', Array, Array) #3 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'umount', Array, Array, 1) #4 {main}dmesg | tail after trying to unmount the partition via webgui: (MAC address hidden)
Code[ 16.565173] EXT4-fs (sda1): re-mounted. Opts: (null) [ 23.518545] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: user_xattr [ 24.998405] IPv6: ADDRCONF(NETDEV_UP): lo: link is not ready [ 27.581603] eth0: device MAC address xx:xx:xx:xx:xx:xx [ 29.580277] libphy: stmmac-0:00 - Link is Up - 1000/Full [ 29.597949] RPC: Registered named UNIX socket transport module. [ 29.604001] RPC: Registered udp transport module. [ 29.608696] RPC: Registered tcp transport module. [ 29.613442] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 29.808225] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).What now?

-
Hello again, subzero!
Before I saw your post, I had edited the /etc/openmediavault/config.xml and added the following:
Code
Display More<fstab> <!-- <mntent> <uuid>b3343e94-52f3-4c18-9060-7ce0c436eb1b</uui$ <fsname>b3343e94-52f3-4c18-9060-7ce0c436eb1b</f$ <dir>/media/b3343e94-52f3-4c18-9060-7ce0c436eb1$ <type>ext4</type> <opts>defaults,nofail,acl,user_xattr,noexec</op$ <freq>0</freq> <passno>2</passno> <hidden>0</hidden> </mntent> --> </fstab>And it did the trick (I mean, the /dev/sda2 is mounting on boot device). So I cannot tell if your new instructions changed something.
At this moment, I cannot unmount via webgui -when I try to do that, I get this error:
CodeError #3003: exception 'OMVException' with message 'Failed to get configuration (xpath=//system/fstab/mntent[dir='/media/b3343e94-52f3-4c18-9060-7ce0c436eb1b'])' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:958 Stack trace: #0 [internal function]: OMVRpcServiceFileSystemMgmt->umount(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('umount', Array, Array) #3 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'umount', Array, Array, 1) #4 {main}My main issue at this moment is, when I try to add a shared folder for instance, I have no device listed. It shows blank.
David got it working today, but all changes just disappeared some moments later (and later on, config.xml went all blank, luckily I had a backup).
Then, my questions are:
a) How can I make the /dev/sda2 show up again on 'devices'?, and
b) Why the hell is it losing the configuration?Thanks again!
-
Hello all,
After all your help, it worked, thanks to subzero and David.
But then, all of sudden, all the changes to the settings were gone and I'm back to start.
Devices not listing again. I found out that config.xml was somehow modified and lost the entire mntent section.
I've rebuild it (according to the instructions above) but nah, not working.
What the heck??
-
Not an USB disk, it's a 2TB HDD on a Iomega Home Media Network Drive Cloud Edition, with Debian Wheezy running.
Code
Display More[root@NAS:~]$.dmesg | tail [ 12.224391] udevd[284]: starting version 175 [ 16.019658] EXT4-fs (sda1): re-mounted. Opts: (null) [ 22.733611] IPv6: ADDRCONF(NETDEV_UP): lo: link is not ready [ 24.975052] eth0: device MAC address be:84:d8:44:84:f6 [ 26.984601] libphy: stmmac-0:00 - Link is Up - 1000/Full [ 27.030827] RPC: Registered named UNIX socket transport module. [ 27.036746] RPC: Registered udp transport module. [ 27.041512] RPC: Registered tcp transport module. [ 27.046205] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 27.220162] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).I can mount it manually. However:
a) Without the additions on /etc/fstab and /openmediavault/config.xml (the ones I had before) it will lose the mount on reboot;
b) Even with manual mount, I have nothing listed on devices dropdown menu when trying to create a new folder/share for instance.To edit fstab and config.xml, I did as this link says: OMV 1.0.29 Partition mount problem.
Thanks for your patience!

-
Here it is:
And still can't mount the partition via webgui:
Code
Display MoreError #6000: exception 'OMVException' with message 'Failed to mount '70c76c02-4223-4018-b741-1aaffbc74570': mount: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so ' in /usr/share/openmediavault/engined/module/fstab.inc:90 Stack trace: #0 /usr/share/openmediavault/engined/rpc/config.inc(206): OMVModuleFsTab->startService() #1 [internal function]: OMVRpcServiceConfig->applyChanges(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('applyChanges', Array, Array) #4 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(878): OMVRpc::exec('Config', 'applyChanges', Array, Array) #5 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array) #6 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array) #7 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('mount', Array, Array) #8 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'mount', Array, Array, 1) #9 {main} -
I had to manually edit that mntent section before because I wasn't able to mount the data partition (/dev/sda2).
So, I did as you told now, and here it is: (getting mad):

Any clues?
-
Hello subzero79,
Didn't work.
Volume still not showing.If I try to unmount the volume via webgui, I get this:
CodeError #3003: exception 'OMVException' with message 'Failed to get configuration (xpath=//system/fstab/mntent[dir='/media/70c76c02-4223-4018-b741-1aaffbc74570'])' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:958 Stack trace: #0 [internal function]: OMVRpcServiceFileSystemMgmt->umount(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('umount', Array, Array) #3 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'umount', Array, Array, 1) #4 {main}Besides,why it keeps saying stuff about arrays, if I have no raid set?
And, not sure if it helps, but here's the content of my /media folder:
Codetotal 20 drwxr-xr-x 5 root root 4096 Jan 9 04:03 . drwxr-xr-x 23 root root 4096 Jan 9 14:08 .. drwx------ 2 root root 4096 Jan 9 02:21 32aaa5e4-2e35-42a8-8769-0f3f4c064a80 drwxr-xr-x 3 root root 4096 Jan 9 03:13 70c76c02-4223-4018-b741-1aaffbc74570 drwx------ 2 root root 4096 Jan 9 03:10 d11f6086-24ea-4d13-b712-43466839e34bThanks again.
-
Sure:
omv-mntent:
Code<mntent> <uuid>70c76c02-4223-4018-b741-1aaffbc74570</uuid> <fsname>70c76c02-4223-4018-b741-1aaffbc74570</fsname> <dir>/media/70c76c02-4223-4018-b741-1aaffbc74570</dir> <type>ext4</type> <opts>defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0</opts> <freq>0</freq> <passno>2</passno> <hidden>0</hidden> </mntent>blkid:
Code/dev/sda1: UUID="3ad4e271-f9ed-4d81-a9a5-ba90b6c3931e" TYPE="ext4" LABEL="System" /dev/sda2: UUID="70c76c02-4223-4018-b741-1aaffbc74570" TYPE="ext4" LABEL="Data"Thanks.