HP MediaVault MV2100 Series "hacking" FAQ
Written by Chris Seto (blue765d-AT-aol.com), with contributions.
Thanks to Lee Devlin for hosting this FAQ!
Please read first -- A warning on "hacking" your MV2
Index
IPKG
Startup.sh
Twonky web access
Mount the mobile rack drive as a separate volume
PHP bootup subsystem
Fixing TTY warning and getting the 'more' command to work
IPKG
IPKG may be added to the MV2. See Lee Devlin's IPKG page here. The linked method uses the Unslung repository.
Startup.sh
One way to start scripts and applications is to use a startup script. The MV1 had this feature, and the way it worked was that a script named "startup.sh" was inserted into the root of Volume1. The MV2 does not currently support this feature by stock, but a PHP script in /etc/init.d may be modified to check for, and execute startup.sh . The instructions for this modification are here.
Mount the mobile rack drive as a separate volume
By default, the mobile rack drive is mounted with the system drive as a JBOD. Nick from the Yahoo group discovered that you can modify the startup scripts to lie and tell the MV that the system only has one drive. You may access the guide here.
PHP bootup subsystem
WARNING: The PHP bootup subsystem is _very_ fragile. Do not edit it unless you know exactly what you are doing, and can risk losing ALL data on your MV2. If you make a mistake when editing these files, you may brick your MV2.
The MV2 uses a PHP based subsystem to boot up. Initially, rcS in /etc/init.d/ is followed. In the script, control is handed off to rc.bootup with is the main PHP file. Functions are defined in .inc files in /etc/inc/.
You may edit the files in init.d and inc, but make sure to reset the files back to their original permissions when you are done. failure to do so may brick your MV2 on the next bootup.
When editing the PHP bootup subsystem files, make sure to check your syntax and form before saving, and rebooting. If you were to typo something, you could brick your MV2 on the next bootup.
Please note that the PHP bootup subsystem is very fragile. You must make sure to do everything correct when editing the files contained in it.
When you edit the files, make sure to do it in these steps
1. Check permissions of the file with SSH
2. Change the permissions to allow editing
3. Edit the file
4. Check syntax, form, and make sure there are no mistakes
5. Save the file
6. Change the file back to the permissions it way on before you edited it.
Fixing the TTY warning and getting the 'more command to
workThe MV2 has an issue when you log in via SSH that generates a
TTY warning. This also prevents the 'more' command from responding
properly to a <space bar> so that you can display files. You can fix it by
copying these commands and executing them in this order. The first command
makes a backup of a file and the second one performs a stream edit on the
original file.
# cp /etc/udev/rules.d/50-udev.rules
/etc/udev/rules.d/50-udev.rules.orig
# sed -i -e '/ttyS0.*SYMLINK="tty"/d; /console.*MODE="0622"/aKERNEL=="tty",
NAME="%k", MODE="0666"' /etc/udev/rules.d/50-udev.rules