craigr

Whew! Thank you sooooo much! I figured it had to be that way, but how intel spelled it out made me really question... Thanks for your help yet again. You’re a real asset to the forum. kind regards, craigr

For reference ark specifies that for my current E3-1275L v3 processors: Note that support is specifically stated for 1x16 or 2x8, and not just 1x16 for the "PCI Express Configurations." Thanks again and kind regards, craigr

I'm trying to figure out if the Intel® Xeon E3-1285L v4 processor will work in my Supermicro X10SLL-F main board. https://www.supermicro.com/en/products/motherboard/X10SLL-F https://ark.intel.com/content/www/us/en/ark/products/88043/intel-xeon-processor-e3-1285l-v4-6m-cache-3-40-ghz.html https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/xeon-e3-1200v4-vol-1-datasheet.pdf (see pages 26-27) From the Supermicro specifications it would appear that the answer would be yes. However, ark.intel specifies "PCI Express Configurations 1x16" for the E3-1285L v4 processor. Furthermore, the motherboard has 2 PCI-E 3.0 x8 slots and 1 PCI-E 2.0 x4 (in x8 slot). I wrote Supermicro and asked if the CPU would be supported and this is what they said: ark.intel TX says the answer is, "E3-1285L V4 is within this family which is supported." And from TX's cryptic response it seems that the PCH controls the PCI-E 2.0 x4 slot. Which then leaves 16x available for the E3-1285L V4 to control. So what I don't understand is can the E3-1285L v4's "PCI Express Configurations 1x16" be used for "2 PCI-E 3.0 x8 slots?" IE can one 1x16 lane CPU be used for 2x8 lane PCIe slots? I hope this makes sense because I have no idea if it will work or not and I don't want to buy a $255 CPU on eBay from China that will not allow all of my PCIe slots to functions as I need both 8x slots for my configuration. Thanks for any help! craigr

Little bug in the GUI:

That's what gets me. Mine is set to "auto" and I have never changed it Should I? Thanks, craigr

May I ask how one knows if this should be adjusted and to what value? Thanks, craigr

When you run the preclear, the two "Current pending sector" should go to zero and not increase if the disc has any hope. Since this is a Western digital drive, if the two sectors pending reallocation are readable the "Current pending sector" count and the "Reallocated event count" will both be zero after the preclear. If the two sectors pending relocation are not readable, then your "Current pending sector" count should go to zero and your "Reallocated event count" should go to two. IMHO if either of the above happen and you run three preclears and another extended SMART test than you could probably use the disc again. However, if the extended SMART test fails or your "Current pending sector" count or "Reallocated event count" goes higher than two, than the disc should be discarded. One of my 8TB REDs with less than a year's worth of hours suddenly had two pending sectors. I replaced the drive and rebuild the array (in your case without parity all you can do is try and copy the data first). I ran a preclear and then "Current pending sector" count and "Reallocated event count" both read zero after. I then ran another two preclears and then an extended SMART test. No new "Current pending sector" count or "Reallocated event count" so I then returned the disc to its original location in the array. The drive has worked flawlessly for many months since then. Best, craigr

Thinking about it more, it would be best to have an option in the SMB GUI to enable or disable v1.

IMHO a server designed primarily with being a media server is going to have to support SMBv1 for many years to come. Too many media tanks only support SMBv1 and they can’t just get phased out anytime soon. SMBv1 may be deprecated, but the media players that run them are not. Best, craigr

Also fwiw my DUNE players are not running Android. I have three Base 3.0 players and one SMART D1. These run Linux. Best, craigr

Sorry about that. I posted over there that it is fixed with "server min protocol = NT1." Thank you! craigr

Adding "server min protocol = NT1" worked for me. My DUNE media players and also my WindowsXP PC's can see unRAID again! Sweet and thanks! craigr

Here is testparm for version 6.6.7. Nothing about "client min protocol = SMB2_02." Just has "server max protocol = SMB3." Kind regards, craigr

Just dropped back to 6.6.7 again and can immediately see unRAID in windows xp again. DUNE's also work again. ugggggg craigr

So I disabled WSD and ran testparm again and the output file still have client min protocol = SMB2_02. More troubling is that my windows xp desktop no longer sees unRAID either. I did not notice this at first because all of my mapped network drives from unRAID still work! However, if I brows the network I can't see unRAID. I discovered this when I tried to copy the testparm.txt file from the flash drive because this drive is not mapped. I had to copy testparm.text to disk1 and the get it. craigr testparm.txt

Thanks for any help you can give. I set the SMB permissions back to default and testparm -sv. It's attached. I noticed "client min protocol = SMB2_02." Still cannot connect with the DUNE players. I see no unRAID folders at all. Best, craigr testparm.txt

what does -i br0 do? That is a zero right? craigr

Firmware update did not help the DUNE players. Still cannot access unRAID. In the unRAID SMB settings do you have "Enable WSD:" set to "yes" or set to "no" as I have tried both since updating the DUNE FW and neither work. Best, craigr

I have three BASE 3.0's and a Smart D1. I haven't updated the FW on the players since 2015 because there have been no new features I am interested in. I am updating one of them now to the latest 2019 beta to see if this helps. Will report back shortly. Thanks, craigr

Well, my DUNE players use the IP address of the unRAID server too. Also, when I go into "network browser > network places" in the DUNE the network places folder is empty. This is strange. As soon as I go back to 6.6.7 I't all fine again. grrr. craigr

I cannot get my DUNE players to connect to 6.8.0-rc3. As soon as I drop back to 6.6.7 the DUNE players work fine again. BRiT suggested it may have to do with the above so I just reinstalled 6.8.0-rc3 again and played with the SMB settings. This got me nowhere. I first tried disabling Enable WSD and that did not work. I tried disabling NetBIOS just for the heck of it and that of course did not help. I basically tried all the combinations even if they did not make sense. I am not positive, but I think the DUNE players do use SMBv1. How can I make this work? Thanks, craigr syslog

Installed RC3 today and now can't access and of my DUNE players via SMB. Tried deleting and recreating the DUNE user and resetting permissions on the shares. Also checked SMB settings. Reverted back to 6.6.7 and everything works fine again. craigr

/Media_4K/Movies/movie name Like that? craigr

Could you please give me the exact syntax for that? Thanks again, craigr

And what's weird is that when I put in that path it continues to recheck in its default download directory.