<center>{{MessageBox|
backgroundcolor = #faa|
image =Warning.png|
heading =WARNING|
message = This is recommended only for advanced ''Advanced'' users, proceed with caution.}}</center>[[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<div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
More hard drives can be added in your '''NOTE:''' The Amahi HDA for additional storage space[https://www.amahi.org/apps/disk-wizard Disk Wizard] application (Amahi 8 or greater '''ONLY''') provides this capability from the Dashboard UI.
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>
<br />
The purpose of this tutorial is to make partitioning, formatting, and mounting hard drives in the Amahi server simple for those new to Linux.
Look for the line that matches the hard drive you added. IDE and SATA hard drives will start with 'In order to keep this process simple, it's important 'ata-''NOT' and USB hard drives will start with '''usb-'''.<br/>Look for your to connect additional hard drive model and serial number(s) until the end of the [[Adding_a_second_hard_drive_to_your_HDA#Preparation|Preparation]] step.
Example=Disclaimer=* [https://www.amahi.org 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.
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin* [http: 3px 3px 1em 3px;"> [gb@hda ~]$ ls -1 /dev/disken.wikipedia.org/by-idwiki/ | egrep GUID_Partition_Table GUID-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>partitioned] hard drives (such as those previously used in a Mac or have GPT partition tables) are not supported in this tutorial.
=Install prerequisites=* [http://en.wikipedia.org/wiki/GNU_nano nano] is used as the command-line text editor (refer to [http://www.howtogeek.com/howto/42980/the-beginners-guide-to-nano-the-linux-command-line-text-editor/ beginners guide to nano] as needed).
=Prerequisites=[[Open Terminal as root|In a Terminal, as root]], type the following (two) commandsverify disk tools are installed by executing:<br />
* Fedora
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left">
yum dnf -y install pmount fuse fuse-libs ntfs-3g gparted util-linux-ngparted nano
</div>
* :'''NOTE:''' <code>yum</code> (deprecated) has been replaced with <code>dnf</code> as the package manager for Fedora 23 and greater.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 :'''NOTE:''' Hard drives must be formatted as '''MBR''' not '''GUID/GPT''' for ''hda-diskmount '' to recognize the diskwork correctly.
=Partition and format Preparation=[[Open_Terminal_as_root|In terminal as root]], execute the following to capture current hard driveconfiguration:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> ls -l /dev/disk/by-id/ > before.txt cat before.txt</div>
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:EXAMPLE: lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V -> ../. You should (unless you have a good reason not to) use GParted to partition and format your hard drive.<br/>sdaNot 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 lrwxrwxrwx 1 root|Terminal, as root]]10 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V-part1 -> ../../sda1
YouPower 'll probably want to create a single partition, and format it as 'OFF'ext3''.<brthe HDA and install/>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 any additional 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(s).<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 =Identify=Power ''ON'' the HDA and format, use collect data about the following commandnew hard drive configuration. Again, in save this to a [[Open Terminal as root|Terminal, as root]]:text file for reference.
[[Open_Terminal_as_root|In a terminal as root]], execute the following to capture current hard drive configuration:<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/
> after.txt cat after.txt
</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="borderEXAMPLE: 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, :'''FYI:''' IDE/dev/sdb would be what I would select in GParted (or use on the cfdisk command). sda in my primary SATA hard drive, drives will start with '''ata-''' and sdb my second USB hard drivedrives will start with '''usb-'''.<br/>
==Using GParted=Partition/Format=From Compare the HDA desktop (or using VNC), [[Open Terminal as root]] difference between before.txt and type '''gparted''' after.txt to launch determine the GParted applicationnew hard drive(s) device name. This can be done automatically.
Select [[Open Terminal as root|In a Terminal, as root]], execute the device (following:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> diff before.txt after.txt</dev/sdX) that you found above.div>
In the above example, :EXAMPLE: lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-ST31000528AS_6VP08W65 -> ../dev../sdb would be what I would select in GParted.
There At this point, partition and format the hard drive(s) if they are many easy new. For hard drive(s) that contain data to follow guides online on how to use GParted. You should Google for onebe preserved, skip to find one that seems clear to youthe [[Adding_a_second_hard_drive_to_your_HDA#Mount|Mount]] step.
[http://www.mepisguides.com/Mepis-6/Install/gparted/gparted-set==Command-line (Fedora)==To partition.html Herethe hard drive(s), substitute sdX with hard drive device name, such as 's one] that looks simple. Just use ext3 instead of fat32 in you follow that tutorial.'sdb'':
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|terminalIn a Terminal, as root]], type execute the following:<blockquote><div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> parted /dev/sdX</div></blockquote>Up to 2TB, at the ''(parted)''cfdisk prompt, enter:# mklabel msdos (answer ''yes'' if prompted)# mkpart primary 0% 100%# quit<br /dev/sdX>Greater than 2TB, at the ''(parted)'' prompt, enter:# mklabel gpt (answer ''yes'' to launch if prompted)# mkpart primary 0% 100%# quit<br />Verify the cfdisk applicationnew partition was created:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> ls -l /dev/disk/by-id/If you have a GUID</div>:EXAMPLE: lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V -partitioned drive, cfdisk will complain> ../. GUID partitions are not supported./sda Make sure to replace lrwxrwxrwx 1 root root 10 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V-part1 -> ../dev../sdX with the actual device (egsda1 lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-ST31000528AS_6VP08W65 -> .. /dev../sdb) that you found above <span style="color:#FF0000">'''lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-ST31000528AS_6VP08W65-part1 -> ../../sdb1'''</span>
If your hard drive contains existing partitions, select them one by one at the top The new partition is named sdX1 (using up/down arrow keys), then select the i.e. sdb1 in <span style="color:#FF0000">'''[ Delete ]RED''' action (using the left</right arrow keysspan>), then hit ENTER.
You should now only have Free Space listed at Format the toppartition, execute (can substitute ext3):<blockquote><div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> mkfs.ext4 -j /dev/sdX1</div><br/blockquote>Select the '''[ New ]''' action, and accept the default (Primary, and size).
You should now have a single partition listed at Repeat the top, of type Linux.<br[[Adding_a_second_hard_drive_to_your_HDA#Partition/Format|Partition/>Select the '''[ Write Format]''' action, then '''[ Quit ]'''step for each hard drive to be partitioned and formatted.
Now that you partitioned your drive==GParted (Ubuntu)==From the HDA desktop (or using VNC), you need [[Open_Terminal_as_root|In a terminal as root]] and type '''gparted''' to format your newly created partitionlaunch the application.<br/>To format as EXT3, use this command:
<div style="border: 1px solid #A3B1BF; paddingHere's a general introduction on [http: //www.youtube.5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> mkfscom/watch?v=vdWkdrnNGRg YouTube].Just use ''ext3 -j /dev/sdX1</div>'' or ''ext4'' instead of ''fat32'' if you follow that tutorial.
Replace ext3 with ext4 For drives > 2.0 TB, following these steps:* Choose hard disk in the above command to format your dropdown menu (top right)* Select Device > Create Partition Table... > Advanced > (Choose 'gpt')* Create 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:<b>NOTE:</b> [http://gparted.1TB==Here is a work around for org GParted] supports GUID-partitioned drives with partitions over 2.1TB like , however, the new 3TB driveshda-mount script do not support currently.
Page: Repeat the [[Partitions_Over_2.1_TBAdding_a_second_hard_drive_to_your_HDA#Partition/Format|Partition/Format]]step for each hard drive to be partitioned and formatted.
=Mount=Mount the hard drive= ==Using hda-diskmount script==A script is provided with Amahi that will look (s)/partition(s) for unmounted partitions use in your system, and mount any it findsthe HDA.
:'''NOTE:''' If you prefer not to use ''hda-diskmount'', refer to [[Open Terminal as rootAdding_a_second_hard_drive_to_your_HDA#hda-diskmount|In a Terminal, as rootTroubleshooting ''hda-diskmount]], type the following command:.
[[Open Terminal as root|In a Terminal, as root]], execute the following(it will create drive1, drive2, etc and mount the hard drive(s) automatically):<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="borderEXAMPLE: 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/sdb1drive1</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=9d972abc547b073d-1639e591-44df4913-a60eb4fb-668618d40236 7c5084353979 /var/hda/files/drives/sdb1 drive1 ext4 defaults 1 2</strong>
****************************************************************
All Linux, Windows and Mac partitions on non-removable disks have been mounted
</small>
</div>
Do The line in <span style="color:#0000FF">'''notBLUE''' edit </etc/fstab just yet. What span> is what you'll need to copy and add there will depend on how you want to use the extra storagebottom of ''/etc/fstab''. More about that below This is '''REQUIRED''' for the hard drive(s) to be permanently mounted.<br/>Just note down the information in bold There will be multiple lines for multiple hard drive(green, red s) added. Ensure you copy and blue)add '''ONLY''' those which were not present in the ''before. Wetxt''ll use them belowfile.
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 The new hard drive storage space can be used to mount your partition. Since that driver is backward compatiblefor [[Adding_a_second_hard_drive_to_your_HDA#All Shares|All Shares]], it can be safely used to mount ext2[[Adding_a_second_hard_drive_to_your_HDA#Some Shares|Some Shares]], ext3 and ext4 partitionsor the [[Adding_a_second_hard_drive_to_your_HDA#Greyhole Storage Pool|Greyhole Storage Pool]]. Follow the guidance below based on desired usage for each hard drive.
If you get something like ==All Shares==Host ''Disk /dev/dm-0 doesn't contain a valid partition tableALL'' 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 shares on the hda-diskmount scriptnew hard drive.
If you have changed Move all the order of your installed hard drivesshares data to the new drive, replacing path in '''<span style="color: red;">RED</span>''' with the path from the ''hda-diskmount may return the following message'' output line in <span style="color:#0000FF">'''BLUE'''</span>.<br />
[[Open Terminal as root|In a Terminal, as root]], execute the following:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
Ignoring mv /devvar/sda1 - already in hda/files/* <strong style="color:red">/var/etchda/fstab as files/devdrives/sda1This device appears to be commented out of your drive1/etc</fstab. You will need to remove it from there for hda-diskmount to be able to mount it.strong>
</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. :'''NOTE:''' First, get the UUID for each drive by opening There may be a terminal and entering command Ubuntu:{{Code|Code=gstreet@gstreet-MicroServer:~$ sudo blkid[sudo] password for gstreet:/dev'''WARNING''' that can be ignored indicating ''/sda1: LABEL="Seagate-Alpha2TB" UUID="55d9333f-d801-425a-b2af-d65c5966d56f" TYPE="ext4" var/devhda/sdb1: LABEL="Seagate-Beta2TB" UUID="5bd5498f-30c1-4780-948e-ca46656507d2" TYPE="ext4" files/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 cannot be moved to a fifth drive, sde. Take note subdirectory of the UUIDitself'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).
Unmount the new hard drive:
<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 umount /var/hda/files/drives/drive1 ext4 defaults 1 2/</div>Mount the new hard drive permanently as ''/var/hda/files'' by editing ''/etc/fstab'':<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> nano /etc/fstab
</div>
Add the line to ''/etc/fstab'' provided in the ''hda-diskmount'' output in '''<span style="color: blue;">BLUE</span>''' and change the second value (path) to ''/var/hda/files''.
It should look something like the following when lines are added for each of the five :EXAMPLE hda-diskmount output (Original): <span style="color: blue;">UUID=547b073d-e591-4913-b4fb-7c5084353979 <strong>/var/hda/files/drives in this example. Note lines beginning with # are comments /drive1</strong> ext4 defaults 1 2</span>:EXAMPLE hda-diskmount output (Modified): where the remainder of the line is ignored) UUID=547b073d-e591-4913-b4fb-7c5084353979 <strong>/var/hda/files</strong> ext4 defaults 1 2
<div style="border: 1px solid #A3B1BF; paddingEXAMPLE /etc/fstab: .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/hdaetc/files/drives/drive1 ext4 defaults 1 2 #fstab # Drive2 = Seagate-Beta2TB in Microserver Bay 2 from left Created by anaconda on Sat Nov 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 29 01:46:39 2013
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=1ebbf241-528c-465e-889f-acc15400dd8c / ext4 defaults 1 1
UUID=087b15a5-c3ca-4615-b6ee-bf5f399a803e /boot ext4 defaults 1 2
UUID=75346b8e-b162-458c-b0e9-a8d48ec2bc82 swap swap defaults 0 0
UUID=ad85eeb9-18f0-4b85-9bfa-b88a5d1489b3 swap swap defaults 0 0
<span style="color:#0000FF">'''UUID=547b073d-e591-4913-b4fb-7c5084353979 /var/hda/files ext4 defaults 1 2'''</span>
Finally, execute the following:
<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>
The last command will display contents of the new hard drive. All shares are now located on the new hard drive.
Note that ==Some Shares==Host '''SOME''' shares on the hda-dismount command had already added lines to mount my OS new hard drive which had two partitions (root or /, and home). Save file and close.
4Move some shares data to the new drive by executing the following command (replace path in '''<span style="color: red;">RED</span>''' with the path from the ''hda-diskmount'' output line in <span style="color:#0000FF">'''BLUE'''</span>; sharename will be the share to move to the new drive) Save file and reboot machine. <br />
5) Check that [[Open Terminal as root|In a Terminal, as root]], execute the following:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> mv /var/hda/files/<strong>sharename</strong> <strong style="color:red">/var/hda/files/drives have successfully mounted in Amahi hda (Setup - Shares - Storage Pool)/drive1/</strong></div>Repeat the process with every share to be moved to the new drive.
In this case, if all Unmount the new hard drive: <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> umount /var/hda/files/drives mounted successfully, it should look like:/drive1</div>
[[FileMount the new hard drive permanently by editing ''/etc/fstab'': <div style="border: 1px solid #A3B1BF; padding:Gstreet_greyhole_pool.png|options|caption]]5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> nano /etc/fstab==Test your hard drive==Optionally, you can test your new drive for bad blocks.<br/div>Note that this step can take a Add the line to ''long'/etc/fstab' time to complete! You'll probably want to start it provided in the evening, to have it completed ''hda-diskmount'' output in the morning'''<span style="color: blue;">BLUE</span>'''.:EXAMPLE /etc/fstab: # # /etc/fstabTo do so # Created by anaconda on Sat Nov 9 01:46:39 2013 # # Accessible filesystems, [[Open Terminal as root|in a Terminalby reference, as root]]are maintained under '/dev/disk' # See man pages fstab(5), type the following command. Replace findfs(8), mount(8) and/or blkid(8) for more info # UUID=1ebbf241-528c-465e-889f-acc15400dd8c / ext4 defaults 1 1 UUID=087b15a5-c3ca-4615-b6ee-bf5f399a803e /boot ext4 defaults 1 2 UUID=75346b8e-b162-458c-b0e9-a8d48ec2bc82 swap swap defaults 0 0 UUID=ad85eeb9-18f0-4b85-9bfa-b88a5d1489b3 swap swap defaults 0 0 <strong span style="color:green#0000FF">sdb1'''UUID=547b073d-e591-4913-b4fb-7c5084353979 /var/hda/files/drives/drive1 ext4 defaults 1 2'''</strongspan> with Verify the hard drive(s)/partition(greens) value you received from hda-diskmountconfiguration is correct in ''/etc/fstab''.
Next, execute the following:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
e2fsck mount -cn a ls /devvar/<strong style="color:green">sdb1<hda/strong>files/drives/drive1
</div>
The last command will display contents of the new hard drive. All shares are now located on the new hard drive.
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''<u>HDA Dashboard Update</n)?"u><br/>'''Answer The location of each share that was moved to the new hard drive will need updated. Select ''Setup''yesfollowed by the ''Shares'' section. The -cn option we're using can safely be used on mounted filesystemsExpand each share that was moved individually and change the location (path) accordingly.
For example, the original movies location was <span style=Use "color:red">/var/hda/files/movies</span> but the hard drivenew location might be <span style="color:blue">/var/hda/files/drives/drive1/movies</span>.
You Repeat for any other shares that you have a choice here on how moved to use your the new hard drive storage space. We'll offer some examplesVerify these shares are accessible from another machine within your network.
==Use '''NOTE:''' If any services depend on the hard drive location of a moved share, ensure they are configured to use the new share location. For example, if [https://www.amahi.org/apps/dlna DLNA] is installed, check the configuration file to verify it can find the new share location. Secondly, validate that that all such services start correctly and behave as expected. If the service doesn't start, it may be that it's looking for all shares==a specific share location during the service start up.
If you want all your shares to be on your ==Greyhole Storage Pool==Use new hard drive, here's how to do thatfor [[Storage_pooling|Greyhole Storage Pool]].
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 mount the
following command. Replace the path in red with the path you received when you ran hda-diskmount.new hard drive permanently by editing ''/etc/fstab'':<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">nano /
varetc/
hda/files/drives/sdb1/</strong>fstab</div>
YouAdd the line to ''/etc/fstab'' provided in the 'll get a warning about 'hda-diskmount'' output in '''<span style="cannot move `color: blue;">BLUE</span>'''.:EXAMPLE /etc/fstab: # # /etc/fstab # Created by anaconda on Sat Nov 9 01:46:39 2013 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # UUID=1ebbf241-528c-465e-889f-acc15400dd8c / ext4 defaults 1 1 UUID=087b15a5-c3ca-4615-b6ee-bf5f399a803e /boot ext4 defaults 1 2 UUID=75346b8e-b162-458c-b0e9-a8d48ec2bc82 swap swap defaults 0 0 UUID=ad85eeb9-18f0-4b85-9bfa-b88a5d1489b3 swap swap defaults 0 0 <span style="color:#0000FF">'''UUID=547b073d-e591-4913-b4fb-7c5084353979 /var/hda/files/drives/drive1 ext4 defaults 1 2'''</span>Verify the hard drive(s)/partition(s) configuration is correct in ''/etc/fstab'' . Refer to [[Greyhole#Amahi 6|Greyhole (Amahi 6)]] for Ubuntu or [[Greyhole#Amahi 7|Greyhole (Amahi 7)]] for Fedora to a subdirectory of itself"; that is fine, ignore thatconfigure the [[Storage_pooling|Greyhole Storage Pool]].
Next, you'll need to unmount your new =Verify/Test=Verify the hard drive, and remount it as /var/hda/filespartition is mounted.
[[Open Terminal as root|In a Terminal, as root]], execute the following:<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/df -h
</div>
<div style="border: 1px solid #A3B1BF; paddingEXAMPLE: Filesystem Size Used Avail Use% Mounted on /dev/sda5 16G 4.3G 11G 30% / devtmpfs 493M 0 493M 0% /dev tmpfs 498M 84K 498M 1% /dev/shm tmpfs 498M 364K 498M 1% /run tmpfs 498M 0 498M 0% /sys/fs/cgroup tmpfs 498M 1.5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">1M 497M 1% /tmp nano /etcdev/sda1 190M 75M 102M 43% /fstabboot< /dev/sdb1 917G 398G 473G 46% /var/hda/files/drives/div>drive1
In nano, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you The hard drive(the blue ones), and change the second value mount point (the path)should be listed for each hard drive added. If not, then further investigation will be needed to determine the problem.<br/>Replace the second value with '''/var/hda/files'''.
hda-diskmount gave me:=Tips=<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> <span style="color:blue">UUIDMount Order==9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files/The following guide will outline how to manually order hard drives/sdb1</strong> ext4 defaults 1 2</span></div>and mount them automatically on boot.
So I should add this instead[[Open Terminal as root|In a Terminal, as root]], executing the following command to obtain the UUID for each hard drive:
<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 2blkid
</div>
:EXAMPLE:
/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"
Make sure you do '''not''' change anything else from In this case, there are four data drives (sda1, sdb1, sdc1, sdd1) and the blue line you received from hda-diskmount.<br/>It might not be the same thing as the above example; you need Operating system assigned to use the values you've receiveda fifth drive, sde.
Save Take note of the UUID's for each drive. Easiest to cut and exit nano (CTRL-X, Y, ENTER), and try your new mount:paste UUID's straight from the terminal.
Edit ''/etc/fstab'' to mount each drive:
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">
mount -a ls nano /var/hda/filesetc/fstab
</div>
Then '''very carefully''' add the following line for each disk into the end of the fstab file. Ensure correct UUID, hard drive number and hard drive file system (ext4 in this case) are added.
That last command should show you the content of you new hard drive.:EXAMPLE: UUID=55d9333f-d801-425a-b2af-d65c5966d56f /var/hda/files/drives/drive1 ext4 defaults 1 2
That's it. All your shares It should look something like the following when lines are added for each of the five drives in /var/hda/files are now on your new hard drivethis example.
:EXAMPLE: # 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=Use the hard drive for only some shares8d881dcb-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 # #
If you want only some :'''NOTE:''' Lines beginning with # are comments where the remainder of your shares to be on your new hard drive, here's how to do that.the line is ignored
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 Verify there are no issues by executing 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>mount -a
</div>
If there are errors,most likely a line was not added properly. If this is not corrected, the machine may not boot and hang trying to mount the hard drives!
Repeat with every share you want on your new drive. NextOnce there are no errors, you'll need to make the mount permanentreboot machine:
<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/fstabreboot
</div>
Verify the hard drives have successfully mounted in the '''HDA Dashboard'''.
In nanoIf all drives mounted successfully, you'll need to add a new line at the bottom. Take the line that hda-diskmount gave you, and insert that.<br/>it should look something like this (Ubuntu):
So, following previous examples, I should add this:EXAMPLE:[[File:Gstreet_greyhole_pool.png|options|caption]]
<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;">UUIDBad Blocks==9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span>Optionally, you can test your new drive for bad blocks.<br/div>
Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:'''NOTE:''' This can take a ''long'' time to complete! Recommend starting it in the evening so it will be completed the next day.
[[Open Terminal as root|In a Terminal, as root]], execute following command (replace '''sdb1''' with the (<strong style="color:blue">BLUE</strong>) 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;">
mount e2fsck -a ls cn /var/hda/files/drivesdev/'''sdb1'''
</div>
You'll receive a message stating '''WARNING!!!''' ''Running e2fsck on a mounted filesystem may cause SEVERE filesystem damage. Do you really want to continue (y/n)?''<br/>
That last command should show you the content of you new hard driveAnswer ''yes''.The <code>-cn</code> option we're using can safely be used on mounted file systems.==Spin Down Hard Drives==
NowLow power is a good thing to have in servers. If you do not use your server very often, you need may want to update force the location of hard drives to spin down faster than the moved shares within Amahidefault. Go to your <strong>Amahi Dashboard</strong>, click on <strong>Setup</strong>, then <strong>Shares</strong>Here is how.
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 First ensure ''hdparm'' package is shown with a dotted underline) and it will change to an edit box. Update the location to match the new share location. installed: sudo dnf install hdparm
For exampleTo force to spin down after 10 minutes of being idle, the original movies location was: add these lines to <span style="color:red"code>/varetc/hda/files/moviesrc.local</spancode>:<br/pre>The new location might be: <span style="color:blue"># power drives down after 10 minutes idle/sbin/varhdparm -S120 /hdadev/filessda/drivessbin/hdparm -S120 /sdb1dev/moviessdb...</spanpre>
Repeat for any other shares that you have moved. Check that you can access these shares from another machine within your networkMost drives will power down on their own without doing this.
FinallyOnce stopped, if you have any services that depend on the location drive may take as long as 30 seconds to respond to a subsequent disk access, though most drives are much quicker. The encoding of the -S timeout value is somewhat peculiar. A value of these shares, make sure they zero means "timeouts are configured to use disabled": the new share locationdevice will not automatically enter standby mode. For example Values from 1 to 240 specify multiples of 5 seconds, if you have a DLNA server installedyielding timeouts from 5 seconds to 20 minutes. Values from 241 to 251 specify from 1 to 11 units of 30 minutes, check its configuration files yielding timeouts from 30 minutes to make sure that it can find any media folders that have been moved5.5 hours. A value of 252 signifies a timeout of 21 minutes. SecondlyA value of 253 sets a vendor-defined timeout period between 8 and 12 hours, <em>check that all such services start correctly and behave as expected</em>. If the service doesn't start, it may be that it value 254 is testing for a specific location during the service startupreserved. Check the startup files in <strong>/etc/init 255 is interpreted as 21 minutes plus 15 seconds.d</strong> to see if this is the case Note that some older drives may have very different interpretations of these values.
That's it. Your shareIt may make the system run cooler and power efficient (sespecially on a Home Server you are rarely using all of the pool drives at the same time) are now on your new hard drive.
=Troubleshooting=Use ==hda-diskmount==If ''hda-diskmount'' does not mount the hard drive in your Greyhole storage pool==or you prefer to do it manually, complete the following steps:
If you want to add your new Create the mount point (choose one '''NOT''' in use) [[Open Terminal as root|in a Terminal, as root]] by executing the following:<blockquote><div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> mkdir -p /var/hda/files/drives/drive1</div></blockquote>Identify the hard drive to your Greyhole storage pool, here's how mount and copy the UUID from the output that corresponds to do thatthe hard drive (i.e. sdb)<blockquote><div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> ls -l /dev/disk/by-uuid/</div></blockquote>
First, you'll need to make the mount permanent:EXAMPLE: lrwxrwxrwx 1 root root 10 Dec 29 18:10 1b8597e0-5d95-4474-b093-53099c8c81c9 -> ../../sda1 lrwxrwxrwx 1 root root 10 Dec 29 18:10 1c161033-c695-4291-aba1-257d3987edf7 -> ../../dm-0 lrwxrwxrwx 1 root root 10 Dec 29 18:10 b7017251-cb54-438b-92a3-781537c565e6 -> ../../sdb lrwxrwxrwx 1 root root 10 Dec 29 18:10 c1fe62b3-41dc-4a67-8a6b-09f90b7893ba -> ../../dm-1 lrwxrwxrwx 1 root root 10 Dec 29 18:10 e0f5a9bd-f52b-431e-89af-61da70659bdd -> ../.. [[Open Terminal as /dm-2 lrwxrwxrwx 1 root|In a Terminal, as root]], type the following command10 Dec 29 18:10 <span style="color:#FF0000">'''547b073d-e591-4913-b4fb-7c5084353979'''</span> -> ../../sdb1
:The UUID for sdX1 (i.e. sdb1 is <span style="color:#FF0000">'''RED'''</span>).Add the following to the end of ''/etc/fstab'', replacing the UUID as captured in the previous step<blockquote><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></blockquote>:EXAMPLE:In nano # # /etc/fstab # Created by anaconda on Sat Nov 9 01:46:39 2013 # # Accessible filesystems, by reference, youare maintained under '/dev/disk'll need to add a new line at the bottom. Take the line that hda-diskmount gave you # See man pages fstab(5), findfs(8), mount(8) and insert that.<br/>or blkid(8) for more info # UUID=1ebbf241-528c-465e-889f-acc15400dd8c / ext4 defaults 1 1 UUID=087b15a5-c3ca-4615-b6ee-bf5f399a803e /boot ext4 defaults 1 2 UUID=75346b8e-b162-458c-b0e9-a8d48ec2bc82 swap swap defaults 0 0So, following previous examples, I should add this UUID=ad85eeb9-18f0-4b85-9bfa-b88a5d1489b3 swap swap defaults 0 0 <span style="color:#0000FF">'''UUID=547b073d-e591-4913-b4fb-7c5084353979 /var/hda/files/drives/drive1 ext4 defaults 1 2'''</span>
<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 The new entry will be mounted as ''/var/hda/files/drives/drive1'' (i.e. sdb1 ext4 defaults 1 2in '''</spanstyle="color:#0000FF">BLUE</divspan>''')
Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:Mount the hard drive<blockquote><div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin:
3px 3px 1em 3px;">
mount -a
</div></blockquote> Finally:If all goes well, you'll need to configure Greyhole to select your new partitionthere should not be any output. To configure GreyholeIf there are errors, Advanced Settings must be enabled under [http://hda/setup?sub=settings&tab=setting Setup > Settings]stop and diagnose the problem.
In the Accomplish [[http:Adding_Hard_Drives_101#Verify/Test|Verify/hda/setup?sub=disk_pooling&tab=share Shares > Storage Pool pageTest]] of your Amahi dashboard, you'll see a list of step to ensure the hard drive is properly mounted partitions, with checkboxes next to each, allowing you to include those partitions in your storage pool.<br />
You should now have a new row in there, referring Repeat this process for each hard drive to /var/hda/files/drives/sdb1be mounted.
Select it (click ==Partitions > 2.1TB==If by following this tutorial you are unable to mount hard drives with partitions > 2.1TB, refer to the checkbox)[[Partitions_Over_2.1_TB|Partitions over 2.1TB]] guidance.
That=Help=If you need assistance, please post in the [https://forums.amahi.org Amahi Forums] or receive '''LIVE'''s itsupport on the [http://talk.amahi. Your new hard drive just increased your Greyhole storage pool capacityorg Amahi IRC channel].
