
UNSOLVED
SSD for a Latitude D830
Hi,
I have a Latitude D830 with BIOS A15. I am thinking to change de HDD for a SSD, but Im not sure if its a good idea. Someone has done it? Im thinking to buy the Corsair Force Series F115, it is SATA300, like laptop, and has TRIM support and Sandforce controller.
Am I going to have some problem for BIOS, AHCI option or detection of this drive? Any know problem in this Dell laptops with SSD drives?
Latitude D830 mounts HDD in 2.5" or 1.8"? I never opened it.
Sorry for my bad english.
Thanks, regards.
Responses (28)
Solutions (0)
At FAQ of this product web on Carsair site says "No settings within your operating system need to be adjusted"
www.corsair.com/.../force-series-f115-solid-state-hard-drive.html
Do you think this isnt true?
This drive has TRIM support
More recent info?
SSD's have a limited number of writes.
I disagree that Windows 7 does everything automatically.
TRIM is not a panacea.
Demons, Zombies, and Dust Bunnies are in no way repelled or vanquished by TRIM. :emotion-14:
The way SSD's work with data written in blocks.
A block may be 256KB: 256 * 1000 * 8 binary bits.
To change even ONE of these bits, you must rewrite the
ENTIRE block.
Windows sees 1 bit being written, but the SSD wear is equivalent
to 256,000 bits being written.
Life is based on:
(Size of SSD) * (Endurance Cycles) = Total data written to SSD before failureHere is the math in very basic rounded numbers.
10,000 writes aka 000001 writes per day for approx 027.37 years. 10,000 days
10,000 writes aka 000010 writes per day for approx 002.737 years. 1000 days
10,000 writes aka 000100 writes per day for approx 000.2737 years. 100 days
10,000 writes aka 001000 writes per day for approx 000.02737 years. 010 days
10,000 writes aka 010000 writes per day for approx 000.002737 years. 001 daysAll of the Items mentioned in the previous post Write to the Drive with great frequency.
Indexing, hibernation, logging, prefetch, superfetch, ready boost, should be switched off and the scheduled defrag is also switched off .
When you get to "too many" writes you are Toast. Congratulations Drive is Dead forever.
Event ID - 51 - An error was detected on device \Device\Harddisk0\D during a paging operation
You can blame this on the fact that operating systems aren’t optimized for SSD technology and do not do everything automatically.
Windows 7 is "aware" of SSDs when you install the operating system on a solid state drive to begin with. However Windows 7 often fails to make numerous settings that Microsoft product discussions claim should be made. That's why it's essential to turn things off on any system, whether that system included an SSD as the system drive for a Windows 7 install, or the SSD is a replacement for an original drive (probably the system drive).
- Turn off prefetch, superfetch and ReadyBoost
- Turn off the Windows System Restore service for the SSD
- Turn off disk defragmentation for the SSD
- Turn off Hybernation (Hiberfile.sys)
- Turn off Virtual Memory (Pagefile.sys)
- Turn off Indexing
- Turn Off Event Log (Sometimes Windows gets an error that writes to the event log every few seconds)
- Limit Maximum event log size and set to overwrite if necessary. (The Drive can literally be filled up with errors otherwise, causing the SSD to DIE FOREVER within a few hours of an event being written every few seconds.)
- DO NOT USE Is NTFS Compression of Files and Directories . If this is ON Temporary internet directories , mail folder directories get large number of file writes in bursts.
How to disable and re-enable hibernation on a computer that is running Windows
(Windows 7, Vista, Server 2008)
http://support.microsoft.com/kb/920730Delete the hibbernation file:
http://www.windows7hacker.com/index.php/2009/05/what-is-hiberfilsys-and-how-to-delete-in-windows-7-free-up-hard-drive-space/How to Enable or Disable Hibernate in Windows 7
http://www.sevenforums.com/tutorials/819-hibernate-enable-disable.htmlTheir Calculations Do not seem to present a 10X greater endurance.
More recent info?
www.storagesearch.com/ssdmyths-endurance.html
"2 million (write endurance) x 64G (capacity) divided by 80M bytes / sec gives the endurance limited life in seconds.
That's a meaningless number - which needs to be divided by seconds in an hour, hours in a day etc etc to give...
The end result is 51 years!"
**********************************************************************************************************************
My calculations said 27 years so the "more recent caclulations" seem to indicate 2X overall durability.
I don't think you will get a vendor to go out on a limb and say
Indexing, logging, hybernation, virtual memory, etc is ok and that they will guarantee the drive for
5 years or 10 years let alone 51 years.
Demons, Zombies, and Dust Bunnies are in no way repelled or vanquished by TRIM.
The way SSD's work with data written in blocks.
A block may be 256KB: 256 * 1000 * 8 binary bits.
To change even ONE of these bits, you must rewrite the
ENTIRE block.
Windows sees 1 bit being written, but the SSD wear is equivalent
to 256,000 bits being written.
Life is based on:
(Size of SSD) * (Endurance Cycles) = Total data written to SSD before failureHere is the math in very basic rounded numbers.
10,000 writes aka 000001 writes per day for approx 027.37 years. 10,000 days
10,000 writes aka 000010 writes per day for approx 002.737 years. 1000 days
10,000 writes aka 000100 writes per day for approx 000.2737 years. 100 days
10,000 writes aka 001000 writes per day for approx 000.02737 years. 010 days
10,000 writes aka 010000 writes per day for approx 000.002737 years. 001 days
Wear leveling and Extra Cells and ECC make the "life calculation" a bit more fuzzy but they do NOT PREVENT the EventualTOO MANY WRITES aka DEATH of the Cells.

_Raul_
7 Posts
5360
0
Posted September 9th, 2011 10:00
Hi,
This Corsair drive is SATA 3G, I know dont bother SATA 6G drives in SATA 3G system.
SATA 3G = SATA II = SATA300.
Regards