[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)