Trouble with hda-diskmount

[gstreet]

I am new to both Linux and Amahi and seeking to set up a home file / media server. Right now, I am having trouble getting all my drives to mount using hda-diskmount as part of the process of adding additional drives into Greyhole.

My problem is similar to http://forums.amahi.org/viewtopic.php?f ... 5&start=10 but his solution isn't what I am looking for.

Hardware
HP N40L Microserver
4 x 2TB hard drives in four "quick plug" bays
1 x 250GB drive for OS, now mounted in the optical drive bay.

What I have done so far
1) Originally had the 250GB OS drive mounted in the quick carrier of the first drive bay; no other drives installed.
2) Installed Ubuntu Desktop 12.04 and then Amahi
3) Set up Amahi per instructions - no problems
4) Used Gparted to partition the OS drive into separate root, home and swap areas; had to follow a tutuorial to relocate home area
5) Installed the four 2TB drives in the quick plug drive bays
6) moved the OS drive to the empty optical drive bay. This may be what is causing my problem but I would like to leave the drive here as a) I want the larger drives in the quick connect bays and 2) the standard bios for the sata connection for the optical bay is slower IDE vs ACHI (can be fixed with a hacked bios but I thought why bother?)
7) Then started following Amahi instructions to add drives to Greyhole

What I found when I ran hda-diskmount was an error that my first 2TB drive (/dev/sda1) already exists in fstab and therefore was being ignored. So I am not getting the UUID info I need to add to fstab for this drive. There appears to be no problems with the other three 2TB drives. I expect this is showing up as a problem as I had the OS drive initially set up as sda1 when I installed Ubuntu / Amahi and now, for reasons stated above, I want it as sde1 (eg fifth drive position).

I'm not sure if there is an easy way to edit fstab and adjust this? I was bit afraid of messing everything up. Appreciate some coaching on what next steps I should be taking.

hda-diskmount info:

Code: Select all

**************************************************************** Ignoring /dev/sda1 - already in /etc/fstab as /dev/sda1 This device appears to be commented out of your /etc/fstab. You will need to remove it from there for hda-diskmount to be able to mount it. **************************************************************** Mounted /dev/sdb1 as '/var/hda/files/drives/drive1' (read-write) You may want your system to mount it every time you boot. To do so, add this line VERY CAREFULLY to /etc/fstab and reboot: UUID=5bd5498f-30c1-4780-948e-ca46656507d2 /var/hda/files/drives/drive1 ext4 defaults 1 2 **************************************************************** Mounted /dev/sdc1 as '/var/hda/files/drives/drive2' (read-write) You may want your system to mount it every time you boot. To do so, add this line VERY CAREFULLY to /etc/fstab and reboot: UUID=a7337504-376a-4d36-9f7a-1a24c0f55fbd /var/hda/files/drives/drive2 ext4 defaults 1 2 **************************************************************** Mounted /dev/sdd1 as '/var/hda/files/drives/drive3' (read-write) You may want your system to mount it every time you boot. To do so, add this line VERY CAREFULLY to /etc/fstab and reboot: UUID=8d881dcb-8de3-4621-b9bd-00025196868a /var/hda/files/drives/drive3 ext4 defaults 1 2

fstab

Code: Select all

# /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc nodev,noexec,nosuid 0 0 # / was on /dev/sda1 during installation UUID=4d6f8004-d190-4234-a03b-b68de988abf0 / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=3c39206c-ba60-47ff-a1fe-f5821b2ab543 none swap sw 0 0 # (identifier) (location, eg sda5) (format, eg ext3 or ext4) (some settings) UUID="d0531fa1-9311-4d53-b838-f35898adbd98" /home ext4 nodev,nosuid 0 2

Thanks!
Carl

[bigfoot65]

When you switched disks around, did you keep the same cabling? If not, drives may be recognized differently.

One user had a similar problem and that was his issue.

[gstreet]

When you switched disks around, did you keep the same cabling? If not, drives may be recognized differently.

One user had a similar problem and that was his issue.

No - you are correct that this is the issue. I cannot use the same cabling if I am to mount the drives where I want. The quick connect bays are where the OS drive was originally located when I installed the software (left bay of the four bays with quick connects). The drives in these bays have quick connect caddy's which is why I want to use them for my larger storage pool drives.


Now the OS Drive has been moved to where the optical drive bay is located for the reasons given in my first post.



I'm hoping there is a non-mechanical (eg not having to swap drives around) solution to this like editing fstab. As someone new to Linux, I wasn't overly keen to start experimenting with editing fstab without some expert help!

Thanks!

[bigfoot65]

Does this command give you the UUID you need?

Code: Select all

ls -1 /dev/disk/by-id/ | egrep -v "part|scsi"

If it does not, you might find some guidance on the internet for your situation.

[gstreet]

Thanks; I'll try it tonight and post back how I went.

Cheers,
Carl

[gstreet]

Well, I gave your suggested command a reply, Bigfoot, and I don't think it is giving me a UUID.

