Skip to main content

Updated my OMV NAS to latest 2.X

It has been a while since I built my own NAS, it was running DEBIAN from the start but I've somehow installed OpenMediaVault somewhere between 2009 and 2015 :) It has been quite a long time since I last turned it on and it had OMV version 0.5.29. The last time I tried to turn it on was a month or so ago and it failed to start but somehow when my daughter asked if she could retrieve her old backup files, it started without a problem. When she was done with her tasks, I used the chance to update the OMV to the latest one, 2.X. Had few hiccup updating from 0.5 to 1.0 and then to 2.0 but everything was resolved (yes, who else did I turn to other than Uncle Google). After successful upgrade, I shut it down without any problem.

The problem came back this evening when my daughter said she need to copy few more files. Pushing the start button will start the fan/light for few seconds and it turned back off. Tried few times without success, changing power cable etc won't solve the problem. Luckily, I've another old AMD PC that staying around in my server rack, no idea how long it has been there but the PSU seems to be okay. Replaced the PSU and wallah, it is working again.

Original configuration:

1. Intel Atom D945GCLF2 (ATOM 330) w/ Built-in 1.6Ghz Dual Core ITX Mobo 
2. Kingmax 1GB DDR2/800
3. Aopen G326/Black  

Added to the original:

1. 1TB Samsung HDD 
2. 40GB Hitachi 2.5" Notebook HDD connected via USB (holding the OMV)



Popular posts from this blog

Configuring TechniColor TG784N V3 (Maxis issued broadband router) to use different DNS servers

Previous write up deleted. It seems to change the DNS servers in as shown on the status, but it does not really work.

Check the following website, this seems to work:

This can be done from the WEB GUI too, go into the following configuration path:

In my example above, I'm using paid service unblock-us instead of google public DNS servers.

Raspberry Pi + svxlink = Low power echolink node

What is the easiest way to get echolink node up and running on raspberry pi? Surely, get a premade image which has everything inside. I've created one image which can fit into 2GB SD card for this, just follow the following steps to get it up and running:

For hardware, you need to have the following:
Raspberry Pi for sure, with a minimum 4GB SD cardA USB echolink interface, can be commercially sourced or DIY. There are many DIY schematics out there that you could follow.  Here is the configuration on how to get the things working together, courtesy of website:

For software:
Download the following prepared image from google drive, it is based on raspbian-2015-02-16 image and has pre-installed svxlink-14.08. raspi-wheezy-svxlink.img.zipUnzip the file and copy it to your SD card using the following instructions that can be found here.Boot up the RasPi, if you do not have an HDMI monitor, you may want to access the RasPi from your terminal emulator (putty or the like), connec…

Debugging DMEE

I've come across many posting on the Internet (via google search), people asking on how to debug a DMEE for payment program. One of the few suggestion was to create a user exit just before the node that we would like to debug and put our breakpoint there. It seems that SAP has built-in this feature without needing us to create a user exit (available in ECC 6, have no idea if this is available on prior releases). Here is how you can put your breakpoint without any coding.

1. Display your DMEE tree using transaction: DMEE_DEBUG.

2. Click on the node that you would like to debug.
3. Go to conditions tab, you could see the Set Breakpoint button. Click to set.

4. Run the SAPFPAYM and specified the payment run date/id, payment format etc. SAP will stop at the node which you point your breakpoint at, as in 2.
5. To remove your breakpoint, just run the DMEE_DEBUG again, there is an option to delete all own breakpoints or all.