I have an odd issue

hardware

Asus m5a97 v2.0 motherboard, supports AMD Virtulization

AMD FX 8350 cpu

24gb ram

7 hard drives

Asus Nvida 750 ti video card

 

I build my server on 6 Beta 15, upgraded to RC 2 and now RC3

On Beta 15 I did the following;

1. built server

2. copied data from old server to new server

3. moved a few drives from old server to new server

4. formatted drives and balanced data between drives

5. attempted to build a VM but realized I was missing the drivers ISO

6. set SMB to join my Active Directory

7. granted a little different perms on a few shares (granted higher perms on a couple shares for a couple users)

 

During this I rebooted several times and all was well (at least as far as I remember)

 

I updated to RC2 and downloaded the drivers ISO and attempted to copy it to a share on the server from my laptop and was prompted for an ID and Password, I entered my ID and Password and as told Password was incorrect, I attempted to log on with domain admin ID and password and again was told ID and password was incorrect. I did the following

1. reset perms, no help

2. disjoined the unraid from the domain

3. rebooted unraid

4. verified it was disjoined

5. rejoined domain

6. rebooted unraid, waited till fully rebooted

7. rebooted AD DC , waited till fully rebooted

8. rebooted client

9. verified I had full connectivity to shares again

10. copied Drivers ISO to share

11. went on to unraid to create VM

12 the VMs menu item was missing

13. went to settings > VM Manager and received a message stating that my hardware didn't support virtulization (I know it does)

14. rebooted unraid (stopped array, then restarted via button on screen as I always do)

15. when the system came back up verified that VMs menu option was available

16. built basic VM

17. attempted to access share from laptop again and again was prompted for ID and password

18 repeated steps 1 through 9 above again

upgraded to RC3

rebooted and lost access to shares again

repeated steps 1 through 9 above again but this time the VM option was still there

I rebooted as a test

lost access to shares again

repeated steps 1 to 9 again and have now left it knowing that I will loose access again if it is rebooted again.

 

 

The other issue/feature I would like is I am not able to directly access my video card through a VM, I was hoping to be able to dedicate this card to 1 VM.

 

I will attach 2 log files one is with the VMs working and shares not working, the other is with everything working prior to reboot

 

Bill

 

Edited for spelling

syslog_all_working.zip

here is the 2nd sys log

syslog_vm_working.zip

I verified this again this evening.....

 

I rebooted the system and lost all access to shares from AD computers

 

so I

1. stopped the array

2. disjoined from the domain (this took 2 or 3 times of attempting to disjoin)

3. changed SMB to No

4. rebooted the Unraid (starts up with array stopped)

5. changed SMD settings to AD

6. joined AD domain (again took several attempts for it to take)

7. rebooted unraid

8. started array

9. rebooted client laptop (Windows 7)

10. verified no access to unraid

11. repeated steps 1 to 6

12. started Array

13. rebooted client laptop

14. verified access to unraid shares.

 

I have access to shares when I join the Unraid to the domain until the server is rebooted, at that point all access is lost until I disjoin and rejoin the server.

It is used on a regular basis.

 

Sorry Aramosko, I don't understand your comment.... Are you saying you use UnRaid with AD Integration on a regular basis (including rebooting the unraid without loosing access, and with following the same upgrade process I had followed) without issues? Or are you saying that this is an important issue because it is used on a regular basis?

It is used on a regular basis.

 

Sorry Aramosko, I don't understand your comment.... Are you saying you use UnRaid with AD Integration on a regular basis (including rebooting the unraid without loosing access, and with following the same upgrade process I had followed) without issues? Or are you saying that this is an important issue because it is used on a regular basis?

 

You can ignore his post, it was a spambot.

I was really hoping this would be better or resolved with RC4 but my server wouldn't update to RC4, so I wiped my 2nd USB and loaded RC4 on it and started from scratch.... I am back up and running,  but had to reboot to try to get a 2nd NIC to pass through to a VM and I lost access to my shares again

 

I am really hoping this this gets resolved, I can't believe I am the only person who has found this issue.... I know UnRaid is used in businesses and it would surprise me if none of them have had this issue!