First, I ran hda-diskmount (as root) again:

Code: Select all

root@gstreet-MicroServer:~# hda-diskmount **************************************************************** Ignoring /dev/sda1 - already in /etc/fstab as /dev/sda1 This device appears to be commented out of your /etc/fstab. You will need to remove it from there for hda-diskmount to be able to mount it. **************************************************************** Mounted /dev/sdb1 as '/var/hda/files/drives/drive4' (read-write) You may want your system to mount it every time you boot. To do so, add this line VERY CAREFULLY to /etc/fstab and reboot: UUID=5bd5498f-30c1-4780-948e-ca46656507d2 /var/hda/files/drives/drive4 ext4 defaults 1 2 **************************************************************** Mounted /dev/sdc1 as '/var/hda/files/drives/drive5' (read-write) You may want your system to mount it every time you boot. To do so, add this line VERY CAREFULLY to /etc/fstab and reboot: UUID=a7337504-376a-4d36-9f7a-1a24c0f55fbd /var/hda/files/drives/drive5 ext4 defaults 1 2 **************************************************************** Mounted /dev/sdd1 as '/var/hda/files/drives/drive6' (read-write) You may want your system to mount it every time you boot. To do so, add this line VERY CAREFULLY to /etc/fstab and reboot: UUID=8d881dcb-8de3-4621-b9bd-00025196868a /var/hda/files/drives/drive6 ext4 defaults 1 2 **************************************************************** Ignoring /dev/sde1 - already mounted Ignoring /dev/sde1 - already in /etc/fstab as UUID=4d6f8004-d190-4234-a03b-b68de988abf0 **************************************************************** Ignoring /dev/sde3 - already mounted **************************************************************** All Linux, Windows and Mac partitions on your disks have been mounted.

Then I ran your command

Code: Select all

gstreet@gstreet-MicroServer:~$ ls -1 /dev/disk/by-id/ | egrep -v "part|scsi" ata-ST2000DM001-1CH164_XXXXXXX ata-ST2000DM001-1CH164_XXXXXXX ata-VB0250EAVER_XXXXXX ata-WDC_WD20EARX-00PASB0_WD-XXXXXXXXXXXX ata-WDC_WD20EARX-00PASB0_WD-XXXXXXXXXXXX wwn-0x5000c5004db61792 wwn-0x5000c5004e311ac9 wwn-0x5000c5004e312711 wwn-0x50014ee104c0269e wwn-0x50014ee1af641233

Note the "XXXXXX" part are just where I removed the serial numbers of the drives.

Comparing the two, your command does not look like it is giving me a UUID for the drives. If I can get a UUID for /dev/sda, I think I will be off and running.

Any other ideas?

I really appreciate your help!

Rgs,
Carl

[gstreet]

Sorry, I posted too soon - I think I may have got it. I googled "UUID hard drives Ubuntu" and found there are several ways to identify UUID's in Ubuntu. See https://help.ubuntu.com/community/UsingUUID

I ran the first one (sudo blkid) and got:

Code: Select all

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

I think this gives me the UUID I need for /dev/sda1. I'm out of time tonight so I will try editing fstab tomorrow night with the UUIDs and see if I can get all the four storage drives into the Greyhole share.

Finally, is it better to make the Greyhole Landing Zone within the drive pool or outside the pool? Should I make a separate partition for it? I was thinking of making a partition of around 200 GB for the LZ.

Cheers,
Carl

[bigfoot65]

As with most things, that is a matter of personal preference. I typically keep it outside the pool. It does not need it's own partition and can often remain on the OS drive if there is sufficient space.

Check out the wiki info on storage pools.

http://wiki.amahi.org/index.php/Greyhole_landing_zone

[gstreet]

Thanks for all your help, Bigfoot. I was successful in editing fstab and mounting all my four storage drives



Now dumb question time: I still really don't understand Greyhole despite reading the Wicki and a number of sites. I understand the purpose of the Landing Zone in moving files into the pool and that the LZ location is listed in the hda Shares area under Location. What I can't figure out is what drive(s) this location path /var/hda/files/Books refers to.



For example, I was just thinking about using the /home area (200 GB) on my OS drive as the Landing Zone which will be out of the pool - but I am totally confused what path this would be. Or should I just leave it alone as installed?

Cheers,
Carl

[bigfoot65]

Good to hear you got it all sorted out.

Here's the easiest way to look a Greyhole. All the shares are still the shares. For example, all pics are still in /var/hda/files/pictures. What Greyhole does, depending on number of copies you set, is copy files per share to each drive in the storage pool. It makes a symlink to the original share location, i.e. /var/hda/files/pictures. You work with files like normal, reading or writing to that location.

When you make changes to a share in the pool, Greyhole replicates that change throughout the other drives. When it comes to the LZ, that is just where files in the share lives until Greyhole moves them (or creates the symlink). So I would leave that setting alone unless there is a real need to move it.

Hope that helps explain it.