Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

Event ID 9 device \iaStor0 did not respond timeout period

Active Directory, Domain, DNS, WINS, DHCP, SBS, New Releases.

Event ID 9 device \iaStor0 did not respond timeout period

Postby blin » Thu Mar 13, 2014 11:10 pm

Event ID 9 The device, \Device\Ide\iaStor0, did not respond within the timeout period.

We are running Windows 20102 R2 on Dell server. I\The is runs vey slow. The event log has this error.

Log Name: System
Source: iaStorV
Date: 3/13/2014 10:45:01 PM
Event ID: 9
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: W2012A.
Description:
The device, \Device\Ide\iaStor0, did not respond within the timeout period.

Any suggestions?
How to Configure and Troubleshoot Cisco
http://www.howtocisco.com

Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com
blin
Site Admin
 
Posts: 3618
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Re: Event ID 9 device \iaStor0 did not respond timeout period

Postby blin » Thu Mar 13, 2014 11:11 pm

I have worked on hundreds of these problems. It boils down to the Bios setting of SATA configuration. In each of the cases I worked on I chaged the setting from IRRT to ATA and the problem was eliminated. We are working with Dell for a solution as this is only a temp fix for now.
How to Configure and Troubleshoot Cisco
http://www.howtocisco.com

Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com
blin
Site Admin
 
Posts: 3618
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Re: Event ID 9 device \iaStor0 did not respond timeout period

Postby blin » Thu Mar 13, 2014 11:11 pm

I think Dell support is a little behind the times. The newest RST is 10.1, not 8.6.

http://downloadcenter.intel.com/SearchR ... px?lang=...
How to Configure and Troubleshoot Cisco
http://www.howtocisco.com

Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com
blin
Site Admin
 
Posts: 3618
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Re: Event ID 9 device \iaStor0 did not respond timeout period

Postby blin » Thu Mar 13, 2014 11:12 pm

First, run the chkdsk utility in DOS-PROMPT or use any other power-full tools to fix the errors in hard drive. While you running the chkdsk utility, you can see something like this "Recover orphan file XXXX XXX", this means your hard disk is having some bad sectors and will going to spoil in future. After you scan and fix the hard drive's sectors, now you can use your computer as normal. But, your System can run without any problem for certain time only. This problem will come again and again. the final solution is replace the hard disk to new.
How to Configure and Troubleshoot Cisco
http://www.howtocisco.com

Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com
blin
Site Admin
 
Posts: 3618
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Re: Event ID 9 device \iaStor0 did not respond timeout period

Postby blin » Thu Mar 13, 2014 11:14 pm

This is a mischievous error generated by Intel Matrix Storage Manager, due to new special power mode for hard drives. According to this site <start link> http://www.paulscomputerservice.net/ind ... Error9.php"; <end link> (Paul's Computer Service) if you do not possess a capable hard drive, you'll get these errors. Intel claims this only happens on Windows Vista PC's, but I get this error on five HP DC7900 Pc's with the Windows XP downgrade installed. Some PC's randomly reboot due to this error. To solve, follow the tips on the previous link or follow <start link> http://h20000.www2.hp.com/bizsupport/Te ... =c01662424 <end link> for HP computers
How to Configure and Troubleshoot Cisco
http://www.howtocisco.com

Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com
blin
Site Admin
 
Posts: 3618
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Re: Event ID 9 device \iaStor0 did not respond timeout period

Postby blin » Thu Mar 13, 2014 11:14 pm

I was having this problem with my new Dell E6400 machines. You can update the driver from the intel site to version 8.9.0.1023. The link is http://downloadcenter.intel.com/Detail_ ... 2&lang=eng

Dell also has a Intel Rapid Storage Technology (AHCI) driver which seems to work. The version is 9.6.0.1014.

Give those a whirl and the errors should go away.
How to Configure and Troubleshoot Cisco
http://www.howtocisco.com

Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com
blin
Site Admin
 
Posts: 3618
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Re: Event ID 9 device \iaStor0 did not respond timeout period

