Event 129, storvsc - "Reset to device, \Device\RaidPort1, was issued"

Question

I have a new Dell PoeerEdgde Server and I have connected 4 Samsungs SSD disks.
The server hangs from time to time and I can't see any problems in the "Windows Admin Center". I have upgradede all the Firmware and Software.
I have a lot os these logs errors - Event ID 129 (I have about 2-3 of these error pr. min)
Reset to device, \Device\RaidPort1, was issued.

The server is running Hyper-V 2019 Core and if I shutdown all the Hyper-Vs I don't see anything in the log and the problem disapears.

I can't find a solution online. :-)

Answer 1

Hi,
You mentioned that have upgraded the Software. Does this mean that the system update has been installed？
If not, I suggest that you could check for update. If any security update could be found, install them to check.
Something here might help.
https://blogs.msdn.microsoft.com/ntdebugging/2011/05/06/understanding-storage-timeouts-and-event-129-errors/
Please also check the information below try to configure power management. It is related HP server. But I consider that Dell also might has power plan setting.
https://h30434.www3.hp.com/t5/Gaming-Notebooks/Reset-to-device-Device-RaidPort1-was-issued/td-p/5315958
Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl

Answer 2

I read on here that there was a registry key that held a timeout value while reading from the disk. If this timeout value is reached then the mini port driver sends a message to the storage driver and the storage driver logs event 129 in event viewer and sends a reset command to the port that the device is connected to and this causes event 153 to be logged in event viewer that states the i/o operation is being retried. This reset of the port disconnects the device and all handles to it are lost. This causes Ntfs corruption on the file system on the disk noted by ntfs event 55 in event viewer

Answer 3

HKLM\System\CurrentControlSet\Services\Disk\TimeOutValue

here is the registry key for the tunable timeout value

Answer 4

I was researching event Id 153 that was logged in my event viewer while doing a surface scan on my hard drive to detect location of bad blocks the timeout value is at fault in this case. When doing a surface scan with chkdsk thes scan locks up when it reads a bad block and the timeout value is reached or exceeded in this instance causing event 129 then event 153 is logged them event 55 is logged and I have to reconned my hard drive

Answer 5

Hello Everyone, I wanted to post my related findings for an issue I was having with my Mid 2012 MacBook Pro. I have bootcamp installed running the latest version of windows 11. I was receiving warnings in the Event viewer for Event 129, storvsc - "Reset to device, \Device\RaidPort0, was issued" and Event 129, storvsc - "Reset to device, \Device\RaidPort1, was issued" The answer was my drive SATA cable was failing - which is a known issue on this MacBook Model. Some further details: The 2012 MacBook was having random slowness where the spinning wheel would show up and the system would lock up for 30 seconds or longer. I attempted to replace the SSD but was unable to install the latest support version of OSX and it would fail at the last 5 minutes of install. I repurposed this Mac as a test Windows machine and started seeing those error logs. Once I replaced the cable I did not see the errors again. So for me, it was a physical issue.