Message Prompt: Recycle Bin * is corrupted

[Mike77]

Hi,

I have an old Vaio SVS13A1W9ES that hasn't enough storage space. I don't seem to be able to get a bigger SSD for this machine because Sony gave it a very special hardware setup. :-S

So I've moved all the user Libraries to a CIF on my Freenas machine (Mapped the network drive on Windows 10) and now I keep getting the following message: "The Recycle Bin on Z:\Libraries\* "(* being the name of the folder i.e. Pictures)" is corrupted. Do you want to Empty the Recycle Bin for this drive?"

This message pops up for all the moved folders at startup and every time I select a file in one or any of these folders. So it's very annoying.

I've already posted my request for help on a couple of Windows forums, but the replies sadly didn'tsolve the problem.

Please help!!

 

[Ericloewe]

I have an old Vaio SVS13A1W9ES that hasn't enough storage space. I don't seem to be able to get a bigger SSD for this machine because Sony gave it a very special hardware setup. :-S

Sony and anticompetitive business practices? No way! /s

How is the share configured?

 

[Mike77]

Sony and anticompetitive business practices? No way! /s

How is the share configured?

Storage:

Volume :NAS-SEAGATE (It's a single 2 TB Seagate)
Dataset: NAS-SEAGATE
Dataset: VAIO-NAS
Dataset: VAIO-BU

Set permissions

Permissions:
Apply Owner (user): Yes
Owner (user): User1
Apply Owner (group): Yes
Owner (group): Vaio-Users
Apply Mode: Yes
Mode: Everything Yes, except write for Other

Permissions type: Windows

Permissions set recursively

Sharing (Windows Cifs)
Path: /mnt/NAS-SEAGATE/VAIO-NAS
Use as homeshare: No
Name: VAIO-NAS
Apply Default Permissions: Yes
Export read only: No
Browsable to network cliënts: No (nobody but the Vaio has to see it)
Export Recycle Bin: Yes
Show Hidden Files: No
Allow Guest Access: No
Only Allow Guest Acces: No
Host Allowed: Non added
Hosts Deny: None added
VFS Objects: Non selected
Snapshots: as it is
Auxiliary Parameters: nothing added

 

[Mike77]

Does my last post contain the correct information?

 

[Mike77]

Anyone?

 

[rogerh]

It does rather look as though no-one here has the slightest idea what is causing your problem. If it is just in Windows 10 it may be a bit new, I suppose!

 

[Ericloewe]

I don't typically map drives, but I haven't seen the problem.

Got a somewhat-surprise update to Windows 10 the other day, even though I was waiting for a Windows 8.1-like OneDrive.

 

[Mike77]

Get it. But might be a problem with permissions.

The point is that Windows 10 creates a $Recycle.bin file in all mapped drives and moved folders. For some unclear reason it can't access those or create those on the FreeNas drives. I already tried replacing the location of the moved userfiles from the FreeNas Machine to an extra internal SSD on the Windows machine, which works.

I've looked at the Windows permissionsregarding the $Recycle.bin file. They give full access to SYSTEM and the local account (administrrator group). I tried adding these to the CIF, but wasn't able to. In this case local seems to mean local with the local domain (name of the computer). But even if I was able to set these permissions correctly, I wonder if they would hold after emptying the recycle bin, because that means that the bin folder and everything in it gets removed and a new $Recycle.bin gets created.

Anotherpoint what I was wondering about is the .recycle folder in FreeNas. Does this work in the same way and when do files on the NAS get moved to it? Maybe it's a problem with two bin's competing over the same files?

On the otherhand this all might just be me ranting like a crazy man. But thats in part at least the fault of me having to klik yes five times everytime I select a file. :)

And please pardon my spelling. English language

 

[rogerh]

Have you tried setting the permissions on your folders in the shares via Windows? This may work better than setting them recursively from the dataset info in FreeNAS.

 

[Mike77]

Have you tried setting the permissions on your folders in the shares via Windows? This may work better than setting them recursively from the dataset info in FreeNAS.

That's the problem. I don't seem to be able to give my local account on the Laptop full permission. Only the account (same name and password) from the NAS Domain. And for some reason that doesn't seem to be enough. In the advanced permissions tab I found an account: Local Account, and an account: Local Account member of the Administrators group. But everytime when I've added them, they soon disappear again. I might be wrong, but it seems to mee that it's not really possible to change the permissions via Windows.

 

[anodos]

Get it. But might be a problem with permissions.

