I would like to copy my old (G:/) drive to my UnRAID server. How do I create that and call it "Old G:/ Drive"?

I would like to copy my old (G:/) drive to my UnRAID server. How do I create that and call it "Old G:/ Drive"?

Probably not possible to have a user share with exactly that name. I'm pretty sure Windows at least would have an issue with the :

Actually, I just want to Map a network drive and call it G:\. How do I set that up?

Actually, I just want to Map a network drive and call it G:\. How do I set that up?

That's in windows.  Hit map network drive and select "G" as the drive letter/

What's the path?

Whatever share you've created on your tower.  eg: \\tower\Old G  if you created a share called "Old G"

Of course....I should've known that!. Thanks for your patience and quick replies.

Got it to map but, when I try to paste files, it indicates that 'Access is Denied'.

Got it to map but, when I try to paste files, it indicates that 'Access is Denied'.

Your windows user probably doesn't have write access to the share.

The Windows user (me) has Admin rights. Is the write access set up in Windows or UnRAID? Can you set up different access rights in UnRAID or do all users who map to the server have write access?

The Windows user (me) has Admin rights. Is the write access set up in Windows or UnRAID? Can you set up different access rights in UnRAID or do all users who map to the server have write access?

Depending on what you want to do, you may have to set it up in both places. Normally you set it up in unRAID to match your Windows logins.

 

Each user share has a security setting. It can be Public, Secure, or Private.

 

Public - anybody can read/write.

Secure - anybody can read but only specified users can write.

Private - you specify which users can read and which users can write.

Ok.....my UnRAID User share is set up as Public. So, how do I check the access rights in Windows XP? Or, do I need to set up an UnRAID Disk share instead?

Ok.....my UnRAID User share is set up as Public.

That means that anyone has full access, so as such the Windows end should not matter.  You may need to run Tools->New Permissions on unRAID to ensure permissions are correct at that end.

I only have the Root user in UnRAID. Should I create another user? Syslog is indicating that the User share that I created is a (30) Read-only file system. When I click on the Size column under the User Shares screen, it drops down and just shows Disk 1. Is that indicating that the User share I set up is just on Disk 1.....why wouldn't it be across all the disks?

 

Also, looking in the Syslog, why does it still refer to my server as Tower when I've changed the name and rebooted?

Go to Tools - Diagnostics and post complete diagnostics zip.

Here are the Diags.

beall-diagnostics-20151101-0919.zip

This thread started with a question about mapping a drive in Windows, but after looking at your syslog, it's not clear that you actually have anything in unRAID to map. I have reviewed the your post history.

 

Are these drives you took from a previous system? Did you preclear them? More importantly, did format them in unRAID?

 

Post a screenshot of Main.

I followed all the videos but, I may have missed something.....

From console or telnet, what do you get with this?

ls -lah /mnt/user

I get this.....

From Windows File Explorer, can you see your server on the network? If so, what is its name?

For some reason, I can see the Flash drive that the UnRAID 6.1.3 is stored on for boot up but, not the server itself. However, I am able to Map to the User share I created. Also, I tried to save a small file to the Flash drive and was able to do that!

From console or telnet, what do you get with these?

ls -lah /mnt/disk1

ls -lah /mnt/disk2

ls -lah /mnt/cache

ls -lah /boot

I get this.....

Your syslog makes me think you may have filesystem corruption rather than an actual permissions / security issue when trying to write to the server from Windows. But that seems unlikely since you have just built the array and the drives are almost empty. So that is why I have been looking at it from the server side instead of Windows.

 

Let's see if you can write to disk1. This command will attempt to copy your syslog to your share on disk1.

cp /var/log/syslog /mnt/disk1/BeallStorage1/syslog.txt