10-28-2009 08:25 PM
UPDATE 10-31-09 @3:20p
I=IDE
A=AHCI R=RAIDBRAND NEW
III - GOOD=01 BAD=00 AAA - GOOD=02 BAD=00 AIA - GOOD=02 BAD=00RIR - GOOD=00 BAD=01
INSTALLED (NO REFORMAT/ERASE)
III - GOOD=03 BAD=00 AAA - GOOD=06 BAD=02 AIA - GOOD=05 BAD=04 RAR - GOOD=02 BAD=00 RIR - GOOD=03 BAD=00REFORMAT/ERASE
AAA - GOOD=01 BAD=00 AIA - GOOD=01 BAD=00 IIA - GOOD=01 BAD=00Also reworded some of the questions. PLEASE POST ANSWERS ONLY. Thx
-----------------------------------------------------------------------------------------------------------
Hey, guys, I think we should take some info of those who updated their g2's. It's really hard to see what's going. I think people should list the stuff on their computer and what was on it before the firmware flash. It might be a lot easier to see a commonality. In my opinon, Intel should have made the flash update a destructive one. Wipe the drive off clean before updating the flash. That way a lot of variables for error is reduced. I have a feeling the trim command is getting some instructions all messed up with a filesystem already present. Yeah i know it's a lot of questions but...
Here' it goes...
1-Bios updated to Latest? (YES or NO)
2-What g2 size 80 or 160g? (80 or 160)
3-Was drive BRAND NEW / ERASED (hdd erase/reformat)/ INSTALLED (OS already installed) before update?
4-Is the drive partitioned? (YES or NO)
5-other harddrives installed? (YES or NO)
6-Was drive aligned BEFORE and AFTER update?
7-OS that you have installed or will be installing?
8-If using windows and already installed, what driver is being used before updating firmware? (Intel or MS, AHCI, IDE) if applicable
9-Bios setting before update? (IDE, AHCI, RAID, etc)
during update? (IDE, AHCI, RAID, etc)
after update? (IDE, AHCI, RAID, etc)
10-Did you run the flasher via USB or CD?
11-How many times did you run the flasher? (1x, 2x, 3x)
12-Was there an error when flashing? (YES or NO)
13-After it flashed and the computer rebooted, did you immediately change the settings back to what it was before booting/installing OS? (YES or NO)
14-When booted in Windows did it install a driver? (YES or NO) if applicable
15-What driver did it install?
16-If possible, what driver is being used in Windows after firmware? (Intel or MS, AHCI, IDE)
17-Is the G2 drive bad or working fine? (BAD or GOOD)
List your system specs too and if possible chipset (south bridge chip)
List you SSD manufacturing date.
Anything else you think I missed please say.
***FOR THOSE WITH BAD DRIVES AFTER UPDATE DID YOU TRY TO HDD ERASE AND REINSTALL? If so, did it work again?
***Don't do it if you're not comfortable with it.
Hopefully the information given can help INTEL resolve this issue quicker as it seems to be easier to get information quicker on the forums than individual emails.
11-02-2009 07:31 AM
1-Bios updated to Latest? YES
2-What g2 size 80 or 160g? 80 G2R5
3-Is the drive partitioned? NO
4-other harddrives installed? YES
5-What version of 7, x86, x64? x64
6-Was windows 7 Installed already or was it clean? INSTALLED
7-Was it aligned before and after update?
8-Did you reformat or leave windows on before update? INSTALLED
9-Was Intel optimizer installed before or after update? AFTER
10-If optimizer was Installed BEFORE the update did you run it? N/A
11-Bios and windows setting before update? AHCI
12-Setting during update? AHCI
13-Setting after update? AHCI
14-Did you run the flasher twice before booting or installing Win7? 1x
15-Was there an error when flashing? NO
16-After it flashed and the computer started (Windows was installed before update), did you immediately change the settings back to what it was before booting into windows? NO
17-When booted in Windows 7 did it install a driver? YES
18-Is the G2 drive bricked or working fine? GOOD
CPU = Intel Core i7 920 @3.20GHz
Mobo = ASUS P6T Deluxe V2 X58
RAM = 6GB Corsair TR3X6G1600C7 XMS3-1600MHz 7-7-7-20
GPU = HIS ATI HD4850
HDD2 = Hitachi HUA721050KLA 7200 500gb 32mb
HDD3 =
HDD4 =
11-02-2009 11:59 AM
1-Bios updated to Latest? YES
2-What g2 size 80 or 160g? 80
3-Was drive BRAND NEW
4-Is the drive partitioned? YES (100mb partition + all remaining space in one part)
5-other harddrives installed? NO
6-Was drive aligned BEFORE and AFTER update? N/A
7-OS that you have installed or will be installing? Win 7 x64
8-If using windows and already installed, what driver is being used before updating firmware? (Intel or MS, AHCI, IDE) if applicable N/A
9-Bios setting before update? (IDE, AHCI, RAID, etc)
during update? (IDE, AHCI, RAID, etc)
after update? (IDE, AHCI, RAID, etc)
10-Did you run the flasher via USB or CD? CD
11-How many times did you run the flasher? 2x (1st flashing, 2nd time to see if all is OK)
12-Was there an error when flashing? NO
13-After it flashed and the computer rebooted, did you immediately change the settings back to what it was before booting/installing OS? NO
14-When booted in Windows did it install a driver? (YES or NO) if applicable N/A
15-What driver did it install? N/A
16-If possible, what driver is being used in Windows after firmware? MS AHCI
17-Is the G2 drive bad or working fine? GOOD
List your system specs too and if possible chipset (south bridge chip)
HP EliteBook 6930p with Intel PM45 & ICH9-M (82801IM)
List you SSD manufacturing date.
Pack Date: 09/25/09
11-02-2009 12:35 PM
1-Bios updated to Latest? YES
2-What g2 size 80 or 160g? 160
3-Is the drive partitioned? YES
4-Other harddrives installed? YES
5-What version of 7, x86, x64? x64
6-Was windows 7 Installed already or was it clean? CLEAN
7-Was it aligned before and after update? AFTER
8-Did you reformat or leave windows on before update? REFORMAT
9-Was Intel optimizer installed before or after update? AFTER
10-If optimizer was Installed BEFORE the update did you run it? N/A
11-Bios and windows setting before update? IDE (compatibility)
12-Setting during update? IDE (compatibility)
13-Setting after update? AHCI
14-Did you run the flasher twice before booting or installing Win7? 2x: THE FIRST TO UPDATE, THE SECOND TO VERIFY
15-Was there an error when flashing? NO
16-After it flashed and the computer started (Windows was installed before update), did you immediately change the settings back to what it was before booting into windows? YES, CHANGED TO AHCI AND THEN INSTALLED W7
17-When booted in Windows 7 did it install a driver? YES
18-Is the G2 drive bricked or working fine? BAD (Windows 7 x64, Vista x64 and even Ubuntu 9.10 all show the same behaviour: after some reboots or a shutdown I get the "not a system disk" error. I can erase the ssd with hdderase 3.3 (ide compatibility mode) and I have no smart errors.)
DRIVE: SSDSA2MH160G2C1
BATCH # CNCV99K802
System:
Asus P6T Deluxe V2
i7 920
6 GB DDR3
Radeon HD 5850
Intel X25-M G2 (SATA port # 0)
WD 1 TB (SATA port # 1)
DVD (SATA port # 2)
11-03-2009 01:33 AM
1-Bios updated to Latest? (YES)
2-What g2 size 80 or 160g? (80)
3-Drive INSTALLED (OS already installed) before update
4-Is the drive partitioned? (NO)
5-other harddrives installed? (YES)
6-Was drive aligned BEFORE and AFTER update? No
7-OS that you have installed or will be installing? Win7 Ultimate x64
8-If using windows and already installed, what driver is being used before updating firmware? (MS, AHCI)
9-Bios setting before update? ( AHCI)
during update? (IDE)
after update? ( AHCI)
10-Run the flasher via CD
11-How many times did you run the flasher? (1x)
12-Was there an error when flashing? (NO)
13-After it flashed and the computer rebooted, did you immediately change the settings back to what it was before booting/installing OS? (YES)
14-When booted in Windows did it install a driver? (YES)
15-What driver did it install? Not sure, cannot get back in after reboot to check
16-If possible, what driver is being used in Windows after firmware? Not sure, cannot get back in after reboot to check
17-Is the G2 drive bad or working fine? (BAD ALL BAD)
Core i7 920
EVGA X58 SLI Mobo
1x 300GB Raptor
1x 1TB CAVIAR BLACK
1x 500GB MAXTOR
SSD manufacturing date: 18 AUG 2009 (PACK DATE)
BATCH # : CNCV98E801
After firmware update and reboot after driver install SSD would not boot Win 7 x64, disk errors were detected, dual booting in VIsta x64 and running HD tune error scan shows red damaged blocks. SSD optimizer used to run but now reports that a drive is missing. Explorer shows the SSD but attempts to access it result in "I/O errors"
11-03-2009 01:47 AM
I'd just brought the X25-M G2 80GB on 24-10-2009, remove the packing until the new firmware were released.
1-Bios updated to Latest? Yes
2-What g2 size 80 or 160g? 80 G2
3-Is the drive partitioned? No
4-other harddrives installed? No
5-What version of 7, x86, x64? x86
6-Was windows 7 Installed already or was it clean? Clean
7-Was it aligned before and after update? No, a brand new SSD
8-Did you reformat or leave windows on before update? No, a brand new SSD
9-Was Intel optimizer installed before or after update? Can't install (see below explanation)
10-If optimizer was Installed BEFORE the update did you run it? No, a brand new SSD
11-Bios and windows setting before update? AHCI
12-Setting during update? AHCI
13-Setting after update? AHCI
14-Did you run the flasher twice before booting or installing Win7? No
15-Was there an error when flashing? No
16-After it flashed and the computer started, did you immediately change the settings back to what it was before booting into windows? No
17-When booted in Windows 7 did it install a driver? Can't install (see below explanation)
18-Is the G2 drive bricked or working fine? Bad
HP Campaq Presario CQ20-130TU Notebook PC
CPU = Intel Core 2 Duo P8400 2.26GHz
RAM = 4GB DDR2 800 x 2GPU = Intel GM45
After the firmware update, I'd tried to install Win7 x86. Everything fine until select the SSD for installation. The installer reported the "System Partition" can't be created and the installation process ceased. I'd tried to install Vista x86 afterwards, but the same symptom was resulted.I'd tried to repair the SSD according to:http://communities.intel.com/message/72371# 72371After a few steps, my drive become usable and Win7 x86 can be smoothly installed. In addition, the SSD toolbox v1.1 can't find any smart error and dead blocks. I can conclude that the problem may be caused by the shifted "alignment" of SSD during the firmware update process.