I did some quick before and after tests using GNOME Disks Utility.
I had backs-up just in case though, and so should you.
No data was lost going from EXT0AB0Q to EXT0DB6Q. Replace (hd6) with the path to your storage device of choice and then boot! boot partition or USB stick) and run the following commands on the GRUB2 command line: To boot this mess, place the files somewhere accessible (i.e. Inside the ISO9660 image is an ISOLINUX bootloader, MEMDISK kernel wrapper and a FreeDOS filesystem.Īfter giving up trying to make the USB stick I flashed the image to boot with my BIOS, I resorted to using GRUB2. I grabbed the EXT0DB6Q 840 EVO firmware update for “Windows” users and took a look ( 2ad2496632c3eee3fc12b1673a2ee3a9965ae773 Samsung_SSD_840_EVO_EXT0DB6Q.iso). Naturally, the update is distributed primarily for Windows users and I run Linux. Today I took some time and bit the bullet to update it and hedge against disaster. I haven’t noticed any issues, so I didn’t rush the update. There was a firmware update in October 2014 and then a another one in April 2015 attempting to correct the issue. There are stories of people seeing decreasing performance as the NAND cells degrade in this TLC SSD. It has performed flawlessly for almost 2 years. Samsung 840 EVO SSD + Linux + Firmware UpdateĪ while back I bought a Samsung 840 EVO as it seemed like the best bang for the buck consumer solid state drive.
0 kommentar(er)
