Amahi Wiki - User contributions [en]

FreeNX

2012-11-10T00:24:30Z

Carl Greenstreet:

NX is a technology for secure remote access - for example, you may want to run your Amahi Server headless (no monitor) and access a full graphical desktop environment on your server from another computer such as a Windows, Apple or Linux machine. NX provides both security and near local speed application responsiveness over high latency, low bandwidth links. The core libraries for NX are provided by NoMachine under the GPL. FreeNX is a GPL implementation of the NX Server and NX Client Components. More information can be found [http://freenx.berlios.de FreeNX project page] or [http://en.wikipedia.org/wiki/NX_technology Wikipedia].

Some users have found FreeNX gives far superior responsiveness to alternative VNC remote access approaches.

Following are the steps to get FreeNX up and running. It is fairly straight forward and easy, although there is one point that can be a little confusing but that is during the client setup, not the server. Basically, you need to install and configure the FreeNX Server onto your Amahi / FreeNX Server machine and then install a FreeNX client on every computer you may want to initiate the remote access from.

=Installation - FreeNX Server=

== Fedora==
First, log into your hda and open a terminal window.

Second, run this command to install FreeNX:

{{Code|yum install freenx-server}}

That's it. FreeNX should now be installed and running on your HDA. In order to use FreeNX, you will need a client to connect with. Go to http://www.nomachine.com/download.php and select the one for your appropriate operating system.

After downloading and installing the client, you will need to copy the client.id_dsa.key into the client. What I did was to scp the key from my server (/etc/nxserver/client.id_dsa.key) to my local system, open the file in a text editor, copy everything in it and paste it into the client. In my client this was under "Configure" then on the "General" tab, there is a button labeled "Key". This is where I pasted the client key information.

*NOTE* If you miss or overlook the step for the client key configuration, the client will attempt to use a default key for the HDA, and this does not work.

Finally, save the configuration, and then run the client to log into the HDA.

Since the Fedora 12 update some users have reported the following error when trying to log into their HDA after installing using the method above.
cat: /var/lib/nxserver/db/running/sessionId{(STDIN)}:
No such file or directory NX> 280 Exiting on signal: 15
A work around for this is to open:
/etc/nxserver/node.conf
And add the following to the end of the file:
{{Text|Text=COMMAND_MD5SUM<nowiki>=</nowiki>"md5sum"}}
.

===Alternative Approach - Install NoMachine NX Free Server===
'''In case you receive any error messages or notification from Fedora that some applications (like gnome-settings-daemon) crashed, you might want to install free NX server from Nomachine web site.''' Note the main difference with this software is that NX Free Edition is licensed as proprietary ( 2 connections limit) unlike FreeNX which is completely free Open Source Software

Go to Nomachine's web site and download NoMachine NX Free Server (http://www.nomachine.com/download-package.php?Prod_Id=1352) for Linux i386 RPM. It consists of three separate downloads: client RPM, node RPM and Server RPM. You can read on their web site detailed info on how to install it and in what order - pretty straightforward. Here is what you need to do to get it installed on Fedora 12:

1) Uninstall completely FreeNX server from your HDA (use Add/Remove software);

2) Go to your System Preferences-->Add Remove Software and do search for "audiofile" (without quotes). It will find for you a piece of software "audiofile-1:0.2.6" and "audiofile-devel-1:0.2.6. Install both development files and a library (Note: this should no longer be necessary after release 3.5).

3) Do search (the same Add/remove software) for "libstdc". It will find C++ libraries, different versions. Install latest ones in case they are not yet installed;

4) Do search (same place) for "GLIBC" - it will find a few libraries there. Install the latest ones in case they are not yet installed

That's it. Then go to terminal and do "sudo rpm -i" command for all three packages that you downloaded before. Here are the commands (you need to run these from the folder where you have dowloaded them):

;[root@localhost ~]# cd /folder_where_files_were_downloaded, example:
:cd /home/frank/Downloads/

*[root@localhost Downloads]# rpm -Uvh nxclient-3.4.0-5.i386.rpm
*[root@localhost Downloads]# rpm -Uvh nxnode-3.4.0-6.i386.rpm
*[root@localhost Downloads]# rpm -Uvh nxserver-3.4.0-8.i386.rpm

You need to install them in order: client, node, server.

It may complain something about permissions for CUPS that you may just ignore. Or if you want, you can follow the instructions the installer gives you, and fix permission problem and re-install. Keep in mind, that these three packages are easily removable thru Add/Remove interface in System Preferences.

==Ubuntu==

You are in luck! A chap named Shannon VanWagner created a script that makes the installation and configuration on Ubuntu 12.04 super easy. His page (including instructions on how to install manually) and the link for the script can be found at [http://www.humans-enabled.com/2012/05/how-to-install-freenx-on-ubuntu-1204.html FreeNX How to Install FreeNx on Ubuntu 12.04]

To Run Script:
# Download script to the Amahi Server
# Extract script from downloaded tar file
#Open terminal window, go to director with the script and type
{{Code|sudo sh heInstallFreeNX.sh}}

If the script runs successfully, it should return a message saying
'''Script Complete! Now you should be able to connect to this server using qtnx or the NX free client from nomachine.com.'''

If you receive errors running the script, it may be that you have a previous failed installation of FreeNx on your system. Try to completely remove FreeNx before attempting this script.

=FreeNX Client Installation=

Last step: you'll need to install a FreeNx client on each computer that you want to initiate remote access into your Amahi / FreeNX Server.

The simplest way is to get a client for various Operating System platforms (Mac OS, Windows, Linux) is downloading a proprietary but free client from NoMachines website. An alternative is the open source qtnx.

Download and install NX client software from the same [http://www.nomachine.com/download.php Nomachine's web site]. You need to install client software on the machine that you want to access your HDA from. Once installed, you can run it with default Key and default settings. Just choose Configure button, and on General tab, choose UNIX---Gnome for the desktop. No need to export/import Keys - can run with default installed keys. For added security, you can later change Keys as described in their knowledge base (article #AR01C00126).

When the gnome desktop loads, you will may get a message that Gnome Power Manager crashed. Ignore it - everything works fine.

=Troubleshooting NX=

#The /etc/hosts file must contain an entry for your HDA which may not be there. If NX is failing to connect to your HDA, check /etc/hosts for an entry as follows: [IP address] [localhost.localdomain] [localhost alias]. This info can be easily entered from your gnome desktop: System > Administration > Network > Hosts Tab.
#The default security keys should match in the server and client, but that could be a reason for not connecting. Check the documentation on the NoMachine website for how to copy the key.
#There is a detailed server administration manual on the NoMachine website, but the information above is sufficient for an install with basic security.

[[Category:Apps]]

FreeNX

2012-11-10T00:23:03Z

Carl Greenstreet:

FreeNX

2012-11-10T00:22:16Z

Carl Greenstreet:

NX is a technology for secure remote access - for example, you may want to run your Amahi Server headless (no monitor) and access a full graphical desktop environment on your server from another computer such as a Windows, Apple or Linux machine. NX provides both security and near local speed application responsiveness over high latency, low bandwidth links. The core libraries for NX are provided by NoMachine under the GPL. FreeNX is a GPL implementation of the NX Server and NX Client Components. More information can be found [http://freenx.berlios.de FreeNX project page] or [http://en.wikipedia.org/wiki/NX_technology Wikipedia].

Some users have found FreeNX gives far superior responsiveness to alternative VNC remote access approaches.

Following are the steps to get FreeNX up and running. It is fairly straight forward and easy, although there is one point that can be a little confusing but that is during the client setup, not the server. Basically, you need to install and configure the FreeNX Server onto your Amahi / FreeNX Server machine and then install a FreeNX client on every computer you may want to initiate the remote access from.

=Installation - FreeNX Server=

== Fedora==
First, log into your hda and open a terminal window.

Second, run this command to install FreeNX:

{{Code|yum install freenx-server}}

That's it. FreeNX should now be installed and running on your HDA. In order to use FreeNX, you will need a client to connect with. Go to http://www.nomachine.com/download.php and select the one for your appropriate operating system.

After downloading and installing the client, you will need to copy the client.id_dsa.key into the client. What I did was to scp the key from my server (/etc/nxserver/client.id_dsa.key) to my local system, open the file in a text editor, copy everything in it and paste it into the client. In my client this was under "Configure" then on the "General" tab, there is a button labeled "Key". This is where I pasted the client key information.

*NOTE* If you miss or overlook the step for the client key configuration, the client will attempt to use a default key for the HDA, and this does not work.

Finally, save the configuration, and then run the client to log into the HDA.

Since the Fedora 12 update some users have reported the following error when trying to log into their HDA after installing using the method above.
cat: /var/lib/nxserver/db/running/sessionId{(STDIN)}:
No such file or directory NX> 280 Exiting on signal: 15
A work around for this is to open:
/etc/nxserver/node.conf
And add the following to the end of the file:
{{Text|Text=COMMAND_MD5SUM<nowiki>=</nowiki>"md5sum"}}
.

===Alternative Approach - Install NoMachine NX Free Server===
'''In case you receive any error messages or notification from Fedora that some applications (like gnome-settings-daemon) crashed, you might want to install free NX server from Nomachine web site.''' Note the main difference with this software is that NX Free Edition is licensed as proprietary ( 2 connections limit) unlike FreeNX which is completely Free Open Source Software

Go to Nomachine's web site and download NoMachine NX Free Server (http://www.nomachine.com/download-package.php?Prod_Id=1352) for Linux i386 RPM. It consists of three separate downloads: client RPM, node RPM and Server RPM. You can read on their web site detailed info on how to install it and in what order - pretty straightforward. Here is what you need to do to get it installed on Fedora 12:

1) Uninstall completely FreeNX server from your HDA (use Add/Remove software);

2) Go to your System Preferences-->Add Remove Software and do search for "audiofile" (without quotes). It will find for you a piece of software "audiofile-1:0.2.6" and "audiofile-devel-1:0.2.6. Install both development files and a library (Note: this should no longer be necessary after release 3.5).

3) Do search (the same Add/remove software) for "libstdc". It will find C++ libraries, different versions. Install latest ones in case they are not yet installed;

4) Do search (same place) for "GLIBC" - it will find a few libraries there. Install the latest ones in case they are not yet installed

That's it. Then go to terminal and do "sudo rpm -i" command for all three packages that you downloaded before. Here are the commands (you need to run these from the folder where you have dowloaded them):

;[root@localhost ~]# cd /folder_where_files_were_downloaded, example:
:cd /home/frank/Downloads/

*[root@localhost Downloads]# rpm -Uvh nxclient-3.4.0-5.i386.rpm
*[root@localhost Downloads]# rpm -Uvh nxnode-3.4.0-6.i386.rpm
*[root@localhost Downloads]# rpm -Uvh nxserver-3.4.0-8.i386.rpm

You need to install them in order: client, node, server.

It may complain something about permissions for CUPS that you may just ignore. Or if you want, you can follow the instructions the installer gives you, and fix permission problem and re-install. Keep in mind, that these three packages are easily removable thru Add/Remove interface in System Preferences.

==Ubuntu==

