01-30-2009 07:28 PM
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?
02-02-2009 10:51 PM
02-03-2009 07:16 AM
same here, using four ST3500320AS with SD1A in a raid10 (raid0+1) on ICH9R.
chipset driver (intel x48) version: 184.108.40.2068
intel matrix storage driver: 220.127.116.117
(both latest version according to the intel website)
02-03-2009 07:31 AM
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 18.104.22.1682. 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.
02-03-2009 09:31 AM - edited 02-03-2009 09:32 AM
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.
02-03-2009 06:45 PM
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.
02-04-2009 10:34 AM