Trusted, Bureaucrats, Administrators
12,424
edits
Changes
From Amahi Wiki
Installing HDA on HP Mediasmart Server (view source)
Revision as of 17:09, 9 January 2021
, 17:09, 9 January 2021no edit summary
{{MessageBox|backgroundcolor = #FBB|image =Warning.png|heading =WARNING|message = '''NOTE:''' This Ubuntu-based systems ONLY. Guidance may not work for Amahi 7 or other Fedora-based releases.}}{{NeedsUpdate}}---- Installing your HDA on an old [http://en.wikipedia.org/wiki/HP_MediaSmart_Server HP MediaSmart server], previously used for Windows Home Server, will bring all the benefits of Amahi to the small device. This is only recommended for users who are comfortable with the terminal, or are willing to set up a headless server with VNC. Experienced users may also migrate from a PC server to the MediaSmart server, avoiding installation of a new HDA and all the hassle of backing-up files that occurs with it.
The steps for this tutorial are from [http://dagolav.prestegarden.com/installing-ubuntu-on-the-hp-mediasmart-ex490/ here]. To continue you will require:
==Starting From Scratch==
===Installing Ubuntu===
1. Connect the hard drive into the spare PC.
2. Install '''Ubuntu 12.04, the server version'''. I was not able to get the GUI version of Ubuntu working on the MediaSmart server. The GUI version is also not recommended since there is no VGA or DVI ports for a monitor, only USB.
3. Do NOT install Amahi yet.
4. Install an ssh server:
5. Verify that the SSH is working by connecting with [[Key-based SSH Logins With Putty|Putty]]. If the SSH is not enabled, enable it:
6. Change the interfaces file to reflect eth1, not eth0:
auto eth1
8. Note the hardware address of the network card:
9. Shutdown the PC:
===Installing Amahi===
1. After rebooting and SSHing into the server, [[Binding Network Devices|change the network card to eth0]] from our previous eth1. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete that whole line. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
So above, we would delete the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.
You should now be able to access your HDA as a share and as the http://hda link. You can [[Install VNC server on Ubuntu Server 12.04|install a VNC server]] to connect to the HDA using a graphical interface.
==Transplanting an existing Amahi server==
Here I will present how I transplanted my current (headless) Amahi server , installed on '''Ubuntu 12.04, the server version''', from a PC to the MediaSmart server. The steps below are mainly a reorganization of the steps above.
===Preparing the HDA===
1. Disconnect all drives. If you are using Greyhole, check out Change the [[Reconnect existing Greyhole storage pool]] page. This will allow you interfaces file to disconnect the data drivesreflect eth1, and only risk the OS drive.not eth0:
auto eth1
iface eth1 inet dhcp
5. Shutdown the server:
===Moving the Hardrive===
1. Move the OS hardrive to the MediaSmart server, slot 1. If you are using Greyhole, ''make sure to move the rest of your data drives'' as well, and plug these into any slot other than slot 1. Turn on the MediaSmart server.
2. Check your router for the server's IP address, use Use [[Key-based SSH Logins With Putty|Putty]] to SSH into that the previously noted IP address.
3. After opening the 70-persistent-net.rules file below, look for the PC network card hardware address and delete comment out that whole line. Do not delete incase the server needs to be put back into the old case. Change the remaining hardware address to come up as eth0 (it is currently eth1 at the end of the line).
# SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1d:60:b5:43:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="5c:d9:98:af:21:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth1eth0"
So above, we would delete commented out the first line and change "eth1" to "eth0" on the second line. The reason is that Amahi is configured by default to recognize eth0, so all apps would go to that. However our eth0 was taken by the host-PC's network card. Again, ctrl+x and y to save.
4. Change all eth1's to eth0's in the interfaces file. Ctrl+x and y to save.
5. Finally, reboot your HDA:
===Reconnect the Storage Drives===
Plug the remaining data drives into the MediaSmart server. If you have Greyhole and are having trouble, check out the [[Reconnect existing Greyhole storage pool]] page. Otherwise, the [[Adding a second hard drive to your HDA]] page may be of service.
== General Troubleshooting==
Q: ''The MediaSmart server's health light is flashing, it is a bluish color''
A: This is normal if using the guide above. After experimenting, it seems that the health light indicates that the MediaSmart server cannot detect a valid Windows Home Server installation. I came to the conclusion after using the Recovery Disk (comes with the HP WHS server) to reinstall Windows Home Server onto the hard drive. The blinking stopped after a reboot with Windows, but it came back after I reinstalled Ubuntu onto the same hard drive.
Q: ''The MediaSmart server is falshing red and blue when booting''
A: I have not found this to be of any consequence, once fully booted the server will just flash the blue health sign indicating that Windows Home Server is not installed.
