Problem adding 3rd HD

[bigfoot65]

When you installed the OS and Amahi, were the two other drives left connected? If so, that could be the issue. We recommend they be disconnected until Amahi is installed, then connect the drives.

Maybe it has something to do with mounting the drive as /var/hda/files. It seems like I had issues with Ubuntu and mounting a separate drive as such. I ended up mounting the drives as drive1 and drive2, then just moved shares to the second drive vs mounting it as /var/hda/files.

Could you post your /etc/fstab lines for those drives? Maybe there is something there we might see that you did not.

[jcostantino]

I unplugged everything except the boot drive when I installed ubuntu and then reconnected them at the time the ubuntu installer said to reboot. Then I installed the amahi package.

Ok, here it is:

Code: Select all

jeff@home-server:~$ more /etc/fstab # /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=415e01a5-9301-4ba0-b2e9-2f61fa00a57f / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=c169694f-21bf-44b3-9dd0-d90ee6a22609 none swap sw 0 0 UUID=3ca810fd-32d4-4de0-9bb2-9ba8540ac983 /var/hda/files ext4 defaults 1 2 UUID=7c5c24eb-aa05-4289-9e9d-f4322a559ef5 /var/hda/files/drives/drive1 ext4 defaults 1 2

[bigfoot65]

Everything looks ok. Not sure what the problem could be. What about not mounting a drive as /var/hda/files? Make them both mount as /var/hda/files/drives/drive# and then see if things work.

Once that is done, you then could try changing it around. Just seems like I recall a problem trying to mount a drive as /var/hda/files for some reason with Ubuntu. Not sure what or why, but I did have some difficulty and not sure if I ever resolved it.

I am currently running Fedora 14 as it works better for me.

[jcostantino]

Ok, that was it. If I comment out drive 2 and reboot, drive 3 mounts. If I reactivate the line for 2 and mount -a, drive 2 is active and 3 goes out.

How do I fix this? I followed the directions in the wiki and the shares moved to that drive are working so (I think) I did it right.

[bigfoot65]

I think what you are going to have to do is mount drive 2 the same as 3. Then you can move all the shares from the OS drive except the drives folder. Once you do that, you will have all your shares on drive 2 as you intended by mounting it as /var/hda files.

The /var/hda/files on the OS drive is still intact. If believe that may be the only way it will work. Now that I think about it, I had to move my shares the same way. Then I had to change the share path in the dashboard to point to drive1 in my case.

Hope that makes sense.

[jcostantino]

Ok so if I understand I leave /var/hda/files on drive 1 and point the shares manually to drive 2 in the control panel, then add drives 2 and 3 to the pool?

[ Post made via Android ]

[bigfoot65]

Yes. I believe that's how I had to do it.

[ Post made via Android ]

[jcostantino]

Well thank you very much! That fixed it for me, now I just have to edit samba.config to fix the inability to browse shares from the server itself.

I added both drives (2 and 3) to the pool and now greyhole -s shows the service doing something.

[bigfoot65]

Should not need to change anything with samba. There is a different issue there.

[ Post made via Android ]

[jcostantino]

Yeah, it's unrelated. Plus I apparently have a permissions issue - files are there on the server but hidden from my user. That's no big deal though.