Postby blin » Thu Mar 13, 2014 11:15 pm

How to Configure and Troubleshoot Cisco
http://www.howtocisco.com

Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com
blin
Site Admin
 
Posts: 3618
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Re: Event ID 9 device \iaStor0 did not respond timeout period

Postby blin » Thu Mar 13, 2014 11:16 pm

Whilst this seemed to alleviate my problems (on a Dell Precision M4600 laptop with a SSD from crucial) The system had experienced frequent lock-ups and would sometimes not come back. However after updating drivers and turning off PCI power management, I still had the odd temporary "freeze" which related to snapshots failing (even though they were turned off)

I found I had to disable vssvc snapshots for this to go away completely (disable the volume shadow copy service, then stop it). I realise this isn't ideal, but it's the only solution I've found to completely stop my laptop hanging.
How to Configure and Troubleshoot Cisco
http://www.howtocisco.com

Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com
blin
Site Admin
 
Posts: 3618
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Re: Event ID 9 device \iaStor0 did not respond timeout period

Postby blin » Thu Mar 13, 2014 11:17 pm

The following are some troubleshooting tips to help diagnose and pinpoint the problem: •Read the SCSI controller manufacturer's technical manual to determine the termination requirements. Many modern SCSI controllers require active terminators (at least one of the devices on the bus must provide termination power). Proper termination involves both a terminator (resistor) and a device that supplies a signal to the bus for termination power. The SCSI-2 standard specifies that a controller (initiator) must supply termination power. Therefore, any controller that claims to be SCSI-2 compatible probably does supply termination power, but you should check if you are unsure. Also, many devices, especially drives, give you the option of providing termination power; if you have a jumper on the drive that reads Trmpwr, you should enable this jumper.
•If both internal and external SCSI devices are attached, make sure the last device on each SCSI chain is terminated, and that intermediary devices are not.
•If only a single SCSI chain is used (either all internal or external), ensure the last device of the SCSI chain is terminated and the SCSI controller itself is terminated. This is usually a BIOS setting.
•Check for loose or poor quality SCSI cabling. When you have a long chain of cables with mixed internal and external cabling, you run the risk of degrading the signal. Even though the SCSI specification may specify a long distance, the specification assumes cabling that allows no leakage or interference, and the reality is generally a shorter distance. Whenever you have 6-foot or longer external cables, you should replace them with 3-foot cables.
•Note when the event messages are posted and try to determine if it coincides with certain processing schedules (such as backups) or heavy disk processing. This will help to determine what device may be causing the errors.

Note The reason that drives tend to have these types of problems under heavy stress is often slow microprocessors. In a multitasking environment, the processor may not be fast enough to process all the I/O commands that come in nearly simultaneously.
•Slow the transfer rate settings if the timeouts are associated with tape drives - using 5MBS transfer rate usually cures the timeouts.
•Simplify the SCSI/IDE chain by removing devices, or move the device in question to another controller. If the problem follows the device, you should replace it.
•Check the revision of SCSI controller BIOS and device firmware revisions. Contact the manufacturer for the latest revisions. See the Checking the Model Number and Firmware Revision section below for the procedure on how to do this.
•Check the SCSI device drivers version. The SCSI driver is located in the %Systemroot%\System32\Drivers directory. Look at the version in the file properties, and check whether the SCSI manufacturer has a newer version.
•Remove other controllers that may create bus contention problems.
•A low-level format performed by the SCSI controller may resolve these event messages.
•Use a different make or model of any suspect hardware.

Checking the model number and firmware revision
The model number of the device and firmware revision are in the Windows registry. To check the model number and firmware revision, follow the steps below.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756

How to back up and restore the registry in Windows1.Run Regedt32.exe.
2.Locate and click the following registry key, where x varies according to device number:

HKEY_LOCAL_MACHINE\Hardware\Devicemap\Scsi\ScsiPortx\ScsiBusx\ TargetIdx\LogicalUnitIdx

