Amahi Wiki - User contributions [en]

Amahi Energy Saver

2011-08-10T13:36:59Z

Herronrobertson:

[[Image:Amahi-Energy-Saver_Logo.png|150px]]<br>

==General==

This is in solid beta stage. Installation requires a little Linux knowledge.

If you like it, like it on facebook: <br>http://www.facebook.com/pages/Amahi-Energy-Saver/218015224890441?sk=wall

==Introduction==
Running servers when they are not needed can waste a considerable amount of energy. This application tells your Amahi server to suspend or power off when its services are not needed.

Amahi Energy Saver regularly scans for connected clients, which are defined in the "monitored host list". If none of these clients is turned on, the system suspends after a configurable period.

So, for instance, you may want to add your client PC and your PS3 to the monitored host list. The Amahi Box will then stay up and running as long as client PC and/or PS3 are up and running. However, you might not want to add your home router to the list, as the router is always turned on.

With the calendar function one can define scheduled wake ups and periods during which the server shall stay awake no matter what.

Amahi Energy Saver also checks shares. As long as shares are accessed, the server does not suspend. If set up to do so, Squeezeboxserver is monitored to prevent suspend while Squeezeboxes are turned on.

When the system is to be used again, simply wake it up with WOL (ref. http://en.wikipedia.org/wiki/Wake-on-LAN). There are many tools to generate WOL packets, and it is even possible to wake your server over the internet (good link: http://www.wakeonlan.me/).

==Download==

Download the latest tested and released version here: http://code.google.com/p/amahienergysaver/downloads/list

Latest untested sources are available at Git:
https://github.com/jayrockk/Amahi-Energy-Saver

==Initial setup==

1. Copy the tar.gz file from the download page to some folder and unpack it with

{{Code|Code=
tar -zxf filename
}}

2. Open a terminal, change to that folder and get superuser rights by running <code>su</code>

3. As root, run
{{Code|Code=
cd installfiles
}}
{{Code|Code=
./aes-install.sh
}}

4. When the installation is finished, reboot the computer. The config app is accessible at

{{Code|Code=
http://hda:6500
}}

==Integration with Amahi calendar==
1. In the config app, select ical in the Calendar field.

2. Hit the "Apply button in the config app

3. Connect your client to the new calendar. NOTE: Please read this article if you are unsure how to do this: [[Calendars]]

4. Use your favourite calendar client to populate the calendar with events.

Done! Your HDA will now wake up and stay powered on according to the events defined in the aes calendar.

*Example: Set up Mozilla Sunbird for use with Amahi Energy Saver calendar

The following description was created based on Sunbird 1.0b1 running on Windows 7.

In Sunbird, select "File" -> "Connect to remote calendar..."
A dialog shows up. Choose "On the network"

[[Image:AES_Sunbird_1.jpg]]<br>

Press "Next". Choose "iCalendar (ICS)" in the dialog and type "http://calendar/aes.ics" in the Location field.

[[Image:AES_Sunbird_2.jpg]]<br>

Press "Next". In the following dialog you may deselect the checkbox "Show Alarms", though it's not neccessary for Amahi Energy Saver to work.

[[Image:AES_Sunbird_3.jpg]]<br>

Press "Next" then "Finish". You will notice an exclamation mark next to the calendar on the right tab.

[[Image:AES_Sunbird_4.jpg]]<br>

Right click the calendar, select "Properties" and make sure "Read Only" is deselected.

[[Image:AES_Sunbird_5.jpg]]<br>

Finished. Below is an example screenshot with a task defined on 2011-07-06 2:30-3:00 and another one 4:30-5:30. In the example, the HDA will not go to sleep during these periods, and will wake up if it is suspended.

[[Image:AES_Sunbird_6.jpg]]<br>

==Selecting ShutdownType==

The different options for ShutdownType are explained here:<br><br>

Deactivated
Amahi Energy Saver is running in the background, however it will never shutdown or suspend the HDA.

Poweroff
This is a full shutdown and should work on most systems. Some mainboards do not allow scheduled wakeup when using this method.<br><br>

ACPI_S1
Legacy ACPI S1 state. Support depends on mainboard and Fedora support<br><br>

ACPI_S3
Legacy ACPI S3 state. Support depends on mainboard and Fedora support<br><br>

ACPI_S4
Legacy ACPI S4 state. Support depends on mainboard and Fedora support<br><br>

mem
Suspend to memory, is intended to replace ACPI S1 but is not widely supported yet<br><br>

disk
Suspend to disk, is intended to replace ACPI S4 but is not widely supported yet<br><br>

standby
Suspend to memory, is intended to replace ACPI S3 but is not widely supported yet<br><br>

When selecting the shutdown type the following procedure is suggested:<br><br>

* Start with Poweroff to do basic checking and configuration. Since this is the safest version, it should also be your resort in case of problems.<br><br>

* Once things are working, select either of the ACPI_S1..3 depending on what level of suspend you want<br><br>

* If you are brave or the ACPI options don't work, try mem, disk or standby.<br><br>

==Logs and LogAnalyzer==
Depending on the version installed the logs are located in /usr/share/aes or /var/hda/web-apps/html/aes/lib. In any case the files are named named aes.log*

In order to view the Amahi Energy Saver logs in the LogAnalyzer (ref. http://www.amahi.org/apps/loganalyzer) navigate on your LogAnalyzer homepage to "Admin Center" then "Sources" and finally klick "Add new Source". Configure the new source for the Energy Saver logs as shown in the screenshot below (note that the directory may have to be adjusted, see above):

[[File:LogAnalyzer_Config_for_Amahi_Energy_Safer.png]]

==Windows client for Wake on LAN==
On the download page there is a Windows client for automatic or manual wakeup of the HDA.

*Installation

Just run the msi file found on the download page. The client will be included in the startup folder.

*Configuration

1. Form the start menu, run AmahiEnergySaver -> AES Client

2. Right click on the icon that will appear in symbol bar, and select "Show config"

3. To get started, make sure that you set "Host MAC" and "Host name" to your HDA configuration. Hit "Select Server" to bring up the "Select HDA" window, and then "Search". If possible the correct server is alreday selected, in that case just hit "Ok" to confirm. Continue with 4.<br><br>
If the server appears on the list but is not automatically selected, click on it and hit return.<br><br>
Should your server not show up at all, press "Cancel" to exit the "Select HDA" dialog and configure MAC and host name manually.<br><br>
Finally, if requried, change the "Port" setting. The default "9" should work in most cases. <br><br>

4. Hit the "OK" butten, then right click on the symbol again, select "Exit" and and restart the program as described in 1.

5. Done! You should now be able to start your HDA by right clicking on the icon in the symbol bar and select "Wake now"

==Mac OS X clients for Wake on LAN==

There exist a few solutions (WOL clients) to wake up your HDA from a Mac OS X computer. In order to wake up your HDA while booting your Mac you may use NASwake (ref. http://trick77.com/2010/12/22/wake-nas-at-boot-time-wake-on-lan-wol/). It comes ready to use as an installable package, you just need to enter the MAC-adress of the HDA.<br><br>
WakeOnLan is a freeware application provided by Readpixel which offers a very comfortable way to wake up your HDA directly from your Mac OS X desktop (ref. http://www.readpixel.com/wakeonlan/index.html).

==OBSELETE: Command Line Interface==

*Note: Root privileges are required to execute the CLI command. Navigate to /usr/share/aes to use the CLI correctly.

{{Code|Code=
./aes.rb --shownetworkhosts
}}
Lists the hosts found in the network, ie, all devices connected to the network. Gives the user the choice to add hosts to the monitored host list.

{{Code|Code=
./aes.rb --showmonitoredhosts
}}
Show a list of all hosts which are monitored by AES (i.e. the monitored host list), and also allows to delete hosts from the list. If these hosts are up and running (and respond to ping), the server does not suspend.

{{Code|Code=
./aes.rb --addhost macadress
}}
Manually add a host to the monitored host list. Observe the MAC address format, which has to be XX:XX:XX:XX:XX:XX. Example is <br> <code>./aes.rb --addhost 12:34:56:78:90:ab</code>

{{Code|Code=
./aes.rb --calendar [off, internal, ical, debug]
}}
<code>./aes.rb --calendar</code> shows the current setting.
<code>./aes.rb --calendar off</code> turns the calendar off,
<code>./aes.rb --calendar internal</code> makes aes use its internal calendar function and
<code>./aes.rb --calendar ical</code> activates the Amahi calendar integration. To show diag information use <code>./aes.rb --calendar debug</code>

{{Code|Code=
./aes.rb --showcalendar
}}
Lists the current entries of the internal calendar. Calendar entries define times when the server does not suspend. Also, the server will be woken up at the beginning of a calendar entry.

{{Code|Code=
./aes.rb --addcalendar startdate starttime stopdate stoptime
}}
Use this command to add an entry to the internal calendar. Format of startdate/stopdate: YYYY-MM-DD Format of starttime/stoptime: hhm:mm. Eg.
<br><code>./aes.rb --addcalendar 2010-12-20 15:00 2010-12-20 16:00</code> <br>
will keep the server awake on Dec 20th, 2010 from 15 to 16 hrs (3 to 4 pm). The server will also wake up at 15 hrs if it is suspended.

{{Code|Code=
./aes.rb --shutdowntype
}}
Show and modifiy the type of shutdown. NOTE: Not all shutdown types may be supported on your system, or may work correctly. Therefore, test that your machine is suspending and coming up correctly before deciding for a setting. Poweroff is safest type.

{{Code|Code=
./aes.rb --sbs [on, off, debug]
}}
<code>./aes.rb --sbs</code> shows the current setting. <code>./aes.rb --sbs on</code> and <code>./aes.rb --sbs off</code> switch monitoring of Squeezeboxserver on or off, respectively. The command <code>./aes.rb --sbs debug</code> displays diagnostic information

{{Code|Code=
./aes.rb --interval
}}
aes checks regularly if the system can be suspended or shut down. This parameter specifies the time in seconds between two such checks. Normally should be left untouched.

{{Code|Code=
./aes.rb --showenergybalance
}}
View the energy savings in kWh due to the use of Amahi Energy Saver.

{{Code|Code=
./aes.rb --setpowerconsumption pc_on pc_standby
}}
Set the average power consumption when working ("pc_on") and powered off ("pc_standby"). Values given in Watts. pc_on must be greater than pc_standby.

{{Code|Code=
./aes.rb --help
}}
Displays command line help

[http://cvresumewritingservices.org/ resume writing]

Amahi 6.1

2011-08-10T13:36:55Z

Herronrobertson:

= Release Notes =

* Huge amount of fixes and improvements for Ubuntu! A few people are rumored to be running Amahi 6 on Ubuntu/Debian. Thanks to the U/D team!
* Fix for running install scripts with elevated privileges for apps without a webapp, e.g. the new [http://www.amahi.org/apps/vnc VNC] one-click app works out of the box
* Fix for properly setting the timezone in php.ini at installation time
* CSS fixes for RTL (right to left) languages
* New translation to Arabian, contributed by Abdulrhman Al-Khamees. Check out [http://dl.dropbox.com/u/196664/Screenshot-6.png one] [http://dl.dropbox.com/u/196664/Screenshot-7.png the] [http://dl.dropbox.com/u/196664/Screenshot-8.png many] [http://dl.dropbox.com/u/196664/Screenshot-9.png screenshots]!
* New translation to Latvian, contributed by Ivo
* New translation to [http://www.kosacrta.hr/ Croatian], contributed by [http://www.kosacrta.hr/ Vladimir]
* Finish off Latvian, Arabian, Hebrew, Russian and Finnish(Suomi) translations
* Update logos to new Amahi logo - thanks BK!
* Fix to add delay to amahi-download for more reliability in webapp installs
* New module in the platform code to capture many/most/all platform-dependent things!
* Dummy mode for development, where hdactl is ignored, so most system stuff is dropped on the floor and no errors are raised
* Add platform bits to be able to run the platform on Mac OS X, mostly for development (don't get too excited :) )
* Switch the available apps to be the first submenu and Installed Apps as the second will make things easier usability-wise - here is a screenshot of the prototype: http://cpg.amahi.me/Public/Screenshots/new-app-area.png
* Enhanced support for uber advanced [[Network customizations]], for the ninja networking guru in you

= To Do =

* Add new disk wizard
* Make it even easier to host apps from outside
[http://cvresumewritingservices.org/ resume writing services]

AjaXplorer

2011-08-10T13:36:49Z

Herronrobertson:

Changing the default location of shares in AjaXplorer is a little hidden.

If your shares are in a different directory than the default /var/hda/files/[share], follow these 5 simple steps (You must know the directory where your shares are located beforehand. Whether on a different hardrive than the Amahi installation, or just a different directory than the default):

1. Click on the arrow by Default Files

[[File:Clipboard02.jpg|frameless|On the top left corner]]

2. In the menu, click on Settings

[[File:Clipboard03.jpg|Settings is towards the bottom]]

3. Click on Repositories

[[File:Clipboard04.jpg|frameless|In the Folders column]]

4. Right click on the share in question and click Editor

[[File:Clipboard05.jpg|frameless|Right clicking will bring up this menu]]

5. Paste in the share's link

[[File:Clipboard06.jpg|frameless|You must know where the share is located beforehand]]

[http://cvresumewritingservices.org/ resume writing service]

Adding an HDA networked printer

2011-08-10T13:36:32Z

Herronrobertson:

To set up a network printer attached to the HDA from Windows, you need to perform a few simple steps. Each machine that will need access to the printer will also need the drivers installed. This will be accomplished at the time you connect them to the printer.

* Connect the printer to the HDA (parallel or USB) and ensure it is powered on. It should automatically detect the printer and set it up for you.

* Samba should be set up already for serving printers

* You can optionally create multiple queues for one printer. We recommend 4 queues, called printer (the default, set to print in black and white), color_draft, color and color_photo. Each printer queue has corresponding settings to print as desired when print jobs are sent to that queue.

* When you created it in the server, under Local Printers, it should say the name of the queue. Make sure the State (under the Settings tab) ''Shared'' is selected. This makes sure it can be accessed remotely.

* Next go to a machine on your network that you want to install the printer. For Windows, from the ''run'' option, enter '''\\hda''' followed by your user ID and password if required.
[[image:Printer1.PNG]]

* You should see the printer now.
[[image:Printer2.PNG]]

*Right click on the printer and select connect. Answer '''Yes''' to install when it prompts to install the printer.
[[image:Printer3.PNG]]

* Now, it won’t find the drivers, so select '''OK''' as we will install the drivers from the printer disk.
[[image:Printer4.PNG]]

*You should now see the add printer wizard. If your driver is in the list, select it. Otherwise, select Have Disk and point it to your drive where the printer driver disk is located.
[[image:Printer5.PNG]]

* Once you install the driver, you can check the Printers and Faxes to see if it is installed. Although it says '''''Access denied, unable to connect''''', it is working. Print a test page. If all works well, you should see it in a matter of seconds.
[[image:Printer6.PNG]]

Optional:
The printer status message problem can be corrected by adding the following line to the '''/etc/samba/smb.conf''' file under the '''''printers''''' section:
{{Text|Text=[printers]
use client driver = yes}}

This must be done on the server using terminal. Then, restart samba by entering '''/etc/init.d/smb restart''' and the message should now display '''''ready''''' on the client machine.

[[image:Printer7.PNG]]

This worked great on my network, but may require some additional adjustments for others. For more assistance, see the FAQ [http://www.amahi.org/faq#I-want-to-add-a-printer-to-my-HDA-and-make-it-a-printer-server-how-do-I-do-it (I want to add a printer to my HDA and make it a printer server, how do I do it?)]

= Troubleshooting on Vista or Windows 7 clients =

# In some windows clients, some users see this: "windows cannot connect to the printer.operation could not be completed (error 0x0000000d)". We've seen this problem with a few printers now, not consistently between any particular makes or models. However, I have found a consistent fix to connect to any network printer from vista:
## Run a command prompt and type the following: "net use LPT2: \\server\printer"
###This sets up a behind-the-scenes connection to the printer.
##Then go through the add printer wizard, choose to add a local printer, and choose port LPT2... It will probably ask for a printer driver, and you can just choose whatever XP driver you might have been using before. The printer is then installed without any errors, and works just fine.
##From poking around, it seems when the error appears that the driver is actually installed, but something between it being installed and it actually being added to vista's list of printers breaks. Doing the above just works though.
##This was from this [http://social.technet.microsoft.com/Forums/en/itprovistaprinting/thread/d02718d8-cf5d-45de-9206-46714a549ee0 Technet page]
# Some users may find that certain printers (for example, the Brother HL2270DW laser printer), will not print from anyone other than the admin. We will have to add permissions for each user from CUPS:
## From the HDA desktop go to: http://localhost:631/printers to open up the CUPS GUI interface.
## Click on your printer
## Under the menu "Administration", select "Set Allowed Users"
## In the text box, type in all the HDA users
### Ex: "user1, user2, user3"
## Make sure "Allow these users to print" is selected, then click "Set Allowed Users".
## Note: to print, each user must be logged onto the HDA using (in Windows) \\hda in Windows Explorer
# Certain users may also find that even though the above steps were followed with no spelling mistakes, the printer shows a "Permission needed", or similar, message. I have not found a way to fix this, except for the following:
## Create a new HDA account for the user effected
## Transfer all files over
## Delete the old HDA account
## Do Troubleshooting 2 above for the new user account. In my case, this has successfully solved the issue.

[http://editingwritingservices.org/ dissertation editing]

Adding a second hard drive to your HDA

2011-08-10T13:35:40Z

Herronrobertson:

{{MessageBox|
backgroundcolor = red|
image =Warning.png|
heading =WARNING|
message = This is recommended only for advanced users, proceed with caution.}}
[[http://wiki.amahi.org/index.php/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 an how-to on how to add 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:

<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>

=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.

=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.

==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.

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.

[http://editingwritingservices.org/article.php article writing service]