download driver hp media vault 2100 for mac Prerequisites for Hacking the HP MediaVault. Note that the information given here, simply reports my experience with the mv5020. I have no experience with other models of HP MediaVault than the mv5020. I provide no warranty, and you should proceed at your own risk. A risk, which is true and real - as stated below. Before you start: BE WARNED. Following these instructions is likely to void any warranty on the HP MediaVault. Following these instructions are highly likely make your HP MediaVault completely and utterly unresponsive and cause loss of data. This is known as "bricking" the MediaVault. Run the Firmware Recovery utility (see below). Attach a serial console following Lee Devlin's instructions and fix your mistake from a console. Dispose of the hardware in an environmentally responsible way. Unfortunately, the recovery-utility will reset the contents of the disks to factory default: Empty . In other words: The recovery-utility WILL WIPE ALL YOUR FILES FROM THE MediaVault DISK(S) . Lee Devlin has located a version of the image, which should be able to restore the firmware without cleaning the disks, but I have not yet heard of anyone using it. You can find the instructions and the modified image here. Another warning: When I had the opportunity to try out the recovery tool, it failed in varying ways 9 out of 10 times - and each attempt took at least 30 minutes. However, don't give up: Suddenly, randomly, the blue light turns on, and you are up-and-running again - time to restore your backup of your disk contents (which you have - right?). Skills you may need. . If you do not already have experience with Linux (or related) operating systems, this may take a while (months to years). HTML and possibly PHP (days to weeks), if you want to play with the web-server. If you plan to use the PostgreSQL database, you should learn SQL (weeks to months). You may want to install PostgreSQL on your PC and play with it there before attempting it on the MediaVault. It is possible to install PostgreSQL ODBC drivers on MS Windows, so you can access the database on the MediaVault from tools like MS Excel - for some nice graphical statistics on hit counts, etc. I have done this - cost me a "bricking" round, but now it works. If you want to use Java Servlets in the Jetty server, you need basic programming skills (years) and specifically experience with the Java programming language (months to years if you did not use this language before) Preparations. Read Lee Devlin's MediaVault FAQ pages and use them as a reference throughout your work with the MediaVault. You may also want to search or join the two MediaVault groups that Chris Seto maintains at Yahoo, in our case, the one on Hacking the HP Mediavault might be particularly relevant. Get ssh access to the MediaVault shell as described in the MediaVault FAQ. This is unfortunately not bash, but just a plain bourne-shell. If you take the time to fix the TTY bug as explained at the bottom of this page, then you can use the "vi" editor on the box. Do also read the other items on that "Hacking FAQ" page. If you are coming in from a Windows box, then you can install PuTTY, or you can use Cygwin, as I do. After setting up SSH on your PC, consider appending your public key to the /.ssh/authorized_keys file on the MediaVault, to allow password-less login. Finding your way around the MediaVault. Directory Contents / Root directory - this is where you are at login /bin Linux executables directory. /usr/bin More Linux executables. /usr/htdocs The root directory for the Apache webserver. This is where web-pages are served from - except JSPs. /usr/jetty-5.1.12/webapps/Webshare This is where JSP pages are located. This is for experts only, so if you don't already know your way around a J2EE directory structure, stay away from this place. /etc Standard Linux configuration files. Your Apache webserver httpd.conf file is here, but it will be overwritten at boot-up. /etc/inc MediaVault boot-scripts. These are very fragile, so handle with care. Any mistake, and you have a "brick". You will, however, be hacking the file func_httpd.inc and possibly also func_daemon.inc and func_webshare.inc /share MediaVault disk(s). The above directories are all on the firmware file-system, whereas the /share directories are on the real hard-drive(s). /share/1000 Here you find the virtual disks (Samba mount-points): Documents, Backup, etc. that you can see from Windows. /share/1000/Documents The mv5020 does not sport an ftp server, so create a directory here for file-transfers between Windows and MV. /share/1000/Documents/web This is what I happened to call my transfer directory. You could also create and mount a new shared directory using the standard GUI for the MediaVault /share/1000/postgres This is where the PostgreSQL database resides. It is not mounted on Samba. I don't think you can, and I wouldn't like to try. /share/1000/postgres/data If you need access to the PostgreSQL database on the MediaVault from Windows, you need to customize the pg_hba.conf file here. Editing Linux files on Windows. You can do that directly on the MediaVault using the vi -editor. It works if you have the terminal settings right, and if you fixed the TTY bug as explained above. Personally, I am not fond of vi , so if you are like me, you may want to transfer the file to Windows, edit it there, and then move it back to the original location. However, you must take care, because there is a subtle difference between text-files on Linux and Windows. On Windows, all lines must end with two characters (bytes) named CR and LF , whereas on Linux, lines must end in the CR byte only. (Aside: CR means CarriageReturn, and LF means LineFeed. When I was a kid, the Teletype terminals were basically remote-controlled typewriters. Moving the type-head back to the beginning of the line was a CR operation, whereas advancing the paper by one line was a LF operation. Doing just the LF was good fun - you could create all sorts of interesting effects by typing several lines on top of eachother). Some Windows tools, such as Wordpad ( C:\Program Files\Windows NT\Accessories\wordpad.exe ) can interpret Linux files correctly, but will write files back containing CR-LF sequences. Other Windows tools, such as Notepad cannot correcly display Linux files. Conversely, some Linux tools can interpret Windows files correctly, whereas others will fail due to the unexpected LF characters inserted by Windows tools. Add Software and More. Easy, secure, real-time disaster protection designed for Windows . Also automatically sync PC's to your Server. Productivity applications. Easily move content between a USB hard drive connected to a HP MediaSmart Server or HP Data Vault. How to download software add-ins. Disk Defragmentation to improve hard drive performance* PerfectDisk® 10 Windows Home Server provides premier disk defragmentation capabilities for faster streaming media and overall performance. Eliminate fragmentation-related slows and lags now. Diskeeper invisibly restores server speed, reliability and performance – automatically. Installing on HP mv2120 and mv5020. In a nutshell, the installation of Debian on your HP mv2120 and mv5020 works like this: you use the recovery mode of the mv2120 to load the Debian installer image via the network. Debian installer will start and allow you to login via SSH to perform the installation. Debian will be installed to disk and the mv2120 will directly boot Debian from disk. If you follow this procedure, Debian will be installed to your SATA disk and the HP firmware on disk will be replaced with Debian. Debian does not install a web interface to configure your machine, although it's possible to install such software. If this is not what you want, please don't proceed with the installation. Requirements and Preparation. In order to install Debian on a HP mv2120, you need the following: A HP mv2120 or compatible device (e.g. HP 5020, mv5140 or mv5150). An internal SATA disk in the HP mv2120. A network connection. Another machine on which you have an SSH client. SSH is included in every Linux distribution as OpenSSH and there is PuTTY for Windows. Another machine with either the HP mv2120 recovery tool (Windows) or uphpmvault (Linux and other systems). Making a Backup. You have to make a backup of all the data stored on your HP mv2120 before starting with the installation of Debian since Debian will format the whole disk during the installation. Starting the Installer. The HP mv2120 has a recovery mode through which it can request a boot image via the local network. This recovery mode will be used to load the Debian installer. HP ships a tool for Windows to serve recovery images to your mv2120 and there is a tool called uphpmvault written by Marc Singer that does the same on Linux and other systems. You can obtain the Windows tool by going to HP's web site. First, search for mv2120 , then choose Software & driver downloads and then download the HP Media Vault Firmware Recovery Utility . uphpmvault is in Debian so you can simply install it with apt . Once you have installed uphpmvault or the Windows tool, you have to tell the tool to serve the recovery image. Download the Debian installer image and start the tool. If you want to use the Windows tool, please follow these instructions. To use uphpmvault, issue the following command: Now you have to put your mv2120 into recovery mode: First of all, turn off your mv2120. Press the reset button and keep it pressed. Press the power button and keep it pressed. After a few seconds, your HP mv2120 should go into recovery mode. Your recovery tool will say that it's recovering the device. At this point, you can release the reset and power buttons. If the recovery mode doesn't start within 5 seconds, please turn your device off and try again. uphpmvault will show the MAC address of the mv2120 and will give a status when it's recovering the device: Once the recovery has completed, your HP mv2120 will automatically reboot and the Debian installer will start. The Installation. Since the HP mv2120 does not have any IO device, SSH will be used for the installation. The installer will bring up the network, start the OpenSSH server and you can then connect to the device using SSH. You have to wait approximately two minutes after starting the system before you can connect. When the installer is ready, it will change the health LED to indicate that you can now login via SSH. Here is a list of stages and the corresponding signals the boot process of Debian installer will go through: Quickly blinking purple: The mv2120 is loading the Debian installer image. The SATA light goes on, the health light continues to blink quickly: the Linux kernel has been loaded. Health light goes blank: the Debian installer ramdisk has been loaded. Slowly blinking blue: Debian installer has finished some critical steps of its startup process. Solid blue: Debian installer is ready and you can login via SSH. Since the HP mv2120 does not have an LCD, the installer cannot tell you which IP address to connect to or which password to use. With regards to the IP address, the following strategy is used: If your HP firmware is configured to use DHCP (the default configuration from HP), Debian installer will try to acquire an IP address with DHCP. You can use the MAC address of your mv2120 to tell your DHCP server to give out a specific IP address to your machine. If you configured a static address in your HP firmware, this configuration will be used. However, if your network configuration was incomplete (e.g. IP address or DNS were missing), the installer will use DHCP instead. If you're using a blank disk (or any disk without the HP firmware), the installer will use DHCP. If DHCP is used but your DHCP server does not respond, the HP mv2120 will use the fallback address `192.168.1.100`. If you are unsure what the address of your HP mv2120 is, unplug the Ethernet cable, start the machine again, wait until Debian installer is ready for SSH and then plug the cable back in and connect to this fallback address. Please make sure that the HP mv2120 is on a local network to which only you have access since the installer uses a very generic password, namely install . The user is installer . Connect to the installer (again, replace the address in the example with the actual IP address of your mv2120): The installation itself should be pretty standard and you can follow the installation guide. The installer knows about the HP mv2120 and will by default choose an appropriate partition layout. If you partition the disk manually, you have to make sure that sda1 is a /boot partition with type ext2 or ext3 (ext2 is recommended for the boot partition). You also have to set the bootable flag for this /boot partition, otherwise your mv2120 will fail to boot. During disk partitioning, Debian installer will find an existing LVM logical volume on the disk and ask you whether it's okay to remove it. This is the existing logical volume from the HP installation but it cannot be used for your new Debian installation because the disk layout used by the HP firmware will not work for Debian. Please answer the question whether the logical volume data should be removed with yes (or cancel the installation and make a backup of your disk if you have not done so yet). At the end of the installation, the installer will create a boot image on disk. Afterwards you will get a confirmation that the installation is complete. Confirm, wait for the installer to finish and once your SSH session terminates, wait a few minutes before you can connect to your newly installed system via SSH. The LEDs of your HP mv2120 will be used to indicate when you can connect via SSH. You will be able to log in as your newly created user. The health LED is used to signal the status of the boot process. Here is a list of stages and the corresponding signals the boot process will go through: Quickly blinking blue: the mv2120 is starting up and is loading the boot image from disk. This stage takes about 2 minutes. The SATA light goes on, the health light continues to blink quickly: the Linux kernel has been loaded. Slowly blinking blue: the ramdisk has been loaded and is now trying to mount your disk. Solid purple: your root partition has been mounted and the boot process will continue from disk. If this stage takes a long time, the system might be checking your disks. Solid blue: the boot process has been completed and you can log in via SSH. Success. You should now have a complete Debian system running on your HP mv2120. You can use apt and other tools to install additional software. The mv2120 is an ARM based device and the armel architecture is fully supported by Debian. In case you run into any bugs or problems, you may want to check the list of known issues and bugs with Debian on the HP mv2120. HP Media Vault MV2120 (500GB) review: HP Media Vault MV2120 (500GB) The Good Very easy to set up with an intuitive Web interface and convenient desktop application; ships with 500GB hard drive and a free bay for the addition of a second drive; USB ports for additional storage; supports RAID 1; includes an iTunes server and Web access for photos. The Bad Does not support writing to external drives formatted in NTFS; installs programs that start automatically and doesn't provide a method to disable them; rigid RAID setup; no print-serving capability; flimsy drive tray. The Bottom Line The HP Media Vault MV2120 is a two-bay NAS drive that novice networkers will find simple to set up and use. While it offers flexible expansion options with a free internal drive bay and two USB ports, the intrusive Media Vault software and lack of a print server dampen our enthusiasm a bit. Review Sections. Review Specs. The HP Media Vault MV2120 is a two-bay network-attached-storage device with 500GB of storage and room to expand. It keeps things simple and serves up basic NAS features, including an iTunes server, remote Web access, and scheduled backups. While the device is a snap to set up, we found the bundled software to be intrusive. We were disappointed by the lack of a print server despite the existence of not one but two USB ports. The Media Vault MV2120 trails behind the Synology Disk Station DS107+ in terms of features and speed. Also, Hewlett-Packard's Media Vault ships with 500GB of storage for roughly the same price as the empty Synology enclosure while offering a second drive bay for data expansion. Priced at $300 for 500GB of storage, the Media Vault MV2120 delivers good value per gigabyte ($0.60 per GB). By focusing on a few essential features, the drive is easy to set up and use. Its affordability coupled with simplicity makes the HP Media Vault MV2120 an attractive choice for novice home users. However, keep shopping if you need a NAS device with the capability to share a printer across your network. Design The MV2120 is solid and relatively compact for a dual-bay NAS device; however, it's nowhere near as small as Buffalo's LinkStation Mini. Blue LED lights glow on the front of the device to indicate power, networking, and hard-drive status. Each bay also has a blue light that shines when there's a hard drive installed. The device has two USB ports, one on the front and the other on the back, that can be used to add external hard drives to increase the storage space or to back up the content on the device. We tried a few external hard drives, and they worked very well. The USB ports were also able to power the bus-powered external hard drives. The MV2120 only supports write and read on external drives formatted in the FAT32 file system; drives formatted in NTFS can only be read. If you want to back up the contents of the MV2120 to an external hard drive, the USB drive needs to be formatted in the EXT3 file system (Linux). Note that once you format an external drive in EXT3, Windows PCs or Macs will no longer recognize it. The Media Vault MV2120 ships with a single 3.5-inch 500GB 7,200rpm hard drive. This hard drive is screwed in, but it is still user-changeable. Unfortunately, the of the MV2120 is hosted on this hard drive, which means you will need to download a utility from HP to rebuild the whole system should you replace the drive. It would be much less of an hassle if HP had installed the device's operating system on a ROM chip, as is done in the Synology DS107+ or many other NAS devices we've reviewed. The second hard-drive bay on the other hand is very flexible. It can take a 3.5-inch SATA hard drive of any capacity and it is even hot- swappable, meaning you can replace it without having to turn off the device. However, it comes with a plastic tray that feels flimsy and cheap. Nonetheless, it does its job well as long as you are gentle with it. Once the second hard drive is installed, you have the option of combining it with the fixed one in a RAID 1 (there's no option for RAID 0) configuration or having it work as a second volume. In either case, the drive will need to be formatted in EXT3. However, make sure you know which configuration you want, because once you have decided to go with the RAID 1, the MV2120 doesn't offer any easy way to change it. Features It's very easy to set up the Media Vault MV2120. The bundled CD contains the Media Vault Monitor application that helps your computer detect NAS drives on the network and the Media Vault Control Center application for accessing the MV2120's main features. Among other things, the software allows for quick access to the MV2120's default shared folders, such as Documents, Music, Photos, and its main functions such as backup (the MV2120 comes with NTI Shadow backup software to support its backup function), Photo Webshare, and iTunes server. We do have one complaint about the installation process: HP automatically sets Media Vault Monitor and HP Update to launch each time you start the computer. There's no option to disable this within the software and we didn't find any reason for it to automatically start up. The MV2120 ran just fine without the software running. During our test, more than once the HP Update popped up suggesting that we run an update, when we did, there was no update to be found. The HP Media Vault MV2120's backup feature is flexible. You can choose to back up your computer's important files (My Documents, My Music, My Picture, and so on) or back up any selected folders from a computer to the MV2120. You can also back up the NAS itself onto a USB external hard drive. Like most other backup solutions, you can do the backups immediately or schedule it. MV2120 even lets you choose to back up files when they change and keep multiple versions of the files. Overall, we found the backup function very through and convenient. HP MediaVault MV2100 Series "hacking" FAQ. Written by Chris Seto (chris12892-AT-gmail.com), with contributions. Thanks to Lee Devlin for hosting this FAQ! IPKG may be added to the MV2. See Lee Devlin's IPKG page here. The linked method uses the Unslung repository. 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. --> Firefly Web Access. It is possible to open the web page for Firefly. You can see (but not change) the Firefly variables. Just add port 3689 your Media Vault's web address and it will open the Firefly configuration window. The user is 'admin' and password is 'mt-daapd'. 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 work. The 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 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. Then you must reboot for this to take effect. Transmission Bittorrent Installation. Transmission is a simple bittorrent client that has a web interface. You can run it on the MV2 and access it from anywhere with a browser at the address http://hpmediavault:9091 (assuming your MV2 is named 'hpmediavault'). It's convenient to have the MV2 run a bittorrent client so that when you want to download a large torrent, you don't have to have PC on continuously. Before installing it, you'll need to use the the ipkg instructions on the MV2 hacking page to get ipkg working as explained here. After setting up ipkg, you can just type: ipkg install transmission. To get it up and running, It is necessary to edit the settings.json file located under this directory: Specifically, change these two lines to read as follows: (On my MV2, "/share/1000/Videos" is a valid directory, yours may be different, check to make sure since that number 1000 can change if you've been adding or removing drives.) (Unless you add 192.168.*.* it will not allow logins from other computers on the network, it generated a 401 error. This assumes your internal network is on address 192.168.*.*, if not, modify accordingly.) Then you'll need to set up these environment variables which, for testing purposes, you can do from the command line: export EVENT_NOEPOLL=1 export TRANSMISSION_WEB_HOME=/opt/share/transmission/web/ Then to start it: The -f option will run it with a text output on its status to your SSH window and help you to see if it's working. If it works, then it will just be a matter of putting those commands in a startup file to allow it to run automatically on startup. Otherwise, it will stop running when you log out of the SSH session. To test it, open a browser and navigate to http://hpmediavault:9091 and see if you get a window. If you do, use a service such as mininova.org to find a valid URL for a torrent and paste it into the URL window to see if it works. I added the lines to the end of /etc/init.d/rc.bootup that make it check for startup.sh as explained here. Inside startup.sh put these lines to set the environment variables and launch Transmission during boot up: export EVENT_NOEPOLL=1 export TRANSMISSION_WEB_HOME=/opt/share/transmission/web/ /opt/bin/transmission-daemon. Netatalk (AFP) Installation. With the introduction of Lion Mac OS X (10.7) Apple broke the compatibility of using Time Machine with the SMB file sharing capabilities of the MV. I first noticed that SMB stopped working when I upgraded to Snow Leopard (10.6.8) so if you've been using your MV2 to back up your Macs with Time Machine, you may find it stops working when you update the OS. In the case of the MV2, it's possible to use the Optware IPKG installer to install Netatalk, an open source implementation of Apple's AFP and thus make Time Machine work again with your MV2. The Itsy package manager (IPKG) is covered as a separate topic of this FAQ and it is necessary to install it first, so please do that if you haven't installed it already. The installation of IPKG is explained here. After setting up ipkg, you can just type: /opt/ipkg install netatalk. /opt/ipkg install libgcrypt. Provided everything installed cleanly, you'll need to edit a few lines in two configuration files before launching netatalk. I am assuming you know how to use the nano or vi editors on the MV2. In /opt/etc/netatalk, edit the file called afpd.conf and add this line to the end of it: - -udp -noddp -uamlist uams_randnum.so,uams_dhx.so,uams_dhx2.so -nosavepassword. Then, in the same directory, edit the file AppleVolumes.default and add this line to the end of it: /share/3595/BackupTM "BackupTM-AFP" allow:lee,lee2 cnidscheme:dbd options:usedots,upriv,tm. In my case, I had set up an SMB share called BackupTM and user lee on the MV2 so match those fields accordingly depending on which MV Share name and user name you intend to use for Time Machine. I appended the letters AFP since you can mount the SMB share or the Apple File Protocol share, and for Time Machine, it can only use the AFP method. Having distinct names helps me keep track of the way that Volume gets mounted in /Volumes. I am going to create a new user called lee2 later, hence that's why I added lee2 as a user. The numbered directory on my MV2 (3595) was set up by the MV2 using some random sequence and yours will likely be different. You'll have to look under the /share directory and find where the share you want to use for the AFP connection is located. I also found it necessary to open up privileges on the folder 3595 for all users like this: chmod 777 /share/3595. Time Machine needs a user/password login on the MV2 and I created one by adding a user in the MV2's web user interface. You'll find that this creates a user in the file /etc/passwd file, but the user's password is not stored there and the shell defaults to /bin/nologin. The /etc/passwd file looks like this: # more /etc/passwd root:$1$2.bH9TLX$Zoyy6sTNJjsEVuAdvu2rt.:0:0::/:/bin/sh nobody:x:99:99:Nobody:/:/bin/nologin postgres:x:500:500:DB User:/:/bin/nologin _ntp:x:501:501:NTP User:/:/bin/nologin lee:x:502:502:Linux User. /:/bin/nologin. Please note how user lee appears to have no password and no shell for login. We will need to fix this. To place the password for user 'lee' in the /etc/passwd file, you can use the passwd command like this: You will be prompted for the password to set for user 'lee' and you should make it the same as password you chose in the MV2's admin web user interface, just to make it easier to remember. It will encrypt it and so don't expect to find the password in the clear, but rather a cryptic looking string in the second field. Next you'll edit the file and change the /bin/nologin to /bin/sh. When you're done, the user entry should look something like this: lee:$1$$TWOx47x1ulv6VemPiLD4p/:502:502:Linux User. /:/bin/sh. During the next reboot, all that work will get undone because the MV2 re-writes the /etc/passwd file on each bootup. So copy that last line into its own file and give the user a new name. I called my new user lee2. Similarly, I called the file lee2 and stored it in /etc. We will need this file to fix the /etc/passwd file on each boot from the startup.sh script. Next we need to get netatalk running. The commands to do that are: We will need to put those commands in the startup.sh file so that netatalk starts automatically. When you type 'ps -ef', you should see /opt/sbin/afpd -D and /opt/sbin/cnid_metad running. We will need to add the lee2 user to /etc/passwd during each startup, so your startup.sh should have these lines: cat /etc/lee2 >> /etc/passwd /opt/sbin/afpd -D /opt/sbin/cnid_metad. The first line adds a new user, lee2 on to the /etc/passwd by appending a line to the end of the /etc/passwd file. This user doesn't exist in the MVs database, but it will have permissions to access the AFP share as configured in AppleVolumes.default file. Add that line to /etc/passwd manually by executing the command: cat /etc/lee2 >> /etc/passwd. Now you will have to create a sparse bundle file on your MV2 that your Time Machine will be able to use to login to an AFP share. The instructions for setting up a sparse bundle on your Mac and copying it over to the share are basically the same as the ones given for the SMB share as explained here. To mount this afp volume, open up the Finder on your Mac and use the K command to bring up a connect to server menu. In the server text box, type in afp://hpmediavault.local (use the actual name of your Media Vault in the event you changed it from its factory default name). It will prompt you for your username and password. Use the user/password that will be appended to the /etc/passwd file. Check the box to store it in your local keystore. Incidently, the procedure to unmount the AFP volume is to look in /Volumes with the terminal, and unmount it with the umount command, i.e., umount /Volumes/BackupTM-AFP. I had to do this a lot of times while I was experimenting. If everything is working properly, when you launch Time Machine on your Mac, you should see the MediaVault's share available as a destination for a backup location. Go ahead and select it and confirm it can backup to it. Once this has been done, Time Machine will be able to find it again on its own.