3.Look at the REG_SZ identifier value to see the model number and firmware revision values. For example, in the following value, the firmware revision value is 0510:
SEAGATE ST32430N 0510

4.Record all the device model numbers and firmware revisions, and check with the manufacturer for any known issues.
Note For Windows 2000 and Windows Server 2003, you can view model and firmware revisions for hardware under the following registry location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum
How to Configure and Troubleshoot Cisco
http://www.howtocisco.com

Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com
blin
Site Admin
 
Posts: 3618
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Re: Event ID 9 device \iaStor0 did not respond timeout period

Postby blin » Thu Mar 13, 2014 11:22 pm

Description

The following issues may occur on Windows Vista* with a supported Intel® RAID controller hub:

•Timeout errors reported by iastor or iastor(v) in Microsoft Event Viewer

Cause

Various desktop Serial ATA devices such as hard drives and CD/DVD drives have been reported that do not comply with the Serial ATA Link Power Management (LPM) device specification and display erratic behavior when LPM is enabled.

Solution

Install Intel Matrix Storage Manager version 7.5 or later. These versions workaround this issue by disabling Link Power Management (LPM).

If you are experiencing installation issues, you can also use one of the following additional workarounds:
•If available, install updated firmware for the device.
•Attach the device(s) to ports 3-5 on the Intel® 82801HR/HH/HO I/O controller hub (ICH8R) or port 3 on the Intel® 82801GR/GH I/O controller hub (ICH7R)
•Switch to IDE mode in the system BIOS.
Note : This change will disable RAID functionality. Contact your BIOS manufacturer for instructions on how to switch to IDE mode.
How to Configure and Troubleshoot Cisco
http://www.howtocisco.com

Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com
blin
Site Admin
 
Posts: 3618
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Re: Event ID 9 device \iaStor0 did not respond timeout period

Postby blin » Thu Mar 13, 2014 11:22 pm

Configuration:
•Dell M6500 laptop
•Vista 64-bit Business SP1
•Intel ICH8M-E/ICH9M-H/PCHM SATA RAID controller
•Intel Matrix Storage Manager 8.9.4.1004
•2 Seagate ST9250410ASG disks
•Raid 1 configuration

Problem: After running without problems for a week after the purchase, one day the drives started failing more or less arbitrarily. About once a day, the Intel Matrix Storage Console would report one of the drives as failed. After a reboot, the drive would reappear and the controller would successfully rebuild to the failed drive, and return to normal state.

I noticed these events in the Windows event log, correlated to the times a drive disappeared: Source isStor, Event ID 9, Description: "The device, \Device\Ide\iaStor0, did not respond within the timeout period."

Solution: I read this article:

http://www.intel.com/support/chipsets/i ... 025783.htm

but since I was already running a much newer version of the Intel Matrix Storage Manager, this does not solve the problem. However, after reading about the relation to Link Power Management in the article, it struck me that on the exact day that the problem started, I had switched the Windows power plan from the default "Dell" plan to the "High performance" plan.

I compared the advanced settings of the power plans, and noticed that they differ in the option PCI Express | Link State Power Management. The high performance plan has Link State Power Management turned off, while the Dell plan has it to "Moderate power savings" while plugged in, and "Maximum power savings" while on battery.

So, I switched the power plan back to "Dell", and since then (for about a month), I've had no problems and no entries in the event log. I've been running plugged in all the time, so it's the "Moderate power savings" setting that I've been using.

So, the solution seems to be to use a Windows power plan that has PCI Express | Link State Power Management set to "Moderate power savings" (or perhaps "Maximum power savings").
How to Configure and Troubleshoot Cisco
http://www.howtocisco.com

Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com
blin
Site Admin
 
Posts: 3618
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Re: Event ID 9 device \iaStor0 did not respond timeout period

Postby blin » Thu Mar 13, 2014 11:23 pm

I have a brand-new Windows 7 laptop that was hanging from time to time with the message (in Event Viewer) "\Device\Ide\iaStor0 did not respond within the timeout period." It would typically hang for 15-30 seconds and then come back to life.

