Amahi Wiki - User contributions [en]

https://wiki.amahi.org/api.php?action=feedcontributions&feedformat=atom&user=TheGeebs Amahi Wiki - User contributions [en] 2026-04-07T15:41:18Z User contributions MediaWiki 1.34.2 https://wiki.amahi.org/index.php?title=Mount_Shares_Locally&diff=46513 Mount Shares Locally 2011-09-10T17:21:56Z

<p>TheGeebs: </p> <hr /> <div>Mounting your Samba shares locally is useful when you are using Greyhole, and want to write or in any way work with those files locally. Greyhole data should only be accessed through shares, so mounting those shares locally is an easy way to work with Greyhole data safely.<br /> <br /> * As '''root:''' Install the mount_shares_locally initd script:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; overflow: scroll"><br /> curl -o /etc/init.d/mount_shares_locally http://dl.dropbox.com/u/3022105/Amahi/mount_shares_locally<br /> chmod +x /etc/init.d/mount_shares_locally<br /> chkconfig --add mount_shares_locally<br /> </div><br /> <br /> * Edit /etc/init.d/mount_shares_locally (as user root) in a text editor, and replace ''your_username'' (on line 12) with your username. Example '''username="amahi"'''<br /> {{Code|Code= nano /etc/init.d/mount_shares_locally}}<br /> * Create the ''/home/your_username/.smb_credentials'' file. This is a simple text file (use your favorite text editor).<br /> {{Code|Code= nano /home/YourHDA_username/.smb_credentials}}<br /> *Enter the following:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> username=your_username<br /> password=your_password<br /> domain=HOME<br /> </div><br /> '''NOTE:''' your_username and your_password in the .smb_credentials file needs to be the original username and password you created when you installed fedora.<br /> <br /> *To test your new mounts, you can execute '''service mount_shares_locally start'''<br/><br /> You will find the mounted shares in ''/mnt/samba/*''<br/><br /> '''service mount_shares_locally stop''' will unmount the local shares.<br/><br /> <br /> Note: if you used /etc/rc.local and /etc/fstab to mount shares locally in the past, you can remove what you added in those files now. The above initd script replaces all this.<br /> <br /> <br /> == Unable to mount localy after upgrading to Amahi6 ==<br /> If you try to run mount using this script after you upgraded to Amahi6 you might get greeted by this type of error.<br /> <br /> [root@localhost ~]# /etc/init.d/mount_shares_locally start<br /> Mounting Samba shares locally: /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> [ OK ]<br /> <br /> It's easily fixed by installing the missing dependency.<br /> <br /> {{Code|yum install cifs-utils}}<br /> <br /> Now it should work fine to run<br /> <br /> {{Code|/etc/init.d/mount_shares_locally start}}<br /> <br /> == MySQL Problems With Newer Versions of Greyhole ==<br /> <br /> Since Greyhole moved from SQL Lite to MySQL, you may hit a problem where Greyhole and the mount_shares_locally script both attempt to start before MySQL in bootup, leading to the services not starting properly. If this happens, you can try this to fix it:<br /> <br /> {{Code|ls /etc/rc.3/}}<br /> * Look for any entries marked S-1. If there are any, they need to be removed. Run the following as root:<br /> <br /> {{Code|rm S-1*}}</div>

TheGeebs https://wiki.amahi.org/index.php?title=Mount_Shares_Locally&diff=46507 Mount Shares Locally 2011-09-10T17:02:26Z

<p>TheGeebs: </p> <hr /> <div>Mounting your Samba shares locally is useful when you are using Greyhole, and want to write or in any way work with those files locally. Greyhole data should only be accessed through shares, so mounting those shares locally is an easy way to work with Greyhole data safely.<br /> <br /> * As '''root:''' Install the mount_shares_locally initd script:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; overflow: scroll"><br /> curl -o /etc/init.d/mount_shares_locally http://dl.dropbox.com/u/3022105/Amahi/mount_shares_locally<br /> chmod +x /etc/init.d/mount_shares_locally<br /> chkconfig --add mount_shares_locally<br /> </div><br /> <br /> * Edit /etc/init.d/mount_shares_locally (as user root) in a text editor, and replace ''your_username'' (on line 12) with your username.<br /> <br /> * Create the ''/home/your_username/.smb_credentials'' file. This is a simple text file (use your favorite text editor).<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> username=your_username<br /> password=your_password<br /> domain=HOME<br /> </div><br /> '''NOTE:''' your_username and your_password in the .smb_credentials file needs to be the original username and password you created when you installed fedora.<br /> <br /> To test your new mounts, you can execute '''service mount_shares_locally start'''<br/><br /> You will find the mounted shares in ''/mnt/samba/*''<br/><br /> '''service mount_shares_locally stop''' will unmount the local shares.<br/><br /> <br /> Note: if you used /etc/rc.local and /etc/fstab to mount shares locally in the past, you can remove what you added in those files now. The above initd script replaces all this.<br /> <br /> <br /> == Unable to mount localy after upgrading to Amahi6 ==<br /> If you try to run mount using this script after you upgraded to Amahi6 you might get greeted by this type of error.<br /> <br /> [root@localhost ~]# /etc/init.d/mount_shares_locally start<br /> Mounting Samba shares locally: /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> [ OK ]<br /> <br /> It's easily fixed by installing the missing dependency.<br /> <br /> {{Code|yum install cifs-utils}}<br /> <br /> Now it should work fine to run<br /> <br /> {{Code|/etc/init.d/mount_shares_locally start}}<br /> <br /> == MySQL Problems With Newer Versions of Greyhole ==<br /> <br /> Since Greyhole moved from SQL Lite to MySQL, you may hit a problem where Greyhole and the mount_shares_locally script both attempt to start before MySQL in bootup, leading to the services not starting properly. If this happens, you can try this to fix it:<br /> <br /> {{Code|ls /etc/rc.3/}}<br /> * Look for any entries marked S-1. If there are any, they need to be removed. Run the following as root:<br /> <br /> {{Code|rm S-1*}}</div>

TheGeebs https://wiki.amahi.org/index.php?title=Mount_Shares_Locally&diff=46501 Mount Shares Locally 2011-09-10T17:01:15Z

<p>TheGeebs: Need to be root to execute commands</p> <hr /> <div>Mounting your Samba shares locally is useful when you are using Greyhole, and want to write or in any way work with those files locally. Greyhole data should only be accessed through shares, so mounting those shares locally is an easy way to work with Greyhole data safely.<br /> <br /> * As ''root'' Install the mount_shares_locally initd script:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; overflow: scroll"><br /> curl -o /etc/init.d/mount_shares_locally http://dl.dropbox.com/u/3022105/Amahi/mount_shares_locally<br /> chmod +x /etc/init.d/mount_shares_locally<br /> chkconfig --add mount_shares_locally<br /> </div><br /> <br /> * Edit /etc/init.d/mount_shares_locally (as user root) in a text editor, and replace ''your_username'' (on line 12) with your username.<br /> <br /> * Create the ''/home/your_username/.smb_credentials'' file. This is a simple text file (use your favorite text editor).<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> username=your_username<br /> password=your_password<br /> domain=HOME<br /> </div><br /> '''NOTE:''' your_username and your_password in the .smb_credentials file needs to be the original username and password you created when you installed fedora.<br /> <br /> To test your new mounts, you can execute '''service mount_shares_locally start'''<br/><br /> You will find the mounted shares in ''/mnt/samba/*''<br/><br /> '''service mount_shares_locally stop''' will unmount the local shares.<br/><br /> <br /> Note: if you used /etc/rc.local and /etc/fstab to mount shares locally in the past, you can remove what you added in those files now. The above initd script replaces all this.<br /> <br /> <br /> == Unable to mount localy after upgrading to Amahi6 ==<br /> If you try to run mount using this script after you upgraded to Amahi6 you might get greeted by this type of error.<br /> <br /> [root@localhost ~]# /etc/init.d/mount_shares_locally start<br /> Mounting Samba shares locally: /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> /etc/init.d/mount_shares_locally: line 27: /sbin/mount.cifs: No such file or directory<br /> [ OK ]<br /> <br /> It's easily fixed by installing the missing dependency.<br /> <br /> {{Code|yum install cifs-utils}}<br /> <br /> Now it should work fine to run<br /> <br /> {{Code|/etc/init.d/mount_shares_locally start}}<br /> <br /> == MySQL Problems With Newer Versions of Greyhole ==<br /> <br /> Since Greyhole moved from SQL Lite to MySQL, you may hit a problem where Greyhole and the mount_shares_locally script both attempt to start before MySQL in bootup, leading to the services not starting properly. If this happens, you can try this to fix it:<br /> <br /> {{Code|ls /etc/rc.3/}}<br /> * Look for any entries marked S-1. If there are any, they need to be removed. Run the following as root:<br /> <br /> {{Code|rm S-1*}}</div>

TheGeebs https://wiki.amahi.org/index.php?title=Sudo&diff=46495 Sudo 2011-09-10T16:46:50Z

<p>TheGeebs: </p> <hr /> <div>=Enable '''sudo''' for a user=<br /> If you receive the message: "'HDA_username' is not in the sudoers file. This incident will be reported."<br /> <br /> ==Command Line Edit==<br /> * Login as root {{Code|Code= su}}<br /> * Copy and Paste: {{Code|Code= echo 'loginname ALL=(ALL) ALL' >> /etc/sudoers }}<br /> * Where ''loginname'' is your user account.<br /> Use 'ALL=(ALL) NOPASSWD:ALL' if you don't want to be prompted a password.<br /> If you are prompted for a password with 'sudo' it is the user password, not root.<br /> <br /> ==Manual Edit of Sudoers File==<br /> * Login as root<br /> * Run: visudo<br /> * Find a line that says<br /> root ALL=(ALL) ALL<br /> * Add another line after that by typing 'o' an entering<br /> <br /> username ALL=(ALL) ALL<br /> * But use your user name instead of username above</div>

TheGeebs https://wiki.amahi.org/index.php?title=Adding_a_second_hard_drive_to_your_HDA&diff=46423 Adding a second hard drive to your HDA 2011-09-07T01:53:26Z

