SOLVED: Moved Landing Zone. Now Hidden/Missing and Still Uses Root?
Posted: Sat Dec 28, 2019 11:21 pm
(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
Per the wiki, I successfully executed the following
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!
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
Code: Select all
mv /var/hda/files/public /var/hda/files/drives/GH_LandingZone/public
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!