Connect
email: vic @ hong . com . au
mobile: +1 604-783-6519
office: +1 604-677-2829


Search
Twitter Updates

    Blog Categories
    Section2

    Entries in windows 2008 (2)

    Thursday
    Aug202009

    NexentaStor 2.0/2.1 + Windows 2008 SP2 FAIL

    Last week, I went ahead and upgraded a client's Windows 2008 domain controllers from SP1 to SP2. Reason, I'm always staying ontop keeping their Linux based NAS boxes working nicely with Active Directory etc, and thought it was a quiet time to update stuff across the board.

    As it turns out, once Windows 2008 was at SP2 level, the NexentaStor 2.0 box now doesn't work on CIFS shares. The only way to access them is to use the "guest" login (a login box appears when you browse to it from the network).

    Viewing the CIFS server log - got this:

    Aug 20 13:27:37 server1 smbd[352]: [ID 526780 daemon.notice] Failed to establish NETLOGON credential chain
    Aug 20 13:27:37 server1 smbd[352]: [ID 871254 daemon.error] smbd: failed joining domain.lan (UNSUCCESSFUL)
    Aug 20 13:27:37 server1 idmap[335]: [ID 694198 daemon.notice] Configuration unchanged

    After sending an email to support, they pointed me to:

    http://www.nexenta.com/nexentastor-relnotes - Scroll down to v1.1.9 - known problem

    and http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6850508

    I have been told this will be addressed in September... or we can roll back to SP1 on the domain controllers! WTF, I guess this is Sun that is just slow to move on a pretty big bug. :(

    Thursday
    May142009

    NexentaStor - n00by tips and tricks

    I now have a full licensed version of NexentaStor up and running for a client.

    During the testing phase, I had run the trial software to make sure it had all the features as advertised and functioned in a way that would be practical for contractors like us, that prefer a slick solution that minimizes the tweaking around as much as possible!

    Trail software was successfully run on:

    • VMWare Player/Fusion
    • Sun VirtualBox
    • ASUS P5W DH Deluxe mobo - with additional PCIe Intel E1000 nic (onboard nics not supported)
    • SuperMicro X6DVA series mobo

    Had no problems joining it to a Windows 2003 Active Directory (mixed mode - with a legacy Windows 2000 DC), setting ACLs, snapshots, browsing the .zfs folder, etc, etc.

    When it came to running on production hardware, we were unsuccessful getting it to run on:

    Next we tried:

    • SuperMicro X7SBL-LN1
    • This was put into a Supermicro 4ru Jbod chassis - 16 x 1tb drives
    • LSI SAS HBA - LSISAS3081E-R - set in jbod mode
    • If you need help with SAS cables - these guys are great help: http://www.cs-electronics.com

    No problems at all booting into NexentaStor now!

    During this time, the production network did have a domain controller upgrade. The old Windows 2000 and Windows 2003 domain controllers were demoted and fresh new Windows 2008 domain controllers took over AD tasks for the network.

    This is when I had the next challenge - I was able to get Nexentastor to join, and sometime NOT join the domain. Everything I did, could not get a AD user that was logged into a Windows box to access a CIFs share on NexentaStor.

    After hitting a Nexenta support, DNF Storage support, and reading every detail in the Nexenta User Guide, I figured there was a problem with our AD upgrade. Soooo, if you have a domain joining issue, I urge you to check every bit of your DNS server setup in AD.

    Even though in the forward zones, _msdcs.domain.lan all the relevant entries were correctly populated, the _msdcs zone within the domain.lan zone was incorrectly populated with old DCs entries.

    Once this was created, everything was good to go.

    One more gotcha... When setting ACLs on the CIF shares, don't just click every box in haste! If I did, I was still denied access to the share.

    Set as follows:

    • execute
    • read
    • create
    • write
    • delete
    • but NO inherit

    the inherit permission seemed to lock out access...