The point is that Windows 10 creates a $Recycle.bin file in all mapped drives and moved folders. For some unclear reason it can't access those or create those on the FreeNas drives. I already tried replacing the location of the moved userfiles from the FreeNas Machine to an extra internal SSD on the Windows machine, which works.

I've looked at the Windows permissionsregarding the $Recycle.bin file. They give full access to SYSTEM and the local account (administrrator group). I tried adding these to the CIF, but wasn't able to. In this case local seems to mean local with the local domain (name of the computer). But even if I was able to set these permissions correctly, I wonder if they would hold after emptying the recycle bin, because that means that the bin folder and everything in it gets removed and a new $Recycle.bin gets created.

Anotherpoint what I was wondering about is the .recycle folder in FreeNas. Does this work in the same way and when do files on the NAS get moved to it? Maybe it's a problem with two bin's competing over the same files?

On the otherhand this all might just be me ranting like a crazy man. But thats in part at least the fault of me having to klik yes five times everytime I select a file. :)

And please pardon my spelling. English language

I just performed the following tests with Windows 10 system:

• Mapped network drives via GUI and "net use"
• Opened mapped network drives on both AD member server and standalone server (via Guest session on standalone)
• Created and deleted files and folders on AD member server and standalone server

I have not been able to reproduce your problem. There is some indication in samba mailing lists that your problem is permissions-related, and possibly related to SID mapping. Review your winbind logs.

 

[Mike77]

Anodos, thanks. But you lost me here.

On a Windows 10 system, using a local account (not the build in Administrator account), you mapped network drives from a FreeNas Box. You used the GUI and the (cmd +R) net use command. I don't understand what a I'm not sure what an AD member server and standalone server are in this context. And then you created files and folders on this machine. If I understand you correctly, this means that you can create files on your FreeNas drives. I can do this to. Otherwise I woudln't be able to use my FreeNas and would be very sad at the moment.

My problem is just with the user files and relocating them (move by using the GUI location menu) to the FreeNas. Microsoft thinks these directory's are special in some way (we even have a new group with more of the same: Quick Acces), so they behave differently. I don't know what SID mapping is but I'm going to look it up in a moment.

I just looked at the permission in the Windows user files and the moved user files on the mapped drive.
Windows user folders:
SYSTEM: full access;
User (local domain and account in Admin group): full access;
HomeUsers (local domain in HomeUsers);
Administrators (local domain): full access.

FreeNas folder:
Everyone
SYSTEM: full access
root (root on FreeNas domain): full access
User1 (user on FreeNas domain, owner, with same name as the user on the local Machine): full access.

I turned Windows file Indexing of via the Windows machine and I removed the files attributes in FreeNas (to speed things up).
I hope it's usefull information.

Edit:

Just found out that you probably mean Active Directory. I don't have/use Activa Directory. But I loooked in computer management and connected to the NAS. But that won't work because it's not browsable to network cliënts. The only computer that has access to it is the Laptop.

I still don't know what you meen with SID and Winbd Log. But I'm looking. I found something about SID files in regard to migrating permissions, but it's not really clear to me in what way this is doing something here.

 

[anodos]

Anodos, thanks. But you lost me here.

On a Windows 10 system, using a local account (not the build in Administrator account), you mapped network drives from a FreeNas Box. You used the GUI and the (cmd +R) net use command. I don't understand what a I'm not sure what an AD member server and standalone server are in this context. And then you created files and folders on this machine. If I understand you correctly, this means that you can create files on your FreeNas drives. I can do this to. Otherwise I woudln't be able to use my FreeNas and would be very sad at the moment.

My problem is just with the user files and relocating them (move by using the GUI location menu) to the FreeNas. Microsoft thinks these directory's are special in some way (we even have a new group with more of the same: Quick Acces), so they behave differently. I don't know what SID mapping is but I'm going to look it up in a moment.

I just looked at the permission in the Windows user files and the moved user files on the mapped drive.
Windows user folders:
SYSTEM: full access;
User (local domain and account in Admin group): full access;
HomeUsers (local domain in HomeUsers);
Administrators (local domain): full access.

FreeNas folder:
Everyone
SYSTEM: full access
root (root on FreeNas domain): full access
User1 (user on FreeNas domain, owner, with same name as the user on the local Machine): full access.

I turned Windows file Indexing of via the Windows machine and I removed the files attributes in FreeNas (to speed things up).
I hope it's usefull information.

Edit:

Just found out that you probably mean Active Directory. I don't have/use Activa Directory. But I loooked in computer management and connected to the NAS. But that won't work because it's not browsable to network cliënts. The only computer that has access to it is the Laptop.

