We have a bit of an unusual one for you today.
We have a seagate central NAS box. It's simple, it stores data and it's fantastic for time machine backups on a mac. But we have a problem...
The problem.
Well it has a public drive. When you first get the box and set it up, you have to create a user via the web interface.
When you create a user interface, it automatically creates that user a private folder on the top level.
Why do you need this user you ask if all you want to do is run a time machine backup? Well to run a time machine backup, you need to access the drive as a registered account. Guests cannot backup via time machine to it.
So we were working well and we stored files in our public drive. But then the problem.
It turns out that if you are logged in as a registered guest to the Seagate Central NAS drive on an Apple Mac, you don't have write permissions on the Public share. Only Read.
This was partially to do with how we copied the data. We performed an rsync from our original data store to the new drive. This seems to be the cause of the problem.
Well we have a solution for you. Follow the below to resolve and give your new account write permissions to the Public share:
If done successfully you will now have write permissions when logged in as a user to the drive.
Please beware. We cannot be held responsible for any damage or data loss caused by performing these steps on your own.
Was this post helpful to you? If so we would like to hear your thoughts. Please comment below or re-tweet below.
We have a seagate central NAS box. It's simple, it stores data and it's fantastic for time machine backups on a mac. But we have a problem...
The problem.
Well it has a public drive. When you first get the box and set it up, you have to create a user via the web interface.
When you create a user interface, it automatically creates that user a private folder on the top level.
Why do you need this user you ask if all you want to do is run a time machine backup? Well to run a time machine backup, you need to access the drive as a registered account. Guests cannot backup via time machine to it.
So we were working well and we stored files in our public drive. But then the problem.
It turns out that if you are logged in as a registered guest to the Seagate Central NAS drive on an Apple Mac, you don't have write permissions on the Public share. Only Read.
This was partially to do with how we copied the data. We performed an rsync from our original data store to the new drive. This seems to be the cause of the problem.
Well we have a solution for you. Follow the below to resolve and give your new account write permissions to the Public share:
- On a mac, open a terminal window (on Windows you will need putty)
- Enter the following ssh username@ipaddressofSeagate e.g. [email protected]
- You will then be prompted for a password, enter the password of the account you set up
- Once logged on, the prompt will change to the hostname of the device. This is how you know you are connected.
- Change to the root user by typing su -
- Change to the root director by entering cd /
- Change directory to the Public drive using cd Data/Public
- Under the public drive, we will then run a command on each of the directories that are causing problems.
- Enter ls to display all folders within the Public directory
- In this example we have a Data folder and an Accounts folder
- Run the following command on each folder that is causing problems chmod 0777 -R Data/
- Once this has returned back to the cursor we can run the same on the Accounts directory chmod 0777 -R Accounts/
- We ran this because we have already changed to the Public drive. If you have not changed to the public drive you will need to run the following commands chmod 0777 -R /Data/Public/Accounts/
- We will then exit out of the root user by typing exit
- We will then type exit once more to exit out of the Seagate console
If done successfully you will now have write permissions when logged in as a user to the drive.
Please beware. We cannot be held responsible for any damage or data loss caused by performing these steps on your own.
Was this post helpful to you? If so we would like to hear your thoughts. Please comment below or re-tweet below.