CLOSED: Windows 10 Doesn't Like Greyhole Shares
Posted: Thu Apr 27, 2017 9:53 pm
Tonight I installed 2x6TB (new) drives. Used Disk Wizard to mount and format (EXT4) and then purchased the Greyhole UI app in hopes of making this easy.
I clicked a few shares to include in the pool and thought I'd test things out by transferring a couple of MP4 format movies over the network from my Windows 10 machine to the HDA.
Good news is that it works. The bad news is that I get an annoying "unexpected error 0x8007003b" pop up. The Internet tells me that this is a semi-common issue with the latest Windows 10 update (Anniversary, not Creator's... yet). Workarounds include hotfixes for Windows 10, disabling search indexes on Windows 10, downgrading the SMB on Windows (as discussed here: viewtopic.php?f=8&t=6292&start=10#p35856), and changing the "strict allocation" setting in smb.conf on the server side.
Before I start doing something drastic I did want to point out that I am NOT having this issue with the non-pooled shares.
Any ideas on what I can do to further investigate the problem? Is it a greyhole setting I should look into or is there possibly some sort of network delay overhead issue that Windows 10 just doesn't like when it comes to dealing with Greyhole shares? Or... ?
I clicked a few shares to include in the pool and thought I'd test things out by transferring a couple of MP4 format movies over the network from my Windows 10 machine to the HDA.
Good news is that it works. The bad news is that I get an annoying "unexpected error 0x8007003b" pop up. The Internet tells me that this is a semi-common issue with the latest Windows 10 update (Anniversary, not Creator's... yet). Workarounds include hotfixes for Windows 10, disabling search indexes on Windows 10, downgrading the SMB on Windows (as discussed here: viewtopic.php?f=8&t=6292&start=10#p35856), and changing the "strict allocation" setting in smb.conf on the server side.
Before I start doing something drastic I did want to point out that I am NOT having this issue with the non-pooled shares.
Any ideas on what I can do to further investigate the problem? Is it a greyhole setting I should look into or is there possibly some sort of network delay overhead issue that Windows 10 just doesn't like when it comes to dealing with Greyhole shares? Or... ?