I still don't know what you meen with SID and Winbd Log. But I'm looking. I found something about SID files in regard to migrating permissions, but it's not really clear to me in what way this is doing something here.

Click on "system" -> "advanced" -> "save debug" and send me the file via PM.

 

[Mike77]

I've send you the file

 

[rogerh]

You do want to allow Windows file attributes on FreeNAS, otherwise Windows permissions won't work properly. I don't know about recursive file permissions in FreeNAS, could there be a problem with Windows successfully overruling them? If the highest level folders within the dataset have their permissions set recursively by Windows the enclosed files may behave more predictably. Edit: now you have an offer of help by an expert you probably don't need to take too much notice of my theories!

 

[anodos]

You do want to allow Windows file attributes on FreeNAS, otherwise Windows permissions won't work properly. I don't know about recursive file permissions in FreeNAS, could there be a problem with Windows successfully overruling them? If the highest level folders within the dataset have their permissions set recursively by Windows the enclosed files may behave more predictably. Edit: now you have an offer of help by an expert you probably don't need to take too much notice of my theories!

I'd hesitate to call myself an expert. "Slightly-enlightened noob who spends too much time on forums" is a more apt description. File attributes and permissions are different things. You can relatively safely disable the file attributes (I do that on my servers). There are a few edge cases where poorly-written or really old software chokes if they're disabled.

I think that you're having some problems with id mapping. log.winbind-idmap contains quite a few of the following entries

Code:

../source3/winbindd/idmap_tdb_common.c:140(idmap_tdb_common_allocate_id)
  Error allocating a new GID

log.smbd has the following message repeated over and over

Code:

  nfs4_acls.c: file [Pictures/Camera Roll]: could not convert S-1-5-113 to uid or gid
[2015/08/13 16:26:13.425088,  1] ../source3/modules/nfs4_acls.c:749(smbacl4_fill_ace4)

Post output of "net groupmap list".

It might be a good idea to reset permissions on the shares by opening the share config, clicking on "apply default permissions", and hitting "OK". I noticed you've had problems in the past with SID-GID resolution. If resetting permissions doesn't work, I'd seriously consider just reinstalling FreeNAS and seeing if the problem persists on a fresh install.

 

[Mike77]

@anodos: thank for your help!!

I could have guessed it. To bad. I think I'll go for the new install and see if that will help.

By the way, I get an errormessage on FreeNas that the firmware and the driver of the raid controller on my motherboard (Supermicro X10SL7-F) are out of sync. I've flashed the new firmware, version 19, but FreeNas seems to be using a driver version 16. Is this driver going to be upgraded, or should I change the firmware back to version 16?

 

[anodos]

@anodos: thank for your help!!

I could have guessed it. To bad. I think I'll go for the new install and see if that will help.

By the way, I get an errormessage on FreeNas that the firmware and the driver of the raid controller on my motherboard (Supermicro X10SL7-F) are out of sync. I've flashed the new firmware, version 19, but FreeNas seems to be using a driver version 16. Is this driver going to be upgraded, or should I change the firmware back to version 16?

Yes. Go back to P16. When you reinstall, make sure to go through the process of 'apply default permissions' again.

 

[diedrichg]

Windows of any flavor does not fair well with mapped drives on initial startup. Because you moved your user folders that are expected to be immediately accessible on the machine, it simply doesn't know what to do when trying to locate your user folders.

What you should have done, and what you should do, is have a dataset for your user. On that dataset you would then create folders such as Pictures, Documents, Videos, etc. and then COPY your files to those new folders - do not MOVE (remap) the user folders. Now that you have verified everything copied over without errors, you can safely delete the data in your user folders on the Windows machine. On Windows you will then map a network drive for the CIFS share that points to the user's dataset. From there you can create symlinks in Windows to your folders. http://www.howtogeek.com/howto/162...symbolic-links-symlinks-on-windows-or-linux/ You can also make those symlinks part of your Libraries.

 

[anodos]

Windows of any flavor does not fair well with mapped drives on initial startup. Because you moved your user folders that are expected to be immediately accessible on the machine, it simply doesn't know what to do when trying to locate your user folders.

What you should have done, and what you should do, is have a dataset for your user. On that dataset you would then create folders such as Pictures, Documents, Videos, etc. and then COPY your files to those new folders - do not MOVE (remap) the user folders. Now that you have verified everything copied over without errors, you can safely delete the data in your user folders on the Windows machine. On Windows you will then map a network drive for the CIFS share that points to the user's dataset. From there you can create symlinks in Windows to your folders. http://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/ You can also make those symlinks part of your Libraries.

+1

I didn't realize we were dealing with user Libraries.