I have found what I think is the source of the problem, and have a workaround. I am reporting it here in case other people are having similar problems. If I'm right, the problem comes about on machines with RAID controllers (Intel Array Storage, otherwise known as Rapid Storage Technology) with disks (in my case, probably a Samsung SSD) that do not support a feature called "Link Power Management."

Link Power Management (LPM) is described by Intel as a “feature described by the Serial ATA specification to overcome the power demand of a high-speed serial interface, SATA and providing the capability of SATA at the minimum power cost.” Apparently, for it to work, it has to be coupled with a disk drive that supports it correctly. If the disk does not support the feature, various people online have reported exactly the symptom I’ve been seeing: The system hangs, and then the Array Storage reports an error code 9 (\Device\Ide\iaStor0 did not respond within the timeout period).

Intel says that it is possible to disable LPM selectively by port. The relevant information is in registry key
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStor\Parameters\Portn\

where n represents the port number, starting from 0. Within each of those keys are the following DWORD values:

LPM: 0 (disable) or 1 (enable); default = enable
LPMSTATE: 0 (partial), 1( slumber); default = disable; ignored when LPM = 0
LPMDSTATE: 0 (partial), 1 (slumber); default = enable
DIPM: 0 (disable), 1 (enable); default = enable

I tried disabling LPM for all six of the ports on my machine, by setting LPM, LPMDSTATE, and DIPM to 0 in the registry for the key corresponding to each port (0 through 5). I have not had a single disk error report since then.

Obviously this experience does not prove for certain that this is the source of my problems. But if you are having similar difficulties on your machine, and you have a RAID controller, and especially if you have a Samsung SSD, I would think this is an experiment worth trying.
How to Configure and Troubleshoot Cisco
http://www.howtocisco.com

Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com
blin
Site Admin
 
Posts: 3618
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Re: Event ID 9 device \iaStor0 did not respond timeout period

Postby blin » Thu Mar 13, 2014 11:24 pm

Solution

In the BIOS I can enable the hot swap function for disk, enabling this solved the whole problem and kept my disk connected. I do not know if this problem and fix is H67/P67 chipset related or specifically Asus related.

So if you are having this problem too, this is what you could try out:
•Update your Intel Rapid Storage driver
•Disable Intel's Link Power Management in Windows' energy management section
•Alter the LPM registry to ensure it is disabled: HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\iaStor
•Try to connect it to a different port if you have multiple SATA controllers
•Enable hot swappable disks in the BIOS if available
•Set disk mode to IDE
•Get a new disk using the ATA standard if it is using the ATAPI standard
How to Configure and Troubleshoot Cisco
http://www.howtocisco.com

Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com
blin
Site Admin
 
Posts: 3618
Joined: Wed Dec 31, 1969 7:00 pm
Location: Chicago, USA

Re: Event ID 9 device \iaStor0 did not respond timeout period

Postby chicagotech » Mon Mar 24, 2014 9:38 pm

We fix this problem by upgrading the driver.
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
chicagotech
Site Admin
 
Posts: 6833
Joined: Mon Nov 27, 2006 1:24 pm
Location: Chicago USA

Re: Event ID 9 device \iaStor0 did not respond timeout period

Postby guest » Tue Mar 25, 2014 7:56 am

This is Microsoft engineer suggestion;
Symptom

When we run Windows 2012 R2 on Dell server, the device didn’t respond with the timeout period.

Possible cause

We didn’t Modify Link State Power Management off.

Registry key was not correct.

Resolution
1.renaming HKLM\SYSTEM\CurrentControlSet\Services\iaSTOR\Parameters to HKLM\SYSTEM\CurrentControlSet\Services\iaSTOR\Parameters.dist in registry.
2.Modify the advanced settings of your active power management scheme in Windows to turn PCI Express Link State Power Management off.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm


Return to Windows

Your Ad Here

Who is online

Users browsing this forum: No registered users and 10 guests