You are in luck! A chap named Shannon VanWagner created a script that makes the installation and configuration on Ubuntu 12.04 super easy. His page (including instructions on how to install manually) and the link for the script can be found at [http://www.humans-enabled.com/2012/05/how-to-install-freenx-on-ubuntu-1204.html FreeNX How to Install FreeNx on Ubuntu 12.04]

To Run Script:
# Download script to the Amahi Server
# Extract script from downloaded tar file
#Open terminal window, go to director with the script and type
{{Code|sudo sh heInstallFreeNX.sh}}

If the script runs successfully, it should return a message saying
'''Script Complete! Now you should be able to connect to this server using qtnx or the NX free client from nomachine.com.'''

If you receive errors running the script, it may be that you have a previous failed installation of FreeNx on your system. Try to completely remove FreeNx before attempting this script.

=FreeNX Client Installation=

Last step: you'll need to install a FreeNx client on each computer that you want to initiate remote access into your Amahi / FreeNX Server.

The simplest way is to get a client for various Operating System platforms (Mac OS, Windows, Linux) is downloading a proprietary but free client from NoMachines website. An alternative is the open source qtnx.

Download and install NX client software from the same [http://www.nomachine.com/download.php Nomachine's web site]. You need to install client software on the machine that you want to access your HDA from. Once installed, you can run it with default Key and default settings. Just choose Configure button, and on General tab, choose UNIX---Gnome for the desktop. No need to export/import Keys - can run with default installed keys. For added security, you can later change Keys as described in their knowledge base (article #AR01C00126).

When the gnome desktop loads, you will may get a message that Gnome Power Manager crashed. Ignore it - everything works fine.

=Troubleshooting NX=

#The /etc/hosts file must contain an entry for your HDA which may not be there. If NX is failing to connect to your HDA, check /etc/hosts for an entry as follows: [IP address] [localhost.localdomain] [localhost alias]. This info can be easily entered from your gnome desktop: System > Administration > Network > Hosts Tab.
#The default security keys should match in the server and client, but that could be a reason for not connecting. Check the documentation on the NoMachine website for how to copy the key.
#There is a detailed server administration manual on the NoMachine website, but the information above is sufficient for an install with basic security.

[[Category:Apps]]

FreeNX

2012-11-10T00:05:37Z

Carl Greenstreet:

NX is a technology for secure remote access - for example, you may want to run your Amahi Server headless (no monitor) and access a full graphical desktop environment on your server from another computer such as a Windows, Apple or Linux machine. NX provides both security and near local speed application responsiveness over high latency, low bandwidth links. The core libraries for NX are provided by NoMachine under the GPL. FreeNX is a GPL implementation of the NX Server and NX Client Components. More information can be found [http://freenx.berlios.de FreeNX open source page] or [http://en.wikipedia.org/wiki/NX_technology Wikipedia].

Some users have found FreeNX gives far superior responsiveness to alternative VNC remote access approaches.

=Installation - FreeNX Server=

Here are the steps to get FreeNX up and running. It is fairly straight forward and easy, although there is one point that can be a little confusing but that is during the client setup, not the server. Basically, you need to install the FreeNX

== Fedora==
First, log into your hda and open a terminal window.

Second, run this command to install FreeNX:

{{Code|yum install freenx-server}}

That's it. FreeNX should now be installed and running on your HDA. In order to use FreeNX, you will need a client to connect with. Go to http://www.nomachine.com/download.php and select the one for your appropriate operating system.

After downloading and installing the client, you will need to copy the client.id_dsa.key into the client. What I did was to scp the key from my server (/etc/nxserver/client.id_dsa.key) to my local system, open the file in a text editor, copy everything in it and paste it into the client. In my client this was under "Configure" then on the "General" tab, there is a button labeled "Key". This is where I pasted the client key information.

*NOTE* If you miss or overlook the step for the client key configuration, the client will attempt to use a default key for the HDA, and this does not work.

Finally, save the configuration, and then run the client to log into the HDA.

Since the Fedora 12 update some users have reported the following error when trying to log into their HDA after installing using the method above.
cat: /var/lib/nxserver/db/running/sessionId{(STDIN)}:
No such file or directory NX> 280 Exiting on signal: 15
A work around for this is to open:
/etc/nxserver/node.conf
And add the following to the end of the file:
{{Text|Text=COMMAND_MD5SUM<nowiki>=</nowiki>"md5sum"}}
.

===Alternative Approach - Install NoMachine NX Free Server===
'''In case you receive any error messages or notification from Fedora that some applications (like gnome-settings-daemon) crashed, you might want to install free NX server from Nomachine web site.''' Note the main difference with this software is that NX Free Edition is licensed as proprietary ( 2 connections limit) unlike FreeNX which is completely Free Open Source Software

Go to Nomachine's web site and download NoMachine NX Free Server (http://www.nomachine.com/download-package.php?Prod_Id=1352) for Linux i386 RPM. It consists of three separate downloads: client RPM, node RPM and Server RPM. You can read on their web site detailed info on how to install it and in what order - pretty straightforward. Here is what you need to do to get it installed on Fedora 12:

1) Uninstall completely FreeNX server from your HDA (use Add/Remove software);

2) Go to your System Preferences-->Add Remove Software and do search for "audiofile" (without quotes). It will find for you a piece of software "audiofile-1:0.2.6" and "audiofile-devel-1:0.2.6. Install both development files and a library (Note: this should no longer be necessary after release 3.5).

3) Do search (the same Add/remove software) for "libstdc". It will find C++ libraries, different versions. Install latest ones in case they are not yet installed;

4) Do search (same place) for "GLIBC" - it will find a few libraries there. Install the latest ones in case they are not yet installed

That's it. Then go to terminal and do "sudo rpm -i" command for all three packages that you downloaded before. Here are the commands (you need to run these from the folder where you have dowloaded them):

;[root@localhost ~]# cd /folder_where_files_were_downloaded, example:
:cd /home/frank/Downloads/

*[root@localhost Downloads]# rpm -Uvh nxclient-3.4.0-5.i386.rpm
*[root@localhost Downloads]# rpm -Uvh nxnode-3.4.0-6.i386.rpm
*[root@localhost Downloads]# rpm -Uvh nxserver-3.4.0-8.i386.rpm

You need to install them in order: client, node, server.

It may complain something about permissions for CUPS that you may just ignore. Or if you want, you can follow the instructions the installer gives you, and fix permission problem and re-install. Keep in mind, that these three packages are easily removable thru Add/Remove interface in System Preferences.

==Ubuntu==