<p>TheGeebs: </p> <hr /> <div>{{MessageBox|<br /> backgroundcolor = red|<br /> image =Warning.png|<br /> heading =WARNING|<br /> message = This is recommended only for advanced users, proceed with caution.}}<br /> [[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.<br /> <br /> More hard drives can be added in your Amahi HDA for additional storage space.<br /> <br /> We'll detail how to add such hard drives, and how to put them to good use.<br /> <br /> =Important Notes=<br /> <br /> * This is an how-to on how to add additional drives to your HDA.<br /> * 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.<br /> * 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><br /> <br /> =Make sure your drive is detected by Fedora=<br /> <br /> Open a Terminal, and type the following command:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 0 1em;"><br /> ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"<br /> </div><br /> <br /> Look for the line that matches the hard drive you added.<br /> <br /> IDE and SATA hard drives will start with '''ata-''' and USB hard drives will start with '''usb-'''.<br/><br /> Look for your hard drive model and serial number.<br /> <br /> Example:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> [gb@hda ~]$ ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"<br /> ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V<br /> ata-ST31000528AS_6VP08W65<br /> ata-ST3750640A_3QD0LJN8<br /> ata-ST3750640A_5QD27A57<br /> ata-WDC_WD10EADS-00L5B1_WD-WCAU4C700358<br /> usb-ST310003_33AS_9E1CA6FFFFFF-0:0<br /> usb-ST375064_0A_2009031309E2-0:0<br /> </div><br /> <br /> =Install prerequisites=<br /> <br /> [[Open Terminal as root|In a Terminal, as root]], type the following (two) commands:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left"><br /> yum -y install pmount fuse fuse-libs ntfs-3g gparted util-linux-ng<br /> </div><br /> <br /> Drives must be formatted as '''MBR''' not '''GUID/GPT''' for hda-diskmount to recognize the disk.<br /> <br /> =Partition and format the hard drive=<br /> <br /> 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.<br /> <br /> You should (unless you have a good reason not to) use GParted to partition and format your hard drive.<br/><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]].<br /> <br /> You'll probably want to create a single partition, and format it as ''ext3''.<br/><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/><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/><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].<br /> <br /> 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]]:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> ls -l /dev/disk/by-id/<br /> </div><br /> <br /> Find the row corresponding to your hard drive, and look at the end of the line to identify the correct device to use.<br /> <br /> Example:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><small><br /> [gb@hda ~]$ ls -l /dev/disk/by-id/<br /> total 0<br /> lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V -> ../../sda<br /> lrwxrwxrwx 1 root root 10 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V-part1 -> ../../sda1<br /> lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-ST31000528AS_6VP08W65 -> ../../sdb<br /> </small><br /> </div><br /> <br /> 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.<br /> <br /> ==Using GParted==<br /> From the HDA desktop (or using VNC), [[Open Terminal as root]] and type '''gparted''' to launch the GParted application.<br /> <br /> Select the device (/dev/sdX) that you found above.<br /> <br /> In the above example, /dev/sdb would be what I would select in GParted.<br /> <br /> 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.<br /> <br /> [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.<br /> <br /> Note that gparted supports GUID-partitioned drives, however, these directions and script do not support it at the moment.<br /> <br /> ==Using cfdisk==<br /> From a [[Open Terminal as root|terminal, as root]], type '''cfdisk /dev/sdX''' to launch the cfdisk application.<br /> <br /> If you have a GUID-partitioned drive, cfdisk will complain. GUID partitions are not supported.<br /> <br /> Make sure to replace /dev/sdX with the actual device (eg. /dev/sdb) that you found above.<br /> <br /> 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.<br /> <br /> You should now only have Free Space listed at the top.<br/><br /> Select the '''[ New ]''' action, and accept the default (Primary, and size).<br /> <br /> You should now have a single partition listed at the top, of type Linux.<br/><br /> Select the '''[ Write ]''' action, then '''[ Quit ]'''.<br /> <br /> Now that you partitioned your drive, you need to format your newly created partition.<br/><br /> To format as EXT3, use this command:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mkfs.ext3 -j /dev/sdX1<br /> </div><br /> <br /> Replace ext3 with ext4 in the above command to format your partition as EXT4 instead of EXT3.<br /> <br /> '''/dev/sdX1''' in the above command refers to the partition your created in cfdisk.<br/><br /> Go back in cfdisk, and check the ''Name'' column if you're unsure.<br/><br /> If you see ''sdb1'' in the name column, you should use '''/dev/sdb1''' in the above command.<br /> <br /> ==Partition over 2.1TB==<br /> Here is a work around for drives with partitions over 2.1TB like the new 3TB drives.<br /> <br /> Page: [[Partitions_Over_2.1_TB]]<br /> <br /> =Mount the hard drive=<br /> <br /> A script is provided with Amahi that will look for unmounted partitions in your system, and mount any it finds.<br /> <br /> [[Open Terminal as root|In a Terminal, as root]], type the following command:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> hda-diskmount<br /> </div><br /> <br /> Example:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;"><br /> <small><br /> [root@hda ~]$ hda-diskmount<br /> ****************************************************************<br /> Ignoring /dev/sda1 - already in /etc/fstab or mounted<br /> ****************************************************************<br /> Mounted /dev/<strong style="color:green">sdb1</strong> as '<strong style="color:red">/var/hda/files/drives/sdb1</strong>' (read-write)<br /> You may want your system to mount it every time you boot.<br /> To do so, add this line VERY CAREFULLY to /etc/fstab and reboot:<br /> <strong style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</strong><br /> ****************************************************************<br /> All Linux, Windows and Mac partitions on non-removable disks have been mounted<br /> </small><br /> </div><br /> <br /> 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/><br /> Just note down the information in bold (green, red and blue). We'll use them below.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> ==Test your hard drive==<br /> Optionally, you can test your new drive for bad blocks.<br/><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.<br /> <br /> 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.<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> e2fsck -cn /dev/<strong style="color:green">sdb1</strong><br /> </div><br /> <br /> 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/><br /> Answer ''yes''. The -cn option we're using can safely be used on mounted filesystems.<br /> <br /> =Use the hard drive=<br /> <br /> You have a choice here on how to use your new hard drive storage space. We'll offer some examples.<br /> <br /> ==Use the hard drive for all shares==<br /> <br /> If you want all your shares to be on your new hard drive, here's how to do that.<br /> <br /> First, you'll want to move all you previous shares data, if any, into your new drive.<br/><br /> You only need to do this next command if you have data that you care about in the /var/hda/files/* folders.<br/><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.<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mv /var/hda/files/* <strong style="color:red">/var/hda/files/drives/sdb1/</strong><br /> </div><br /> You'll get a warning about "cannot move `/var/hda/files/drives' to a subdirectory of itself"; that is fine, ignore that.<br /> <br /> Next, you'll need to unmount your new hard drive, and remount it as /var/hda/files<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> umount /var/hda/files/drives/sdb1/<br /> </div><br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> nano /etc/fstab<br /> </div><br /> <br /> 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/><br /> Replace the second value with '''/var/hda/files'''.<br /> <br /> hda-diskmount gave me:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> <span style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files/drives/sdb1</strong> ext4 defaults 1 2</span><br /> </div><br /> <br /> So I should add this instead:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files</strong> ext4 defaults 1 2<br /> </div><br /> <br /> Make sure you do '''not''' change anything else from the blue line you received from hda-diskmount.<br/><br /> It might not be the same thing as the above example; you need to use the values you've received.<br /> <br /> Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mount -a<br /> ls /var/hda/files/<br /> </div><br /> <br /> That last command should show you the content of you new hard drive.<br /> <br /> That's it. All your shares in /var/hda/files are now on your new hard drive.<br /> <br /> ==Use the hard drive for only some shares==<br /> <br /> If you want only some of your shares to be on your new hard drive, here's how to do that.<br /> <br /> First, you'll want to move your previous shares data, if any, into your new drive.<br/><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/><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).<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mv /var/hda/files/<strong>something</strong> <strong style="color:red">/var/hda/files/drives/sdb1/</strong><br /> </div><br /> <br /> Repeat with every share you want on your new drive.<br /> <br /> Next, you'll need to make the mount permanent<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> umount /var/hda/files/drives/sdb1<br/><br /> nano /etc/fstab<br /> </div><br /> <br /> 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/><br /> <br /> So, following previous examples, I should add this:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;"><br /> <span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span><br /> </div><br /> <br /> Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mount -a<br /> ls /var/hda/files/drives/sdb1<br /> </div><br /> <br /> That last command should show you the content of you new hard drive.<br /> <br /> That's it. Your share(s) are now on your new hard drive.<br /> <br /> ==Use the hard drive in your Greyhole storage pool==<br /> <br /> If you want to add your new hard drive to your Greyhole storage pool, here's how to do that.<br /> <br /> First, you'll need to make the mount permanent. [[Open Terminal as root|In a Terminal, as root]], type the following command:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> umount /var/hda/files/drives/sdb1<br /> nano /etc/fstab<br /> </div><br /> <br /> 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/><br /> <br /> So, following previous examples, I should add this:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;"><br /> <span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span><br /> </div><br /> <br /> Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mount -a<br /> </div><br /> <br /> 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 &gt; Settings].<br /> <br /> In the [http://hda/setup?sub=disk_pooling&tab=share Shares &gt; 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.<br /> <br /> You should now have a new row in there, referring to /var/hda/files/drives/sdb1.<br /> <br /> Select it (click the checkbox).<br /> <br /> That's it. Your new hard drive just increased your Greyhole storage pool capacity.</div>

TheGeebs https://wiki.amahi.org/index.php?title=Adding_a_second_hard_drive_to_your_HDA&diff=46417 Adding a second hard drive to your HDA 2011-09-07T01:51:32Z

<p>TheGeebs: Added reminder that hda-diskmount doesn't support GUID and added a link to GUID mounting wiki page</p> <hr /> <div>{{MessageBox|<br /> backgroundcolor = red|<br /> image =Warning.png|<br /> heading =WARNING|<br /> message = This is recommended only for advanced users, proceed with caution.}}<br /> [[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.<br /> <br /> More hard drives can be added in your Amahi HDA for additional storage space.<br /> <br /> We'll detail how to add such hard drives, and how to put them to good use.<br /> <br /> =Important Notes=<br /> <br /> * This is an how-to on how to add additional drives to your HDA.<br /> * 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.<br /> * 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><br /> <br /> =Make sure your drive is detected by Fedora=<br /> <br /> Open a Terminal, and type the following command:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 0 1em;"><br /> ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"<br /> </div><br /> <br /> Look for the line that matches the hard drive you added.<br /> <br /> IDE and SATA hard drives will start with '''ata-''' and USB hard drives will start with '''usb-'''.<br/><br /> Look for your hard drive model and serial number.<br /> <br /> Example:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> [gb@hda ~]$ ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"<br /> ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V<br /> ata-ST31000528AS_6VP08W65<br /> ata-ST3750640A_3QD0LJN8<br /> ata-ST3750640A_5QD27A57<br /> ata-WDC_WD10EADS-00L5B1_WD-WCAU4C700358<br /> usb-ST310003_33AS_9E1CA6FFFFFF-0:0<br /> usb-ST375064_0A_2009031309E2-0:0<br /> </div><br /> <br /> =Install prerequisites=<br /> <br /> [[Open Terminal as root|In a Terminal, as root]], type the following (two) commands:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left"><br /> yum -y install pmount fuse fuse-libs ntfs-3g gparted util-linux-ng<br /> </div><br /> <br /> Drives must be formatted as '''MBR''' not '''GUID/GPT''' for hda-diskmount to recognize the disk.<br /> <br /> =Partition and format the hard drive=<br /> <br /> 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.<br /> <br /> You should (unless you have a good reason not to) use GParted to partition and format your hard drive.<br/><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]].<br /> <br /> You'll probably want to create a single partition, and format it as ''ext3''.<br/><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/><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/><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].<br /> <br /> 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]]:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> ls -l /dev/disk/by-id/<br /> </div><br /> <br /> Find the row corresponding to your hard drive, and look at the end of the line to identify the correct device to use.<br /> <br /> Example:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><small><br /> [gb@hda ~]$ ls -l /dev/disk/by-id/<br /> total 0<br /> lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V -> ../../sda<br /> lrwxrwxrwx 1 root root 10 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V-part1 -> ../../sda1<br /> lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-ST31000528AS_6VP08W65 -> ../../sdb<br /> </small><br /> </div><br /> <br /> 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.<br /> <br /> ==Using GParted==<br /> From the HDA desktop (or using VNC), [[Open Terminal as root]] and type '''gparted''' to launch the GParted application.<br /> <br /> Select the device (/dev/sdX) that you found above.<br /> <br /> In the above example, /dev/sdb would be what I would select in GParted.<br /> <br /> 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.<br /> <br /> [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.<br /> <br /> Note that gparted supports GUID-partitioned drives, however, these directions and script do not support it at the moment.<br /> <br /> ==Using cfdisk==<br /> From a [[Open Terminal as root|terminal, as root]], type '''cfdisk /dev/sdX''' to launch the cfdisk application.<br /> <br /> If you have a GUID-partitioned drive, cfdisk will complain. GUID partitions are not supported.<br /> <br /> Make sure to replace /dev/sdX with the actual device (eg. /dev/sdb) that you found above.<br /> <br /> 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.<br /> <br /> You should now only have Free Space listed at the top.<br/><br /> Select the '''[ New ]''' action, and accept the default (Primary, and size).<br /> <br /> You should now have a single partition listed at the top, of type Linux.<br/><br /> Select the '''[ Write ]''' action, then '''[ Quit ]'''.<br /> <br /> Now that you partitioned your drive, you need to format your newly created partition.<br/><br /> To format as EXT3, use this command:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mkfs.ext3 -j /dev/sdX1<br /> </div><br /> <br /> Replace ext3 with ext4 in the above command to format your partition as EXT4 instead of EXT3.<br /> <br /> '''/dev/sdX1''' in the above command refers to the partition your created in cfdisk.<br/><br /> Go back in cfdisk, and check the ''Name'' column if you're unsure.<br/><br /> If you see ''sdb1'' in the name column, you should use '''/dev/sdb1''' in the above command.<br /> <br /> ==Partition over 2.1TB== .<br/><br /> Here is a work around for drives with partitions over 2.1TB like the new 3TB drives. .<br/><br /> Page: [[Partitions_Over_2.1_TB]]<br /> <br /> =Mount the hard drive=<br /> <br /> A script is provided with Amahi that will look for unmounted partitions in your system, and mount any it finds.<br /> <br /> [[Open Terminal as root|In a Terminal, as root]], type the following command:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> hda-diskmount<br /> </div><br /> <br /> Example:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;"><br /> <small><br /> [root@hda ~]$ hda-diskmount<br /> ****************************************************************<br /> Ignoring /dev/sda1 - already in /etc/fstab or mounted<br /> ****************************************************************<br /> Mounted /dev/<strong style="color:green">sdb1</strong> as '<strong style="color:red">/var/hda/files/drives/sdb1</strong>' (read-write)<br /> You may want your system to mount it every time you boot.<br /> To do so, add this line VERY CAREFULLY to /etc/fstab and reboot:<br /> <strong style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</strong><br /> ****************************************************************<br /> All Linux, Windows and Mac partitions on non-removable disks have been mounted<br /> </small><br /> </div><br /> <br /> 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/><br /> Just note down the information in bold (green, red and blue). We'll use them below.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> ==Test your hard drive==<br /> Optionally, you can test your new drive for bad blocks.<br/><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.<br /> <br /> 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.<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> e2fsck -cn /dev/<strong style="color:green">sdb1</strong><br /> </div><br /> <br /> 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/><br /> Answer ''yes''. The -cn option we're using can safely be used on mounted filesystems.<br /> <br /> =Use the hard drive=<br /> <br /> You have a choice here on how to use your new hard drive storage space. We'll offer some examples.<br /> <br /> ==Use the hard drive for all shares==<br /> <br /> If you want all your shares to be on your new hard drive, here's how to do that.<br /> <br /> First, you'll want to move all you previous shares data, if any, into your new drive.<br/><br /> You only need to do this next command if you have data that you care about in the /var/hda/files/* folders.<br/><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.<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mv /var/hda/files/* <strong style="color:red">/var/hda/files/drives/sdb1/</strong><br /> </div><br /> You'll get a warning about "cannot move `/var/hda/files/drives' to a subdirectory of itself"; that is fine, ignore that.<br /> <br /> Next, you'll need to unmount your new hard drive, and remount it as /var/hda/files<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> umount /var/hda/files/drives/sdb1/<br /> </div><br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> nano /etc/fstab<br /> </div><br /> <br /> 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/><br /> Replace the second value with '''/var/hda/files'''.<br /> <br /> hda-diskmount gave me:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> <span style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files/drives/sdb1</strong> ext4 defaults 1 2</span><br /> </div><br /> <br /> So I should add this instead:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files</strong> ext4 defaults 1 2<br /> </div><br /> <br /> Make sure you do '''not''' change anything else from the blue line you received from hda-diskmount.<br/><br /> It might not be the same thing as the above example; you need to use the values you've received.<br /> <br /> Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mount -a<br /> ls /var/hda/files/<br /> </div><br /> <br /> That last command should show you the content of you new hard drive.<br /> <br /> That's it. All your shares in /var/hda/files are now on your new hard drive.<br /> <br /> ==Use the hard drive for only some shares==<br /> <br /> If you want only some of your shares to be on your new hard drive, here's how to do that.<br /> <br /> First, you'll want to move your previous shares data, if any, into your new drive.<br/><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/><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).<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mv /var/hda/files/<strong>something</strong> <strong style="color:red">/var/hda/files/drives/sdb1/</strong><br /> </div><br /> <br /> Repeat with every share you want on your new drive.<br /> <br /> Next, you'll need to make the mount permanent<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> umount /var/hda/files/drives/sdb1<br/><br /> nano /etc/fstab<br /> </div><br /> <br /> 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/><br /> <br /> So, following previous examples, I should add this:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;"><br /> <span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span><br /> </div><br /> <br /> Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mount -a<br /> ls /var/hda/files/drives/sdb1<br /> </div><br /> <br /> That last command should show you the content of you new hard drive.<br /> <br /> That's it. Your share(s) are now on your new hard drive.<br /> <br /> ==Use the hard drive in your Greyhole storage pool==<br /> <br /> If you want to add your new hard drive to your Greyhole storage pool, here's how to do that.<br /> <br /> First, you'll need to make the mount permanent. [[Open Terminal as root|In a Terminal, as root]], type the following command:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> umount /var/hda/files/drives/sdb1<br /> nano /etc/fstab<br /> </div><br /> <br /> 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/><br /> <br /> So, following previous examples, I should add this:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;"><br /> <span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span><br /> </div><br /> <br /> Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mount -a<br /> </div><br /> <br /> 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 &gt; Settings].<br /> <br /> In the [http://hda/setup?sub=disk_pooling&tab=share Shares &gt; 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.<br /> <br /> You should now have a new row in there, referring to /var/hda/files/drives/sdb1.<br /> <br /> Select it (click the checkbox).<br /> <br /> That's it. Your new hard drive just increased your Greyhole storage pool capacity.</div>

TheGeebs https://wiki.amahi.org/index.php?title=Adding_a_second_hard_drive_to_your_HDA&diff=46411 Adding a second hard drive to your HDA 2011-09-06T16:29:49Z

<p>TheGeebs: Removed an extra space before ls</p> <hr /> <div>{{MessageBox|<br /> backgroundcolor = red|<br /> image =Warning.png|<br /> heading =WARNING|<br /> message = This is recommended only for advanced users, proceed with caution.}}<br /> [[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.<br /> <br /> More hard drives can be added in your Amahi HDA for additional storage space.<br /> <br /> We'll detail how to add such hard drives, and how to put them to good use.<br /> <br /> =Important Notes=<br /> <br /> * This is an how-to on how to add additional drives to your HDA.<br /> * 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.<br /> * 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><br /> <br /> =Make sure your drive is detected by Fedora=<br /> <br /> Open a Terminal, and type the following command:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 0 1em;"><br /> ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"<br /> </div><br /> <br /> Look for the line that matches the hard drive you added.<br /> <br /> IDE and SATA hard drives will start with '''ata-''' and USB hard drives will start with '''usb-'''.<br/><br /> Look for your hard drive model and serial number.<br /> <br /> Example:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> [gb@hda ~]$ ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"<br /> ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V<br /> ata-ST31000528AS_6VP08W65<br /> ata-ST3750640A_3QD0LJN8<br /> ata-ST3750640A_5QD27A57<br /> ata-WDC_WD10EADS-00L5B1_WD-WCAU4C700358<br /> usb-ST310003_33AS_9E1CA6FFFFFF-0:0<br /> usb-ST375064_0A_2009031309E2-0:0<br /> </div><br /> <br /> =Install prerequisites=<br /> <br /> [[Open Terminal as root|In a Terminal, as root]], type the following (two) commands:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left"><br /> yum -y install pmount fuse fuse-libs ntfs-3g gparted util-linux-ng<br /> </div><br /> <br /> =Partition and format the hard drive=<br /> <br /> 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.<br /> <br /> You should (unless you have a good reason not to) use GParted to partition and format your hard drive.<br/><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]].<br /> <br /> You'll probably want to create a single partition, and format it as ''ext3''.<br/><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/><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/><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].<br /> <br /> 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]]:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> ls -l /dev/disk/by-id/<br /> </div><br /> <br /> Find the row corresponding to your hard drive, and look at the end of the line to identify the correct device to use.<br /> <br /> Example:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><small><br /> [gb@hda ~]$ ls -l /dev/disk/by-id/<br /> total 0<br /> lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V -> ../../sda<br /> lrwxrwxrwx 1 root root 10 2010-02-18 03:24 ata-Hitachi_HDS722020ALA330_JK1131YAGDU37V-part1 -> ../../sda1<br /> lrwxrwxrwx 1 root root 9 2010-02-18 03:24 ata-ST31000528AS_6VP08W65 -> ../../sdb<br /> </small><br /> </div><br /> <br /> 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.<br /> <br /> ==Using GParted==<br /> From the HDA desktop (or using VNC), [[Open Terminal as root]] and type '''gparted''' to launch the GParted application.<br /> <br /> Select the device (/dev/sdX) that you found above.<br /> <br /> In the above example, /dev/sdb would be what I would select in GParted.<br /> <br /> 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.<br /> <br /> [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.<br /> <br /> Note that gparted supports GUID-partitioned drives, however, these directions and script do not support it at the moment.<br /> <br /> ==Using cfdisk==<br /> From a [[Open Terminal as root|terminal, as root]], type '''cfdisk /dev/sdX''' to launch the cfdisk application.<br /> <br /> If you have a GUID-partitioned drive, cfdisk will complain. GUID partitions are not supported.<br /> <br /> Make sure to replace /dev/sdX with the actual device (eg. /dev/sdb) that you found above.<br /> <br /> 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.<br /> <br /> You should now only have Free Space listed at the top.<br/><br /> Select the '''[ New ]''' action, and accept the default (Primary, and size).<br /> <br /> You should now have a single partition listed at the top, of type Linux.<br/><br /> Select the '''[ Write ]''' action, then '''[ Quit ]'''.<br /> <br /> Now that you partitioned your drive, you need to format your newly created partition.<br/><br /> To format as EXT3, use this command:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mkfs.ext3 -j /dev/sdX1<br /> </div><br /> <br /> Replace ext3 with ext4 in the above command to format your partition as EXT4 instead of EXT3.<br /> <br /> '''/dev/sdX1''' in the above command refers to the partition your created in cfdisk.<br/><br /> Go back in cfdisk, and check the ''Name'' column if you're unsure.<br/><br /> If you see ''sdb1'' in the name column, you should use '''/dev/sdb1''' in the above command.<br /> <br /> =Mount the hard drive=<br /> <br /> A script is provided with Amahi that will look for unmounted partitions in your system, and mount any it finds.<br /> <br /> [[Open Terminal as root|In a Terminal, as root]], type the following command:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> hda-diskmount<br /> </div><br /> <br /> Example:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;"><br /> <small><br /> [root@hda ~]$ hda-diskmount<br /> ****************************************************************<br /> Ignoring /dev/sda1 - already in /etc/fstab or mounted<br /> ****************************************************************<br /> Mounted /dev/<strong style="color:green">sdb1</strong> as '<strong style="color:red">/var/hda/files/drives/sdb1</strong>' (read-write)<br /> You may want your system to mount it every time you boot.<br /> To do so, add this line VERY CAREFULLY to /etc/fstab and reboot:<br /> <strong style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</strong><br /> ****************************************************************<br /> All Linux, Windows and Mac partitions on non-removable disks have been mounted<br /> </small><br /> </div><br /> <br /> 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/><br /> Just note down the information in bold (green, red and blue). We'll use them below.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> ==Test your hard drive==<br /> Optionally, you can test your new drive for bad blocks.<br/><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.<br /> <br /> 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.<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> e2fsck -cn /dev/<strong style="color:green">sdb1</strong><br /> </div><br /> <br /> 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/><br /> Answer ''yes''. The -cn option we're using can safely be used on mounted filesystems.<br /> <br /> =Use the hard drive=<br /> <br /> You have a choice here on how to use your new hard drive storage space. We'll offer some examples.<br /> <br /> ==Use the hard drive for all shares==<br /> <br /> If you want all your shares to be on your new hard drive, here's how to do that.<br /> <br /> First, you'll want to move all you previous shares data, if any, into your new drive.<br/><br /> You only need to do this next command if you have data that you care about in the /var/hda/files/* folders.<br/><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.<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mv /var/hda/files/* <strong style="color:red">/var/hda/files/drives/sdb1/</strong><br /> </div><br /> You'll get a warning about "cannot move `/var/hda/files/drives' to a subdirectory of itself"; that is fine, ignore that.<br /> <br /> Next, you'll need to unmount your new hard drive, and remount it as /var/hda/files<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> umount /var/hda/files/drives/sdb1/<br /> </div><br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> nano /etc/fstab<br /> </div><br /> <br /> 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/><br /> Replace the second value with '''/var/hda/files'''.<br /> <br /> hda-diskmount gave me:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> <span style="color:blue">UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files/drives/sdb1</strong> ext4 defaults 1 2</span><br /> </div><br /> <br /> So I should add this instead:<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> UUID=9d972abc-1639-44df-a60e-668618d40236 <strong>/var/hda/files</strong> ext4 defaults 1 2<br /> </div><br /> <br /> Make sure you do '''not''' change anything else from the blue line you received from hda-diskmount.<br/><br /> It might not be the same thing as the above example; you need to use the values you've received.<br /> <br /> Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mount -a<br /> ls /var/hda/files/<br /> </div><br /> <br /> That last command should show you the content of you new hard drive.<br /> <br /> That's it. All your shares in /var/hda/files are now on your new hard drive.<br /> <br /> ==Use the hard drive for only some shares==<br /> <br /> If you want only some of your shares to be on your new hard drive, here's how to do that.<br /> <br /> First, you'll want to move your previous shares data, if any, into your new drive.<br/><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/><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).<br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mv /var/hda/files/<strong>something</strong> <strong style="color:red">/var/hda/files/drives/sdb1/</strong><br /> </div><br /> <br /> Repeat with every share you want on your new drive.<br /> <br /> Next, you'll need to make the mount permanent<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> umount /var/hda/files/drives/sdb1<br/><br /> nano /etc/fstab<br /> </div><br /> <br /> 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/><br /> <br /> So, following previous examples, I should add this:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;"><br /> <span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span><br /> </div><br /> <br /> Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mount -a<br /> ls /var/hda/files/drives/sdb1<br /> </div><br /> <br /> That last command should show you the content of you new hard drive.<br /> <br /> That's it. Your share(s) are now on your new hard drive.<br /> <br /> ==Use the hard drive in your Greyhole storage pool==<br /> <br /> If you want to add your new hard drive to your Greyhole storage pool, here's how to do that.<br /> <br /> First, you'll need to make the mount permanent. [[Open Terminal as root|In a Terminal, as root]], type the following command:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> umount /var/hda/files/drives/sdb1<br /> nano /etc/fstab<br /> </div><br /> <br /> 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/><br /> <br /> So, following previous examples, I should add this:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left;"><br /> <span style="color: blue;">UUID=9d972abc-1639-44df-a60e-668618d40236 /var/hda/files/drives/sdb1 ext4 defaults 1 2</span><br /> </div><br /> <br /> Save and exit nano (CTRL-X, Y, ENTER), and try your new mount:<br /> <br /> <div style="border: 1px solid #A3B1BF; padding: .5em 1em; background-color: #E6F2FF; margin: 3px 3px 1em 3px;"><br /> mount -a<br /> </div><br /> <br /> 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 &gt; Settings].<br /> <br /> In the [http://hda/setup?sub=disk_pooling&tab=share Shares &gt; 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.<br /> <br /> You should now have a new row in there, referring to /var/hda/files/drives/sdb1.<br /> <br /> Select it (click the checkbox).<br /> <br /> That's it. Your new hard drive just increased your Greyhole storage pool capacity.</div>

TheGeebs https://wiki.amahi.org/index.php?title=Greyhole&diff=46399 Greyhole 2011-09-05T22:34:29Z

<p>TheGeebs: Fixed Emptying Attic link</p> <hr /> <div>[[Category:apps]]<br /> <div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;"><br /> '''NEW:''' [http://code.google.com/p/greyhole/wiki/MigrateFromWHS Widows Home Server Drive Extender Migration Guide]<br /> <br /> '''NEW:''' [[Greyhole troubleshooting]] guide<br /> </div><br /> <br /> <br /> == What is Greyhole ==<br /> <br /> [http://greyhole.pommepause.com/ Greyhole] is Amahi's [[Storage pooling]] technology. Storage Pooling combines the space of multiple disk drives and makes them look as if they were all part of a single pool of disk space.<br /> Specifically, Greyhole:<br /> * Combines the space from multiple drives into a single volume<br /> * Distributes files across all drives in the pool<br /> * Creates multiple copies of files in admin-specified shares<br /> <br /> This feature is installed by default, but requires a few simple steps to begin utilizing the features.<br /> <br /> You can add additional drives to your hda and prepare them for use in Greyhole by following [[Adding a second hard drive to your HDA|this tutorial]].<br /> <br /> To add a drive to your Greyhole storage pool. Open your HDA dashboard and navigate to the Shares tab. Then click on the Storage Pool sub-category. You will see a page similar to the one below.<br /> <br /> == Important Warnings ==<br /> <div style="color:darkred">You should '''never''' change or delete files in the shared directories (''/var/hda/files/*'' by default) directly on the HDA, using the terminal, or the Gnome file browser, for the shares for which you checked the ''Uses pool'' option in the Amahi dashboard. If you want to work with files on Greyhole shares on the HDA, you should [[Mount Shares Locally]].<br/><br /> You should be safe reading existing files directly, or adding new files directly, as long as don't care that your new files will only be moved into the storage pool during the next check, which runs automatically at midnight (or manually using ''greyhole --fsck''). Until then, your new files will be stored in your shared directories (normally ''/var/hda/files/share_name/'').<br /> <br /> Also, touching anything inside the '''gh''' directories that Greyhole creates at the root of your partitions is a recipe for disaster.<br /> <br /> We [[Greyhole not on root | strongly discourage you from using the root partition in a drive pool]].<br /> </div><br/><br/><br /> <br /> == First things first ==<br /> <br /> You need to go in the Settings tab, and enable '''Advanced Settings'''.<br/><br /> Without Advanced Settings enabled, you won't see the following page and options.<br /> <br /> == For Storage Pool (Partitions) ==<br /> <br /> [[File:Storage_Pool_1.png|600px|thumb|left]]<br /> <br /> Select the drives you want available for your storage pool.<br /> <br /> == Greyhole options ==<br /> <br /> The next step is to select the share you want to replicate across the pool.<br /> <br /> From the Shares tab, select the Shares sub-catagory. We chose the Pictures share for this tutorial.<br /> <br /> [[File:Greyhole_Options_1.png|600px|thumb|left]]<br /> <br /> Check the option for "Uses pool" and choose the number of drives to replicate this share. In this instance we have chosen to use all drives available to the greyhole pool.<br /> <br /> Note: Greyhole is not a backup solution. If a file is removed, all copies are removed.<br /> <br /> == Greyhole advanced options ==<br /> <br /> You can further configure Greyhole by manually editing the following file:<br/><br /> '''/var/hda/platform/html/config/greyhole.yml'''<br /> <br /> To see what options are available, and what they do, refer to the [http://greyhole.googlecode.com/svn/trunk/greyhole.example.conf sample greyhole.conf] provided with Greyhole.<br /> <br /> greyhole.yml is in in YAML format. Most of it should be easy enough to modify. The only exception would be the sticky_files (and optional sticky_into) options.<br/><br /> Here's an example of how those should appear:<br /> <br /> To specify the following to Greyhole in greyhole.conf:<br /> <br /> {{Text|Text=sticky_files <nowiki>=</nowiki> Music/<br /> sticky_files <nowiki>=</nowiki> Videos/Movies/<br /> stick_into <nowiki>=</nowiki> /mnt/hdd1/gh<br /> stick_into <nowiki>=</nowiki> /mnt/hdd5/gh<br /> sticky_files <nowiki>=</nowiki> Backups/CrashPlan/<br /> stick_into <nowiki>=</nowiki> /mnt/hdd0/gh}}<br /> <br /> one should specify this in the greyhole.yml file, where '''precise indentation matters''':<br /> <br /> {{Text|Text=sticky_files: <br /> - - Music/<br /> - - Videos/Movies/<br /> - - /mnt/hdd1/gh<br /> - /mnt/hdd5/gh<br /> - - Backups/CrashPlan/<br /> - - /mnt/hdd0/gh}}<br /> <br /> For your changes to be effective, you'll need to force Amahi to regenerate the greyhole.conf file. You can do so by editing a share, clicking it's path, and just clicking the Save button without actually changing the path.<br /> <br /> == Copying your data into Greyhole shares the first time ==<br /> <br /> When you start using Greyhole, you might want to copy or move all your exiting files into your new shares that use the storage pool.<br /> <br /> Note: This is not necessary if your files are already in Amahi shares. If they are there, and you enable the ''Uses pool'' option in the Amahi dashboard, the files will start getting moved around into the drives in your storage pool during the night (starting at midnight), when the nightly storage pool check starts.<br/><br /> The instructions below are for users who have more data to copy into the Greyhole shares than their currently free space in the /var/hda/files/ folder.<br /> <br /> One way to do that is to mount the shares that use the Greyhole storage pool, either on the HDA itself, or on a client computer on your local network, and copy your data from their existing location into the mounted shares.<br /> This can be time consuming, but it is the safest way to use Greyhole.<br /> <br /> Another way to move your files from their current location into the storage pool is to share their current location using an Amahi share that ''Uses pool'', then let Greyhole nightly check move the files from there into the pool.<br /> <br /> Here's a more detailed walkthrough for this method:<br /> <br /> # Setup the Greyhole Storage Pool in the Amahi dashboard, Shares > Storage Pool page.<br /> # Go in the Shares > Shares page. In there, make sure you have an existing share for each share you have data for. Create new ones if you need, remove the ones you don't need.<br /> # Edit the ''path'' of each of those shares, and enter the current location of your existing data. For example, the Movies share could have a path = ''/media/External Drive/Movies''<br /> # Enable the ''Uses pool'' option for each of your shares, and select the number of extra copies you'd like, if any.<br /> # Now, you either need to wait for Greyhole'S nightly check to start, or you can start it manually from a terminal, as root, using this command: greyhole --fsck<br /> # Monitor /var/log/greyhole.log to see when the ''fsck'' operation is done.<br /> # Once ''fsck'' is done, your data has now been moved into the Greyhole storage pool (in the drives you selected in Shares > Storage Pool). All that should be left in the previous location of your data (''/media/External Drive/Movies'' from the previous example) should be symbolic links pointing to the new file copies. If the previous location is just empty directories (no symlinks), do not panic. This is normal if your previous location is an NTFS or FAT partition (drive).<br /> # Move all those directories / symlinks from there into the correct folders in /var/hda/files/share_name<br /> # Back in the Amahi dashboard, edit the path of the shares once again, and put back ''/var/hda/files/share_name'' (i.e. the folders where you moved the symbolic links).<br /> # If you used an NTFS or FAT partition for the previous location, you'll need another fsck to create the symlinks where they should be. Either wait for midnight, or launch it manually, from a command line, as root: ''greyhole --fsck''<br /> <br /> You're done. All your existing data is now stored in the various drives included in your storage pool, and are accessible via the Samba shares you have defined in the Amahi dashboard.<br /> <br /> <br /> == Adding a new drive to your HDA and storage pool ==<br /> This wiki page discusses how to add a new drive to your HDA and to your greyhole storage pool<br /> [[Adding_a_second_hard_drive_to_your_HDA]]<br /> <br /> <br /> == Drive Mounted as /media ==<br /> Including any drive mounted as /media/Something in your storage pool is usually a bad idea.<br/><br /> Those mounts are created by the ''gnome-automounter'', which requires you to be logged in into X (Gnome) to become available.<br/><br /> This will create issues with Greyhole, which expects drives to always be available, and will take action when some of them are missing.<br /> <br /> Follow this guide to [[Adding a second hard drive to your HDA|permanently mount your drives]], before you include them in your storage pool.<br /> <br /> == Monitoring Greyhole ==<br /> Sometimes you might want to monitor what Greyhole is doing, for example when writing data to your greyhole shares for the first time. Here are a few commands you can type in a terminal to follow along.<br /> <br /> '''Scrolling view of total Greyhole operations queue:'''<br /> {{Code|while [ 1 <nowiki>==</nowiki> 1 ]; do greyhole --view-queue <nowiki>|</nowiki> grep Total; sleep 60; done}}<br /> <br /> '''Scrolling log of what files Greyhole is working on right now:'''<br /> {{Code|tail -f /var/log/greyhole.log}}<br /> <br /> == Convert Greyhole from SQLite to MySQL ==<br /> Greyhole is already using MySQL in Amahi 6.0<br /> <br /> Greyhole was previously using SQLite as the default database for queueing up tasks on Amahi. This was unqie to Amahi as Greyhole was originally designed to use MySQL for this task.<br /> <br /> There are some major performance benefits to using MySQL over SQLite when writing large amounts of files. Switching can be especially useful when moving data to greyhole shares for the first time. For now there is a script you can run if you want to switch over. This script has been tested to be safe while greyhole is working but should be used with discresion.<br /> <br /> ''To Convert to MySQL, run as root:''<br /> <br /> {{Code|/usr/share/greyhole/db_migration-sqlite2mysql.sh}}<br /> <br /> To see what DB engine is Greyhole using, do this:<br /> <br /> {{Code|grep db_engine /etc/greyhole.conf}}<br /> <br /> == Disable Greyhole ==<br /> For those who do not use Greyhole, you can disable it. This is based on the fact you never have used it by enabling 'Uses pool' on any share. Recommend using extreme caution as this could have unpredictable results.<br /> <br /> Perform the following steps as user '''root''':<br /> <br /> {{Code|chkconfig greyhole off<br /> rm /etc/monit.d/greyhole.conf<br /> service monit restart<br /> service greyhole stop}}<br /> <br /> '''DO NOT''' attempt to remove the Greyhole package as it is a dependency of the HDA software. Doing so will break your HDA.<br /> <br /> = Testing and Reliability =<br /> <br /> Check out the [[Greyhole grinder]] to help make Greyhole rock solid.<br /> <br /> = Reconnect the Greyhole storage pool after re-install of Fedora / Amahi =<br /> <br /> <br /> * Disconnect all data drives before you reinstall. This will prevent you from destroying them by mistake during the Fedora/Amahi install!<br /> * Install Amahi per the regular instructions.<br /> * Connect the data drives, and use hda-diskmount to remount all of them.<br /> Note that if you can, it would be faster if you can re-mount the drives in the same paths they used to have.<br /> <br /> '''Example:''' If you have one 1TB and one 2TB, and the 1TB was mounted as /var/hda/files/drives/drive1, and the 2TB was mounted as /var/hda/files/drives/drive2, it would be better to re-mount that like that on your new HDA. If you mount them otherwise, it will still work, but Greyhole will work a while to re-build the links in your share before they can be usable.<br /> * Select the drives in the Amahi Dashboard: Setup > Shares > Storage Pool<br /> * Re-create your shares in the Amahi Dashboard: Setup > Shares.<br /> Make sure to select 'Use Pool', and select the correct number of extra copies.<br /> If you don't remember all the shares you had, just check inside the 'gh' folder found at the root of your drives to get a reminder!<br /> <br /> '''Example:'''<br /> {{Code|ls -1 /var/hda/files/drives/*/gh/ <nowiki>|</nowiki> grep -v : <nowiki>|</nowiki> sort -u}}<br /> <br /> * Launch a fsck to have Greyhole rebuild your shares.<br /> {{Code|greyhole --fsck}}<br /> <br /> Until this completes, some of your files will be missing from your shares.<br /> <br /> = Greyhole Troubleshooting =<br /> <br /> Page: [[Greyhole troubleshooting]]<br /> <br /> = Landing Zone Considerations =<br /> <br /> The landing zone or LZ is the area where files arrive first before being distributed to their final destination. See details in the [[Greyhole landing zone]] page.<br /> <br /> = Manually updating Greyhole for Amahi =<br /> Page: [[Greyhole updating]]<br /> <br /> = Emptying Greyhole Attic =<br /> {{Code|greyhole --empty-attic}}<br /> About the attic: The attic is used like a Recycle Bin, or Trash.<br /> That means you'll need to manually empty it once in a while.<br /> To do so, use the --empty-attic parameter (see above).<br /> Another option is to create a 'Greyhole Attic' Samba share.<br /> More details about that here: https://github.com/gboudreau/Greyhole/wiki/AboutTrash<br /> <br /> = Reference =<br /> Good [http://revxatlarge.blogspot.com/2011/04/restoring-deleted-files-in-greyhole-and.html article] on Greyhole with terms explained.</div>

TheGeebs https://wiki.amahi.org/index.php?title=Greyhole&diff=46393 Greyhole 2011-09-05T22:32:03Z

<p>TheGeebs: Add info on Emptying Attic</p> <hr /> <div>[[Category:apps]]<br /> <div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;"><br /> '''NEW:''' [http://code.google.com/p/greyhole/wiki/MigrateFromWHS Widows Home Server Drive Extender Migration Guide]<br /> <br /> '''NEW:''' [[Greyhole troubleshooting]] guide<br /> </div><br /> <br /> <br /> == What is Greyhole ==<br /> <br /> [http://greyhole.pommepause.com/ Greyhole] is Amahi's [[Storage pooling]] technology. Storage Pooling combines the space of multiple disk drives and makes them look as if they were all part of a single pool of disk space.<br /> Specifically, Greyhole:<br /> * Combines the space from multiple drives into a single volume<br /> * Distributes files across all drives in the pool<br /> * Creates multiple copies of files in admin-specified shares<br /> <br /> This feature is installed by default, but requires a few simple steps to begin utilizing the features.<br /> <br /> You can add additional drives to your hda and prepare them for use in Greyhole by following [[Adding a second hard drive to your HDA|this tutorial]].<br /> <br /> To add a drive to your Greyhole storage pool. Open your HDA dashboard and navigate to the Shares tab. Then click on the Storage Pool sub-category. You will see a page similar to the one below.<br /> <br /> == Important Warnings ==<br /> <div style="color:darkred">You should '''never''' change or delete files in the shared directories (''/var/hda/files/*'' by default) directly on the HDA, using the terminal, or the Gnome file browser, for the shares for which you checked the ''Uses pool'' option in the Amahi dashboard. If you want to work with files on Greyhole shares on the HDA, you should [[Mount Shares Locally]].<br/><br /> You should be safe reading existing files directly, or adding new files directly, as long as don't care that your new files will only be moved into the storage pool during the next check, which runs automatically at midnight (or manually using ''greyhole --fsck''). Until then, your new files will be stored in your shared directories (normally ''/var/hda/files/share_name/'').<br /> <br /> Also, touching anything inside the '''gh''' directories that Greyhole creates at the root of your partitions is a recipe for disaster.<br /> <br /> We [[Greyhole not on root | strongly discourage you from using the root partition in a drive pool]].<br /> </div><br/><br/><br /> <br /> == First things first ==<br /> <br /> You need to go in the Settings tab, and enable '''Advanced Settings'''.<br/><br /> Without Advanced Settings enabled, you won't see the following page and options.<br /> <br /> == For Storage Pool (Partitions) ==<br /> <br /> [[File:Storage_Pool_1.png|600px|thumb|left]]<br /> <br /> Select the drives you want available for your storage pool.<br /> <br /> == Greyhole options ==<br /> <br /> The next step is to select the share you want to replicate across the pool.<br /> <br /> From the Shares tab, select the Shares sub-catagory. We chose the Pictures share for this tutorial.<br /> <br /> [[File:Greyhole_Options_1.png|600px|thumb|left]]<br /> <br /> Check the option for "Uses pool" and choose the number of drives to replicate this share. In this instance we have chosen to use all drives available to the greyhole pool.<br /> <br /> Note: Greyhole is not a backup solution. If a file is removed, all copies are removed.<br /> <br /> == Greyhole advanced options ==<br /> <br /> You can further configure Greyhole by manually editing the following file:<br/><br /> '''/var/hda/platform/html/config/greyhole.yml'''<br /> <br /> To see what options are available, and what they do, refer to the [http://greyhole.googlecode.com/svn/trunk/greyhole.example.conf sample greyhole.conf] provided with Greyhole.<br /> <br /> greyhole.yml is in in YAML format. Most of it should be easy enough to modify. The only exception would be the sticky_files (and optional sticky_into) options.<br/><br /> Here's an example of how those should appear:<br /> <br /> To specify the following to Greyhole in greyhole.conf:<br /> <br /> {{Text|Text=sticky_files <nowiki>=</nowiki> Music/<br /> sticky_files <nowiki>=</nowiki> Videos/Movies/<br /> stick_into <nowiki>=</nowiki> /mnt/hdd1/gh<br /> stick_into <nowiki>=</nowiki> /mnt/hdd5/gh<br /> sticky_files <nowiki>=</nowiki> Backups/CrashPlan/<br /> stick_into <nowiki>=</nowiki> /mnt/hdd0/gh}}<br /> <br /> one should specify this in the greyhole.yml file, where '''precise indentation matters''':<br /> <br /> {{Text|Text=sticky_files: <br /> - - Music/<br /> - - Videos/Movies/<br /> - - /mnt/hdd1/gh<br /> - /mnt/hdd5/gh<br /> - - Backups/CrashPlan/<br /> - - /mnt/hdd0/gh}}<br /> <br /> For your changes to be effective, you'll need to force Amahi to regenerate the greyhole.conf file. You can do so by editing a share, clicking it's path, and just clicking the Save button without actually changing the path.<br /> <br /> == Copying your data into Greyhole shares the first time ==<br /> <br /> When you start using Greyhole, you might want to copy or move all your exiting files into your new shares that use the storage pool.<br /> <br /> Note: This is not necessary if your files are already in Amahi shares. If they are there, and you enable the ''Uses pool'' option in the Amahi dashboard, the files will start getting moved around into the drives in your storage pool during the night (starting at midnight), when the nightly storage pool check starts.<br/><br /> The instructions below are for users who have more data to copy into the Greyhole shares than their currently free space in the /var/hda/files/ folder.<br /> <br /> One way to do that is to mount the shares that use the Greyhole storage pool, either on the HDA itself, or on a client computer on your local network, and copy your data from their existing location into the mounted shares.<br /> This can be time consuming, but it is the safest way to use Greyhole.<br /> <br /> Another way to move your files from their current location into the storage pool is to share their current location using an Amahi share that ''Uses pool'', then let Greyhole nightly check move the files from there into the pool.<br /> <br /> Here's a more detailed walkthrough for this method:<br /> <br /> # Setup the Greyhole Storage Pool in the Amahi dashboard, Shares > Storage Pool page.<br /> # Go in the Shares > Shares page. In there, make sure you have an existing share for each share you have data for. Create new ones if you need, remove the ones you don't need.<br /> # Edit the ''path'' of each of those shares, and enter the current location of your existing data. For example, the Movies share could have a path = ''/media/External Drive/Movies''<br /> # Enable the ''Uses pool'' option for each of your shares, and select the number of extra copies you'd like, if any.<br /> # Now, you either need to wait for Greyhole'S nightly check to start, or you can start it manually from a terminal, as root, using this command: greyhole --fsck<br /> # Monitor /var/log/greyhole.log to see when the ''fsck'' operation is done.<br /> # Once ''fsck'' is done, your data has now been moved into the Greyhole storage pool (in the drives you selected in Shares > Storage Pool). All that should be left in the previous location of your data (''/media/External Drive/Movies'' from the previous example) should be symbolic links pointing to the new file copies. If the previous location is just empty directories (no symlinks), do not panic. This is normal if your previous location is an NTFS or FAT partition (drive).<br /> # Move all those directories / symlinks from there into the correct folders in /var/hda/files/share_name<br /> # Back in the Amahi dashboard, edit the path of the shares once again, and put back ''/var/hda/files/share_name'' (i.e. the folders where you moved the symbolic links).<br /> # If you used an NTFS or FAT partition for the previous location, you'll need another fsck to create the symlinks where they should be. Either wait for midnight, or launch it manually, from a command line, as root: ''greyhole --fsck''<br /> <br /> You're done. All your existing data is now stored in the various drives included in your storage pool, and are accessible via the Samba shares you have defined in the Amahi dashboard.<br /> <br /> <br /> == Adding a new drive to your HDA and storage pool ==<br /> This wiki page discusses how to add a new drive to your HDA and to your greyhole storage pool<br /> [[Adding_a_second_hard_drive_to_your_HDA]]<br /> <br /> <br /> == Drive Mounted as /media ==<br /> Including any drive mounted as /media/Something in your storage pool is usually a bad idea.<br/><br /> Those mounts are created by the ''gnome-automounter'', which requires you to be logged in into X (Gnome) to become available.<br/><br /> This will create issues with Greyhole, which expects drives to always be available, and will take action when some of them are missing.<br /> <br /> Follow this guide to [[Adding a second hard drive to your HDA|permanently mount your drives]], before you include them in your storage pool.<br /> <br /> == Monitoring Greyhole ==<br /> Sometimes you might want to monitor what Greyhole is doing, for example when writing data to your greyhole shares for the first time. Here are a few commands you can type in a terminal to follow along.<br /> <br /> '''Scrolling view of total Greyhole operations queue:'''<br /> {{Code|while [ 1 <nowiki>==</nowiki> 1 ]; do greyhole --view-queue <nowiki>|</nowiki> grep Total; sleep 60; done}}<br /> <br /> '''Scrolling log of what files Greyhole is working on right now:'''<br /> {{Code|tail -f /var/log/greyhole.log}}<br /> <br /> == Convert Greyhole from SQLite to MySQL ==<br /> Greyhole is already using MySQL in Amahi 6.0<br /> <br /> Greyhole was previously using SQLite as the default database for queueing up tasks on Amahi. This was unqie to Amahi as Greyhole was originally designed to use MySQL for this task.<br /> <br /> There are some major performance benefits to using MySQL over SQLite when writing large amounts of files. Switching can be especially useful when moving data to greyhole shares for the first time. For now there is a script you can run if you want to switch over. This script has been tested to be safe while greyhole is working but should be used with discresion.<br /> <br /> ''To Convert to MySQL, run as root:''<br /> <br /> {{Code|/usr/share/greyhole/db_migration-sqlite2mysql.sh}}<br /> <br /> To see what DB engine is Greyhole using, do this:<br /> <br /> {{Code|grep db_engine /etc/greyhole.conf}}<br /> <br /> == Disable Greyhole ==<br /> For those who do not use Greyhole, you can disable it. This is based on the fact you never have used it by enabling 'Uses pool' on any share. Recommend using extreme caution as this could have unpredictable results.<br /> <br /> Perform the following steps as user '''root''':<br /> <br /> {{Code|chkconfig greyhole off<br /> rm /etc/monit.d/greyhole.conf<br /> service monit restart<br /> service greyhole stop}}<br /> <br /> '''DO NOT''' attempt to remove the Greyhole package as it is a dependency of the HDA software. Doing so will break your HDA.<br /> <br /> = Testing and Reliability =<br /> <br /> Check out the [[Greyhole grinder]] to help make Greyhole rock solid.<br /> <br /> = Reconnect the Greyhole storage pool after re-install of Fedora / Amahi =<br /> <br /> <br /> * Disconnect all data drives before you reinstall. This will prevent you from destroying them by mistake during the Fedora/Amahi install!<br /> * Install Amahi per the regular instructions.<br /> * Connect the data drives, and use hda-diskmount to remount all of them.<br /> Note that if you can, it would be faster if you can re-mount the drives in the same paths they used to have.<br /> <br /> '''Example:''' If you have one 1TB and one 2TB, and the 1TB was mounted as /var/hda/files/drives/drive1, and the 2TB was mounted as /var/hda/files/drives/drive2, it would be better to re-mount that like that on your new HDA. If you mount them otherwise, it will still work, but Greyhole will work a while to re-build the links in your share before they can be usable.<br /> * Select the drives in the Amahi Dashboard: Setup > Shares > Storage Pool<br /> * Re-create your shares in the Amahi Dashboard: Setup > Shares.<br /> Make sure to select 'Use Pool', and select the correct number of extra copies.<br /> If you don't remember all the shares you had, just check inside the 'gh' folder found at the root of your drives to get a reminder!<br /> <br /> '''Example:'''<br /> {{Code|ls -1 /var/hda/files/drives/*/gh/ <nowiki>|</nowiki> grep -v : <nowiki>|</nowiki> sort -u}}<br /> <br /> * Launch a fsck to have Greyhole rebuild your shares.<br /> {{Code|greyhole --fsck}}<br /> <br /> Until this completes, some of your files will be missing from your shares.<br /> <br /> = Greyhole Troubleshooting =<br /> <br /> Page: [[Greyhole troubleshooting]]<br /> <br /> = Landing Zone Considerations =<br /> <br /> The landing zone or LZ is the area where files arrive first before being distributed to their final destination. See details in the [[Greyhole landing zone]] page.<br /> <br /> = Manually updating Greyhole for Amahi =<br /> Page: [[Greyhole updating]]<br /> <br /> = Emptying Greyhole Attic =<br /> {{Code|greyhole --empty-attic}}<br /> About the attic: The attic is used like a Recycle Bin, or Trash.<br /> That means you'll need to manually empty it once in a while.<br /> To do so, use the --empty-attic parameter (see above).<br /> Another option is to create a 'Greyhole Attic' Samba share.<br /> More details about that here: http://greyhole.pommepause.com/doc/attic<br /> <br /> = Reference =<br /> Good [http://revxatlarge.blogspot.com/2011/04/restoring-deleted-files-in-greyhole-and.html article] on Greyhole with terms explained.</div>

TheGeebs https://wiki.amahi.org/index.php?title=Greyhole&diff=46387 Greyhole 2011-09-05T22:14:15Z

<p>TheGeebs: Greyhole is now using MySQL, updated to reflect this</p> <hr /> <div>[[Category:apps]]<br /> <div style="border: 1px solid #A3B1BF; padding: .8em 1em; background-color: #E6F2FF; margin: 0px 1em;"><br /> '''NEW:''' [http://code.google.com/p/greyhole/wiki/MigrateFromWHS Widows Home Server Drive Extender Migration Guide]<br /> <br /> '''NEW:''' [[Greyhole troubleshooting]] guide<br /> </div><br /> <br /> <br /> == What is Greyhole ==<br /> <br /> [http://greyhole.pommepause.com/ Greyhole] is Amahi's [[Storage pooling]] technology. Storage Pooling combines the space of multiple disk drives and makes them look as if they were all part of a single pool of disk space.<br /> Specifically, Greyhole:<br /> * Combines the space from multiple drives into a single volume<br /> * Distributes files across all drives in the pool<br /> * Creates multiple copies of files in admin-specified shares<br /> <br /> This feature is installed by default, but requires a few simple steps to begin utilizing the features.<br /> <br /> You can add additional drives to your hda and prepare them for use in Greyhole by following [[Adding a second hard drive to your HDA|this tutorial]].<br /> <br /> To add a drive to your Greyhole storage pool. Open your HDA dashboard and navigate to the Shares tab. Then click on the Storage Pool sub-category. You will see a page similar to the one below.<br /> <br /> == Important Warnings ==<br /> <div style="color:darkred">You should '''never''' change or delete files in the shared directories (''/var/hda/files/*'' by default) directly on the HDA, using the terminal, or the Gnome file browser, for the shares for which you checked the ''Uses pool'' option in the Amahi dashboard. If you want to work with files on Greyhole shares on the HDA, you should [[Mount Shares Locally]].<br/><br /> You should be safe reading existing files directly, or adding new files directly, as long as don't care that your new files will only be moved into the storage pool during the next check, which runs automatically at midnight (or manually using ''greyhole --fsck''). Until then, your new files will be stored in your shared directories (normally ''/var/hda/files/share_name/'').<br /> <br /> Also, touching anything inside the '''gh''' directories that Greyhole creates at the root of your partitions is a recipe for disaster.<br /> <br /> We [[Greyhole not on root | strongly discourage you from using the root partition in a drive pool]].<br /> </div><br/><br/><br /> <br /> == First things first ==<br /> <br /> You need to go in the Settings tab, and enable '''Advanced Settings'''.<br/><br /> Without Advanced Settings enabled, you won't see the following page and options.<br /> <br /> == For Storage Pool (Partitions) ==<br /> <br /> [[File:Storage_Pool_1.png|600px|thumb|left]]<br /> <br /> Select the drives you want available for your storage pool.<br /> <br /> == Greyhole options ==<br /> <br /> The next step is to select the share you want to replicate across the pool.<br /> <br /> From the Shares tab, select the Shares sub-catagory. We chose the Pictures share for this tutorial.<br /> <br /> [[File:Greyhole_Options_1.png|600px|thumb|left]]<br /> <br /> Check the option for "Uses pool" and choose the number of drives to replicate this share. In this instance we have chosen to use all drives available to the greyhole pool.<br /> <br /> Note: Greyhole is not a backup solution. If a file is removed, all copies are removed.<br /> <br /> == Greyhole advanced options ==<br /> <br /> You can further configure Greyhole by manually editing the following file:<br/><br /> '''/var/hda/platform/html/config/greyhole.yml'''<br /> <br /> To see what options are available, and what they do, refer to the [http://greyhole.googlecode.com/svn/trunk/greyhole.example.conf sample greyhole.conf] provided with Greyhole.<br /> <br /> greyhole.yml is in in YAML format. Most of it should be easy enough to modify. The only exception would be the sticky_files (and optional sticky_into) options.<br/><br /> Here's an example of how those should appear:<br /> <br /> To specify the following to Greyhole in greyhole.conf:<br /> <br /> {{Text|Text=sticky_files <nowiki>=</nowiki> Music/<br /> sticky_files <nowiki>=</nowiki> Videos/Movies/<br /> stick_into <nowiki>=</nowiki> /mnt/hdd1/gh<br /> stick_into <nowiki>=</nowiki> /mnt/hdd5/gh<br /> sticky_files <nowiki>=</nowiki> Backups/CrashPlan/<br /> stick_into <nowiki>=</nowiki> /mnt/hdd0/gh}}<br /> <br /> one should specify this in the greyhole.yml file, where '''precise indentation matters''':<br /> <br /> {{Text|Text=sticky_files: <br /> - - Music/<br /> - - Videos/Movies/<br /> - - /mnt/hdd1/gh<br /> - /mnt/hdd5/gh<br /> - - Backups/CrashPlan/<br /> - - /mnt/hdd0/gh}}<br /> <br /> For your changes to be effective, you'll need to force Amahi to regenerate the greyhole.conf file. You can do so by editing a share, clicking it's path, and just clicking the Save button without actually changing the path.<br /> <br /> == Copying your data into Greyhole shares the first time ==<br /> <br /> When you start using Greyhole, you might want to copy or move all your exiting files into your new shares that use the storage pool.<br /> <br /> Note: This is not necessary if your files are already in Amahi shares. If they are there, and you enable the ''Uses pool'' option in the Amahi dashboard, the files will start getting moved around into the drives in your storage pool during the night (starting at midnight), when the nightly storage pool check starts.<br/><br /> The instructions below are for users who have more data to copy into the Greyhole shares than their currently free space in the /var/hda/files/ folder.<br /> <br /> One way to do that is to mount the shares that use the Greyhole storage pool, either on the HDA itself, or on a client computer on your local network, and copy your data from their existing location into the mounted shares.<br /> This can be time consuming, but it is the safest way to use Greyhole.<br /> <br /> Another way to move your files from their current location into the storage pool is to share their current location using an Amahi share that ''Uses pool'', then let Greyhole nightly check move the files from there into the pool.<br /> <br /> Here's a more detailed walkthrough for this method:<br /> <br /> # Setup the Greyhole Storage Pool in the Amahi dashboard, Shares > Storage Pool page.<br /> # Go in the Shares > Shares page. In there, make sure you have an existing share for each share you have data for. Create new ones if you need, remove the ones you don't need.<br /> # Edit the ''path'' of each of those shares, and enter the current location of your existing data. For example, the Movies share could have a path = ''/media/External Drive/Movies''<br /> # Enable the ''Uses pool'' option for each of your shares, and select the number of extra copies you'd like, if any.<br /> # Now, you either need to wait for Greyhole'S nightly check to start, or you can start it manually from a terminal, as root, using this command: greyhole --fsck<br /> # Monitor /var/log/greyhole.log to see when the ''fsck'' operation is done.<br /> # Once ''fsck'' is done, your data has now been moved into the Greyhole storage pool (in the drives you selected in Shares > Storage Pool). All that should be left in the previous location of your data (''/media/External Drive/Movies'' from the previous example) should be symbolic links pointing to the new file copies. If the previous location is just empty directories (no symlinks), do not panic. This is normal if your previous location is an NTFS or FAT partition (drive).<br /> # Move all those directories / symlinks from there into the correct folders in /var/hda/files/share_name<br /> # Back in the Amahi dashboard, edit the path of the shares once again, and put back ''/var/hda/files/share_name'' (i.e. the folders where you moved the symbolic links).<br /> # If you used an NTFS or FAT partition for the previous location, you'll need another fsck to create the symlinks where they should be. Either wait for midnight, or launch it manually, from a command line, as root: ''greyhole --fsck''<br /> <br /> You're done. All your existing data is now stored in the various drives included in your storage pool, and are accessible via the Samba shares you have defined in the Amahi dashboard.<br /> <br /> <br /> == Adding a new drive to your HDA and storage pool ==<br /> This wiki page discusses how to add a new drive to your HDA and to your greyhole storage pool<br /> [[Adding_a_second_hard_drive_to_your_HDA]]<br /> <br /> <br /> == Drive Mounted as /media ==<br /> Including any drive mounted as /media/Something in your storage pool is usually a bad idea.<br/><br /> Those mounts are created by the ''gnome-automounter'', which requires you to be logged in into X (Gnome) to become available.<br/><br /> This will create issues with Greyhole, which expects drives to always be available, and will take action when some of them are missing.<br /> <br /> Follow this guide to [[Adding a second hard drive to your HDA|permanently mount your drives]], before you include them in your storage pool.<br /> <br /> == Monitoring Greyhole ==<br /> Sometimes you might want to monitor what Greyhole is doing, for example when writing data to your greyhole shares for the first time. Here are a few commands you can type in a terminal to follow along.<br /> <br /> '''Scrolling view of total Greyhole operations queue:'''<br /> {{Code|while [ 1 <nowiki>==</nowiki> 1 ]; do greyhole --view-queue <nowiki>|</nowiki> grep Total; sleep 60; done}}<br /> <br /> '''Scrolling log of what files Greyhole is working on right now:'''<br /> {{Code|tail -f /var/log/greyhole.log}}<br /> <br /> == Convert Greyhole from SQLite to MySQL ==<br /> Greyhole is already using MySQL in Amahi 6.0<br /> <br /> Greyhole was previously using SQLite as the default database for queueing up tasks on Amahi. This was unqie to Amahi as Greyhole was originally designed to use MySQL for this task.<br /> <br /> There are some major performance benefits to using MySQL over SQLite when writing large amounts of files. Switching can be especially useful when moving data to greyhole shares for the first time. For now there is a script you can run if you want to switch over. This script has been tested to be safe while greyhole is working but should be used with discresion.<br /> <br /> ''To Convert to MySQL, run as root:''<br /> <br /> {{Code|/usr/share/greyhole/db_migration-sqlite2mysql.sh}}<br /> <br /> To see what DB engine is Greyhole using, do this:<br /> <br /> {{Code|grep db_engine /etc/greyhole.conf}}<br /> <br /> == Disable Greyhole ==<br /> For those who do not use Greyhole, you can disable it. This is based on the fact you never have used it by enabling 'Uses pool' on any share. Recommend using extreme caution as this could have unpredictable results.<br /> <br /> Perform the following steps as user '''root''':<br /> <br /> {{Code|chkconfig greyhole off<br /> rm /etc/monit.d/greyhole.conf<br /> service monit restart<br /> service greyhole stop}}<br /> <br /> '''DO NOT''' attempt to remove the Greyhole package as it is a dependency of the HDA software. Doing so will break your HDA.<br /> <br /> = Testing and Reliability =<br /> <br /> Check out the [[Greyhole grinder]] to help make Greyhole rock solid.<br /> <br /> = Reconnect the Greyhole storage pool after re-install of Fedora / Amahi =<br /> <br /> <br /> * Disconnect all data drives before you reinstall. This will prevent you from destroying them by mistake during the Fedora/Amahi install!<br /> * Install Amahi per the regular instructions.<br /> * Connect the data drives, and use hda-diskmount to remount all of them.<br /> Note that if you can, it would be faster if you can re-mount the drives in the same paths they used to have.<br /> <br /> '''Example:''' If you have one 1TB and one 2TB, and the 1TB was mounted as /var/hda/files/drives/drive1, and the 2TB was mounted as /var/hda/files/drives/drive2, it would be better to re-mount that like that on your new HDA. If you mount them otherwise, it will still work, but Greyhole will work a while to re-build the links in your share before they can be usable.<br /> * Select the drives in the Amahi Dashboard: Setup > Shares > Storage Pool<br /> * Re-create your shares in the Amahi Dashboard: Setup > Shares.<br /> Make sure to select 'Use Pool', and select the correct number of extra copies.<br /> If you don't remember all the shares you had, just check inside the 'gh' folder found at the root of your drives to get a reminder!<br /> <br /> '''Example:'''<br /> {{Code|ls -1 /var/hda/files/drives/*/gh/ <nowiki>|</nowiki> grep -v : <nowiki>|</nowiki> sort -u}}<br /> <br /> * Launch a fsck to have Greyhole rebuild your shares.<br /> {{Code|greyhole --fsck}}<br /> <br /> Until this completes, some of your files will be missing from your shares.<br /> <br /> = Greyhole Troubleshooting =<br /> <br /> Page: [[Greyhole troubleshooting]]<br /> <br /> = Landing Zone Considerations =<br /> <br /> The landing zone or LZ is the area where files arrive first before being distributed to their final destination. See details in the [[Greyhole landing zone]] page.<br /> <br /> = Manually updating Greyhole for Amahi =<br /> Page: [[Greyhole updating]]<br /> <br /> = Reference =<br /> Good [http://revxatlarge.blogspot.com/2011/04/restoring-deleted-files-in-greyhole-and.html article] on Greyhole with terms explained.</div>

TheGeebs https://wiki.amahi.org/index.php?title=VPNMacTunnelBlick&diff=38773 VPNMacTunnelBlick 2011-04-16T17:32:49Z

<p>TheGeebs: Page formatting. Nothing more</p> <hr /> <div>== Mac VPN Client - Tunnelblick ==<br /> <br /> [http://www.tunnelblick.net/ Tunnelblick] is an open source client for Mac OS X.<br /> <br /> ''NOTE: Tunnelblick may not work if you have the Cisco VPN client installed at the same time!''<br /> <br /> == Preferred Installation Method ==<br /> # Download and install the latest 3.1.x version of [http://code.google.com/p/tunnelblick/downloads/list Tunnelblick] for Mac OS X<br /> # Download and install the [http://dl.amahi.org/vpn/Amahi%20VPN%20Client%20Configuration.pkg.zip Amahi VPN Client Configuration package]<br /> # Replace YourNicknameHere in the first line with your Username<br /> # Open Tunnelblick under Applications<br /> # Click Connect MyHDA (Tunnelblick icon next to Spotlight in top right corner of menubar<br /> * If you'd like to automatically connect when Tunnelblick is opened: Choose ''' Details ''' from the drop-down and check ''' "Connect Automatically" '''<br /> <br /> = Alternate Installation Methods: =<br /> == Semi-automatic Method - Tunnelblick 3.0 ==<br /> If the above Amahi VPN Client Configuration package fails to install, you should try the steps below.<br /> <br /> * We have a script to help in the installation:<br /> curl -so install-amahi-vpn <nowiki>http://dl.amahi.org/vpn/mac.sh</nowiki><br /> chmod 755 install-amahi-vpn<br /> ./install-amahi-vpn<br /> * The above should open a text editor with the conf file<br /> * Replace YourNicknameHere in the first line, for your nickname <br /> * Start the VPN!<br /> <br /> == Semi-automatic Method - Tunnelblick 3.1 ==<br /> If the above Amahi VPN Client Configuration package fails to install, you should try the steps below.<br /> <br /> * We have a script to help in the installation:<br /> curl -so install-amahi-vpn <nowiki>http://dl.amahi.org/vpn/tunnelblick-beta.sh</nowiki><br /> chmod 755 install-amahi-vpn<br /> ./install-amahi-vpn<br /> * The above should open a text editor with the conf file<br /> * Replace YourNicknameHere in the first line, for your nickname <br /> * Start the VPN!<br /> <br /> <br /> == Manual Method ==<br /> <br /> * Detailed instructions<br /> * There are three .ctr/.key files needed (make sure you follow the links to these in this wiki properly) Right click and save as to save these to your computer:<br /> ** [http://dl.amahi.org/vpn/AmahiHDAClient.crt AmahiHDAClient.crt]<br /> ** [http://dl.amahi.org/vpn/AmahiHDAClient.key AmahiHDAClient.key]<br /> ** [http://dl.amahi.org/vpn/ca-cert.crt ca-cert.crt]<br /> * Download the .ctr/.key files and save them in the /Users/'''username'''/Library/Application Support/Tunnelblick/Configurations/ folder, where '''username''' is the home directory of the current user.<br /> * Go to the configuration for Tunnelblick and edit the config file.<br /> * Click on the Tunnelblick icon in the upper right corner of the display, then click '''''Details...'''''<br />[[Image:tunnelblick-pulldown.png]]<br /> * "OpenVPN Log Output" window should appear, click on '''''Edit Configuration'''''. Make sure the ''Set Nameserver (Experimental)'' option is ''checked.''<br />[[Image:tunnelblick-editconfig.png]]<br /> * Delete the default sample configuration<br />[[Image:openvpn_conf1.png]]<br /> * Copy and paste the configuration below into the OpenVPN.conf file, replacing XYZ for your HDA's nickname:<br /> <pre><nowiki><br /> remote XYZ.yourhda.com 1194<br /> client<br /> dev tun<br /> proto udp<br /> resolv-retry infinite<br /> nobind<br /> persist-key<br /> persist-tun<br /> ca Ca-cert.crt<br /> cert AmahiHDAClient.crt<br /> key AmahiHDAClient.key<br /> comp-lzo<br /> verb 3<br /> auth-user-pass<br /> </nowiki></pre><br /> <br /> <br /> * Any time you want to connect '''from outside of your home network''' and '''into your home network''', simply click on '''Connect'''<br /> * Don't forget to click on the DNS option.<br /> * Input your username and password<br /> * It is possible to use keyrings. Will link here the details when available.<br /> <br /> Note:<br /> * The procedure above has been tested with an Intel-based Mac.<br /> <br /> Acessing Shares:<br /> * Once connected, in Finder, go to "Go" > "Connect to Server". You'll be prompted to type in your HDA address (smb://hda)<br /> * There have been cases in which the hda name did not work due to DNS issues. If this is the case, you can connect via ip address of your HDA (smb://192.168.X.X)<br /> [[Category: VPN]]</div>

TheGeebs https://wiki.amahi.org/index.php?title=VPNMacTunnelBlick&diff=38767 VPNMacTunnelBlick 2011-04-16T17:27:49Z

<p>TheGeebs: Expanded and cleaned up Normal Install. Semi-automatic didn't work for me</p> <hr /> <div>== Mac VPN Client - Tunnelblick ==<br /> <br /> [http://www.tunnelblick.net/ Tunnelblick] is an open source client for Mac OS X.<br /> <br /> ''NOTE: Tunnelblick may not work if you have the Cisco VPN client installed at the same time!''<br /> <br /> = Preferred Installation Method =<br /> # Download and install the latest 3.1.x version of [http://code.google.com/p/tunnelblick/downloads/list Tunnelblick] for Mac OS X<br /> # Download and install the [http://dl.amahi.org/vpn/Amahi%20VPN%20Client%20Configuration.pkg.zip Amahi VPN Client Configuration package]<br /> # Replace YourNicknameHere in the first line with your Username<br /> # Open Tunnelblick under Applications<br /> # Click Connect MyHDA (Tunnelblick icon next to Spotlight in top right corner of menubar<br /> * If you'd like to automatically connect when Tunnelblick is opened: Choose ''' Details ''' from the drop-down and check ''' "Connect Automatically" '''<br /> <br /> == Semi-automatic Method - Tunnelblick 3.0 ==<br /> If the above Amahi VPN Client Configuration package fails to install, you should try the steps below.<br /> <br /> * We have a script to help in the installation:<br /> curl -so install-amahi-vpn <nowiki>http://dl.amahi.org/vpn/mac.sh</nowiki><br /> chmod 755 install-amahi-vpn<br /> ./install-amahi-vpn<br /> * The above should open a text editor with the conf file<br /> * Replace YourNicknameHere in the first line, for your nickname <br /> * Start the VPN!<br /> <br /> == Semi-automatic Method - Tunnelblick 3.1 ==<br /> If the above Amahi VPN Client Configuration package fails to install, you should try the steps below.<br /> <br /> * We have a script to help in the installation:<br /> curl -so install-amahi-vpn <nowiki>http://dl.amahi.org/vpn/tunnelblick-beta.sh</nowiki><br /> chmod 755 install-amahi-vpn<br /> ./install-amahi-vpn<br /> * The above should open a text editor with the conf file<br /> * Replace YourNicknameHere in the first line, for your nickname <br /> * Start the VPN!<br /> <br /> <br /> == Manual Method ==<br /> <br /> * Detailed instructions<br /> * There are three .ctr/.key files needed (make sure you follow the links to these in this wiki properly) Right click and save as to save these to your computer:<br /> ** [http://dl.amahi.org/vpn/AmahiHDAClient.crt AmahiHDAClient.crt]<br /> ** [http://dl.amahi.org/vpn/AmahiHDAClient.key AmahiHDAClient.key]<br /> ** [http://dl.amahi.org/vpn/ca-cert.crt ca-cert.crt]<br /> * Download the .ctr/.key files and save them in the /Users/'''username'''/Library/Application Support/Tunnelblick/Configurations/ folder, where '''username''' is the home directory of the current user.<br /> * Go to the configuration for Tunnelblick and edit the config file.<br /> * Click on the Tunnelblick icon in the upper right corner of the display, then click '''''Details...'''''<br />[[Image:tunnelblick-pulldown.png]]<br /> * "OpenVPN Log Output" window should appear, click on '''''Edit Configuration'''''. Make sure the ''Set Nameserver (Experimental)'' option is ''checked.''<br />[[Image:tunnelblick-editconfig.png]]<br /> * Delete the default sample configuration<br />[[Image:openvpn_conf1.png]]<br /> * Copy and paste the configuration below into the OpenVPN.conf file, replacing XYZ for your HDA's nickname:<br /> <pre><nowiki><br /> remote XYZ.yourhda.com 1194<br /> client<br /> dev tun<br /> proto udp<br /> resolv-retry infinite<br /> nobind<br /> persist-key<br /> persist-tun<br /> ca Ca-cert.crt<br /> cert AmahiHDAClient.crt<br /> key AmahiHDAClient.key<br /> comp-lzo<br /> verb 3<br /> auth-user-pass<br /> </nowiki></pre><br /> <br /> <br /> * Any time you want to connect '''from outside of your home network''' and '''into your home network''', simply click on '''Connect'''<br /> * Don't forget to click on the DNS option.<br /> * Input your username and password<br /> * It is possible to use keyrings. Will link here the details when available.<br /> <br /> Note:<br /> * The procedure above has been tested with an Intel-based Mac.<br /> <br /> Acessing Shares:<br /> * Once connected, in Finder, go to "Go" > "Connect to Server". You'll be prompted to type in your HDA address (smb://hda)<br /> * There have been cases in which the hda name did not work due to DNS issues. If this is the case, you can connect via ip address of your HDA (smb://192.168.X.X)<br /> [[Category: VPN]]</div>

TheGeebs https://wiki.amahi.org/index.php?title=CouchPotato&diff=37513 CouchPotato 2011-03-24T05:27:52Z

<p>TheGeebs: </p> <hr /> <div>[[Category:apps]]<br /> <br /> '''CouchPotato''' is an automatic NZB and torrent downloader. You can keep a "movies I want"-list and it will search for NZBs/torrents of these movies every X hours. Once a movie is found, it will send it to SABnzbd or download the .nzb or .torrent to a specified directory. <br /> <br /> === Prerequisits: ===<br /> # SABnzbd<br /> # CouchPotato<br /> <br /> CouchPotato can be accessed from http://cpotato:5000/ -or- yourHDAip:5000 (i.e. 192.168.1.10:5000)<br /> <br /> === How to configure with SABnzbd: ===<br /> Open your config page at http://cpotato:5000/config/ or by clicking the gear at the top.<br /> <br /> '''General'''<br /> * Uncheck Launch Browser<br /> * Leave Host: 0.0.0.0 and Port: 5000<br /> '''NZBs / Torrents'''<br /> * Select “Sabnzbd” from Download to dropdown<br /> * Set Host to: localhost:25914<br /> * Get your Sabnzbd Apikey from http://sabnzbd/config/general/<br /> * Set Category to: Movies<br /> '''Providers'''<br /> * Set your provider account information<br /> '''Quality'''<br /> * Set your quality preferences<br /> '''Renaming'''<br /> * Set “Download Folder" to: /var/spool/sabnzbd/incoming/Movies/ (By default, SABnzbd's completed downloads folder is "/var/spool/sabnzbd/incoming/")<br /> * Set your "Movie destination" anywhere you like (i.e. /var/hda/files/Movies)<br /> <br /> <br /> === Warnings: ===<br /> * Leave your host as 0.0.0.0, this allows you to access from any pc on your network<br /> * If you change the port from 5000 you will break the proxy http://cpotato. You can still access CouchPotato from yourHDAip:port-you-set (i.e. http://192.168.1.10:8082)</div>

TheGeebs https://wiki.amahi.org/index.php?title=Sick_Beard&diff=37507 Sick Beard 2011-03-24T04:30:15Z

<p>TheGeebs: </p> <hr /> <div>[[Category: apps]]<br /> '''NOTE:''' This Amahi [http://www.amahi.org/apps/sick-beard application] is currently in '''ALPHA''' and integrates with [http://www.amahi.org/apps/sabnzbd SABnzbd]. <br /> <br /> === Prerequisites (Amahi Apps) ===<br /> # SABnzbd<br /> # Sick Beard ('''ONLY''' available to testers)<br /> <br /> === SABnzbd Config ===<br /> # First you should make sure you have designated a "scripts" folder. This is found on the "folders" tab of the "config" option in SABnzbd. Set it to "/var/hda/web-apps/sickbeard/html/autoProcessTV/"<br /> # Open that scripts folder. Then open the folder titled "autoProcessTV" that you got with your SickBeard installation. Copy all the contents over into your "Scripts" folder.<br /> # Rename the "autoProcessTV.cfg.sample" to just "autoProcess.TV.cfg"<br /> # Open that .cfg file in an editor. Change the host, port, username, and password values to the appropriate settings for your Sick Beard server. Then save it and close it.<br /> # Go back to SABnzbd and click on the "sorting" tab. Disable sorting for TV shows.<br /> # Go to the "categories" tab. Set the appropriate script as your postprocessing script for your TV shows (sabToSickbeard.py).<br /> <br /> <br /> '''NOTE:''' The above was modified from [http://sickbeard.com/forums/viewtopic.php?f=3&t=10#p28 Sick Beard Forums].<br /> <br /> === Sick Beard Config ===<br /> * General<br /> # Tell it what port to listen on and what login to use. (If installed from Dashboard the default is http://localhost:25914/ Username/Password: Blank/Blank)<br /> # Create Meta Data & Images ( I leave this off since I let XBMC do it. I don't like the extra files in the directory. XBMC allows me to delete shows from it's interface but it will only delete the show file, not associated meta data files. Hence you'll be left with a bunch of extra files in the folder that you don't need. I let XBMC do this so I can just delete the show (and the file) from XBMC after I've watched it.) This is personal preference though, if you don't want XBMC to take a long time looking things up, download the meta data when the show downloads so that XBMC doesn't have to look for it.<br /> # Episode Naming: I chose "include show name" and "include episode name". I use dashes (-) and the format (S01E01) for mine. This is personal preference though.<br /> # For quality I use "Custom" and then choose "720p TV" and "720p WEB-DL". I leave the second box empty (since I only want the show downloaded once) and I select the check box for "use season folders".<br /> * Episode Downloads:<br /> # Episode Search: NZB (duh)<br /> # NZB Options: Found NZBs go to SABnzbd<br /> # Retention = 600<br /> # Enter your SABnzbd server info<br /> # Fill in TV download directory (where you keep all your TV shows for XBMC to scan)<br /> # Check "rename episodes" and leave the other two boxes unchecked.<br /> * Search providers: <br /> # Fill in your credentials for the providers you use (I use NZBMatrix.com and NZBs.org) <br /> # Be sure to set the look-up order on the left.<br /> * Notifications: I have it do the first three notifications for XBMC (notify on snatched (nzb retrieval), download complete, and update library)<br /> * Save the settings, and that's it. You should be fully configured now.</div>

TheGeebs https://wiki.amahi.org/index.php?title=CouchPotato&diff=37501 CouchPotato 2011-03-24T04:21:05Z

<p>TheGeebs: </p> <hr /> <div>[[Category:apps]]<br /> <br /> '''CouchPotato''' is an automatic NZB and torrent downloader. You can keep a "movies I want"-list and it will search for NZBs/torrents of these movies every X hours. Once a movie is found, it will send it to SABnzbd or download the .nzb or .torrent to a specified directory. <br /> <br /> === Prerequisits: ===<br /> # SABnzbd<br /> # CouchPotato<br /> <br /> CouchPotato can be accessed from http://cpotato:5000/ -or- yourHDAip:5000 (i.e. 192.168.1.10:5000)<br /> <br /> === How to configure with SABnzbd: ===<br /> Open your config page at http://cpotato:5000/config/ or by clicking the gear at the top.<br /> <br /> '''General'''<br /> * Uncheck Launch Browser<br /> * Leave Host: 0.0.0.0 and Port: 5000<br /> '''NZBs / Torrents'''<br /> * Select “Sabnzbd” from Download to dropdown<br /> * Set Host to: localhost:25914<br /> * Get your Sabnzbd Apikey from http://sabnzbd/config/general/<br /> * Set Category to: Movies<br /> '''Providers'''<br /> * Set your provider account information<br /> '''Quality'''<br /> * Set your quality preferences<br /> '''Renaming'''<br /> * Set “Download Folder to: /var/spool/sabnzbd/incoming/Movies/ (By default, SABnzbd's completed downloads folder is "/var/spool/sabnzbd/incoming/")<br /> * Set your Movie destination anywhere you like (i.e. /var/hda/files/Movies)<br /> <br /> <br /> === Warnings: ===<br /> * Leave your host as 0.0.0.0, this allows you to access from any pc on your network<br /> * If you change the port from 5000 you will break the proxy http://cpotato. You can still access CouchPotato from yourHDAip:port-you-set (i.e. http://192.168.1.10:8082)</div>

TheGeebs https://wiki.amahi.org/index.php?title=CouchPotato&diff=37495 CouchPotato 2011-03-24T04:17:06Z

<p>TheGeebs: </p> <hr /> <div>[[Category:apps]]<br /> <br /> '''CouchPotato''' is an automatic NZB and torrent downloader. You can keep a "movies I want"-list and it will search for NZBs/torrents of these movies every X hours. Once a movie is found, it will send it to SABnzbd or download the .nzb or .torrent to a specified directory. <br /> <br /> === Prerequisits: ===<br /> # SABnzbd<br /> # CouchPotato<br /> <br /> CouchPotato can be accessed from http://cpotato:5000/ -or- yourHDAip:5000 (i.e. 192.168.1.10:5000)<br /> <br /> === How to configure with SABnzbd: ===<br /> # '''General'''<br /> * Uncheck Launch Browser<br /> * Leave Host: 0.0.0.0 and Port: 5000<br /> # '''NZBs / Torrents'''<br /> * Select “Sabnzbd” from Download to dropdown<br /> * Set Host to: localhost:25914<br /> * Get your Sabnzbd Apikey from http://sabnzbd/config/general/<br /> * Set Category to: Movies<br /> # '''Providers'''<br /> * Set your provider account information<br /> # '''Quality'''<br /> * Set your quality preferences<br /> # '''Renaming'''<br /> * Set “Download Folder to: /var/spool/sabnzbd/incoming/Movies/ (By default, SABnzbd's completed downloads folder is "/var/spool/sabnzbd/incoming/")<br /> * Set your Movie destination anywhere you like (i.e. /var/hda/files/Movies)<br /> <br /> <br /> <br /> === Warnings: ===<br /> * Leave your host as 0.0.0.0, this allows you to access from any pc on your network<br /> * If you change the port from 5000 you will break the proxy http://cpotato. You can still access CouchPotato from yourHDAip:port-you-set (i.e. http://192.168.1.10:8082)</div>

TheGeebs https://wiki.amahi.org/index.php?title=CouchPotato&diff=37489 CouchPotato 2011-03-24T04:15:58Z

<p>TheGeebs: Copied my working config</p> <hr /> <div>[[Category:apps]]<br /> <br /> '''CouchPotato''' is an automatic NZB and torrent downloader. You can keep a "movies I want"-list and it will search for NZBs/torrents of these movies every X hours. Once a movie is found, it will send it to SABnzbd or download the .nzb or .torrent to a specified directory. <br /> <br /> === Prerequisits: ===<br /> # SABnzbd<br /> # CouchPotato<br /> <br /> CouchPotato can be accessed from http://cpotato:5000/ -or- yourHDAip:5000 (i.e. 192.168.1.10:5000)<br /> <br /> === How to configure with SABnzbd: ===<br /> # ‘’’General’’’<br /> * Uncheck Launch Browser<br /> * Leave Host: 0.0.0.0 and Port: 5000<br /> # ‘’’NZBs / Torrents’’’<br /> * Select “Sabnzbd” from Download to dropdown<br /> * Set Host to: localhost:25914<br /> * Get your Sabnzbd Apikey from http://sabnzbd/config/general/<br /> * Set Category to: Movies<br /> # ‘’’Providers’’’<br /> * Set your provider account information<br /> # ‘’’Quality’’’<br /> * Set your quality preferences<br /> # ‘’’Renaming’’’<br /> * Set “Download Folder to: /var/spool/sabnzbd/incoming/Movies/ (By default, SABnzbd's completed downloads folder is "/var/spool/sabnzbd/incoming/")<br /> * Set your Movie destination anywhere you like (i.e. /var/hda/files/Movies)<br /> <br /> <br /> <br /> === Warnings: ===<br /> * Leave your host as 0.0.0.0, this allows you to access from any pc on your network<br /> * If you change the port from 5000 you will break the proxy http://cpotato. You can still access CouchPotato from yourHDAip:port-you-set (i.e. http://192.168.1.10:8082)</div>

TheGeebs https://wiki.amahi.org/index.php?title=CouchPotato&diff=37129 CouchPotato 2011-03-23T04:43:20Z

<p>TheGeebs: </p> <hr /> <div>[[Category:apps]]<br /> <br /> '''CouchPotato''' is an automatic NZB and torrent downloader. You can keep a "movies I want"-list and it will search for NZBs/torrents of these movies every X hours. Once a movie is found, it will send it to SABnzbd or download the .nzb or .torrent to a specified directory. <br /> <br /> === Prerequisits: ===<br /> # SABnzbd<br /> # CouchPotato<br /> <br /> CouchPotato can be accessed from http://cpotato:5000/ -or- yourHDAip:5000 (i.e. 192.168.1.10:5000)<br /> <br /> === How to configure with SABnzbd: ===<br /> * Please Add Instructions<br /> * Instructions are incomplete and untested<br /> * By default, SABnzbd's completed downloads folder is "/var/spool/sabnzbd/incoming/"<br /> * CouchPotato should be set to look for downloads in "/var/spool/sabnzbd/incoming/Movies"<br /> * Your SABnzbd API key can be found at http://sabnzbd/config/general/<br /> * Host might be "localhost:25914" or "yourHDAip:25914"<br /> * Category should be set as Movies<br /> <br /> === Warnings: ===<br /> * Leave your host as 0.0.0.0, this allows you to access from any pc on your network<br /> * If you change the port from 5000 you will break the proxy http://cpotato. You can still access CouchPotato from yourHDAip:port-you-set (i.e. http://192.168.1.10:8082)</div>

TheGeebs https://wiki.amahi.org/index.php?title=CouchPotato&diff=37123 CouchPotato 2011-03-23T04:38:14Z

<p>TheGeebs: </p> <hr /> <div>[[Category:apps]]<br /> <br /> CouchPotato is an automatic NZB and torrent downloader. You can keep a "movies I want"-list and it will search for NZBs/torrents of these movies every X hours. Once a movie is found, it will send it to SABnzbd or download the .nzb or .torrent to a specified directory. <br /> <br /> CouchPotato can be accessed from http://cpotato:5000/ -or- yourHDAip:5000 (i.e. 192.168.1.10:5000)<br /> <br /> How to configure with SABnzbd:<br /> * Please Add Instructions<br /> * Instructions are incomplete and untested<br /> * By default, SABnzbd's completed downloads folder is "/var/spool/sabnzbd/incoming/"<br /> * CouchPotato should be set to look for downloads in "/var/spool/sabnzbd/incoming/Movies"<br /> * Your SABnzbd API key can be found at http://sabnzbd/config/general/<br /> * Host might be "localhost:25914" or "yourHDAip:25914"<br /> * Category should be set as Movies<br /> <br /> Warnings:<br /> * Leave your host as 0.0.0.0, this allows you to access from any pc on your network<br /> * If you change the port from 5000 you will break the proxy http://cpotato. You can still access CouchPotato from yourHDAip:port-you-set (i.e. http://192.168.1.10:8082)</div>

TheGeebs https://wiki.amahi.org/index.php?title=CouchPotato&diff=37117 CouchPotato 2011-03-23T04:37:29Z

<p>TheGeebs: </p> <hr /> <div>[[Category:apps]]<br /> <br /> CouchPotato is an automatic NZB and torrent downloader. You can keep a "movies I want"-list and it will search for NZBs/torrents of these movies every X hours. Once a movie is found, it will send it to SABnzbd or download the .nzb or .torrent to a specified directory. <br /> <br /> CouchPotato can be accessed from http://cpotato:5000/ -or- yourHDAip:5000 (i.e. 192.168.1.10:5000)<br /> <br /> How to configure with SABnzbd:<br /> * Please Add Instructions<br /> * Instructions are incomplete and untested<br /> * By default, SABnzbd's completed downloads folder is "/var/spool/sabnzbd/incoming/"<br /> * CouchPotato should be set to look for downloads in "var/spool/sabnzbd/incoming/Movies"<br /> * Your SABnzbd API key can be found at http://sabnzbd/config/general/<br /> * Host might be "localhost:25914" or "yourHDAip:25914"<br /> * Category should be set as Movies<br /> <br /> Warnings:<br /> * Leave your host as 0.0.0.0, this allows you to access from any pc on your network<br /> * If you change the port from 5000 you will break the proxy http://cpotato. You can still access CouchPotato from yourHDAip:port-you-set (i.e. http://192.168.1.10:8082)</div>

TheGeebs https://wiki.amahi.org/index.php?title=CouchPotato&diff=37111 CouchPotato 2011-03-23T04:12:49Z

<p>TheGeebs: Begining of CouchPotato wiki</p> <hr /> <div>[[Category:apps]]<br /> <br /> CouchPotato is an automatic NZB and torrent downloader. You can keep a "movies I want"-list and it will search for NZBs/torrents of these movies every X hours. Once a movie is found, it will send it to SABnzbd or download the .nzb or .torrent to a specified directory. <br /> <br /> CouchPotato can be accessed from http://cpotato:5000/ -or- yourHDAip:5000 (i.e. 192.168.1.10:5000)<br /> <br /> How to configure with SABnzbd:<br /> * Please Add Instructions<br /> * Instructions are incomplete and untested<br /> * By default, SABnzbd's completed downloads folder is "/var/spool/sabnzbd/incoming/"<br /> * CouchPotato should be set to look for downloads in "var/spool/sabnzbd/Movies"<br /> * Your SABnzbd API key can be found at http://sabnzbd/config/general/</div>

TheGeebs https://wiki.amahi.org/index.php?title=CouchPotato&diff=37105 CouchPotato 2011-03-23T04:05:26Z

<p>TheGeebs: Created page with "Category:apps CouchPotato is an automatic NZB and torrent downloader. You can keep a "movies I want"-list and it will search for NZBs/torrents of these movies every X hours...."</p> <hr /> <div>[[Category:apps]]<br /> <br /> CouchPotato is an automatic NZB and torrent downloader. You can keep a "movies I want"-list and it will search for NZBs/torrents of these movies every X hours. Once a movie is found, it will send it to SABnzbd or download the .nzb or .torrent to a specified directory. <br /> <br /> CouchPotato can be accessed from http://cpotato:5000/ or @Port:5000 i.e. 192.168.1.10:5000 with no special configuration<br /> <br /> How to configure with SABnzbd:<br /> * Please Add Instructions</div>

TheGeebs https://wiki.amahi.org/index.php?title=Sabnzbd&diff=37093 Sabnzbd 2011-03-23T03:54:36Z

<p>TheGeebs: Sabnzbd created from sabnzb</p> <hr /> <div>[[Category:apps]]<br /> How to update to newer version:<br /> <br /> * Download the new version from the website<br /> * Extract the sabnzbd folder from the zip file<br /> (WHEN DOWNLOADING THE LATEST VERSION AND EXTRACTING THE sabnzbd FOLDER ,IT MAY CONTAIN THE VERSION NUMBER IN THE FOLDER NAME. ENSURE THAT YOU CHANGE THE FOLDER NAME TO JUST sabnzbd IF THIS IS THE CASE)<br /> * Login to the hda and replace the folder sabnzd in /usr/share with the one from the zip.<br /> * Then do<br /> service sabnzbd restart<br /> <br /> * ... and you should be good to go.<br /> <br /> <br /> Accessing sabnzbd using an IP address and port number.<br /> (needed for using some sabnzbd remote control apps such as mynzb for the iPad)<br /> <br /> * Open sabnzbd using http://sabnzbd<br /> * Navigate to the sabnzbd configuration page<br /> * Ensure the option for host is set to 0.0.0.0<br /> * Save changes using the icon at the bottom of the sabnzbd configuration page and then restart sabnzbd.<br /> * You should now be able to access sabnzbd using x.x.x.x:25914 (where "x" is the hda IP address and "25914" is the default port of sabnzbd when installed via the hda.</div>

TheGeebs