Changes

From Amahi Wiki
Jump to: navigation, search
A secondary hard drive (fat32, ntfs, etc) can be added <center>{{MessageBox|backgroundcolor = #faa|image =Warning.png|heading =WARNING|message = This is recommended only for additional storage in your Amahi HDA. First thing's first'Advanced'' users, make sure your drive is connected properly and detected by the biosproceed with caution.}}</center><div style="border: 1px solid #A3B1BF; padding: . 8em 1em; background-color: #E6F2FF; margin: 0px 1em;">
It can be configured to mount permanently using the '''NOTE:''' The Amahi [httphttps://wikiwww.amahi.org/images/c/c6apps/Diskmounter.sh diskmounterdisk-wizard Disk Wizard] script application (thanks to Dennis Kaarsemaker and Luigi CapriottiAmahi 8 or greater '''ONLY''')provides this capability from the Dashboard UI.
* Execute the script as ''root'' and answer YES to the prompt </div><br />The purpose of this tutorial is to make the drive writable to all users. * Once completepartitioning, formatting, reboot and mounting hard drives in the secondary drive should automatically mount. * As user ''root'', edit '''''/etc/fstab''''' to change location of shared ''//hda'' folders Amahi server simple for those new to the secondary driveLinux.
This is what the script added for my drive: In order to keep this process simple, it's important 'Added by diskmounter utility'' NOT''/dev/sdb1 /var/hda/files vfat rw,user,fmask=0111,dmask=0000 0 0'' to connect additional hard drive(s) until the end of the [[Adding_a_second_hard_drive_to_your_HDA#Preparation|Preparation]] step.
I changed second path to '''''=Disclaimer=* [https:/var/hda/files''''' to enable all shared files to www.amahi.org Amahi] cannot be stored on held responsible for any data breakage or destruction arising from the secondary hard driveuse or misuse of this script. We provide it as a service in good will. This is You accept this automatically if you use the default path for ''//hda'' file storage systemscript.
=If the script doesn't work for you=* [http://en.wikipedia.org/wiki/GUID_Partition_Table GUID-partitioned] hard drives (such as those previously used in a Mac or have GPT partition tables) are not supported in this tutorial.
These instructions are adapted from * [http://en.wikipedia.org/wiki/GNU_nano nano] is used as the command-line text editor (refer to [http://www.mjmwiredhowtogeek.netcom/resourceshowto/mjm42980/the-fedorabeginners-f9guide-to-nano-the-linux-command-line-text-editor/ beginners guide to nano] as needed).html#ntfs here]
If you're planning to mount =Prerequisites=[[Open Terminal as root|In a NTFS diskTerminal, you'll need to make sure you have ntfs-3gas root]], fuse and fuse libs all verify disk tools are installed. If not, login as root and runby 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-3gutil-linux-ng parted nano</div>
Then use fdisk to find the disk by running fdisk -l :'''NOTE:''' <code>yum</code> (this is a lower case L not a 1deprecated)has been replaced with <code>dnf</code> as the package manager for Fedora 23 and greater.Ubuntu <div style="border: 1px solid #A3B1BF; padding: . You may have to give the path (5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left"> sudo apt-get -y install gparted</sbin/fdisk) to make it work.div>
:'''NOTE:''' $ Hard drives must be formatted as '''MBR''' not '''GUID/sbin/fdisk GPT''' for ''hda-ldiskmount'' to work correctly.
This should return =Preparation=[[Open_Terminal_as_root|In terminal as root]], execute the needed information about all your disksfollowing to capture current hard drive configuration:<div style="border: 1px solid #A3B1BF; padding: . Look out for your newly attached 5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> ls -l /dev/disk/by-id/ > before. In my case in among the results I can find:txt cat before.txt</div>
Disk /dev/sdb: 120EXAMPLE: lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V -> ..0GB 120034123776 bytes255 heads, 63 sectors/track../sda lrwxrwxrwx 1 root root 10 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V-part1 -> ../. etc etc./sda1
I know my disk is 120GB so thatPower ''OFF'' the HDA and install/connect any additional hard drive(s the right one. This tells us the name of the new disk which is "sdb" in my case). Running $ sudo /sbin/fdisk -lu /dev<br /sdb | grep NTFS>
=Identify=Power ''ON'' the HDA and collect data about the new hard drive configuration..will give you a break down of partitions. In my case, there's just one partition Again, sdb1, so save this is the partition I will mountto a text file for reference.
Now we can go on to create the mount points if needs be. But because my disk contains all my music, I want it to be mounted [[Open_Terminal_as_root|In a terminal as if it were my local "Music" folderroot]], so for me execute the mount point already exists. But if just want following to access your disk easily you could just as easily mount it anywherecapture current hard drive configuration:<div style="border: 1px solid #A3B1BF; padding: . Commonly mount points are put in either 5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> ls -l /mntdev/ or disk/mediaby-id/> after. It doesn't matter where - just be consistent when you are doing thistxt cat after. txtTo do this run these commands as root: $ cd /mnt</ $ mkdir my_ntfs_diskdiv>
Substituting my_ntfs_disk for whatever you want to call it:EXAMPLE: 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
Now we can mount the disk in the desired location. Again as root run this command:'''FYI:''' $ mount IDE/dev/sdb1 /mnt/my_ntfs_drive SATA hard drives will start with '''ata-t ntfs''' and USB hard drives will start with '''usb-3g -r -o umask=0222'''.<br/>
This command will make =Partition/Format=Compare the difference between before.txt and after.txt to determine the mounted new hard drive read only(s) device name. That's great if that's what you want, but for me, since I want to save my music there, I need it to This can be read and writeabledone automatically. For this you'll use:
[[Open Terminal as root|In a Terminal, as root]], execute the following:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> $ mount /devdiff before.txt after.txt</sdb1 /mnt/my_ntfs_drive -t ntfs-3g -rw -o umask=0000div>
or in my case:EXAMPLE: lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-ST31000528AS_6VP08W65 -> ../../sdb
At this point, partition and format the hard drive(s) if they are new. $ mount /dev/sdb1 /home/USERNAME/Music -t ntfs-3g -rw -o umask=0000For hard drive(s) that contain data to be preserved, skip to the [[Adding_a_second_hard_drive_to_your_HDA#Mount|Mount]] step.
because I want it mounted in my "Music" file.==Command-line (Fedora)==To partition the hard drive(s), substitute sdX with hard drive device name, such as ''sdb'':
Remember in both of these commands you[[Open Terminal as root|In a Terminal, as root]], 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)'' prompt, enter:# mklabel msdos (answer ''yes'' if prompted)# mkpart primary 0% 100%# quit<br />Greater than 2TB, at the ''(parted)'' prompt, enter:# mklabel gpt (answer ''yes''ll need to substitute sdb1 with whatever if prompted)# mkpart primary 0% 100%# quit<br />Verify the new partition namewas created:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> ls -l /dev/disk/by-id/</div>:EXAMPLE: 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 <span style="color:#FF0000">'''lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-ST31000528AS_6VP08W65-part1 -> ../number is on your machine. And in the second command USERNAME is your linux username./sdb1'''</span>
If you now go to your desktop, you should see the drive The new partition is mounted therenamed sdX1 (i. Click on it to see the contents are theree. If yousdb1 in <span style="color:#FF0000">'ve mounted it as say So far so good? Ok, let's continue'RED'''</span>).
What you've achieved so far is a temporary mounting of Format the drive/partition. That shows it , execute (can be done but you'll need to make it permanent otherwise when you reboot it'll disappear againsubstitute ext3):<blockquote><div style="border: 1px solid #A3B1BF; padding: . For this you need to edit fstab with your favourite text editor5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> mkfs. As root run:ext4 -j /dev/sdX1</div></blockquote>
$ gedit Repeat the [[Adding_a_second_hard_drive_to_your_HDA#Partition/etcFormat|Partition/fstabFormat]] step for each hard drive to be partitioned and formatted.
A text editor window will pop up==GParted (Ubuntu)==From the HDA desktop (or using VNC), [[Open_Terminal_as_root|In a terminal as root]] and type '''gparted''' to launch the application. Enter this on the last line:
Here's a general introduction on [http:/dev/sdb1 www.youtube.com/mnt/my_ntfs_drive ntfs-3g ro,defaults,umaskwatch?v=0222 0 0vdWkdrnNGRg YouTube]. Just use ''ext3'' or ''ext4'' instead of ''fat32'' if you follow that tutorial.
For drives > 2.0 TB, following these steps:* change Choose hard disk in the dropdown menu (top right)* Select Device > Create Partition Table... > Advanced > (Choose 'gpt''ro to rw''' and '''umask=0222 to umask=0000''' if you want it to be writable.)* Create partition
You'll need to do this for every partition, so if you have several partitions on sdb, the last lines of you fstab may look something like this
:<b>NOTE:</devb> [http:/sdb1 /mnt/my_ntfs_drive_C ntfs-3g ro,defaults,umask=0222 0 0/dev/sdb2 /mnt/my_ntfs_drive_D ntfsgparted.org GParted] supports GUID-3g ropartitioned drives,defaultshowever,umask=0222 0 0/dev/sdb3 /mnt/my_ntfs_drive_E ntfsthe hda-3g ro,defaults,umask=0222 0 0mount script do not support currently.
When you reboot, you should find your data where you want itRepeat the [[Adding_a_second_hard_drive_to_your_HDA#Partition/Format|Partition/Format]] step for each hard drive to be partitioned and formatted.
= Guide to Adding a Hard Drive to Fedora Mount=Mount the hard drive(s)/partition(s) for use in the HDA.
This is a good guide, for advanced users:'''NOTE:''' If you prefer not to use ''hda-diskmount'', refer to adding a hard drive to Fedora:[[Adding_a_second_hard_drive_to_your_HDA#hda-diskmount|Troubleshooting ''hda-diskmount]].
[[Open Terminal as root|In a Terminal, as root]], execute the following(it will create drive1, drive2, etc httpand mount the hard drive(s) automatically):<div style="border: 1px solid #A3B1BF; padding://fedoranews.org/tchung/storage5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> hda-diskmount</div>
And a good fedora 9 guide here:EXAMPLE: **************************************************************** 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/drive1</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=547b073d-e591-4913-b4fb-7c5084353979 /var/hda/files/drives/drive1 ext4 defaults 1 2</strong> **************************************************************** All Linux, including a section Windows and Mac partitions on adding a hard drive here:non-removable disks have been mounted
httpThe line in <span style="color:#0000FF">'''BLUE'''</span> is what you need to copy and add to the bottom of ''/etc/fstab''. This is '''REQUIRED''' for the hard drive(s) to be permanently mounted. There will be multiple lines for multiple hard drive(s) added. Ensure you copy and add '''ONLY''' those which were not present in the ''before.txt'' file.  The new hard drive storage space can be used for [[Adding_a_second_hard_drive_to_your_HDA#All Shares|All Shares]], [[Adding_a_second_hard_drive_to_your_HDA#Some Shares|Some Shares]], or 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. ==All Shares==Host '''ALL''' shares on the new hard drive. Move all the shares data to the new drive, replacing path in '''<span style="color: red;">RED</span>''' with the path from the ''hda-diskmount'' 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;"> mv /var/hda/files/* <strong style="color:red">/var/hda/files/drives/drive1/</strong></div> :'''NOTE:''' There may be a '''WARNING''' that can be ignored indicating ''/var/hda/files/drives cannot be moved to a subdirectory of itself''. 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/drive1/</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''. :EXAMPLE hda-diskmount output (Original): <span style="color: blue;">UUID=547b073d-e591-4913-b4fb-7c5084353979 <strong>/var/hda/files/drives/drive1</strong> ext4 defaults 1 2</span>:EXAMPLE hda-diskmount output (Modified): UUID=547b073d-e591-4913-b4fb-7c5084353979 <strong>/var/hda/files</strong> ext4 defaults 1 2 :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 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. ==Some Shares==Host '''SOME''' shares on the new hard drive.  Move 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).<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;"> mv /var/hda/files/<strong>sharename</strong> <strong style="color:red">/var/hda/files/drives/drive1/</strong></div>Repeat the process with every share to be moved to the new drive. 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/drive1</div> Mount the new hard drive permanently 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>'''.: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''. Next, 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/drives/drive1</div>The last command will display contents of the new hard drive. All shares are now located on the new hard drive. '''<u>HDA Dashboard Update</u><br />'''The location of each share that was moved to the new hard drive will need updated. Select ''Setup'' followed by the ''Shares'' section. Expand each share that was moved individually and change the location (path) accordingly.  For example, the original movies location was <span style="color:red">/var/hda/files/movies</span> but the new location might be <span style="color:blue">/var/hda/files/drives/drive1/movies</span>. Repeat for any other shares that you have moved to the new hard drive. Verify these shares are accessible from another machine within your network. '''NOTE:''' If any services depend on the location of a moved share, ensure they are configured to use the new share location. For example, if [https://www.mjmwiredamahi.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 a specific share location during the service start up. ==Greyhole Storage Pool==Use new hard drive for [[Storage_pooling|Greyhole Storage Pool]]. [[Open Terminal as root|In a Terminal, as root]], mount the new hard drive permanently 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>'''.: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 configure the [[Storage_pooling|Greyhole Storage Pool]]. =Verify/Test=Verify the hard drive/partition is mounted. [[Open Terminal as root|In a Terminal, as root]], execute the following:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> df -h</div> :EXAMPLE: 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.1M 497M 1% /tmp /dev/sda1 190M 75M 102M 43% /boot /dev/sdb1 917G 398G 473G 46% /var/hda/files/drives/drive1 The hard drive(s) and the mount point (path) should be listed for each hard drive added. If not, then further investigation will be needed to determine the problem.<br /> =Tips===Mount Order==The following guide will outline how to manually order hard drives and mount them automatically on boot. [[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;"> blkid</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" In this case, there are 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. 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;"> nano /etc/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.  :EXAMPLE: UUID=55d9333f-d801-425a-b2af-d65c5966d56f /var/hda/files/drives/drive1 ext4 defaults 1 2 It should look something like the following when lines are added for each of the five drives in this 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=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 # # :'''NOTE:''' Lines beginning with # are comments where the remainder of the line is ignored  Verify there are no issues by executing the following:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> 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! Once there are no errors, reboot machine:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"> reboot</div>Verify the hard drives have successfully mounted in the '''HDA Dashboard'''. If all drives mounted successfully, it should look something like this (Ubuntu): :EXAMPLE:[[File:Gstreet_greyhole_pool.png|options|caption]] ==Bad Blocks==Optionally, you can test your new drive for bad blocks.<br/> :'''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;"> e2fsck -cn /dev/'''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/> Answer ''yes''. The <code>-cn</code> option we're using can safely be used on mounted file systems.==Spin Down Hard Drives== Low power is a good thing to have in servers. If you do not use your server very often, you may want to force the hard drives to spin down faster than the default. Here is how. First ensure ''hdparm'' package is installed: sudo dnf install hdparm To force to spin down after 10 minutes of being idle, add these lines to <code>/etc/rc.local</code>:<pre># power drives down after 10 minutes idle/sbin/hdparm -S120 /dev/sda/sbin/hdparm -S120 /dev/sdb...</pre> Most drives will power down on their own without doing this. Once stopped, the 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 zero means "timeouts are disabled": the device will not automatically enter standby mode. Values from 1 to 240 specify multiples of 5 seconds, yielding timeouts from 5 seconds to 20 minutes. Values from 241 to 251 specify from 1 to 11 units of 30 minutes, yielding timeouts from 30 minutes to 5.5 hours. A value of 252 signifies a timeout of 21 minutes. A value of 253 sets a vendor-defined timeout period between 8 and 12 hours, and the value 254 is reserved. 255 is interpreted as 21 minutes plus 15 seconds. Note that some older drives may have very different interpretations of these values. It may make the system run cooler and power efficient (especially on a Home Server you are rarely using all of the pool drives at the same time). =Troubleshooting===hda-diskmount==If ''hda-diskmount'' does not mount the hard drive or you prefer to do it manually, complete the following steps: 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 mount and copy the UUID from the output that corresponds to the 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> :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 -> ../../dm-2 lrwxrwxrwx 1 root root 10 Dec 29 18:10 <span style="color:#FF0000">'''547b073d-e591-4913-b4fb-7c5084353979'''</span> -> ../../sdb1 :The UUID for sdX1 (i.e.netsdb1 is <span style="color:#FF0000">'''RED'''</resourcesspan>).Add the following to the end of ''/mjmetc/fstab'', replacing the UUID as captured in the previous step<blockquote><div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-fedoracolor: #E6F2FF; margin: 3px 3px 1em 3px;"> nano /etc/fstab</div></blockquote>:EXAMPLE: # # /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-f9528c-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> :The new entry will be mounted as ''/var/hda/files/drives/drive1'' (i.e. sdb1 in '''<span style="color:#0000FF">BLUE</span>''') 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>:If all goes well, there should not be any output. If there are errors, stop and diagnose the problem. Accomplish [[Adding_Hard_Drives_101#Verify/Test|Verify/Test]] step to ensure the hard drive is properly mounted.<br /> Repeat this process for each hard drive to be mounted. ==Partitions > 2.1TB==If by following this tutorial you are unable to mount hard drives with partitions > 2.1TB, refer to the [[Partitions_Over_2.1_TB|Partitions over 2.1TB]] guidance. =Help=If you need assistance, please post in the [https://forums.amahi.org Amahi Forums] or receive '''LIVE''' support on the [http://talk.amahi.org Amahi IRC channel].html
12,424

edits