Linkstation LS-QV4.OTL/RS as Active Directory domain member.

[digithead]

Ok... sorry in advance as this is likely a really foolish question.  :-)

 

We just recently replaced an LS-QV4.OTL/RS for what appeared to be a failed motherboard. My question is this:

 

Is it possible for one of these devices to be forced into "EM mode" when they are an Active Directory Domain member and the "Password server"  of the domain suddenly becomes unavailable for a prolonged period of time? Although I do have quite a bit of experience with Samba and have never seen any adverse side effects of it not being able to contact the "password server" or the WINS server, just currious if I should be cautious about any potential risks.

 

Thank you in advance.

[davo]

digithead wrote:

Is it possible for one of these devices to be forced into "EM mode" when they are an Active Directory Domain member and the "Password server"

 

Yes it is possible and can happen any time regardless of network integration.

[digithead]

Ouch... ok, now that's a little scary.  :-)

[digithead]

Hhmm... looks like a second LS-QV4.OTL/RS may be having a problem. (That's a 100% failure rate for me if it is).

 

A scheduled RAID scan (which is currently still runing) and the LED is flashing amber, 1 long, 5 short which if I am not mistaken indicates it's trying to" load an update".  However, the firmware had already been updated back in December of 2012 the day it was brought home from the store and joined to the network.

 

Firmware: 1.64 (DTCP-IP:1.64-20121203)

 

Going to let the RAID scan complete before doing anything at all with it, but I'll be quite surprised if it comes out of this state and goes back to normal operation. This is the exact same thing the last one did which it never recovered from.

[digithead]

Oops... forgot to followup with this.

 

Yup... the device "recovered" on it's own just as I was hoping. Thinking about this logically would seem to indicate that the OS has a little bit of trouble "loading" what ever it was trying to load while the RAID scan was in progress. This would indeed seem to cause the caution LED flashing that I experienced.

 

The lesson here: Be patient when a RAID scan is running. Just let it complete as one should.  :-)