I was really hoping this would be better or resolved with RC4 but my server wouldn't update to RC4, so I wiped my 2nd USB and loaded RC4 on it and started from scratch.... I am back up and running,  but had to reboot to try to get a 2nd NIC to pass through to a VM and I lost access to my shares again

 

I am really hoping this this gets resolved, I can't believe I am the only person who has found this issue.... I know UnRaid is used in businesses and it would surprise me if none of them have had this issue!

What Windows domain controller are you using (OS version)?

Currently 2008 r2. I will be building a new vm DC so if there is an OS that is known to work better I am game, as am IT geek I would like to stay fairly currently so that I am working on tech that is commonly used.

 

 

Well I think Tom patched something on this but need to check if that's in the internal RC we are testing right now or of this is in rc4.

In RC4 Something changed, I can disjoin the domain, but i CANNOT change the SMB type from AD to workgroup, or no.

 

Thankfully Disjoining the the domain, rejoining to the domain, and then rebooting the client does work. but it is troubling that I cant modify the SMB setting now in RC4.

one other issue that is kinda related....

 

When I have access to the my AD shares, I loos both VMs and Dockers in the top menu bar (and my 1 current Docker is not running). If I reboot the server I gain access to VMs and Dockers again, but I loose access to my network shares.

 

With not being able to change SMB settings to workgroup or none this is a 100% deal breaker.

 

I just verified... I rebooted, I have both docker and VM in the top menu, Docker is running (VM isn't due to another issue in another thread) shares are not accessible. I dis-joined server from AD domain, rejoined to AD Domain and Docker and VM disapeared from top menu bar.

 

The only Docker I have running is Koma (combo Mariadb and Kodi) to act as central DB for all my Kodi systems running, so they all need access to BOTH shares and docker at the same time.

Ok I stopped the array

Disjoined from the domain

Was able to change SMB setting (I think I hadn't stopped array previously)

Rebooted the server

Before starting the array rejoined the domain and changed SMB settings

Started the array

All 3 items are working, VM, dockers, and shares.

 

This doesnt correct the issue of loosing access to the shares on reboot, or having to choose between access to the shares and access to the dockers and vms, but at least i have figured out a work around.

 

Bill

A side note - I've experienced this once or twice myself.

 

What I found was that if I did a

net use \\tower\ipc$

and entered credentials (may need the

/user:domain\username *

snippet too) everything magically sprang back to life, and remained that way. I'm not sure if it was a client issue or a server config issue, as I only ever had my primary workstation fail.

 

From memory, this happened after initially joining the domain, and also after re-joining. Also after one upgrade (where the join fell away).

 

Another thing to use to try to establish a look - connect your Computer Management MMC to the UNRAID server. May need to do the above net use first. Most of the WMI interfaces obviously don't provide you detail (event logs would be very cool Tom!!), but you should be able to see all your shares under:

- Computer Management (Tower)

-- System Tools

--- Shared Folders

---- Shares

 

Haven't had a problem for the last three or four upgrades (b12 onwards or so)

Small update - this just occurred on upgrading from rc5 to 6.0.0.

 

My AD unjoined itself; manifesting as nothing responding to \\TOWER (correct since SMB was in AD mode)

 

Rejoined the domain

 

Try to browse in explorer and prompted for credentials. Didn't try entering; instead did a command line net use \\tower\ipc$ and entered my domain credentials.

 

Everything fine after that.

 

Note I access via shortname (NetBIOS equivalent naming) rather than FQDNs internally. Small network and FQDNs always give zone warnings that I cannot be bothered resolving when the former works well for me.

 

I am seeing the same behavior Schar is reporting on server reboots now.

 

This is slightly different from what I originally reported but still a big issue if we need to go in and rejoin the server to the domain each time the server is rebooted.

I've not had a problem since the upgrade; but I also don't reboot that often.

 

Having said that, I installed a new spinning and solid state drive last week (6.0.1) and rebooted without issue. Still joined and still have access.

I've not had a problem since the upgrade; but I also don't reboot that often.

 

Having said that, I installed a new spinning and solid state drive last week (6.0.1) and rebooted without issue. Still joined and still have access.

I've noticed if the array shuts down incorrectly (needs to do a parity check on startup), AD does not join automatically.