F
F
FloorZ2015-09-22 05:13:01
RAID
FloorZ, 2015-09-22 05:13:01

How to treat error 129 in win?

Good afternoon. There is a server on the R1208GZ4GC platform. He has an Intel C600 Raid controller. It has two mirrors. Two 500GB SSDs, the model is unknown, this is \Device\RaidPort0. Two 800GB SSDs, this is SDSC2BX800G401, port \Device\RaidPort1.
That's just after installing the second raid, the problems started. After about 23 hours of active work, errors begin to appear in the OS log

Reverted back to \Device\RaidPort1.

Error code 129.
Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="iaStorS" /> 
  <EventID Qualifiers="32772">129</EventID> 
  <Level>3</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2015-09-21T21:25:54.420981100Z" /> 
  <EventRecordID>61362</EventRecordID> 
  <Channel>System</Channel> 
  <Computer>sql09</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>\Device\RaidPort1</Data> 
  <Binary>0F001800010000000000000081000480040000000000000000000000000000000000000000000000000000000000000008020000810004800000000000000000</Binary> 
  </EventData>
  </Event>

As a result, everything that was spinning on this disk hangs tightly, including services. Only a complete reboot of the system helps and helps for about 20-23 hours, and then on a new one.
C600 Chipset SAS RAID (SATA mode) driver version: 3.8.0.1106
Now I moved the mirror to another slot for experimentation and updated the chipset driver, but I'm afraid it will come out again in 23 hours.
Intel SSD Toolbox says the SSD has the latest firmware.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
A
Alejandro Esquire, 2015-09-22
@A1ejandro

Once upon a time, on one of the servers I also had a problem that manifested itself once every 24 hours.
The server was on Novell Netware 5.0 (it was a long time ago). In short, I set up a backup for the night, and immediately after it the server rebooted (everything was implemented by cron). It had a very good effect on performance and the elimination of problems ....
But I do not argue, this is a workaround of the problem, it would be even better to understand the problem and solve it.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question