06-23-2011 03:30 AM
I can report successful update of SAMSUNG MMCRE28G8MXP-0VBL1 from firmware VBM1EL1Q (no TRIM, only NTFS garbage collection) to VBM19C1Q (TRIM supported), using Blue_Frog's hot-plug method (http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/TRIM-firmware-for-the-128-GB-Samsung-SSD/td...) with Thinkpad X301 laptop:
hdparm -I /dev/sda|grep -i trim
* Data Set Management indeterminate TRIM supported
* "indeterminate" in string above was not really expected, however it seems TRIM is working correctly, write performance is reasonable. I updated it just today, so it might be too early for conclusions.
* towolf's "hdparm --read-sector" test (http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/TRIM-firmware-for-the-128-GB-Samsung-SSD/td...) did not really work, sectors used by deleted file still contain data (not zeros). This is probably because:
> If TRIM is working, the sector is supposed to contain all zeros.
That is only if the SSD implements TRIM so that it zeroes the discarded
blocks. You can check if the device at least knows enough to report
In my case, discard_zeroes_data contains "0". Still, because following command succeeds (carefull, may destroy your data):
hdparm --trim-sector-ranges 40502170:1 --please-destroy-my-drive /dev/sda
I have a good reason to believe FW update worked and drive really supports TRIM now.
* Originally, I had SAMSUNG MMCQE28G8MUP-0VA firmware VAM08L1Q. Because I could not find any documented case of successful FW update, I did not risk it and talked to Lenovo support instead. They were very professional, after I explained that write performance went down from 75 to 30 MB/s, they exchanged SSD for a model noted above (whole process took 3 weeks). However, replaced SSD still did not support TRIM, even it supported garbage collection for NTFS under Windows 7, so under Windows 7 effect would be same (or better) as with TRIM. However, since I am running Linux, it did not help me much, so I went FW update way.
07-03-2011 07:32 PM
I have been trying to flash my Samsung 128gb drive for my x301 for the past 2 days. The first challenge was obtaining a bootable USB disk. The HP utility worked but wouldn't accept my Dos 6.22 files. Eventually I went real old school and used a USB floppy drive, booted MS-DOS 6.22, and then swapped the disk to the maindiag.exe files.
My procedure is:
1. Update BIOS to enable secure erase.
2. Shutdown, remove SSD
3. Boot MS-DOS 6.22
4. Insert drive
5. Run Maindiag
6. Drive is recognized, i.e. Model, Serial, and Firmware fields are populated.
7. Initialize Firmware.
8. Long wait for ". . . . . . . . . ."
9. "Erase Fail" "Check System" "ATA command timed out" Screen shot
Following Blue-Frog's advice on Page 15 of this thread.
10. Tried Updated MainFirmware with the same result.
I was able to reboot and never got the locked password screen
When I try to reimage the drive, Windows 7 wants me to repair the disk. Clonezilla doesn't report any errors on the disk write, my rate in Clonezilla is a paltry 1.06 GB/min.
07-03-2011 07:44 PM
The windows system was asking for a repair disk because I didn't change the SATA bios setting back to AHCI.
I can boot up again (whew).
I ordered a microsata to sata adapter, should I try on my desktop or just abort this whole effort?
09-10-2011 11:58 PM
Since my SSD performance has been deteriorating, I decided to (finally) upgrade the MMCRE28G8MXP-0VBL1 in my X301 from the VBM1EL1Q Lenovo firmware to the VBM19C1Q Samsung-direct firmware. This operation succeeded -- thank you!
Before the flashing bonnie++ was showing sequential output at ~50MiB/s, far below the >= 100MiB/s I had previously. Unfortunately, there is no improvement on this benchmark after the firmware change and procedure below. Sequential reads continue to be ~250MiB/s. (File size: 8GB)
Procedure on Linux
* I created a DOS boot disk from a USB flashdrive using cfdisk to partition the drive (mark the primary partition bootable, FAT16), ms-sys -s to write the MBR, mkdosfs -F16 to format the the first partition, and sys F: within DosEmu to load a DOS environment into the partition. (N.B.: qemu is not a good test for whether or not your USB stick works, as it's much less finicky than an actual BIOS.)
* To get the firmware loading to work I had to plug in the SSD *after* I started the flashing software, otherwise the drive was being identified. I did action 4 first, then 2 and 1. I had to repeat this cycle of unplugging the disk, restarting the flashing software, then re-plugging the disk before actions 2 and 1.
* hdparm -I /dev/sda indicates TRIM is enabled, and a test using hdparm --fibmap and hdparm --read-sector shows that TRIM is working.
* I created a file with random data that filled the empty space in my drive (~40GB) and deleted it, using sync afterwards. I then waited 30 minutes before running the bonnie++ benchmark. (Perhaps I should have just done an hdparm --trim-sector-ranges before restoring my disk ...)
09-11-2011 02:52 PM
A different benchmark on Linux (run as root, somewhere with enough space):
# dd if=/dev/zero of=tempfile bs=1M count=1024 conv=fdatasync,notrunc 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB) copied, 17.7783 s, 60.4 MB/s # echo 3 > /proc/sys/vm/drop_caches # dd if=tempfile of=/dev/null bs=1M count=1024 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB) copied, 4.97858 s, 216 MB/s # dd if=tempfile of=/dev/null bs=1M count=1024 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB) copied, 0.510984 s, 2.1 GB/s
I was hoping for the first number to be >= 100 MB/s.
10-03-2011 05:04 PM - edited 10-03-2011 05:12 PM
10-29-2011 07:04 AM
The Samsung SSD in my X301 has slowed down over the last months. I've done a benchmark a few days ago and tried to "refresh" the drive using the BIOS secure erase and linux' "dd if=/dev/zero..." command. After this "refresh" the performance hasn't increased significantly:
What's your opinion on this drive, is a warranty replacement due?
11-03-2011 11:47 PM
Reporting SUCCESS here using instructions from Lev.
Updated firmware on two Samsung MMCRE28G8MXP-0VBL1 (from VBM1EL1Q to VBM19C1Q) using a HP 2530p EliteBook.
Here are my steps, they are very similar to Lev's:
CrystalDiskInfo shows my SSD features: AAM, NCQ, TRIM
Windows Experience Index score for Primary Hard Disk went from "5.9" to "7.2".
Thanks Blue_Frog and Lev!
Hopefully this helps others...
11-17-2011 02:46 PM
I just followed the same procedure and was able to update the firmware on my drive from VBM1EL1Q to VBM19C1Q. Overall, some of the disk intensive tasks that I regularly do seem to be performing better, however when I reran the Windows Experience Index, my Primary Hard Disk rating didn't change from it's 5.9 rating. Are there any other benchmarks that others are using to validate if the drive is performing as it should be? Does anyone have any suggestions as to things I may have done wrong or should check to see if I can get my WEI up to 7.9 like others have been experiencing? CrystalDiskInfo shows that TRIM is enabled....