I dont often have a problem that i cant work out myself but this one has me stumpted I have a adaptec 72405 raid controller and about 2 months ago it started giving IO errors and raid port reset entries in windows event viewer but the thing is it works fine sometimes not very often mind you also if i dont log into windows the Vms using the raid arrays work fine last time i left it 2 weeks before i logged into windows and it worked fine for another week before i had to reset the system for other reasons then not long after logging into windows task manager shows 100% disk usage on both arrays but 0MBS read write speeds and going anymore that 1 layer deep into the file structure locks up windows explorer i have reinstalled windows a couple of times every time it seems to work for a bit then goes back to doing the same thing i also swapped out the power supply tryed 2 different 2nd hand PSU's i have nothing changed i tried popping acouple of disks of each array out it started fine when i put the disks back in it rebuilt them and worked fine untill i reset the system then went back to the same old problem so im thinking either windows is installing a update that my raid card doesnt like which loads once a user is logged on or all my power supplies are stuffed which i think would be unlikely. Im open to any suggestions as what my problem could be
Adaptec 72405 SH***S Itself after logging into windows
- Thread starter Brokenbitsagain
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
When I Google raid port reset windows event I get quite a few articles suggesting various fixes. Have you tried any of them? Like these pages:
www.dell.com
www.diskinternals.com
.
You may have a drive (or multiple) which are close to failing, and when the system tries to read/write certain regions of the disk in a certain way, it causes the disk(s) to go into panic/recovery mode - Consumer drives not meant for NAS can do this, and prevent the controller from accessing them for a long time while they attempt to recover. Since they are in a wait state, the controller doesn't know whether to consider them failed, or to wait.
Even when reinstalling windows, the OS installer and controller may be laying down the same bits in the same places on the disks, setting it up for failure again. Using the system as a hypervisor may not trigger the same issue in the same way, perhaps because the corrupted portion of the filesystem is not being accessed until a user logs in.
Let me know which of the potential fixes you've tried. Good Luck.
Reset to device, \Device\RaidPort0, was issued. Event id: 129 storahci
Hi, I have a DELL XPS 13 9343. I have made a Clean install of Windows 10 and downloaded drivers from dell.com. I am also running Hyper-V. I get repeated Warnings in my System Envent Viewer saying: Reset to device, \Device\RaidPort0, was issued. Source: storahci Just Before i get these events my...
Reset to device, device, raidport0, was issued error can be fixed
While Windows is running, your desktop may freeze for about 30 seconds - this is a fairly common Windows problem. The Event Viewer will most likely display the error
You may have a drive (or multiple) which are close to failing, and when the system tries to read/write certain regions of the disk in a certain way, it causes the disk(s) to go into panic/recovery mode - Consumer drives not meant for NAS can do this, and prevent the controller from accessing them for a long time while they attempt to recover. Since they are in a wait state, the controller doesn't know whether to consider them failed, or to wait.
Even when reinstalling windows, the OS installer and controller may be laying down the same bits in the same places on the disks, setting it up for failure again. Using the system as a hypervisor may not trigger the same issue in the same way, perhaps because the corrupted portion of the filesystem is not being accessed until a user logs in.
Let me know which of the potential fixes you've tried. Good Luck.
Ok so its a amd board so the rules out intel storage drivers I tried sfc come up no integrity violations although i had previously done that aswell as updated the driver from microsofts to adaptecs latest after the registry tweeks and checking the ahci settings it was already set to what the page recommended i also disabled fast startup still the same. Reluctant to blame a failing disk as ive pulled disks and done rebuilds without problems out side of windows then once its done log into windows and it just refuses to respond shares file tranfers/backup all work flawlessly untill i login to windows im now having a similar problem on a second system that i though was fixed with a new power supply but now is having similar issue but not exactly the same as the first it was working fine after the power supply replacement until i tried expanding the array with new disks just yesterday but this one doesnt work fine even if not logged into windows its my backup system luckily i have a 3rd system that backs up that system so as long as the 3rd system doesnt have issues my data should be safe.
Locking up and generally misbehaving only when you login to windows along with device reset errors sounds to me like either a failing drive or a corrupted volume. The reason it only manifests (for now) when you login is because the act of login in is reaching parts of the volume that normally are not used if you are not logged in ... ie, some files are only going to be referenced during a live session - if these files reside on a problematic part of the filesystem then that is likely whats causing the bizarre behaviour.
You'd hope that a RAID controller would notice a drive with a serious problem, drop it from the stack and continue to serve up the volume - but I've had many _many_ cases of serious drive problems locking up a RAID volume and thereby locking up the machine. Pull the drive and life is good again.
You'd hope that a RAID controller would notice a drive with a serious problem, drop it from the stack and continue to serve up the volume - but I've had many _many_ cases of serious drive problems locking up a RAID volume and thereby locking up the machine. Pull the drive and life is good again.
Last edited:
