Hey everyone, I've been having a problem with my Raid array. I'm using an ASUS Sabertooth 990fx R2.0 on Windows 8.1 with Two Western Digital Caviar Black 1Tb HDD's in Raid 0 and Two 60gb SSD's for my OS. The problem occurs when I start my computer and it goes to the Desktop. Sometimes I get an error saying Logical drive 'HDD has gone offline' and I cannot get access to the drive.
I have updated my Bios and drivers but there wasn't an update for the RAID array for W8.1. So I'm still using the drivers from Windows 8 on my RAID. Could this be a sign that my HDD's are failing and I'll need to replace them? I've only had them for two years. Any help is much appreciated! Yes the first step would be to test the drives outside of the raid array.Disconnect the 2 blacks from the amd ports and connect one of them to the asmedia port. Enable the asmedia sata3 controller in ahci mode and then boot up and test the drive.Then you can repeat the test with the other drive connected.When you're done you can connect them back to the AMD raid ports and power back up.Note - this will not affect the raid unless the drive(s) actually has problem.
I assume you already have a current backup of important data, which you should always have, but if not then that would be the first thing to do.
This cmdlet is available only in Exchange Server 2010.Use the Remove-ClientAccessArray cmdlet to remove RPC Client Access arrays (load-balanced arrays of Client Access servers within a single Active Directory site).For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax.In this article Syntax Remove-ClientAccessArray-Identity -Confirm-DomainController -WhatIf DescriptionYou need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet. Examples- Example 1 - Remove-ClientAccessArray -Identity casarray01.contoso.comThis example removes the existing Client Access array with the FQDN value casarray01.contoso.com. The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.Destructive cmdlets (for example, Remove-.
cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.Most other cmdlets (for example, New-. and Set-.
This cmdlet is available only in Exchange Server 2010. Use the Remove-ClientAccessArray cmdlet to remove RPC Client Access arrays (load-balanced arrays of Client Access servers within a single Active Directory site).
cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.Type:SwitchParameterAliases:cfPosition:NamedDefault value:NoneAccept pipeline input:FalseAccept wildcard characters:FalseApplies to:Exchange Server 2010. The WhatIf switch simulates the actions of the command.
You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. Type:SwitchParameterAliases:wiPosition:NamedDefault value:NoneAccept pipeline input:FalseAccept wildcard characters:FalseApplies to:Exchange Server 2010InputsTo see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. OutputsTo see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn't return data. Related Links.