You are in luck! A chap named Shannon VanWagner created a script that makes the installation and configuration on Ubuntu 12.04 super easy. His page (including instructions on how to install manually) and the link for the script can be found at [http://www.humans-enabled.com/2012/05/how-to-install-freenx-on-ubuntu-1204.html FreeNX How to Install FreeNx on Ubuntu 12.04]

To Run Script:
# Download script to the Amahi Server
# Extract script from downloaded tar file
#Open terminal window, go to director with the script and type
{{Code|sudo sh heInstallFreeNX.sh}}

If the script runs successfully, it should return a message saying
'''Script Complete! Now you should be able to connect to this server using qtnx or the NX free client from nomachine.com.'''

=FreeNX Client Installation=

Last step. Download and install NX client software (not the same as above) from the same Nomachine's web site. You need to install client software on the machine that you want to access your HDA from. In my case it's a Windows based laptop - so I chose Windows version. Once installed, you can run it with default Key and default settings. Just choose Configure button, and on General tab, choose UNIX---Gnome for the desktop. No need to export/import Keys - can run with default installed keys. For added security, you can later change Keys as described in their knowledge base (article #AR01C00126).

When the gnome desktop loads, you will likely get a message that Gnome Power Manager crashed. Ignore it - everything works fine.

=Troubleshooting NX=

#The /etc/hosts file must contain an entry for your HDA which may not be there. If NX is failing to connect to your HDA, check /etc/hosts for an entry as follows: [IP address] [localhost.localdomain] [localhost alias]. This info can be easily entered from your gnome desktop: System > Administration > Network > Hosts Tab.
#The default security keys should match in the server and client, but that could be a reason for not connecting. Check the documentation on the NoMachine website for how to copy the key.
#There is a detailed server administration manual on the NoMachine website, but the information above is sufficient for an install with basic security.

[[Category:Apps]]

Adding a second hard drive to your HDA

2012-11-08T11:41:37Z

Carl Greenstreet: /* Manually setting up the disk mount order */

{{MessageBox|
backgroundcolor = #faa|
image =Warning.png|
heading =WARNING|
message = This is recommended only for advanced users, proceed with caution.}}
[[Adding_drives_to_your_HDA|Adding drives to your HDA]] is another howto on doing this, a bit shorter and less elaborate, which can be good for some people, specially a novice unfamiliar with doing any of this.

More hard drives can be added in your Amahi HDA for additional storage space.

We'll detail how to add such hard drives, and how to put them to good use.

=Important Notes=

* This is a how-to on adding additional drives to your HDA.
* Amahi cannot be held responsible for any data breakage or destruction arising from the use or misuse of this script. We provide it as a service in good will. You accept this automatically if you use the script.
* This page and script does not support GUID-partitioned drives (such as drives previously in a Mac or have GPT partition tables). You can find what your partition is like with <code>fdisk -l</code>

=Make sure your drive is detected by Fedora=

Open a Terminal, and type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 0 1em;">
ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"
</div>

Look for the line that matches the hard drive you added.

IDE and SATA hard drives will start with '''ata-''' and USB hard drives will start with '''usb-'''.<br/>
Look for your hard drive model and serial number.

Example:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
[gb@hda ~]$ ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"
ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V
ata-ST31000528AS_6VP08W65
ata-ST3750640A_3QD0LJN8
ata-ST3750640A_5QD27A57
ata-WDC_WD10EADS-00L5B1_WD-WCAU4C700358
usb-ST310003_33AS_9E1CA6FFFFFF-0:0
usb-ST375064_0A_2009031309E2-0:0
</div>

=Install prerequisites=

[[Open Terminal as root|In a Terminal, as root]], type the following (two) commands:

* Fedora
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
yum -y install pmount fuse fuse-libs ntfs-3g gparted util-linux-ng
</div>

* Ubuntu
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
sudo apt-get -y install gparted
</div>

Drives must be formatted as '''MBR''' not '''GUID/GPT''' for hda-diskmount to recognize the disk.

=Partition and format the hard drive=

This step is optional, and should only be executed if you want to delete the content of your new hard drive, or if the hard drive has not yet been formatted.

You should (unless you have a good reason not to) use GParted to partition and format your hard drive.<br/>
Not having X installed would qualify as a good reason! In such cases, either use SSH X11 Forwarding (Google that if you'd like to use this), or [[Adding_a_second_hard_drive_to_your_HDA#Using_cfdisk|use cfdisk]] from a [[Open Terminal as root|Terminal, as root]].

You'll probably want to create a single partition, and format it as ''ext3''.<br/>
Note that Windows can't read ext3 partitions, so if you want dual-boot Windows on your Amahi PC, or if you intend to connect this hard drive to a Windows computer later, you should format as NTFS instead, and you should do that on Windows before you connect the drive in your HDA.<br/>
Remember that using NTFS partitions on Linux will be slower that using ext3 partitions, so you should only use NTFS if you really need it.<br/>
How much slower: compare the blue bars (NTFS-3G) with the red bars (ext3) on [http://www.tuxera.com/products/tuxera-ntfs-commercial/performance/ this graph].

To know what device (/dev/sdX) you need to partition and format, use the following command, in a [[Open Terminal as root|Terminal, as root]]:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
ls -l /dev/disk/by-id/
</div>

Find the row corresponding to your hard drive, and look at the end of the line to identify the correct device to use.

Example:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><small>
[gb@hda ~]$ ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V -> ../../sda
lrwxrwxrwx 1 root root 10 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V-part1 -> ../../sda1
lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-ST31000528AS_6VP08W65 -> ../../sdb
</small>
</div>

In the above example, /dev/sdb would be what I would select in GParted (or use on the cfdisk command). sda in my primary hard drive, and sdb my second hard drive.

==Using GParted==
From the HDA desktop (or using VNC), [[Open Terminal as root]] and type '''gparted''' to launch the GParted application.

Select the device (/dev/sdX) that you found above.

In the above example, /dev/sdb would be what I would select in GParted.

There are many easy to follow guides online on how to use GParted. You should Google for one, to find one that seems clear to you.

[http://www.mepisguides.com/Mepis-6/Install/gparted/gparted-set-partition.html Here's one] that looks simple. Just use ext3 instead of fat32 in you follow that tutorial.

Note that gparted supports GUID-partitioned drives, however, these directions and script do not support it at the moment.

==Using cfdisk==
From a [[Open Terminal as root|terminal, as root]], type '''cfdisk /dev/sdX''' to launch the cfdisk application.

If you have a GUID-partitioned drive, cfdisk will complain. GUID partitions are not supported.

Make sure to replace /dev/sdX with the actual device (eg. /dev/sdb) that you found above.

If your hard drive contains existing partitions, select them one by one at the top (using up/down arrow keys), then select the '''[ Delete ]''' action (using the left/right arrow keys), then hit ENTER.

You should now only have Free Space listed at the top.<br/>
Select the '''[ New ]''' action, and accept the default (Primary, and size).

You should now have a single partition listed at the top, of type Linux.<br/>
Select the '''[ Write ]''' action, then '''[ Quit ]'''.

Now that you partitioned your drive, you need to format your newly created partition.<br/>
To format as EXT3, use this command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mkfs.ext3 -j /dev/sdX1
</div>

Replace ext3 with ext4 in the above command to format your partition as EXT4 instead of EXT3.

'''/dev/sdX1''' in the above command refers to the partition your created in cfdisk.<br/>
Go back in cfdisk, and check the ''Name'' column if you're unsure.<br/>
If you see ''sdb1'' in the name column, you should use '''/dev/sdb1''' in the above command.

==Partition over 2.1TB==
Here is a work around for drives with partitions over 2.1TB like the new 3TB drives.

Page: [[Partitions_Over_2.1_TB]]

=Mount the hard drive=

==Using hda-diskmount script==
A script is provided with Amahi that will look for unmounted partitions in your system, and mount any it finds.

[[Open Terminal as root|In a Terminal, as root]], type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
hda-diskmount
</div>

Example:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<small>
[root@hda ~]$ hda-diskmount
****************************************************************
Ignoring /dev/sda1 - already in /etc/fstab or mounted
****************************************************************
Mounted /dev/<strong style="color:green">sdb1</strong> as '<strong style="color:red">/var/hda/files/drives/sdb1</strong>' (read-write)
You may want your system to mount it every time you boot.
To do so, add this line VERY CAREFULLY to /etc/fstab and reboot:
<strong style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</strong>
****************************************************************
All Linux, Windows and Mac partitions on non-removable disks have been mounted
</small>
</div>

Do '''not''' edit /etc/fstab just yet. What you'll need to add there will depend on how you want to use the extra storage. More about that below.<br/>
Just note down the information in bold (green, red and blue). We'll use them below.

Note about ext4 in the blue line above: that doesn't necessarily mean your partition is formatted as ext4. It means the ext4 driver will be used to mount your partition. Since that driver is backward compatible, it can be safely used to mount ext2, ext3 and ext4 partitions.

If you get something like ''Disk /dev/dm-0 doesn't contain a valid partition table'' or ''mount: unknown file system type 'lvm2pv''' its because you have LVM's that 'fdisk' can not recognize (or something similar). It's nothing to worry about if you get that when executing the hda-diskmount script.

If you have changed the order of your installed hard drives, hda-diskmount may return the following message:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
Ignoring /dev/sda1 - already in /etc/fstab as /dev/sda1
This device appears to be commented out of your /etc/fstab. You will need to remove it from there for hda-diskmount to be able to mount it.
</div>

This might occur if you have made changes to the drive configuration order after you installed Amahi. If you want to stay with the reconfigured drive order, instructions on how to fix this are in the next section, Manually setting up the disk mount order.

==Manually setting up the disk mount order ==

1. First, get the UUID for each drive by opening a terminal and entering command

Ubuntu:
{{Code|Code=
gstreet@gstreet-MicroServer:~$ sudo blkid
[sudo] password for gstreet:
/dev/sda1: LABEL="Seagate-Alpha2TB" UUID="55d9333f-d801-425a-b2af-d65c5966d56f" TYPE="ext4"
/dev/sdb1: LABEL="Seagate-Beta2TB" UUID="5bd5498f-30c1-4780-948e-ca46656507d2" TYPE="ext4"
/dev/sdc1: LABEL="WD-Charlie2TB" UUID="a7337504-376a-4d36-9f7a-1a24c0f55fbd" TYPE="ext4"
/dev/sdd1: LABEL="WD-Delta2TB" UUID="8d881dcb-8de3-4621-b9bd-00025196868a" TYPE="ext4"
/dev/sde1: LABEL="root" UUID="4d6f8004-d190-4234-a03b-b68de988abf0" TYPE="ext4"
/dev/sde3: LABEL="home" UUID="d0531fa1-9311-4d53-b838-f35898adbd98" TYPE="ext4"
/dev/sde5: LABEL="swap" UUID="3c39206c-ba60-47ff-a1fe-f5821b2ab543" TYPE="swap"
}}

In this case, the user has four data drives (sda1, sdb1, sdc1, sdd1) and the Operating system assigned to a fifth drive, sde.

Take note of the UUID's for each drive. Easiest to cut and paste UUID's straight from the terminal - no typo's!

2. Then edit /etc/fstab to mount each drive - for novices, easiest to do this using a graphical editor. You might consider first making a copy called fstab.bak (use the "save as" command, close file and then gedit the original fstab again) so that you can recover the original fstab file if you make mistakes.

Ubuntu: {{Code|Code=
sudo gedit /etc/fstab
}}

3. Then carefully add the following line for each disk into the end of the fstab file. Make sure you paste in the right UUID, drive number and drive file system (ext4 in this case).

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
UUID=55d9333f-d801-425a-b2af-d65c5966d56f /var/hda/files/drives/drive1 ext4 defaults 1 2
</div>

It should look something like the following when lines are added for each of the five drives in this example. Note lines beginning with # are comments where the remainder of the line is ignored)

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
# Mounting Greyhole Drives for Drive Pool.
#
# Drive1 = Seagate-Alpha2TB in Microserver Bay 1 from left
UUID=55d9333f-d801-425a-b2af-d65c5966d56f /var/hda/files/drives/drive1 ext4 defaults 1 2
#
# Drive2 = Seagate-Beta2TB in Microserver Bay 2 from left
UUID=5bd5498f-30c1-4780-948e-ca46656507d2 /var/hda/files/drives/drive2 ext4 defaults 1 2
#
# Drive3 = WD-Charlie2TB in Microserver Bay 3 from left
UUID=a7337504-376a-4d36-9f7a-1a24c0f55fbd /var/hda/files/drives/drive3 ext4 defaults 1 2
#
# Drive4 = WD-Delta2TB in Microserver Bay 4 from left
UUID=8d881dcb-8de3-4621-b9bd-00025196868a /var/hda/files/drives/drive4 ext4 defaults 1 2
#
# Drive5 = 250GB OS Drive mounted in Optical Drive bay
UUID="4d6f8004-d190-4234-a03b-b68de988abf0 /var/hda/files/drives/drive5 ext4 defaults 1 2
#
#
</div>

Note that the hda-dismount command had already added lines to mount my OS drive which had two partitions (root or /, and home). Save file and close.

4) Save file and reboot machine.

5) Check that drives have successfully mounted in Amahi hda (Setup - Shares - Storage Pool)

In this case, if all drives mounted successfully, it should look like:

[[File:Gstreet_greyhole_pool.png|options|caption]]

==Test your hard drive==
Optionally, you can test your new drive for bad blocks.<br/>
Note that this step can take a ''long'' time to complete! You'll probably want to start it in the evening, to have it completed in the morning.

To do so, [[Open Terminal as root|in a Terminal, as root]], type the following command. Replace <strong style="color:green">sdb1</strong> with the (green) value you received from hda-diskmount.

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
e2fsck -cn /dev/<strong style="color:green">sdb1</strong>
</div>

You'll receive a warning that says "WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage. Do you really want to continue (y/n)?"<br/>
Answer ''yes''. The -cn option we're using can safely be used on mounted filesystems.

=Use the hard drive=

You have a choice here on how to use your new hard drive storage space. We'll offer some examples.

==Use the hard drive for all shares==

If you want all your shares to be on your new hard drive, here's how to do that.

First, you'll want to move all you previous shares data, if any, into your new drive.<br/>
You only need to do this next command if you have data that you care about in the /var/hda/files/* folders.<br/>
[[Open Terminal as root|In a Terminal, as root]], type the following command. Replace the path in red with the path you received when you ran hda-diskmount.
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mv /var/hda/files/* <strong style="color:red">/var/hda/files/drives/sdb1/</strong>
</div>
You'll get a warning about "cannot move `/var/hda/files/drives' to a subdirectory of itself"; that is fine, ignore that.

Next, you'll need to unmount your new hard drive, and remount it as /var/hda/files

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1/
</div>

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you (the blue one), and change the second value (the path).<br/>
Replace the second value with '''/var/hda/files'''.

hda-diskmount gave me:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
<span style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files/drives/sdb1</strong> ext4 defaults 1 2</span>
</div>

So I should add this instead:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files</strong> ext4 defaults 1 2
</div>

Make sure you do '''not''' change anything else from the blue line you received from hda-diskmount.<br/>
It might not be the same thing as the above example; you need to use the values you've received.

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
ls /var/hda/files/
</div>

That last command should show you the content of you new hard drive.

That's it. All your shares in /var/hda/files are now on your new hard drive.

==Use the hard drive for only some shares==

If you want only some of your shares to be on your new hard drive, here's how to do that.

First, you'll want to move your previous shares data, if any, into your new drive.<br/>
You only need to do this next command if you have data that you care about in the /var/hda/files/* folders (that you want on the new drive).<br/>
[[Open Terminal as root|In a Terminal, as root]], type the following command. Replace the path in red with the path you received when you ran hda-diskmount. Replace '''something''' with the name of the share you want to have on your new drive (the share should already exist).
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mv /var/hda/files/<strong>something</strong> <strong style="color:red">/var/hda/files/drives/sdb1/</strong>
</div>

Repeat with every share you want on your new drive.

Next, you'll need to make the mount permanent

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1<br/>
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you, and insert that.<br/>

So, following previous examples, I should add this:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span>
</div>

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
ls /var/hda/files/drives/sdb1
</div>

That last command should show you the content of you new hard drive.

Now, you need to update the location of the moved shares within Amahi. Go to your <strong>Amahi Dashboard</strong>, click on <strong>Setup</strong>, then <strong>Shares</strong>.

Click on one of the shares that you have moved. This will open a panel revealing the share settings. Click on the location (the bit that is shown with a dotted underline) and it will change to an edit box. Update the location to match the new share location.

For example, the original movies location was: <span style="color:red">/var/hda/files/movies</span><br/>
The new location might be: <span style="color:blue">/var/hda/files/drives/sdb1/movies</span>

Repeat for any other shares that you have moved. Check that you can access these shares from another machine within your network.

Finally, if you have any services that depend on the location of these shares, make sure they are configured to use the new share location. For example, if you have a DLNA server installed, check its configuration files to make sure that it can find any media folders that have been moved. Secondly, <em>check that all such services start correctly and behave as expected</em>. If the service doesn't start, it may be that it is testing for a specific location during the service startup. Check the startup files in <strong>/etc/init.d</strong> to see if this is the case.

That's it. Your share(s) are now on your new hard drive.

==Use the hard drive in your Greyhole storage pool==

If you want to add your new hard drive to your Greyhole storage pool, here's how to do that.

First, you'll need to make the mount permanent. [[Open Terminal as root|In a Terminal, as root]], type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you, and insert that.<br/>

So, following previous examples, I should add this:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span>
</div>

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
</div>

Finally, you'll need to configure Greyhole to select your new partition. To configure Greyhole, Advanced Settings must be enabled under [http://hda/setup?sub=settings&tab=setting Setup > Settings].

In the [http://hda/setup?sub=disk_pooling&tab=share Shares > Storage Pool page] of your Amahi dashboard, you'll see a list of mounted partitions, with checkboxes next to each, allowing you to include those partitions in your storage pool.

You should now have a new row in there, referring to /var/hda/files/drives/sdb1.

Select it (click the checkbox).

That's it. Your new hard drive just increased your Greyhole storage pool capacity.

Adding a second hard drive to your HDA

2012-11-08T11:38:48Z

Carl Greenstreet: /* Manually setting up the disk mount order */

{{MessageBox|
backgroundcolor = #faa|
image =Warning.png|
heading =WARNING|
message = This is recommended only for advanced users, proceed with caution.}}
[[Adding_drives_to_your_HDA|Adding drives to your HDA]] is another howto on doing this, a bit shorter and less elaborate, which can be good for some people, specially a novice unfamiliar with doing any of this.

More hard drives can be added in your Amahi HDA for additional storage space.

We'll detail how to add such hard drives, and how to put them to good use.

=Important Notes=

* This is a how-to on adding additional drives to your HDA.
* Amahi cannot be held responsible for any data breakage or destruction arising from the use or misuse of this script. We provide it as a service in good will. You accept this automatically if you use the script.
* This page and script does not support GUID-partitioned drives (such as drives previously in a Mac or have GPT partition tables). You can find what your partition is like with <code>fdisk -l</code>

=Make sure your drive is detected by Fedora=

Open a Terminal, and type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 0 1em;">
ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"
</div>

Look for the line that matches the hard drive you added.

IDE and SATA hard drives will start with '''ata-''' and USB hard drives will start with '''usb-'''.<br/>
Look for your hard drive model and serial number.

Example:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
[gb@hda ~]$ ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"
ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V
ata-ST31000528AS_6VP08W65
ata-ST3750640A_3QD0LJN8
ata-ST3750640A_5QD27A57
ata-WDC_WD10EADS-00L5B1_WD-WCAU4C700358
usb-ST310003_33AS_9E1CA6FFFFFF-0:0
usb-ST375064_0A_2009031309E2-0:0
</div>

=Install prerequisites=

[[Open Terminal as root|In a Terminal, as root]], type the following (two) commands:

* Fedora
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
yum -y install pmount fuse fuse-libs ntfs-3g gparted util-linux-ng
</div>

* Ubuntu
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
sudo apt-get -y install gparted
</div>

Drives must be formatted as '''MBR''' not '''GUID/GPT''' for hda-diskmount to recognize the disk.

=Partition and format the hard drive=

This step is optional, and should only be executed if you want to delete the content of your new hard drive, or if the hard drive has not yet been formatted.

You should (unless you have a good reason not to) use GParted to partition and format your hard drive.<br/>
Not having X installed would qualify as a good reason! In such cases, either use SSH X11 Forwarding (Google that if you'd like to use this), or [[Adding_a_second_hard_drive_to_your_HDA#Using_cfdisk|use cfdisk]] from a [[Open Terminal as root|Terminal, as root]].

You'll probably want to create a single partition, and format it as ''ext3''.<br/>
Note that Windows can't read ext3 partitions, so if you want dual-boot Windows on your Amahi PC, or if you intend to connect this hard drive to a Windows computer later, you should format as NTFS instead, and you should do that on Windows before you connect the drive in your HDA.<br/>
Remember that using NTFS partitions on Linux will be slower that using ext3 partitions, so you should only use NTFS if you really need it.<br/>
How much slower: compare the blue bars (NTFS-3G) with the red bars (ext3) on [http://www.tuxera.com/products/tuxera-ntfs-commercial/performance/ this graph].

To know what device (/dev/sdX) you need to partition and format, use the following command, in a [[Open Terminal as root|Terminal, as root]]:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
ls -l /dev/disk/by-id/
</div>

Find the row corresponding to your hard drive, and look at the end of the line to identify the correct device to use.

Example:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><small>
[gb@hda ~]$ ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V -> ../../sda
lrwxrwxrwx 1 root root 10 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V-part1 -> ../../sda1
lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-ST31000528AS_6VP08W65 -> ../../sdb
</small>
</div>

In the above example, /dev/sdb would be what I would select in GParted (or use on the cfdisk command). sda in my primary hard drive, and sdb my second hard drive.

==Using GParted==
From the HDA desktop (or using VNC), [[Open Terminal as root]] and type '''gparted''' to launch the GParted application.

Select the device (/dev/sdX) that you found above.

In the above example, /dev/sdb would be what I would select in GParted.

There are many easy to follow guides online on how to use GParted. You should Google for one, to find one that seems clear to you.

[http://www.mepisguides.com/Mepis-6/Install/gparted/gparted-set-partition.html Here's one] that looks simple. Just use ext3 instead of fat32 in you follow that tutorial.

Note that gparted supports GUID-partitioned drives, however, these directions and script do not support it at the moment.

==Using cfdisk==
From a [[Open Terminal as root|terminal, as root]], type '''cfdisk /dev/sdX''' to launch the cfdisk application.

If you have a GUID-partitioned drive, cfdisk will complain. GUID partitions are not supported.

Make sure to replace /dev/sdX with the actual device (eg. /dev/sdb) that you found above.

If your hard drive contains existing partitions, select them one by one at the top (using up/down arrow keys), then select the '''[ Delete ]''' action (using the left/right arrow keys), then hit ENTER.

You should now only have Free Space listed at the top.<br/>
Select the '''[ New ]''' action, and accept the default (Primary, and size).

You should now have a single partition listed at the top, of type Linux.<br/>
Select the '''[ Write ]''' action, then '''[ Quit ]'''.

Now that you partitioned your drive, you need to format your newly created partition.<br/>
To format as EXT3, use this command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mkfs.ext3 -j /dev/sdX1
</div>

Replace ext3 with ext4 in the above command to format your partition as EXT4 instead of EXT3.

'''/dev/sdX1''' in the above command refers to the partition your created in cfdisk.<br/>
Go back in cfdisk, and check the ''Name'' column if you're unsure.<br/>
If you see ''sdb1'' in the name column, you should use '''/dev/sdb1''' in the above command.

==Partition over 2.1TB==
Here is a work around for drives with partitions over 2.1TB like the new 3TB drives.

Page: [[Partitions_Over_2.1_TB]]

=Mount the hard drive=

==Using hda-diskmount script==
A script is provided with Amahi that will look for unmounted partitions in your system, and mount any it finds.

[[Open Terminal as root|In a Terminal, as root]], type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
hda-diskmount
</div>

Example:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<small>
[root@hda ~]$ hda-diskmount
****************************************************************
Ignoring /dev/sda1 - already in /etc/fstab or mounted
****************************************************************
Mounted /dev/<strong style="color:green">sdb1</strong> as '<strong style="color:red">/var/hda/files/drives/sdb1</strong>' (read-write)
You may want your system to mount it every time you boot.
To do so, add this line VERY CAREFULLY to /etc/fstab and reboot:
<strong style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</strong>
****************************************************************
All Linux, Windows and Mac partitions on non-removable disks have been mounted
</small>
</div>

Do '''not''' edit /etc/fstab just yet. What you'll need to add there will depend on how you want to use the extra storage. More about that below.<br/>
Just note down the information in bold (green, red and blue). We'll use them below.

Note about ext4 in the blue line above: that doesn't necessarily mean your partition is formatted as ext4. It means the ext4 driver will be used to mount your partition. Since that driver is backward compatible, it can be safely used to mount ext2, ext3 and ext4 partitions.

If you get something like ''Disk /dev/dm-0 doesn't contain a valid partition table'' or ''mount: unknown file system type 'lvm2pv''' its because you have LVM's that 'fdisk' can not recognize (or something similar). It's nothing to worry about if you get that when executing the hda-diskmount script.

If you have changed the order of your installed hard drives, hda-diskmount may return the following message:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
Ignoring /dev/sda1 - already in /etc/fstab as /dev/sda1
This device appears to be commented out of your /etc/fstab. You will need to remove it from there for hda-diskmount to be able to mount it.
</div>

This might occur if you have made changes to the drive configuration order after you installed Amahi. If you want to stay with the reconfigured drive order, instructions on how to fix this are in the next section, Manually setting up the disk mount order.

==Manually setting up the disk mount order ==

1. First, get the UUID for each drive by opening a terminal and entering command

Ubuntu:
{{Code|Code=
gstreet@gstreet-MicroServer:~$ sudo blkid
[sudo] password for gstreet:
/dev/sda1: LABEL="Seagate-Alpha2TB" UUID="55d9333f-d801-425a-b2af-d65c5966d56f" TYPE="ext4"
/dev/sdb1: LABEL="Seagate-Beta2TB" UUID="5bd5498f-30c1-4780-948e-ca46656507d2" TYPE="ext4"
/dev/sdc1: LABEL="WD-Charlie2TB" UUID="a7337504-376a-4d36-9f7a-1a24c0f55fbd" TYPE="ext4"
/dev/sdd1: LABEL="WD-Delta2TB" UUID="8d881dcb-8de3-4621-b9bd-00025196868a" TYPE="ext4"
/dev/sde1: LABEL="root" UUID="4d6f8004-d190-4234-a03b-b68de988abf0" TYPE="ext4"
/dev/sde3: LABEL="home" UUID="d0531fa1-9311-4d53-b838-f35898adbd98" TYPE="ext4"
/dev/sde5: LABEL="swap" UUID="3c39206c-ba60-47ff-a1fe-f5821b2ab543" TYPE="swap"
}}

In this case, the user has four data drives (sda1, sdb1, sdc1, sdd1) and the Operating system assigned to a fifth drive, sde.

Take note of the UUID's for each drive. Easiest to cut and paste UUID's straight from the terminal - no typo's!

2. Then edit /etc/fstab to mount each drive - for novices, easiest to do this using a graphical editor. You might consider first making a copy called fstab.bak (use the "save as" command, close file and then gedit the original fstab again) so that you can recover the original fstab file if you make mistakes.

Ubuntu: {{Code|Code=
sudo gedit /etc/fstab
}}

3. Then carefully add the following line for each disk into the end of the fstab file

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
UUID=55d9333f-d801-425a-b2af-d65c5966d56f /var/hda/files/drives/drive1 ext4 defaults 1 2
</div>

It should look something like the following when lines are added for each of the five drives in this example. Make sure you paste in the right UUID, drive number and drive file system (ext4 in this case). Note lines beginning with # are comments where the remainder of the line is ignored)

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
# Mounting Greyhole Drives for Drive Pool.
#
# Drive1 = Seagate-Alpha2TB in Microserver Bay 1 from left
UUID=55d9333f-d801-425a-b2af-d65c5966d56f /var/hda/files/drives/drive1 ext4 defaults 1 2
#
# Drive2 = Seagate-Beta2TB in Microserver Bay 2 from left
UUID=5bd5498f-30c1-4780-948e-ca46656507d2 /var/hda/files/drives/drive2 ext4 defaults 1 2
#
# Drive3 = WD-Charlie2TB in Microserver Bay 3 from left
UUID=a7337504-376a-4d36-9f7a-1a24c0f55fbd /var/hda/files/drives/drive3 ext4 defaults 1 2
#
# Drive4 = WD-Delta2TB in Microserver Bay 4 from left
UUID=8d881dcb-8de3-4621-b9bd-00025196868a /var/hda/files/drives/drive4 ext4 defaults 1 2
#
# Drive5 = 250GB OS Drive mounted in Optical Drive bay
UUID="4d6f8004-d190-4234-a03b-b68de988abf0 /var/hda/files/drives/drive5 ext4 defaults 1 2
#
#
</div>

Note that the hda-dismount command had already added lines to mount my OS drive which had two partitions (root or /, and home). Save file and close.

4) Save file and reboot machine.

5) Check drives in Amahi hda (Setup - Shares - Storage Pool)

In this case, if all drives mounted successfully, it should look like:

[[File:Gstreet_greyhole_pool.png|options|caption]]

==Test your hard drive==
Optionally, you can test your new drive for bad blocks.<br/>
Note that this step can take a ''long'' time to complete! You'll probably want to start it in the evening, to have it completed in the morning.

To do so, [[Open Terminal as root|in a Terminal, as root]], type the following command. Replace <strong style="color:green">sdb1</strong> with the (green) value you received from hda-diskmount.

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
e2fsck -cn /dev/<strong style="color:green">sdb1</strong>
</div>

You'll receive a warning that says "WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage. Do you really want to continue (y/n)?"<br/>
Answer ''yes''. The -cn option we're using can safely be used on mounted filesystems.

=Use the hard drive=

You have a choice here on how to use your new hard drive storage space. We'll offer some examples.

==Use the hard drive for all shares==

If you want all your shares to be on your new hard drive, here's how to do that.

First, you'll want to move all you previous shares data, if any, into your new drive.<br/>
You only need to do this next command if you have data that you care about in the /var/hda/files/* folders.<br/>
[[Open Terminal as root|In a Terminal, as root]], type the following command. Replace the path in red with the path you received when you ran hda-diskmount.
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mv /var/hda/files/* <strong style="color:red">/var/hda/files/drives/sdb1/</strong>
</div>
You'll get a warning about "cannot move `/var/hda/files/drives' to a subdirectory of itself"; that is fine, ignore that.

Next, you'll need to unmount your new hard drive, and remount it as /var/hda/files

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1/
</div>

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you (the blue one), and change the second value (the path).<br/>
Replace the second value with '''/var/hda/files'''.

hda-diskmount gave me:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
<span style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files/drives/sdb1</strong> ext4 defaults 1 2</span>
</div>

So I should add this instead:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files</strong> ext4 defaults 1 2
</div>

Make sure you do '''not''' change anything else from the blue line you received from hda-diskmount.<br/>
It might not be the same thing as the above example; you need to use the values you've received.

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
ls /var/hda/files/
</div>

That last command should show you the content of you new hard drive.

That's it. All your shares in /var/hda/files are now on your new hard drive.

==Use the hard drive for only some shares==

If you want only some of your shares to be on your new hard drive, here's how to do that.

First, you'll want to move your previous shares data, if any, into your new drive.<br/>
You only need to do this next command if you have data that you care about in the /var/hda/files/* folders (that you want on the new drive).<br/>
[[Open Terminal as root|In a Terminal, as root]], type the following command. Replace the path in red with the path you received when you ran hda-diskmount. Replace '''something''' with the name of the share you want to have on your new drive (the share should already exist).
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mv /var/hda/files/<strong>something</strong> <strong style="color:red">/var/hda/files/drives/sdb1/</strong>
</div>

Repeat with every share you want on your new drive.

Next, you'll need to make the mount permanent

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1<br/>
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you, and insert that.<br/>

So, following previous examples, I should add this:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span>
</div>

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
ls /var/hda/files/drives/sdb1
</div>

That last command should show you the content of you new hard drive.

Now, you need to update the location of the moved shares within Amahi. Go to your <strong>Amahi Dashboard</strong>, click on <strong>Setup</strong>, then <strong>Shares</strong>.

Click on one of the shares that you have moved. This will open a panel revealing the share settings. Click on the location (the bit that is shown with a dotted underline) and it will change to an edit box. Update the location to match the new share location.

For example, the original movies location was: <span style="color:red">/var/hda/files/movies</span><br/>
The new location might be: <span style="color:blue">/var/hda/files/drives/sdb1/movies</span>

Repeat for any other shares that you have moved. Check that you can access these shares from another machine within your network.

Finally, if you have any services that depend on the location of these shares, make sure they are configured to use the new share location. For example, if you have a DLNA server installed, check its configuration files to make sure that it can find any media folders that have been moved. Secondly, <em>check that all such services start correctly and behave as expected</em>. If the service doesn't start, it may be that it is testing for a specific location during the service startup. Check the startup files in <strong>/etc/init.d</strong> to see if this is the case.

That's it. Your share(s) are now on your new hard drive.

==Use the hard drive in your Greyhole storage pool==

If you want to add your new hard drive to your Greyhole storage pool, here's how to do that.

First, you'll need to make the mount permanent. [[Open Terminal as root|In a Terminal, as root]], type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you, and insert that.<br/>

So, following previous examples, I should add this:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span>
</div>

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
</div>

Finally, you'll need to configure Greyhole to select your new partition. To configure Greyhole, Advanced Settings must be enabled under [http://hda/setup?sub=settings&tab=setting Setup > Settings].

In the [http://hda/setup?sub=disk_pooling&tab=share Shares > Storage Pool page] of your Amahi dashboard, you'll see a list of mounted partitions, with checkboxes next to each, allowing you to include those partitions in your storage pool.

You should now have a new row in there, referring to /var/hda/files/drives/sdb1.

Select it (click the checkbox).

That's it. Your new hard drive just increased your Greyhole storage pool capacity.

File:Gstreet greyhole pool.png

2012-11-08T11:36:21Z

Carl Greenstreet: screen capture of greyhole pool in Amahi settings to illustrate outcomes of manually mounting drives

screen capture of greyhole pool in Amahi settings to illustrate outcomes of manually mounting drives

Adding a second hard drive to your HDA

2012-11-08T11:21:18Z

Carl Greenstreet: /* Manually setting up the disk mount order */

{{MessageBox|
backgroundcolor = #faa|
image =Warning.png|
heading =WARNING|
message = This is recommended only for advanced users, proceed with caution.}}
[[Adding_drives_to_your_HDA|Adding drives to your HDA]] is another howto on doing this, a bit shorter and less elaborate, which can be good for some people, specially a novice unfamiliar with doing any of this.

More hard drives can be added in your Amahi HDA for additional storage space.

We'll detail how to add such hard drives, and how to put them to good use.

=Important Notes=

* This is a how-to on adding additional drives to your HDA.
* Amahi cannot be held responsible for any data breakage or destruction arising from the use or misuse of this script. We provide it as a service in good will. You accept this automatically if you use the script.
* This page and script does not support GUID-partitioned drives (such as drives previously in a Mac or have GPT partition tables). You can find what your partition is like with <code>fdisk -l</code>

=Make sure your drive is detected by Fedora=

Open a Terminal, and type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 0 1em;">
ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"
</div>

Look for the line that matches the hard drive you added.

IDE and SATA hard drives will start with '''ata-''' and USB hard drives will start with '''usb-'''.<br/>
Look for your hard drive model and serial number.

Example:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
[gb@hda ~]$ ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"
ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V
ata-ST31000528AS_6VP08W65
ata-ST3750640A_3QD0LJN8
ata-ST3750640A_5QD27A57
ata-WDC_WD10EADS-00L5B1_WD-WCAU4C700358
usb-ST310003_33AS_9E1CA6FFFFFF-0:0
usb-ST375064_0A_2009031309E2-0:0
</div>

=Install prerequisites=

[[Open Terminal as root|In a Terminal, as root]], type the following (two) commands:

* Fedora
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
yum -y install pmount fuse fuse-libs ntfs-3g gparted util-linux-ng
</div>

* Ubuntu
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
sudo apt-get -y install gparted
</div>

Drives must be formatted as '''MBR''' not '''GUID/GPT''' for hda-diskmount to recognize the disk.

=Partition and format the hard drive=

This step is optional, and should only be executed if you want to delete the content of your new hard drive, or if the hard drive has not yet been formatted.

You should (unless you have a good reason not to) use GParted to partition and format your hard drive.<br/>
Not having X installed would qualify as a good reason! In such cases, either use SSH X11 Forwarding (Google that if you'd like to use this), or [[Adding_a_second_hard_drive_to_your_HDA#Using_cfdisk|use cfdisk]] from a [[Open Terminal as root|Terminal, as root]].

You'll probably want to create a single partition, and format it as ''ext3''.<br/>
Note that Windows can't read ext3 partitions, so if you want dual-boot Windows on your Amahi PC, or if you intend to connect this hard drive to a Windows computer later, you should format as NTFS instead, and you should do that on Windows before you connect the drive in your HDA.<br/>
Remember that using NTFS partitions on Linux will be slower that using ext3 partitions, so you should only use NTFS if you really need it.<br/>
How much slower: compare the blue bars (NTFS-3G) with the red bars (ext3) on [http://www.tuxera.com/products/tuxera-ntfs-commercial/performance/ this graph].

To know what device (/dev/sdX) you need to partition and format, use the following command, in a [[Open Terminal as root|Terminal, as root]]:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
ls -l /dev/disk/by-id/
</div>

Find the row corresponding to your hard drive, and look at the end of the line to identify the correct device to use.

Example:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><small>
[gb@hda ~]$ ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V -> ../../sda
lrwxrwxrwx 1 root root 10 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V-part1 -> ../../sda1
lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-ST31000528AS_6VP08W65 -> ../../sdb
</small>
</div>

In the above example, /dev/sdb would be what I would select in GParted (or use on the cfdisk command). sda in my primary hard drive, and sdb my second hard drive.

==Using GParted==
From the HDA desktop (or using VNC), [[Open Terminal as root]] and type '''gparted''' to launch the GParted application.

Select the device (/dev/sdX) that you found above.

In the above example, /dev/sdb would be what I would select in GParted.

There are many easy to follow guides online on how to use GParted. You should Google for one, to find one that seems clear to you.

[http://www.mepisguides.com/Mepis-6/Install/gparted/gparted-set-partition.html Here's one] that looks simple. Just use ext3 instead of fat32 in you follow that tutorial.

Note that gparted supports GUID-partitioned drives, however, these directions and script do not support it at the moment.

==Using cfdisk==
From a [[Open Terminal as root|terminal, as root]], type '''cfdisk /dev/sdX''' to launch the cfdisk application.

If you have a GUID-partitioned drive, cfdisk will complain. GUID partitions are not supported.

Make sure to replace /dev/sdX with the actual device (eg. /dev/sdb) that you found above.

If your hard drive contains existing partitions, select them one by one at the top (using up/down arrow keys), then select the '''[ Delete ]''' action (using the left/right arrow keys), then hit ENTER.

You should now only have Free Space listed at the top.<br/>
Select the '''[ New ]''' action, and accept the default (Primary, and size).

You should now have a single partition listed at the top, of type Linux.<br/>
Select the '''[ Write ]''' action, then '''[ Quit ]'''.

Now that you partitioned your drive, you need to format your newly created partition.<br/>
To format as EXT3, use this command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mkfs.ext3 -j /dev/sdX1
</div>

Replace ext3 with ext4 in the above command to format your partition as EXT4 instead of EXT3.

'''/dev/sdX1''' in the above command refers to the partition your created in cfdisk.<br/>
Go back in cfdisk, and check the ''Name'' column if you're unsure.<br/>
If you see ''sdb1'' in the name column, you should use '''/dev/sdb1''' in the above command.

==Partition over 2.1TB==
Here is a work around for drives with partitions over 2.1TB like the new 3TB drives.

Page: [[Partitions_Over_2.1_TB]]

=Mount the hard drive=

==Using hda-diskmount script==
A script is provided with Amahi that will look for unmounted partitions in your system, and mount any it finds.

[[Open Terminal as root|In a Terminal, as root]], type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
hda-diskmount
</div>

Example:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<small>
[root@hda ~]$ hda-diskmount
****************************************************************
Ignoring /dev/sda1 - already in /etc/fstab or mounted
****************************************************************
Mounted /dev/<strong style="color:green">sdb1</strong> as '<strong style="color:red">/var/hda/files/drives/sdb1</strong>' (read-write)
You may want your system to mount it every time you boot.
To do so, add this line VERY CAREFULLY to /etc/fstab and reboot:
<strong style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</strong>
****************************************************************
All Linux, Windows and Mac partitions on non-removable disks have been mounted
</small>
</div>

Do '''not''' edit /etc/fstab just yet. What you'll need to add there will depend on how you want to use the extra storage. More about that below.<br/>
Just note down the information in bold (green, red and blue). We'll use them below.

Note about ext4 in the blue line above: that doesn't necessarily mean your partition is formatted as ext4. It means the ext4 driver will be used to mount your partition. Since that driver is backward compatible, it can be safely used to mount ext2, ext3 and ext4 partitions.

If you get something like ''Disk /dev/dm-0 doesn't contain a valid partition table'' or ''mount: unknown file system type 'lvm2pv''' its because you have LVM's that 'fdisk' can not recognize (or something similar). It's nothing to worry about if you get that when executing the hda-diskmount script.

If you have changed the order of your installed hard drives, hda-diskmount may return the following message:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
Ignoring /dev/sda1 - already in /etc/fstab as /dev/sda1
This device appears to be commented out of your /etc/fstab. You will need to remove it from there for hda-diskmount to be able to mount it.
</div>

This might occur if you have made changes to the drive configuration order after you installed Amahi. If you want to stay with the reconfigured drive order, instructions on how to fix this are in the next section, Manually setting up the disk mount order.

==Manually setting up the disk mount order ==

1. First, get the UUID for each drive by opening a terminal and entering command

Ubuntu:
{{Code|Code=
gstreet@gstreet-MicroServer:~$ sudo blkid
[sudo] password for gstreet:
/dev/sda1: LABEL="Seagate-Alpha2TB" UUID="55d9333f-d801-425a-b2af-d65c5966d56f" TYPE="ext4"
/dev/sdb1: LABEL="Seagate-Beta2TB" UUID="5bd5498f-30c1-4780-948e-ca46656507d2" TYPE="ext4"
/dev/sdc1: LABEL="WD-Charlie2TB" UUID="a7337504-376a-4d36-9f7a-1a24c0f55fbd" TYPE="ext4"
/dev/sdd1: LABEL="WD-Delta2TB" UUID="8d881dcb-8de3-4621-b9bd-00025196868a" TYPE="ext4"
/dev/sde1: LABEL="root" UUID="4d6f8004-d190-4234-a03b-b68de988abf0" TYPE="ext4"
/dev/sde3: LABEL="home" UUID="d0531fa1-9311-4d53-b838-f35898adbd98" TYPE="ext4"
/dev/sde5: LABEL="swap" UUID="3c39206c-ba60-47ff-a1fe-f5821b2ab543" TYPE="swap"
}}

In this case, the user has four data drives (sda1, sdb1, sdc1, sdd1) and the Operating system assigned to a fifth drive, sde.

Take note of the UUID's for each drive. Easiest to cut and paste UUID's straight from the terminal - no typo's!

2. Then edit /etc/fstab to mount each drive - for novices, easiest to do this using a graphical editor. You might consider first making a copy called fstab.bak (use the "save as" command, close file and then gedit the original fstab again) so that you can recover the original fstab file if you make mistakes.

Ubuntu: {{Code|Code=
sudo gedit /etc/fstab
}}

3. Then carefully add the following line for each disk into the end of the fstab file

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
UUID=55d9333f-d801-425a-b2af-d65c5966d56f /var/hda/files/drives/drive1 ext4 defaults 1 2
</div>

It should look something like the following when lines are added for each of the five drives in this example. Make sure you paste in the right UUID, drive number and drive file system (ext4 in this case). Note lines beginning with # are comments where the remainder of the line is ignored)

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
# Mounting Greyhole Drives for Drive Pool.
#
# Drive1 = Seagate-Alpha2TB in Microserver Bay 1 from left
UUID=55d9333f-d801-425a-b2af-d65c5966d56f /var/hda/files/drives/drive1 ext4 defaults 1 2
#
# Drive2 = Seagate-Beta2TB in Microserver Bay 2 from left
UUID=5bd5498f-30c1-4780-948e-ca46656507d2 /var/hda/files/drives/drive2 ext4 defaults 1 2
#
# Drive3 = WD-Charlie2TB in Microserver Bay 3 from left
UUID=a7337504-376a-4d36-9f7a-1a24c0f55fbd /var/hda/files/drives/drive3 ext4 defaults 1 2
#
# Drive4 = WD-Delta2TB in Microserver Bay 4 from left
UUID=8d881dcb-8de3-4621-b9bd-00025196868a /var/hda/files/drives/drive4 ext4 defaults 1 2
#
# Drive5 = 250GB OS Drive mounted in Optical Drive bay
UUID="4d6f8004-d190-4234-a03b-b68de988abf0 /var/hda/files/drives/drive5 ext4 defaults 1 2
#
#
</div>

Note that the hda-dismount command had already added lines to mount my OS drive which had two partitions (root or /, and home). Save file and close.

4) Save file and reboot machine.

5) Check drives in Amahi hda (Setup - Shares - Storage Pool)

In my case looked like
[img]https://docs.google.com/viewer?pid=explorer&srcid=0B4db0S5lBIq8enc1M0pJM3R1Mzg&docid=1b9781c1bebebe893591963b49cd0ab8%7C714e2385b5a30391311cd1211c8e3b8b&a=bi&pagenumber=1&w=800[/img]

==Test your hard drive==
Optionally, you can test your new drive for bad blocks.<br/>
Note that this step can take a ''long'' time to complete! You'll probably want to start it in the evening, to have it completed in the morning.

To do so, [[Open Terminal as root|in a Terminal, as root]], type the following command. Replace <strong style="color:green">sdb1</strong> with the (green) value you received from hda-diskmount.

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
e2fsck -cn /dev/<strong style="color:green">sdb1</strong>
</div>

You'll receive a warning that says "WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage. Do you really want to continue (y/n)?"<br/>
Answer ''yes''. The -cn option we're using can safely be used on mounted filesystems.

=Use the hard drive=

You have a choice here on how to use your new hard drive storage space. We'll offer some examples.

==Use the hard drive for all shares==

If you want all your shares to be on your new hard drive, here's how to do that.

First, you'll want to move all you previous shares data, if any, into your new drive.<br/>
You only need to do this next command if you have data that you care about in the /var/hda/files/* folders.<br/>
[[Open Terminal as root|In a Terminal, as root]], type the following command. Replace the path in red with the path you received when you ran hda-diskmount.
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mv /var/hda/files/* <strong style="color:red">/var/hda/files/drives/sdb1/</strong>
</div>
You'll get a warning about "cannot move `/var/hda/files/drives' to a subdirectory of itself"; that is fine, ignore that.

Next, you'll need to unmount your new hard drive, and remount it as /var/hda/files

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1/
</div>

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you (the blue one), and change the second value (the path).<br/>
Replace the second value with '''/var/hda/files'''.

hda-diskmount gave me:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
<span style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files/drives/sdb1</strong> ext4 defaults 1 2</span>
</div>

So I should add this instead:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files</strong> ext4 defaults 1 2
</div>

Make sure you do '''not''' change anything else from the blue line you received from hda-diskmount.<br/>
It might not be the same thing as the above example; you need to use the values you've received.

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
ls /var/hda/files/
</div>

That last command should show you the content of you new hard drive.

That's it. All your shares in /var/hda/files are now on your new hard drive.

==Use the hard drive for only some shares==

If you want only some of your shares to be on your new hard drive, here's how to do that.

First, you'll want to move your previous shares data, if any, into your new drive.<br/>
You only need to do this next command if you have data that you care about in the /var/hda/files/* folders (that you want on the new drive).<br/>
[[Open Terminal as root|In a Terminal, as root]], type the following command. Replace the path in red with the path you received when you ran hda-diskmount. Replace '''something''' with the name of the share you want to have on your new drive (the share should already exist).
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mv /var/hda/files/<strong>something</strong> <strong style="color:red">/var/hda/files/drives/sdb1/</strong>
</div>

Repeat with every share you want on your new drive.

Next, you'll need to make the mount permanent

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1<br/>
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you, and insert that.<br/>

So, following previous examples, I should add this:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span>
</div>

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
ls /var/hda/files/drives/sdb1
</div>

That last command should show you the content of you new hard drive.

Now, you need to update the location of the moved shares within Amahi. Go to your <strong>Amahi Dashboard</strong>, click on <strong>Setup</strong>, then <strong>Shares</strong>.

Click on one of the shares that you have moved. This will open a panel revealing the share settings. Click on the location (the bit that is shown with a dotted underline) and it will change to an edit box. Update the location to match the new share location.

For example, the original movies location was: <span style="color:red">/var/hda/files/movies</span><br/>
The new location might be: <span style="color:blue">/var/hda/files/drives/sdb1/movies</span>

Repeat for any other shares that you have moved. Check that you can access these shares from another machine within your network.

Finally, if you have any services that depend on the location of these shares, make sure they are configured to use the new share location. For example, if you have a DLNA server installed, check its configuration files to make sure that it can find any media folders that have been moved. Secondly, <em>check that all such services start correctly and behave as expected</em>. If the service doesn't start, it may be that it is testing for a specific location during the service startup. Check the startup files in <strong>/etc/init.d</strong> to see if this is the case.

That's it. Your share(s) are now on your new hard drive.

==Use the hard drive in your Greyhole storage pool==

If you want to add your new hard drive to your Greyhole storage pool, here's how to do that.

First, you'll need to make the mount permanent. [[Open Terminal as root|In a Terminal, as root]], type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you, and insert that.<br/>

So, following previous examples, I should add this:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span>
</div>

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
</div>

Finally, you'll need to configure Greyhole to select your new partition. To configure Greyhole, Advanced Settings must be enabled under [http://hda/setup?sub=settings&tab=setting Setup > Settings].

In the [http://hda/setup?sub=disk_pooling&tab=share Shares > Storage Pool page] of your Amahi dashboard, you'll see a list of mounted partitions, with checkboxes next to each, allowing you to include those partitions in your storage pool.

You should now have a new row in there, referring to /var/hda/files/drives/sdb1.

Select it (click the checkbox).

That's it. Your new hard drive just increased your Greyhole storage pool capacity.

Adding a second hard drive to your HDA

2012-11-08T11:17:36Z

Carl Greenstreet:

{{MessageBox|
backgroundcolor = #faa|
image =Warning.png|
heading =WARNING|
message = This is recommended only for advanced users, proceed with caution.}}
[[Adding_drives_to_your_HDA|Adding drives to your HDA]] is another howto on doing this, a bit shorter and less elaborate, which can be good for some people, specially a novice unfamiliar with doing any of this.

More hard drives can be added in your Amahi HDA for additional storage space.

We'll detail how to add such hard drives, and how to put them to good use.

=Important Notes=

* This is a how-to on adding additional drives to your HDA.
* Amahi cannot be held responsible for any data breakage or destruction arising from the use or misuse of this script. We provide it as a service in good will. You accept this automatically if you use the script.
* This page and script does not support GUID-partitioned drives (such as drives previously in a Mac or have GPT partition tables). You can find what your partition is like with <code>fdisk -l</code>

=Make sure your drive is detected by Fedora=

Open a Terminal, and type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 0 1em;">
ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"
</div>

Look for the line that matches the hard drive you added.

IDE and SATA hard drives will start with '''ata-''' and USB hard drives will start with '''usb-'''.<br/>
Look for your hard drive model and serial number.

Example:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
[gb@hda ~]$ ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"
ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V
ata-ST31000528AS_6VP08W65
ata-ST3750640A_3QD0LJN8
ata-ST3750640A_5QD27A57
ata-WDC_WD10EADS-00L5B1_WD-WCAU4C700358
usb-ST310003_33AS_9E1CA6FFFFFF-0:0
usb-ST375064_0A_2009031309E2-0:0
</div>

=Install prerequisites=

[[Open Terminal as root|In a Terminal, as root]], type the following (two) commands:

* Fedora
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
yum -y install pmount fuse fuse-libs ntfs-3g gparted util-linux-ng
</div>

* Ubuntu
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
sudo apt-get -y install gparted
</div>

Drives must be formatted as '''MBR''' not '''GUID/GPT''' for hda-diskmount to recognize the disk.

=Partition and format the hard drive=

This step is optional, and should only be executed if you want to delete the content of your new hard drive, or if the hard drive has not yet been formatted.

You should (unless you have a good reason not to) use GParted to partition and format your hard drive.<br/>
Not having X installed would qualify as a good reason! In such cases, either use SSH X11 Forwarding (Google that if you'd like to use this), or [[Adding_a_second_hard_drive_to_your_HDA#Using_cfdisk|use cfdisk]] from a [[Open Terminal as root|Terminal, as root]].

You'll probably want to create a single partition, and format it as ''ext3''.<br/>
Note that Windows can't read ext3 partitions, so if you want dual-boot Windows on your Amahi PC, or if you intend to connect this hard drive to a Windows computer later, you should format as NTFS instead, and you should do that on Windows before you connect the drive in your HDA.<br/>
Remember that using NTFS partitions on Linux will be slower that using ext3 partitions, so you should only use NTFS if you really need it.<br/>
How much slower: compare the blue bars (NTFS-3G) with the red bars (ext3) on [http://www.tuxera.com/products/tuxera-ntfs-commercial/performance/ this graph].

To know what device (/dev/sdX) you need to partition and format, use the following command, in a [[Open Terminal as root|Terminal, as root]]:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
ls -l /dev/disk/by-id/
</div>

Find the row corresponding to your hard drive, and look at the end of the line to identify the correct device to use.

Example:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><small>
[gb@hda ~]$ ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V -> ../../sda
lrwxrwxrwx 1 root root 10 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V-part1 -> ../../sda1
lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-ST31000528AS_6VP08W65 -> ../../sdb
</small>
</div>

In the above example, /dev/sdb would be what I would select in GParted (or use on the cfdisk command). sda in my primary hard drive, and sdb my second hard drive.

==Using GParted==
From the HDA desktop (or using VNC), [[Open Terminal as root]] and type '''gparted''' to launch the GParted application.

Select the device (/dev/sdX) that you found above.

In the above example, /dev/sdb would be what I would select in GParted.

There are many easy to follow guides online on how to use GParted. You should Google for one, to find one that seems clear to you.

[http://www.mepisguides.com/Mepis-6/Install/gparted/gparted-set-partition.html Here's one] that looks simple. Just use ext3 instead of fat32 in you follow that tutorial.

Note that gparted supports GUID-partitioned drives, however, these directions and script do not support it at the moment.

==Using cfdisk==
From a [[Open Terminal as root|terminal, as root]], type '''cfdisk /dev/sdX''' to launch the cfdisk application.

If you have a GUID-partitioned drive, cfdisk will complain. GUID partitions are not supported.

Make sure to replace /dev/sdX with the actual device (eg. /dev/sdb) that you found above.

If your hard drive contains existing partitions, select them one by one at the top (using up/down arrow keys), then select the '''[ Delete ]''' action (using the left/right arrow keys), then hit ENTER.

You should now only have Free Space listed at the top.<br/>
Select the '''[ New ]''' action, and accept the default (Primary, and size).

You should now have a single partition listed at the top, of type Linux.<br/>
Select the '''[ Write ]''' action, then '''[ Quit ]'''.

Now that you partitioned your drive, you need to format your newly created partition.<br/>
To format as EXT3, use this command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mkfs.ext3 -j /dev/sdX1
</div>

Replace ext3 with ext4 in the above command to format your partition as EXT4 instead of EXT3.

'''/dev/sdX1''' in the above command refers to the partition your created in cfdisk.<br/>
Go back in cfdisk, and check the ''Name'' column if you're unsure.<br/>
If you see ''sdb1'' in the name column, you should use '''/dev/sdb1''' in the above command.

==Partition over 2.1TB==
Here is a work around for drives with partitions over 2.1TB like the new 3TB drives.

Page: [[Partitions_Over_2.1_TB]]

=Mount the hard drive=

==Using hda-diskmount script==
A script is provided with Amahi that will look for unmounted partitions in your system, and mount any it finds.

[[Open Terminal as root|In a Terminal, as root]], type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
hda-diskmount
</div>

Example:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<small>
[root@hda ~]$ hda-diskmount
****************************************************************
Ignoring /dev/sda1 - already in /etc/fstab or mounted
****************************************************************
Mounted /dev/<strong style="color:green">sdb1</strong> as '<strong style="color:red">/var/hda/files/drives/sdb1</strong>' (read-write)
You may want your system to mount it every time you boot.
To do so, add this line VERY CAREFULLY to /etc/fstab and reboot:
<strong style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</strong>
****************************************************************
All Linux, Windows and Mac partitions on non-removable disks have been mounted
</small>
</div>

Do '''not''' edit /etc/fstab just yet. What you'll need to add there will depend on how you want to use the extra storage. More about that below.<br/>
Just note down the information in bold (green, red and blue). We'll use them below.

Note about ext4 in the blue line above: that doesn't necessarily mean your partition is formatted as ext4. It means the ext4 driver will be used to mount your partition. Since that driver is backward compatible, it can be safely used to mount ext2, ext3 and ext4 partitions.

If you get something like ''Disk /dev/dm-0 doesn't contain a valid partition table'' or ''mount: unknown file system type 'lvm2pv''' its because you have LVM's that 'fdisk' can not recognize (or something similar). It's nothing to worry about if you get that when executing the hda-diskmount script.

If you have changed the order of your installed hard drives, hda-diskmount may return the following message:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
Ignoring /dev/sda1 - already in /etc/fstab as /dev/sda1
This device appears to be commented out of your /etc/fstab. You will need to remove it from there for hda-diskmount to be able to mount it.
</div>

This might occur if you have made changes to the drive configuration order after you installed Amahi. If you want to stay with the reconfigured drive order, instructions on how to fix this are in the next section, Manually setting up the disk mount order.

==Manually setting up the disk mount order ==

1. First, get the UUID for each drive by opening a terminal and entering command

Ubuntu:
{{Code|Code=
gstreet@gstreet-MicroServer:~$ sudo blkid
[sudo] password for gstreet:
/dev/sda1: LABEL="Seagate-Alpha2TB" UUID="55d9333f-d801-425a-b2af-d65c5966d56f" TYPE="ext4"
/dev/sdb1: LABEL="Seagate-Beta2TB" UUID="5bd5498f-30c1-4780-948e-ca46656507d2" TYPE="ext4"
/dev/sdc1: LABEL="WD-Charlie2TB" UUID="a7337504-376a-4d36-9f7a-1a24c0f55fbd" TYPE="ext4"
/dev/sdd1: LABEL="WD-Delta2TB" UUID="8d881dcb-8de3-4621-b9bd-00025196868a" TYPE="ext4"
/dev/sde1: LABEL="root" UUID="4d6f8004-d190-4234-a03b-b68de988abf0" TYPE="ext4"
/dev/sde3: LABEL="home" UUID="d0531fa1-9311-4d53-b838-f35898adbd98" TYPE="ext4"
/dev/sde5: LABEL="swap" UUID="3c39206c-ba60-47ff-a1fe-f5821b2ab543" TYPE="swap"
}}

In this case, the user has four data drives (sda1, sdb1, sdc1, sdd1) and the Operating system assigned to a fifth drive, sde.

Take note of the UUID's for each drive. Easiest to cut and paste UUID's straight from the terminal - no typo's!

2. Then edit /etc/fstab to mount each drive - for novices, easiest to do this using a graphical editor. You might consider first making a copy called fstab.bak (use the "save as" command, close file and then gedit the original fstab again) so that you can recover the original fstab file if you make mistakes.

Ubuntu: {{Code|Code=
sudo gedit /etc/fstab
}}

3. Then carefully add the following line for each disk into the end of the fstab file

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
UUID=55d9333f-d801-425a-b2af-d65c5966d56f /var/hda/files/drives/drive1 ext4 defaults 1 2
</div>

It should look something like the following when lines are added for each of the five drives in this example. Make sure you paste in the right UUID, drive number and drive file system (ext4 in this case). Note lines beginning with # are comments where the remainder of the line is ignored)

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
"# Mounting Greyhole Drives for Drive Pool.
"#
# Drive1 = Seagate-Alpha2TB in Microserver Bay 1 from left
UUID=55d9333f-d801-425a-b2af-d65c5966d56f /var/hda/files/drives/drive1 ext4 defaults 1 2
#
# Drive2 = Seagate-Beta2TB in Microserver Bay 2 from left
UUID=5bd5498f-30c1-4780-948e-ca46656507d2 /var/hda/files/drives/drive2 ext4 defaults 1 2
#
# Drive3 = WD-Charlie2TB in Microserver Bay 3 from left
UUID=a7337504-376a-4d36-9f7a-1a24c0f55fbd /var/hda/files/drives/drive3 ext4 defaults 1 2
#
# Drive4 = WD-Delta2TB in Microserver Bay 4 from left
UUID=8d881dcb-8de3-4621-b9bd-00025196868a /var/hda/files/drives/drive4 ext4 defaults 1 2
#
</div>

Note that the hda-dismount command had already added lines to mount my OS drive which had two partitions (root or /, and home). Save file and close.

4) Save file and reboot machine.

5) Check drives in Amahi hda (Setup - Shares - Storage Pool)

In my case looked like
[img]https://docs.google.com/viewer?pid=explorer&srcid=0B4db0S5lBIq8enc1M0pJM3R1Mzg&docid=1b9781c1bebebe893591963b49cd0ab8%7C714e2385b5a30391311cd1211c8e3b8b&a=bi&pagenumber=1&w=800[/img]

==Test your hard drive==
Optionally, you can test your new drive for bad blocks.<br/>
Note that this step can take a ''long'' time to complete! You'll probably want to start it in the evening, to have it completed in the morning.

To do so, [[Open Terminal as root|in a Terminal, as root]], type the following command. Replace <strong style="color:green">sdb1</strong> with the (green) value you received from hda-diskmount.

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
e2fsck -cn /dev/<strong style="color:green">sdb1</strong>
</div>

You'll receive a warning that says "WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage. Do you really want to continue (y/n)?"<br/>
Answer ''yes''. The -cn option we're using can safely be used on mounted filesystems.

=Use the hard drive=

You have a choice here on how to use your new hard drive storage space. We'll offer some examples.

==Use the hard drive for all shares==

If you want all your shares to be on your new hard drive, here's how to do that.

First, you'll want to move all you previous shares data, if any, into your new drive.<br/>
You only need to do this next command if you have data that you care about in the /var/hda/files/* folders.<br/>
[[Open Terminal as root|In a Terminal, as root]], type the following command. Replace the path in red with the path you received when you ran hda-diskmount.
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mv /var/hda/files/* <strong style="color:red">/var/hda/files/drives/sdb1/</strong>
</div>
You'll get a warning about "cannot move `/var/hda/files/drives' to a subdirectory of itself"; that is fine, ignore that.

Next, you'll need to unmount your new hard drive, and remount it as /var/hda/files

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1/
</div>

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you (the blue one), and change the second value (the path).<br/>
Replace the second value with '''/var/hda/files'''.

hda-diskmount gave me:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
<span style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files/drives/sdb1</strong> ext4 defaults 1 2</span>
</div>

So I should add this instead:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files</strong> ext4 defaults 1 2
</div>

Make sure you do '''not''' change anything else from the blue line you received from hda-diskmount.<br/>
It might not be the same thing as the above example; you need to use the values you've received.

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
ls /var/hda/files/
</div>

That last command should show you the content of you new hard drive.

That's it. All your shares in /var/hda/files are now on your new hard drive.

==Use the hard drive for only some shares==

If you want only some of your shares to be on your new hard drive, here's how to do that.

First, you'll want to move your previous shares data, if any, into your new drive.<br/>
You only need to do this next command if you have data that you care about in the /var/hda/files/* folders (that you want on the new drive).<br/>
[[Open Terminal as root|In a Terminal, as root]], type the following command. Replace the path in red with the path you received when you ran hda-diskmount. Replace '''something''' with the name of the share you want to have on your new drive (the share should already exist).
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mv /var/hda/files/<strong>something</strong> <strong style="color:red">/var/hda/files/drives/sdb1/</strong>
</div>

Repeat with every share you want on your new drive.

Next, you'll need to make the mount permanent

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1<br/>
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you, and insert that.<br/>

So, following previous examples, I should add this:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span>
</div>

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
ls /var/hda/files/drives/sdb1
</div>

That last command should show you the content of you new hard drive.

Now, you need to update the location of the moved shares within Amahi. Go to your <strong>Amahi Dashboard</strong>, click on <strong>Setup</strong>, then <strong>Shares</strong>.

Click on one of the shares that you have moved. This will open a panel revealing the share settings. Click on the location (the bit that is shown with a dotted underline) and it will change to an edit box. Update the location to match the new share location.

For example, the original movies location was: <span style="color:red">/var/hda/files/movies</span><br/>
The new location might be: <span style="color:blue">/var/hda/files/drives/sdb1/movies</span>

Repeat for any other shares that you have moved. Check that you can access these shares from another machine within your network.

Finally, if you have any services that depend on the location of these shares, make sure they are configured to use the new share location. For example, if you have a DLNA server installed, check its configuration files to make sure that it can find any media folders that have been moved. Secondly, <em>check that all such services start correctly and behave as expected</em>. If the service doesn't start, it may be that it is testing for a specific location during the service startup. Check the startup files in <strong>/etc/init.d</strong> to see if this is the case.

That's it. Your share(s) are now on your new hard drive.

==Use the hard drive in your Greyhole storage pool==

If you want to add your new hard drive to your Greyhole storage pool, here's how to do that.

First, you'll need to make the mount permanent. [[Open Terminal as root|In a Terminal, as root]], type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you, and insert that.<br/>

So, following previous examples, I should add this:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span>
</div>

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
</div>

Finally, you'll need to configure Greyhole to select your new partition. To configure Greyhole, Advanced Settings must be enabled under [http://hda/setup?sub=settings&tab=setting Setup > Settings].

In the [http://hda/setup?sub=disk_pooling&tab=share Shares > Storage Pool page] of your Amahi dashboard, you'll see a list of mounted partitions, with checkboxes next to each, allowing you to include those partitions in your storage pool.

You should now have a new row in there, referring to /var/hda/files/drives/sdb1.

Select it (click the checkbox).

That's it. Your new hard drive just increased your Greyhole storage pool capacity.

Adding a second hard drive to your HDA

2012-11-08T10:34:58Z

Carl Greenstreet: /* Mount the hard drive */

{{MessageBox|
backgroundcolor = #faa|
image =Warning.png|
heading =WARNING|
message = This is recommended only for advanced users, proceed with caution.}}
[[Adding_drives_to_your_HDA|Adding drives to your HDA]] is another howto on doing this, a bit shorter and less elaborate, which can be good for some people, specially a novice unfamiliar with doing any of this.

More hard drives can be added in your Amahi HDA for additional storage space.

We'll detail how to add such hard drives, and how to put them to good use.

=Important Notes=

* This is a how-to on adding additional drives to your HDA.
* Amahi cannot be held responsible for any data breakage or destruction arising from the use or misuse of this script. We provide it as a service in good will. You accept this automatically if you use the script.
* This page and script does not support GUID-partitioned drives (such as drives previously in a Mac or have GPT partition tables). You can find what your partition is like with <code>fdisk -l</code>

=Make sure your drive is detected by Fedora=

Open a Terminal, and type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 0 1em;">
ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"
</div>

Look for the line that matches the hard drive you added.

IDE and SATA hard drives will start with '''ata-''' and USB hard drives will start with '''usb-'''.<br/>
Look for your hard drive model and serial number.

Example:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
[gb@hda ~]$ ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"
ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V
ata-ST31000528AS_6VP08W65
ata-ST3750640A_3QD0LJN8
ata-ST3750640A_5QD27A57
ata-WDC_WD10EADS-00L5B1_WD-WCAU4C700358
usb-ST310003_33AS_9E1CA6FFFFFF-0:0
usb-ST375064_0A_2009031309E2-0:0
</div>

=Install prerequisites=

[[Open Terminal as root|In a Terminal, as root]], type the following (two) commands:

* Fedora
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
yum -y install pmount fuse fuse-libs ntfs-3g gparted util-linux-ng
</div>

* Ubuntu
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
sudo apt-get -y install gparted
</div>

Drives must be formatted as '''MBR''' not '''GUID/GPT''' for hda-diskmount to recognize the disk.

=Partition and format the hard drive=

This step is optional, and should only be executed if you want to delete the content of your new hard drive, or if the hard drive has not yet been formatted.

You should (unless you have a good reason not to) use GParted to partition and format your hard drive.<br/>
Not having X installed would qualify as a good reason! In such cases, either use SSH X11 Forwarding (Google that if you'd like to use this), or [[Adding_a_second_hard_drive_to_your_HDA#Using_cfdisk|use cfdisk]] from a [[Open Terminal as root|Terminal, as root]].

You'll probably want to create a single partition, and format it as ''ext3''.<br/>
Note that Windows can't read ext3 partitions, so if you want dual-boot Windows on your Amahi PC, or if you intend to connect this hard drive to a Windows computer later, you should format as NTFS instead, and you should do that on Windows before you connect the drive in your HDA.<br/>
Remember that using NTFS partitions on Linux will be slower that using ext3 partitions, so you should only use NTFS if you really need it.<br/>
How much slower: compare the blue bars (NTFS-3G) with the red bars (ext3) on [http://www.tuxera.com/products/tuxera-ntfs-commercial/performance/ this graph].

To know what device (/dev/sdX) you need to partition and format, use the following command, in a [[Open Terminal as root|Terminal, as root]]:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
ls -l /dev/disk/by-id/
</div>

Find the row corresponding to your hard drive, and look at the end of the line to identify the correct device to use.

Example:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><small>
[gb@hda ~]$ ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V -> ../../sda
lrwxrwxrwx 1 root root 10 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V-part1 -> ../../sda1
lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-ST31000528AS_6VP08W65 -> ../../sdb
</small>
</div>

In the above example, /dev/sdb would be what I would select in GParted (or use on the cfdisk command). sda in my primary hard drive, and sdb my second hard drive.

==Using GParted==
From the HDA desktop (or using VNC), [[Open Terminal as root]] and type '''gparted''' to launch the GParted application.

Select the device (/dev/sdX) that you found above.

In the above example, /dev/sdb would be what I would select in GParted.

There are many easy to follow guides online on how to use GParted. You should Google for one, to find one that seems clear to you.

[http://www.mepisguides.com/Mepis-6/Install/gparted/gparted-set-partition.html Here's one] that looks simple. Just use ext3 instead of fat32 in you follow that tutorial.

Note that gparted supports GUID-partitioned drives, however, these directions and script do not support it at the moment.

==Using cfdisk==
From a [[Open Terminal as root|terminal, as root]], type '''cfdisk /dev/sdX''' to launch the cfdisk application.

If you have a GUID-partitioned drive, cfdisk will complain. GUID partitions are not supported.

Make sure to replace /dev/sdX with the actual device (eg. /dev/sdb) that you found above.

If your hard drive contains existing partitions, select them one by one at the top (using up/down arrow keys), then select the '''[ Delete ]''' action (using the left/right arrow keys), then hit ENTER.

You should now only have Free Space listed at the top.<br/>
Select the '''[ New ]''' action, and accept the default (Primary, and size).

You should now have a single partition listed at the top, of type Linux.<br/>
Select the '''[ Write ]''' action, then '''[ Quit ]'''.

Now that you partitioned your drive, you need to format your newly created partition.<br/>
To format as EXT3, use this command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mkfs.ext3 -j /dev/sdX1
</div>

Replace ext3 with ext4 in the above command to format your partition as EXT4 instead of EXT3.

'''/dev/sdX1''' in the above command refers to the partition your created in cfdisk.<br/>
Go back in cfdisk, and check the ''Name'' column if you're unsure.<br/>
If you see ''sdb1'' in the name column, you should use '''/dev/sdb1''' in the above command.

==Partition over 2.1TB==
Here is a work around for drives with partitions over 2.1TB like the new 3TB drives.

Page: [[Partitions_Over_2.1_TB]]

=Mount the hard drive=

A script is provided with Amahi that will look for unmounted partitions in your system, and mount any it finds.

[[Open Terminal as root|In a Terminal, as root]], type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
hda-diskmount
</div>

Example:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<small>
[root@hda ~]$ hda-diskmount
****************************************************************
Ignoring /dev/sda1 - already in /etc/fstab or mounted
****************************************************************
Mounted /dev/<strong style="color:green">sdb1</strong> as '<strong style="color:red">/var/hda/files/drives/sdb1</strong>' (read-write)
You may want your system to mount it every time you boot.
To do so, add this line VERY CAREFULLY to /etc/fstab and reboot:
<strong style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</strong>
****************************************************************
All Linux, Windows and Mac partitions on non-removable disks have been mounted
</small>
</div>

Do '''not''' edit /etc/fstab just yet. What you'll need to add there will depend on how you want to use the extra storage. More about that below.<br/>
Just note down the information in bold (green, red and blue). We'll use them below.

Note about ext4 in the blue line above: that doesn't necessarily mean your partition is formatted as ext4. It means the ext4 driver will be used to mount your partition. Since that driver is backward compatible, it can be safely used to mount ext2, ext3 and ext4 partitions.

If you get something like ''Disk /dev/dm-0 doesn't contain a valid partition table'' or ''mount: unknown file system type 'lvm2pv''' its because you have LVM's that 'fdisk' can not recognize (or something similar). It's nothing to worry about if you get that when executing the hda-diskmount script.

If you have changed the order of your installed hard drives, hda-diskmount may return the following message:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
Ignoring /dev/sda1 - already in /etc/fstab as /dev/sda1
This device appears to be commented out of your /etc/fstab. You will need to remove it from there for hda-diskmount to be able to mount it.
</div>

This might occur if you have made changes to the drive configuration order after you installed Amahi. If you want to stay with the reconfigured drive order, instructions on how to fix this are here.

==Test your hard drive==
Optionally, you can test your new drive for bad blocks.<br/>
Note that this step can take a ''long'' time to complete! You'll probably want to start it in the evening, to have it completed in the morning.

To do so, [[Open Terminal as root|in a Terminal, as root]], type the following command. Replace <strong style="color:green">sdb1</strong> with the (green) value you received from hda-diskmount.

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
e2fsck -cn /dev/<strong style="color:green">sdb1</strong>
</div>

You'll receive a warning that says "WARNING!!! Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage. Do you really want to continue (y/n)?"<br/>
Answer ''yes''. The -cn option we're using can safely be used on mounted filesystems.

=Use the hard drive=

You have a choice here on how to use your new hard drive storage space. We'll offer some examples.

==Use the hard drive for all shares==

If you want all your shares to be on your new hard drive, here's how to do that.

First, you'll want to move all you previous shares data, if any, into your new drive.<br/>
You only need to do this next command if you have data that you care about in the /var/hda/files/* folders.<br/>
[[Open Terminal as root|In a Terminal, as root]], type the following command. Replace the path in red with the path you received when you ran hda-diskmount.
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mv /var/hda/files/* <strong style="color:red">/var/hda/files/drives/sdb1/</strong>
</div>
You'll get a warning about "cannot move `/var/hda/files/drives' to a subdirectory of itself"; that is fine, ignore that.

Next, you'll need to unmount your new hard drive, and remount it as /var/hda/files

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1/
</div>

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you (the blue one), and change the second value (the path).<br/>
Replace the second value with '''/var/hda/files'''.

hda-diskmount gave me:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
<span style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files/drives/sdb1</strong> ext4 defaults 1 2</span>
</div>

So I should add this instead:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files</strong> ext4 defaults 1 2
</div>

Make sure you do '''not''' change anything else from the blue line you received from hda-diskmount.<br/>
It might not be the same thing as the above example; you need to use the values you've received.

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
ls /var/hda/files/
</div>

That last command should show you the content of you new hard drive.

That's it. All your shares in /var/hda/files are now on your new hard drive.

==Use the hard drive for only some shares==

If you want only some of your shares to be on your new hard drive, here's how to do that.

First, you'll want to move your previous shares data, if any, into your new drive.<br/>
You only need to do this next command if you have data that you care about in the /var/hda/files/* folders (that you want on the new drive).<br/>
[[Open Terminal as root|In a Terminal, as root]], type the following command. Replace the path in red with the path you received when you ran hda-diskmount. Replace '''something''' with the name of the share you want to have on your new drive (the share should already exist).
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mv /var/hda/files/<strong>something</strong> <strong style="color:red">/var/hda/files/drives/sdb1/</strong>
</div>

Repeat with every share you want on your new drive.

Next, you'll need to make the mount permanent

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1<br/>
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you, and insert that.<br/>

So, following previous examples, I should add this:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span>
</div>

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
ls /var/hda/files/drives/sdb1
</div>

That last command should show you the content of you new hard drive.

Now, you need to update the location of the moved shares within Amahi. Go to your <strong>Amahi Dashboard</strong>, click on <strong>Setup</strong>, then <strong>Shares</strong>.

Click on one of the shares that you have moved. This will open a panel revealing the share settings. Click on the location (the bit that is shown with a dotted underline) and it will change to an edit box. Update the location to match the new share location.

For example, the original movies location was: <span style="color:red">/var/hda/files/movies</span><br/>
The new location might be: <span style="color:blue">/var/hda/files/drives/sdb1/movies</span>

Repeat for any other shares that you have moved. Check that you can access these shares from another machine within your network.

Finally, if you have any services that depend on the location of these shares, make sure they are configured to use the new share location. For example, if you have a DLNA server installed, check its configuration files to make sure that it can find any media folders that have been moved. Secondly, <em>check that all such services start correctly and behave as expected</em>. If the service doesn't start, it may be that it is testing for a specific location during the service startup. Check the startup files in <strong>/etc/init.d</strong> to see if this is the case.

That's it. Your share(s) are now on your new hard drive.

==Use the hard drive in your Greyhole storage pool==

If you want to add your new hard drive to your Greyhole storage pool, here's how to do that.

First, you'll need to make the mount permanent. [[Open Terminal as root|In a Terminal, as root]], type the following command:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
umount /var/hda/files/drives/sdb1
nano /etc/fstab
</div>

In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you, and insert that.<br/>

So, following previous examples, I should add this:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;">
<span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span>
</div>

Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:

<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a
</div>

Finally, you'll need to configure Greyhole to select your new partition. To configure Greyhole, Advanced Settings must be enabled under [http://hda/setup?sub=settings&tab=setting Setup > Settings].

In the [http://hda/setup?sub=disk_pooling&tab=share Shares > Storage Pool page] of your Amahi dashboard, you'll see a list of mounted partitions, with checkboxes next to each, allowing you to include those partitions in your storage pool.

You should now have a new row in there, referring to /var/hda/files/drives/sdb1.

Select it (click the checkbox).

That's it. Your new hard drive just increased your Greyhole storage pool capacity.