Barracuda XT, Barracuda, Barracuda Green, DiamondMax and other desktop SATA and IDE drives

[casewindow]

I've had SD1A on for about a week. I accidentally double flashed the drive with SD1A but it didn't seem to cause any problems that I could tell. I ran Seatools long test after each flash and also checked SMART through Everest for any problems which seemed to come up fine.

But once I have got this in the eventlog - the system stopped properly responding and I eventually had to do a hard reset:

"The device, \Device\Ide\iaStor0, did not respond within the timeout period."

Has anyone else had this issue?

[wld770]

yes, & looking back thru my event viewer that goes back months, i see none prior to updating sd15->sd1a.

[JefUK]

I had exaclty the same problem after updating the firmware, but at the same time I got a warning that Vista was incompatible with my chipset (X58). I installed the latest Intel chipset drivers (9.1.0.1012 ) and I have not had the problem since.

[ModProbe]

Same problem for me (RAID 1 + ICH9R).

No problem before with SD15 .

Hopefully Seagate fixes the problem quickly.

[Sark]

same here, using four ST3500320AS with SD1A in a raid10 (raid0+1) on ICH9R.

chipset driver (intel x48) version: 9.0.0.1008

intel matrix storage driver: 8.7.0.1007

(both latest version according to the intel website)

[JefUK]

There is a later driver for the x48 chipset. Look at the drivers for an Intel board that uses the same chipset as you have. I think you will find that there is version 9.1.0.1012. Look at the readme inside the file and you should see that it supports your chipset and not only the Intel board.

I had the same problem, but after using the same chipset driver the iastor error messages have stopped ( and the system does not momentarily pause). I don't understand why Intel are not putting this later driver under the chipset downloads.

I hope this solves your problem.

[ModProbe]

My driver was already the 1012 and my chipset is an Intel P35.

I think the firmware really has a problem because in SD15 it was perfect with the same drivers.

Message Edited by ModProbe on 02-03-2009 09:32 AM

[wld770]

mine is p35 chipset also.

i don't think it's the chipset, i think it's the sd1a firmware.  I have 4 of these st3500320as drives. 

I get the error in the subject on sd1a drives attached to ich9 controller.  On ones in a RAID1 on a 3ware 9650SE-2LP, i am getting a fair number (so far 2 dozen) of these:

WARNING :  Feb 02, 2009 08:08:07 PM: Controller 0: Sector repair completed: port=1, LBA=0x9F769
WARNING :  Feb 02, 2009 08:07:30 PM: Controller 0: Sector repair completed: port=1, LBA=0x9F765
WARNING :  Feb 02, 2009 08:07:04 PM: Controller 0: Sector repair completed: port=1, LBA=0x9F761

never got any of these before.  It could be coincidental that both controllers and/or drives on both are suddenly having issues, but I seriously doubt it.  I already had to return 1 of the 4 two weeks after I bought it when it died, and now 6 mos. later it appears I'm having issues with the rest.  I've already gone & bought some WD drives to migrate to, but now I'm stuck with 4 of these I'm scared to trust with any data.  

[AlanM]

Hello:

To consolidate the discussion regarding the Seagate Barracuda 7200.11 Firmware issues, please post all related messages in the new thread that we have begun for the purpose of centering a.... Please do not post firmware-related content in another thread. We are closing this thread to redirect.

Thank you for your understanding!


-The Moderator Team