SOLVED: Moved Landing Zone. Now Hidden/Missing and Still Uses Root?

[astinusofmetate]

(Running Amahi 9 w/ Fedora 23)

I recently attempted to move one of the landing zones and it appears I only performed the process half right.

The tools I use to interface with the server is the PuTTY program and the web-app eXtplorer (through my Windows 10 PC)

I first used the disk wizard to format and mount a new internal hard drive /dev/sdb1 to the following mount point

Code: Select all

/var/hda/files/drives/GH_LandingZone

Per the wiki, I successfully executed the following

Code: Select all

mv /var/hda/files/public /var/hda/files/drives/GH_LandingZone/public

Restarted the servers and updated the share location on the dashboard (note: the web-app couldn't find the folder to be able to calculate the size)

The good news is that the /files/public folder is now gone. The bad news is that eXtplorer does not show any contents within /files/drives/GH_LandingZone. Furthermore, when testing out the new landing zone (by monitoring disk usage with the web app "eZ Server Monitor" while I drop a large file onto the network shared folder with my Windows pc), it looks like the root drive is still being used as a landing zone for the share.

To make things more interesting, when I navigate to the same folder location (/files/drives/GH_LandingZone) using PuTTY and query the directory contents, I see the "public" folder listed with sub-folder contents as expected.

So I managed to screw something up, but I'm not really sure what. Is it a folder permissions thing or did I screw up something more significant?

Last minute note. When I execute the ls command, I see this

GH_LandingZone WDRED6TB_1 WDRED6TB_2 WDRED6TB_3

where GH_LandingZone is highlighted green and the other drive directories are not. Expected?

Any suggestions on what to check next?

Thanks!

[bigfoot65]

disk-wizard App is broken in Amahi 11 and should not be used. Was supposed to be moved back to BETA, but I see it was not. That has since been corrected.

Based on the details you provided, it sounds like the drive is not mounted. You will need to follow the manual guidance in order to get the drive mounted.

To verify, do the following in terminal:

Code: Select all

df -h

The drive should show up if mounted.

Once mounted, you may need to move your share folders again to the new location if they did not show up.

[astinusofmetate]

Thanks for the quick reply! Does any of this make sense? Drive is found but not mounted properly? (where is the "public" folder now then??)

Code: Select all

[astinusofmetate@localhost drives]$ df -h

Filesystem Size Used Avail Use% Mounted on
devtmpfs 3.8G 0 3.8G 0% /dev
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 3.9G 828K 3.9G 1% /run
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sda4 48G 6.7G 41G 15% /
tmpfs 3.9G 84K 3.9G 1% /tmp
/dev/sde1 5.5T 1.8T 3.4T 35% /var/hda/files/drives/WDRED6TB_1
/dev/sdd1 5.5T 1.8T 3.4T 35% /var/hda/files/drives/WDRED6TB_2
/dev/sdc1 5.5T 937G 4.3T 18% /var/hda/files/drives/WDRED6TB_3
/dev/sda2 477M 96M 352M 22% /boot
/dev/sda1 200M 8.3M 192M 5% /boot/efi
/dev/sda5 24G 33M 24G 1% /home
tmpfs 780M 0 780M 0% /run/user/48
none 4.0M 0 4.0M 0% /var/spool/greyhole/mem
tmpfs 780M 0 780M 0% /run/user/0
tmpfs 780M 0 780M 0% /run/user/1000

Code: Select all

[root@localhost ~]# ls -l /dev/disk/by-id/ > before.txt

Code: Select all

[root@localhost ~]# cat before.txt

total 0
lrwxrwxrwx 1 root root 9 Dec 27 10:37 ata-ST380817AS_4MR0HWX8 -> ../../sdb
lrwxrwxrwx 1 root root 10 Dec 27 10:37 ata-ST380817AS_4MR0HWX8-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Dec 27 10:37 ata-ST380817AS_4MR0JHSQ -> ../../sda
lrwxrwxrwx 1 root root 10 Dec 27 10:37 ata-ST380817AS_4MR0JHSQ-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Dec 27 10:37 ata-ST380817AS_4MR0JHSQ-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Dec 27 10:37 ata-ST380817AS_4MR0JHSQ-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Dec 27 10:37 ata-ST380817AS_4MR0JHSQ-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Dec 27 10:37 ata-ST380817AS_4MR0JHSQ-part5 -> ../../sda5
lrwxrwxrwx 1 root root 9 Dec 27 10:37 ata-WDC_WD60EFRX-68L0BN1_WD-WX11D76EP7SJ -> ../../sdc
lrwxrwxrwx 1 root root 10 Dec 27 10:37 ata-WDC_WD60EFRX-68L0BN1_WD-WX11D76EP7SJ-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 9 Dec 27 10:37 ata-WDC_WD60EFRX-68L0BN1_WD-WXB1HB4LAD22 -> ../../sde
lrwxrwxrwx 1 root root 10 Dec 27 10:37 ata-WDC_WD60EFRX-68L0BN1_WD-WXB1HB4LAD22-part1 -> ../../sde1
lrwxrwxrwx 1 root root 9 Dec 27 10:37 ata-WDC_WD60EFRX-68L0BN1_WD-WXB1HB4UKA21 -> ../../sdd
lrwxrwxrwx 1 root root 10 Dec 27 10:37 ata-WDC_WD60EFRX-68L0BN1_WD-WXB1HB4UKA21-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 9 Dec 27 10:37 wwn-0x1e73b88c4ee25001 -> ../../sdc
lrwxrwxrwx 1 root root 10 Dec 27 10:37 wwn-0x1e73b88c4ee25001-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 9 Dec 27 10:37 wwn-0x5259b8304ee25001 -> ../../sdd
lrwxrwxrwx 1 root root 10 Dec 27 10:37 wwn-0x5259b8304ee25001-part1 -> ../../sdd1
lrwxrwxrwx 1 root root 9 Dec 27 10:37 wwn-0x8da4b8304ee25001 -> ../../sde
lrwxrwxrwx 1 root root 10 Dec 27 10:37 wwn-0x8da4b8304ee25001-part1 -> ../../sde1

Code: Select all

[root@localhost ~]# hda-diskmount

****************************************************************
Ignoring /dev/gpt - already in /etc/fstab as UUID=
****************************************************************
Ignoring /dev/sda2 - already mounted
Ignoring /dev/sda2 - already in /etc/fstab as UUID=0ab472e6-da4f-4fc0-b628-bd970f3e6677
****************************************************************
Ignoring /dev/sda4 - already mounted
Ignoring /dev/sda4 - already in /etc/fstab as UUID=d625da35-a626-4832-928b-c2ae7ccf3d90
****************************************************************
Ignoring /dev/sda5 - already mounted
Ignoring /dev/sda5 - already in /etc/fstab as UUID=a21bc753-4c75-457b-a565-fd9b95d05b0e
****************************************************************
Ignoring /dev/sdb1 - already in /etc/fstab as UUID=13a88a68-fb16-4abd-8c1f-c1db72775f18
****************************************************************
Ignoring /dev/gpt - already in /etc/fstab as UUID=
****************************************************************
Ignoring /dev/sdc1 - already mounted
Ignoring /dev/sdc1 - already in /etc/fstab as UUID=aaab39fe-521e-4981-802e-477aaee45a75
****************************************************************
Ignoring /dev/gpt - already in /etc/fstab as UUID=
****************************************************************
Ignoring /dev/sdd1 - already mounted
Ignoring /dev/sdd1 - already in /etc/fstab as UUID=4ec1e25f-0185-4220-8119-bc629a58f030
****************************************************************
Ignoring /dev/gpt - already in /etc/fstab as UUID=
****************************************************************
Ignoring /dev/sde1 - already mounted
Ignoring /dev/sde1 - already in /etc/fstab as UUID=f7d1a1fa-2cbc-476a-899d-825a2decfca5
****************************************************************
No usable Linux, Windows or Mac partitions found on your disks.

# /etc/fstab
# Created by anaconda on Thu Apr 20 06:59:33 2017
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=d625da35-a626-4832-928b-c2ae7ccf3d90 / xfs defaults 0 0
UUID=0ab472e6-da4f-4fc0-b628-bd970f3e6677 /boot ext4 defaults 1 2
UUID=EA57-9A79 /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=a21bc753-4c75-457b-a565-fd9b95d05b0e /home xfs defaults 0 0
UUID=ff0f13e8-dfef-4e92-b6e6-1645a4bca194 swap swap defaults 0 0
UUID=f7d1a1fa-2cbc-476a-899d-825a2decfca5 /var/hda/files/drives/WDRED6TB_1 auto auto,rw,exec 0 0
UUID=4ec1e25f-0185-4220-8119-bc629a58f030 /var/hda/files/drives/WDRED6TB_2 auto auto,rw,exec 0 0
UUID=aaab39fe-521e-4981-802e-477aaee45a75 /var/hda/files/drives/WDRED6TB_3 auto auto,rw,exec 0 0
UUID=13a88a68-fb16-4abd-8c1f-c1db72775f18 /var/hda/files/drives/GH_LandingZone auto auto,rw,exec 0 0

[bigfoot65]

It appears that the drive is not mounted.

Check to see that /var/hda/files/drives/GH_LandingZone folder exists.

Then do:

Code: Select all

sudo mount -a

Check and see if it's now mounted.

[astinusofmetate]

[root@localhost ~]# cd /var/hda/files/drive
[root@localhost drives]# dir
GH_LandingZone WDRED6TB_1 WDRED6TB_2 WDRED6TB_3
[root@localhost drives]# cd GH_LandingZone
[root@localhost GH_LandingZone]# dir
public

Before mounting drive the information appeared to exist....?

[root@localhost GH_LandingZone]# sudo mount -a
[root@localhost GH_LandingZone]# hda-diskmount
****************************************************************
Ignoring /dev/gpt - already in /etc/fstab as UUID=
****************************************************************
Ignoring /dev/sda2 - already mounted
Ignoring /dev/sda2 - already in /etc/fstab as UUID=0ab472e6-da4f-4fc0-b628-bd970f3e6677
****************************************************************
Ignoring /dev/sda4 - already mounted
Ignoring /dev/sda4 - already in /etc/fstab as UUID=d625da35-a626-4832-928b-c2ae7ccf3d90
****************************************************************
Ignoring /dev/sda5 - already mounted
Ignoring /dev/sda5 - already in /etc/fstab as UUID=a21bc753-4c75-457b-a565-fd9b95d05b0e
****************************************************************
Ignoring /dev/sdb1 - already mounted
Ignoring /dev/sdb1 - already in /etc/fstab as UUID=13a88a68-fb16-4abd-8c1f-c1db72775f18
****************************************************************
Ignoring /dev/gpt - already in /etc/fstab as UUID=
****************************************************************
Ignoring /dev/sdc1 - already mounted
Ignoring /dev/sdc1 - already in /etc/fstab as UUID=aaab39fe-521e-4981-802e-477aaee45a75
****************************************************************
Ignoring /dev/gpt - already in /etc/fstab as UUID=
****************************************************************
Ignoring /dev/sdd1 - already mounted
Ignoring /dev/sdd1 - already in /etc/fstab as UUID=4ec1e25f-0185-4220-8119-bc629a58f030
****************************************************************
Ignoring /dev/gpt - already in /etc/fstab as UUID=
****************************************************************
Ignoring /dev/sde1 - already mounted
Ignoring /dev/sde1 - already in /etc/fstab as UUID=f7d1a1fa-2cbc-476a-899d-825a2decfca5
****************************************************************
No usable Linux, Windows or Mac partitions found on your disks.

[root@localhost files]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 3.8G 0 3.8G 0% /dev
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 3.9G 828K 3.9G 1% /run
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sda4 48G 6.7G 41G 15% /
tmpfs 3.9G 84K 3.9G 1% /tmp
/dev/sde1 5.5T 1.8T 3.4T 35% /var/hda/files/drives/WDRED6TB_1
/dev/sdd1 5.5T 1.8T 3.4T 35% /var/hda/files/drives/WDRED6TB_2
/dev/sdc1 5.5T 937G 4.3T 18% /var/hda/files/drives/WDRED6TB_3
/dev/sda2 477M 96M 352M 22% /boot
/dev/sda1 200M 8.3M 192M 5% /boot/efi
/dev/sda5 24G 33M 24G 1% /home
tmpfs 780M 0 780M 0% /run/user/48
none 4.0M 0 4.0M 0% /var/spool/greyhole/mem
tmpfs 780M 0 780M 0% /run/user/0
tmpfs 780M 0 780M 0% /run/user/1000
/dev/sdb1 74G 52M 70G 1% /var/hda/files/drives/GH_LandingZone

[root@localhost GH_LandingZone]# ls /var/hda/files
books drives mobile_media music other_audio pictures tv webcollab
docs greyhole trash movies network_backup owncloud9 software_repository videos
[root@localhost GH_LandingZone]# cd ..
[root@localhost drives]# ls[/code]
GH_LandingZone WDRED6TB_1 WDRED6TB_2 WDRED6TB_3
[root@localhost drives]# cd GH_LandingZone
[root@localhost GH_LandingZone]# ls
lost+found
[root@localhost GH_LandingZone]# dir
lost+found

(NOTE: Underline = green highlighted text in PuTTY. Not sure why some folders are marked and some are not...)

After mounting the drive, the public folder is now... gone? Oops? Is it recoverable or does this now mean that the real files located in the storage pool (WDRED...) are unlinked and therefore unusable unless I find a way to manually extract then and re-load?

Also, after mounting I now see that I now have two listings under the drive pooling dashboard for

/var/hda/files/drives/GH_LandingZone

I suppose I should delete one and if so... how do I know which one and how should I do that?

I restarted the Samba and Greyhole servers assuming that would fix everything but that didn't appear to make a difference in that the Public share is now inaccessible after mounting.

How can I look to see if those symbolic links got "misplaced"? Or maybe its not worth the effort? I backed up the public folder (since I wanted to test out this process before I move the important shares). So I could...

• create a new public directory with the right permissions (/var/files/drives/GH_LandingZone/public)
• manually delete the files in the Greyhole directory since it wasn't duplicated (/var/files/drives/WDRED6TB_3/gh/Public)
• and then copy new files to the share location from my Windows PC to make new links...?

I'll first try rebooting the entire machine first but after that... what do you suggest next to get this ironed out?

EDIT: Internet searching tells me that the "public" files that lived at /var/files/drives/GH_LandingZone/public BEFORE mounting the drive are still there, just hidden while the drive is mounted. In theory, if I un-mount the drive, move those files elsewhere temporarily, re-mount the drive, and then move them back... all should be well...?

(though that doesn't explain the duplicated partitions shown in Drive Pooling)

[bigfoot65]

EDIT: Internet searching tells me that the "public" files that lived at /var/files/drives/GH_LandingZone/public BEFORE mounting the drive are still there, just hidden while the drive is mounted. In theory, if I un-mount the drive, move those files elsewhere temporarily, re-mount the drive, and then move them back... all should be well...?

Yes if you unmount the drive, you can then move the public folder and it's contents. That would probable be best.

Also, after mounting I now see that I now have two listings under the drive pooling dashboard for

The only way to remove the duplicate is by editing the hda_production database. It's best to do using a web app, such as adminer App or phpmyadmin App.

Once you have done that and remounted the drive, all should work itself out.

All of this could have been avoided by not using the disk-wizard App. Always best to add drives manually and mount them as you have full control of the outcome. Until it's fixed, I have moved the app to BETA for Amahi 11 to deter users from installing it.

[astinusofmetate]

Yes if you unmount the drive, you can then move the public folder and it's contents. That would probable be best.
...
The only way to remove the duplicate is by editing the hda_production database. It's best to do using a web app, such as adminer App or phpmyadmin App.

unmount, move contents, re-mount, and move contents back seemed to work out well. Network share is now working as intended and all information has been retained.

As for the duplicate listing issue, that worked itself out when I rebooted the server (thankfully).

Appreciate the help and guidance on this issue.

[bigfoot65]

Glad to hear it's all working as designed now.

Marking topic as resolved.