FreeNAS 0.69 Accessing Drive Data on Rebuilt Server
I had a a FreeNAS 0.69 RC1 Server which I used a few large drives to store data (shocker, I know). Using the Samba share feature I was able to use AD to connect to my Domain and make these shares available to the other users via drive mapping logon scripts. I was also able to use the types of shares in the Domain DFS without a problem.
Not understanding UNIX\Linux access permissions I kept my configurations in terms I understood. I shared out a specific directory and then I opened to the child directories and set the permissions on them. This allowed me to restrict/allow as needed.
...Then we bought a house in another town. My FreeNAS boot partition got corrupted and a reinstall didn't work as I'd expected. My answer to this was to rebuild the box as ver0.69 and reattach the drive. Simple, right?
Wrong. After adding the disks (as UFS EPT), creating Mount Points, Connecting to AD and creating Shares IF I am able to connect to a share (and that seems hit or miss) I ALWAYS seem to get "Access Denied" when trying to drill-down to child containers.
Two questions:
1) Why is setup so different now when it was BLISSFULLY simple with the RC1?
2) How can I reset the File & Folder permissions on EVERYTHING so that I can AT LEAST access the data that is already on the FreeNAS disks (..eh,..formatting the drives is a joke I've ALREADY heard one too many times, thank you :o Z )?
I'm trying to locate a specific backup job but, not being able to access any container other than the root of a share, I can't browse the child containers in order to look for it.
Not understanding UNIX\Linux access permissions I kept my configurations in terms I understood. I shared out a specific directory and then I opened to the child directories and set the permissions on them. This allowed me to restrict/allow as needed.
...Then we bought a house in another town. My FreeNAS boot partition got corrupted and a reinstall didn't work as I'd expected. My answer to this was to rebuild the box as ver0.69 and reattach the drive. Simple, right?
Wrong. After adding the disks (as UFS EPT), creating Mount Points, Connecting to AD and creating Shares IF I am able to connect to a share (and that seems hit or miss) I ALWAYS seem to get "Access Denied" when trying to drill-down to child containers.
Two questions:
1) Why is setup so different now when it was BLISSFULLY simple with the RC1?
2) How can I reset the File & Folder permissions on EVERYTHING so that I can AT LEAST access the data that is already on the FreeNAS disks (..eh,..formatting the drives is a joke I've ALREADY heard one too many times, thank you :o Z )?
I'm trying to locate a specific backup job but, not being able to access any container other than the root of a share, I can't browse the child containers in order to look for it.
You have to use production release - 0.69.1, not prerelease RC1
ASKER
I am using:
0.69 Kwisatz Haderach (revision 4276)
(SHAME on me for not including that theFIRST time)
0.69 Kwisatz Haderach (revision 4276)
(SHAME on me for not including that theFIRST time)
ASKER
....eh...additionally, The 0.69.1 is designated for AMD64 use. I'm i386 x32. I couldn't use that, correct?
ASKER
HEY!
Let m ask it this way:
"What is the linux command to reset file permissions of an entire volume?"
Let m ask it this way:
"What is the linux command to reset file permissions of an entire volume?"
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK. Good. This will need to be run for each directory?
I have downloaded a couple of whitepapers of Linux commands and I plan to study them as it is obvious I need to up my level of proficiency with Linux. I hoped against hope that I would be able to skirt-by with something simple. Oh well, if it makes my data available AND prevents any future moment of panic in the future......so much the better.
I have downloaded a couple of whitepapers of Linux commands and I plan to study them as it is obvious I need to up my level of proficiency with Linux. I hoped against hope that I would be able to skirt-by with something simple. Oh well, if it makes my data available AND prevents any future moment of panic in the future......so much the better.
in place of "dir" you can mention many directories to adjust permissions recursivly
Also chown command changes owner and/or group/
Also chown command changes owner and/or group/
ASKER
If I use this at the top-most container, will it reset the permissions all the way to the file-level?
Yes, it resets all permissions in all subdirectories.
Yes, it resets all permissions in all subdirectories.
ASKER
I will try it in the morning and award points once it's completed.
Sweet !! I'm psyched to have learned something AND to get my data back.
Sweet !! I'm psyched to have learned something AND to get my data back.
ASKER
OK. I'm trying to use the command now by using the Command function in the WebGUI. While I can still access the root of the share I can not access certain folders which were established under a different Windows account in my original setup (Months ago).
I know that Linux is case sensitive. When trying to reset the permissions do I replace 'dir' with the sharename+folder or is the sharename enough?
My goal is to restore the data to it's original state. I had shared the drives and then managed access and permissions via the Windows accounts on my Domain. Since I first install FreeNAS I have since rebuilt the MS Domain so I realize that there will/are AD SIDs which cannot be resolved by FreeNAS as these accounts no longer exist.
Any help is appreciated. I am reviewing the use of chmod and chown and hopefully a light will go on in my head eventually.
I know that Linux is case sensitive. When trying to reset the permissions do I replace 'dir' with the sharename+folder or is the sharename enough?
My goal is to restore the data to it's original state. I had shared the drives and then managed access and permissions via the Windows accounts on my Domain. Since I first install FreeNAS I have since rebuilt the MS Domain so I realize that there will/are AD SIDs which cannot be resolved by FreeNAS as these accounts no longer exist.
Any help is appreciated. I am reviewing the use of chmod and chown and hopefully a light will go on in my head eventually.
ASKER
Mapping a drive from Windows XP to...
FreeBSD
FreeNAS 0.69 RC1
NAS Server
I'm TRYING to reset the folder and file permissions on the drive's contents so that I can "Start Over" and repermission appropriately.
ANY Help in adding a Zone, or Zones is appreciated.
Thanks.