MMM
Page 1 of 2 12 LastLast
Results 1 to 25 of 27

Thread: Crunching on SSDs: What you need to know

  1. #1
    Back from the Dead
    Join Date
    Oct 2007
    Location
    Stuttgart, Germany
    Posts
    6,602

    Crunching on SSDs: What you need to know

    Okay folks, inspired by Bob's thread here I figured it was time to do a short FAQ/guideline on SSDs and crunching. If you are familiar with SSDs, please note that I am solely talking about MLC (multy layer cell)-based SSDs here. SLC is and was too expensive for most people to be a viable option.



    Part I: What you (probably) already know

    Solid State Drives (SSDs) are the new generation of storage media everyone has been waiting for. In the past decade, incredible advances have been made in all areas of PC architecture: Today, CPUs are a hundred times as fast as they were just ten or fifteen years ago. Ram speed and capacities have increased tenfold, and modern graphics processing units (GPUs) have several billion transistors and the ability to run specialized code originally intended for CPUs via CUDA or CAL. About the only part that didn't really evolve that much was the good old magnetic hard drive, a device we trust with all our data, and the one that is responsible for roughly 80% of the subjective impression of PC performance - ie the performance that everybody will notice while booting up your computer, starting up applications, etc.

    Only a good 2 years have passed since SSDs finally entered the end user market. A data storage medium without any moving physical part (such as magnetic spindles kept in rotation by a motor), an SSD has a few groundbraking advantages over a traditional magnetic hard drive. SSDs are fully resistant to shock, no noise or significant heat is generated by operating an SSD, minimal power draw and potentially unlimited potential for performance improvements due to the nature of the tech (SSDs are evolving with the NAND flash memory, which they use for storing the data) make the Solid State Drive THE long overdue replacement for magnetic hard drives as system drives.

    Like any new technology, SSDs need(ed) time to evolve. The first generation had a lot of bugs & quirks, causing some of them to actually perform worse than standard hard drives in certain situations, or even leading to premature death.



    Part II: Known issues with (mostly) early-generation SSDs

    2 years ago, the SSD market was very straightforward. There were only Intel and Jmicron present, as far as controller manufacturers go, with a few Samsung-based drives thrown in the mix (which were strictly OEM for expensive subnotebooks and the like). The Intel X25-M was fast and relatively bug-free even in the beginning, if we don't count the inevitable performance degradation that took place over time. However, paying 500€ (roughly 600$ back then) for just 80 GB of space wasn't everyone's cup of tea.

    So Jmicron stepped in, offering their JMF602 controller to other manufacturers like OCZ, Patriot and many more at a very reasonable price. Capacities started as low as 16GB, and since most people only needed 20-60GB for their OS drive anyways, the drives were very popular at first.

    However, the JMF602 had a few terrible design flaws, not the least of which could cause the "stuttering" effect that so many people were experiencing. It also had a very weak wear-leveling routine (used to minimize degradation of the flash cells in SSDs), causing the drives to fail quickly if a lot of writing was done to the SSD.



    Part III: Different SSD "classes"

    In the following, I would like to give an indication how well-suited a particular type of SSD is for crunching, meaning whether or not you should put your BOINC install on them, and what to watch out for.

    Class 1: Rather bad for crunching

    Or any heavy/constant writes to disk, for that matter. We are talking generation 1 SSDs here. In this class, there's pretty much only the JMF602-based drives. Unfortunately, there were a LOT of them. I will try and list a few here:

    A-Data XPG SX81 series
    Compustocx Q1 series
    OCZ Core series
    OCZ solid series
    Patriot Warp V1 and V2 series
    Supertalent MasterDrive series
    TakeMS Rapid series
    Transcend SSDs (all)


    And many more. Basically anything that has the JMF602 (usually not advertised), a designated linear read speed of 130 to 180MB/s, and linear write speeds not higher than 120MB/s.

    Class 2: Ok for crunching with a few tweaks

    In this category I'd put the older Intel X25-M G1 (SSD Generation 1) drives, along with the VERY popular Indilinx-based drives (SSD Generation 2).

    A-Data Nobility series
    Compustocx Q2 series
    Corsair Extreme & Nova series
    Crucial M225 series
    Gskill Falcon series
    Mushkin Enhanced IO series
    OCZ Agility, Colossus, Enyo, Onyx, Solid 2, Vertex series
    RunCore Pro IV series
    Patriot Torx series
    Supertalent Ultradrive ME/GX/GX2 series

    Intel X25-M G1


    Probably a few more Indilinx-based drives out there.
    Anyway, the Indilinx-controller was the first decent and affordable one, which made it very popular. It doesn't stutter, usually lasts pretty long and offers an overall good performance for a decent price.

    Class 3: 3rd generation SSDs that are basically fit for any use

    Among this class of recent models are the Intel X25-M G2 (Postville), Intel X25-V, as well as many SSDs based on the current Samsung, Toshiba (mostly using Jmicron JMF612/618), Sandforce SF1200/1500 and Marvell controllers.

    Too numerous to list them all really, here are some common examples:

    A-Data 700, S596, S599 series
    Compustocx Q3 series (SF-1200)
    Corsair Force, Performance, Reactor series
    Crucial C300 series (Marvell, supports SATA 3.0)
    Gskill Phoenix series (SF-1200)
    Intel X25-M G2
    Intel X25-V G2
    Kingston SSDNow M/V/V+ series (Intel/Toshiba/JMF612)
    Mushkin Callisto series (SF-1200)
    OCZ Agility 2, Onyx 2, Vertex 2, Vertex LE series (all Sandforce-based)
    Patriot Inferno, PS100, Zephyr series (Sandforce/Phison/JMF612)
    Runcore Pro V (Sandforce)
    Samsung SSD 470 series
    Solidata K8 series (Sandforce)
    Supertalent TeraDrive series (Sandforce)
    Western Digital SiliconEdge Blue series (JMF612/618)


    These 3rd Generation SSDs all support TRIM (with a few exceptions, such as the Kingston SSDNow series) and have very good wear leveling algorythms, preventing an untimely death of the drive. Performance-wise the Crucial C300 and all Sandforce-based drives pretty much share the crown with Intel's X25-M G2, depending on the benchmark.




    Part IV: How to tweak my SSD for crunching usage

    So, now we know the problems that our SSD drives may or may not have. But what do we do to make them last AND perform, especially with the added strain of 24/7 crunching in mind?

    There's a few tips/advice for ALL SSDs that ALWAYS help, or can't hurt to do, for that matter.

    0.Before doing anything else, check whether there is a firmware update available for your particular SSD. Especially Indilinx-drives have received a LOT of FW updates, so make sure to get the latest one onto your SSD.


    01.Be sure to set your motehrboard's SATA mode to AHCI or RAID in bios before installing the OS! Do NOT use IDE mode!

    1. Next, choosing the right OS is the most important step if you already have your SSD. For us Windows peeps, that would have to be any version of Windows 7 or Server 2008 R2, for that matter. Why? Because Windows 7 is almost perfectly ready for SSDs out-of-the-box, so you have to do VERY little tweaking, if any. Windows 7 also supports TRIM, which helps your SSD retain its incredible performance.
    As far as Linux goes, you should be fine with almost any distro, as Linux tends to write to disk a lot less than Windows does. But you better ask D_A about that.. of course, someone would have to get him an SSD first *hint hint*
    Linux does support TRIM now if it uses Linux 2.6.33 kernel <--- thanks to kjeldoran for that!

    If you absolutely need to run another version of Windows like XP, things are a bit more complicated. Have a look over here on how to align your partition correctly. You need to do this BEFORE installing your OS.

    2.Install your current motherboard chipset and especially storage controller drivers! For Intel chipsets, there is a special Intel Rapid Storage Manager available, which MUST be installed for some model-dependent features (like Garbage Collection on Indilinx Drives) to work correctly. This is NOT the Intel Chipset driver, but a separate one, so you still need to install the Intel chipset driver (as you normally would). Not sure how it works for AMD, Via and Nvidia-based chipsets, but I would guess you need to install the latest driver there as well.

    3. Okay.. so you got your Windows 7 running off your shiney new (or old...) SSD - what to do next? Easy - go download a simple tool called SSD tweaker. Just hit auto tune, it will modify your Windows 7 in such a way that is optimal for SSDs (for example, it will turn Superfetch off). The tool also reminds you to de-activate the Windows auto-defrag feature for your SSD, which you should check (Win7 can detect most SSDs and automatically disabled auto defrag for them). Don't forget to reboot for the changes to take effect.



    4.Now, about the BOINC client. As you know, the work units are crunched in ram, and after a given intervall X, the progress for each WU is written to disk in order to save the WUs computing progress.
    The corresponding setting is called write to disk at most every [60] seconds and can be found in the BOINC manager under Extras --> Settings --> Disk and Memory usage. Default value here is 60s, which means that BOINC will write to your disk (SSD) every 60 seconds.
    As you can imagine, this can put quite a strain on your SSD if you are crunching 24/7. So what we want to do here is change the value to something higher - I recommend an increase to 600s when using SSDs.



    Any disadvantages to this? you might ask. Well, yeah - on non-dedicated crunchers or machines that are rebooted often, you may loose a few minutes of progress now and then. Sometimes when you shut down or reboot (or when your PC crashes/power fails etc), BOINC fails to write its progress since the last checkpoint to disk, meaning you loose whatever processing has been gone on since the last checkpoint. The higher your setting, the more you can potentially loose here.
    However, when using a recent BOINC version, you usually don't loose anything. To be safe you can shut down BOINC manually before rebooting/shutting down a machine, that will definitely save your progress.

    Okay folks, that's all for now. I may add a Part V later on, got some ideas left on what to write.. for now I'm done. This has already gone on WAY longer than I had planned

    Happy crunching everyone
    Last edited by jcool; 10-16-2010 at 05:11 PM.
    World Community Grid - come join a great team and help us fight for a better tomorrow![size=1]


  2. #2
    Xtreme Legend
    Join Date
    Mar 2008
    Location
    Plymouth (UK)
    Posts
    5,279
    Thanks J ...lots of useful info there....kinda feels like a sticky is needed or at the very least added to one


    My Biggest Fear Is When I die, My Wife Sells All My Stuff For What I Told Her I Paid For It.
    79 SB threads and 32 IB Threads across 4 rigs 111 threads Crunching!!

  3. #3
    Xtreme Enthusiast
    Join Date
    Jun 2010
    Location
    Bournemouth (UK)
    Posts
    786
    Nice one Jcool, very informative
    Nymph - Xeon 5675 @ 4.1 w/ x2 680
    Ikaros - i7 920 w/ 275 - Build In Progress

    Long live LGA1366

  4. #4
    Devil kept pokin'
    Join Date
    Jan 2010
    Location
    South Kakalaky
    Posts
    1,299
    Thx Jcool I'd wondered about boinc and its impact on writing to my ssd.
    1440 writes per a day just from boinc is something to think about for sure.

  5. #5
    Xtreme Member
    Join Date
    Feb 2007
    Location
    St. Louis
    Posts
    477
    Just wanted to add some more info:

    Some of the 2nd generation SSDs do support TRIM (I know that the indilinx Vertex and Agility support TRIM).

    Linux does support TRIM now if it uses Linux 2.6.33 kernel. I haven't messed with linux and TRIM so someone with linux and an SSD would need to test, but it is supported based on the release notes.

    I believe the Intel Rapid Storage Manager is for RAID only. TRIM is built into the OS and requires AHCI to be set for the SATA controller. I believe it is for RAID only because I do not have it installed on my socket 1156 system and TRIM is working properly.

  6. #6
    Worlds Fastest F5
    Join Date
    Aug 2006
    Location
    Room 101, Ministry of Truth
    Posts
    1,615
    SSD alignment checking guide for XP and other Windows OS users:

    SSD Partitions created with Vista, Windows 7 and almost any Linux distro should be correctly aligned automatically.

    This is however not the case with any version of XP and has to be done manually.

    One of the easiest ways to test partition alignment on your drives is by downloading the AS SSD benchmark tool (grab it here).

    I would not recommend running the benchmark suite as it writes 3-9 TB of data to your drive each time it is run but if you just start it up it will display the alignment of whatever drive you point it at in the top left.

    If the status is OK in Green then partition alignment is fine, if labelled Bad in red it is misaligned.

    To start up AS SSD you need to have Microsoft .Net framework 3 or higher installed so remember this if you have problems running it

    Another method to check alignment in Windows is to load a dos window (Start > RUN > cmd.exe) and to then use diskpar.exe...

    Just download it to somewhere like the root of your C: drive, then open a dos window then type cd\ and hit return to get to the root directory...

    Now go to Start>Settings contorl panel> Administrative tools > Computer management then click on disk management under storage.

    This will bring up a list of the drives and partitions on your system.

    If you have only one disk on your system then it will almost always be disk 0

    Make a note of what disk number your OS has assigned to the drive or array you are interested in checking the alignment of...

    Now go back to your dos window and type (I have used disk 0 in this example)

    Diskpar -i 0

    This should give you a list of partition information.

    The line you are interested in is Startingoffset =

    This should read 524288 or be a multiple of 524288.

    If the above figure is 524288 or the number displayed is divisible by 524288 then the partition is aligned.

    If not then it is not aligned...

    You can also use Diskpar to align drives but this is totally destructive so only use it on new or empty drives!!!

    Using this method ALL partitions and ALL data on your target drive / array will be destroyed so be very careful you have the right drive with no data on it!

    To align drive 1 in a system open a dos window again and type

    Diskpar -s 1

    Then answer yes to both questions then type in 2048 for a starting offset and whatever you decide the partition size will be.

    After that go back to disk management and format the disk using an allocation unit size of 4096 and the quick format option.

    Your blank disk will then be perfectly aligned

    Paragon released a non destructive tool to automate this process and it was free for a while but it is almost $30 now :/
    Last edited by Biker; 10-16-2010 at 03:57 PM.
    X5670 B1 @175x24=4.2GHz @1.24v LLC on
    Rampage III Extreme Bios 0003
    G.skill Eco @1600 (7-7-7-20 1T) @1.4v
    EVGA GTX 580 1.5GB
    Auzen X-FI Prelude
    Seasonic X-650 PSU
    Intel X25-E SLC RAID 0
    Samsung F3 1TB
    Corsair H70 with dual 1600 rpm fan
    Corsair 800D
    3008WFP A00



  7. #7
    Back from the Dead
    Join Date
    Oct 2007
    Location
    Stuttgart, Germany
    Posts
    6,602
    Quote Originally Posted by kjeldoran View Post
    Some of the 2nd generation SSDs do support TRIM (I know that the indilinx Vertex and Agility support TRIM).
    Yes, they do. Did I say they don't?
    If so I need to edit that.


    Linux does support TRIM now if it uses Linux 2.6.33 kernel. I haven't messed with linux and TRIM so someone with linux and an SSD would need to test, but it is supported based on the release notes.
    Good to know

    I believe the Intel Rapid Storage Manager is for RAID only. TRIM is built into the OS and requires AHCI to be set for the SATA controller. I believe it is for RAID only because I do not have it installed on my socket 1156 system and TRIM is working properly.
    No, it's for AHCI and Raid. If you set your board to Raid, but don't actually create any Raid volumes, the drives will runj in AHCI mode automatically.
    It's true that TRIM probably works without that driver, but GC on Indilinx-SSDs doesn't. So it's better to have it installed.
    World Community Grid - come join a great team and help us fight for a better tomorrow![size=1]


  8. #8
    Da Goose
    Join Date
    Oct 2005
    Location
    Chicago
    Posts
    4,913
    Very nice jcool...


    i7-860 Farm with nVidia GPU's

  9. #9
    Xtreme Member
    Join Date
    Feb 2007
    Location
    St. Louis
    Posts
    477
    Quote Originally Posted by jcool View Post
    Yes, they do. Did I say they don't?
    If so I need to edit that.
    Oh no, I just didn't see it mentioned for the 2nd generation of SSDs.

    No, it's for AHCI and Raid. If you set your board to Raid, but don't actually create any Raid volumes, the drives will runj in AHCI mode automatically.
    It's true that TRIM probably works without that driver, but GC on Indilinx-SSDs doesn't. So it's better to have it installed.
    True, GC probably needs the driver to run on XP/Mac/Linux and RAID. I didn't know it was for AHCI, but I think Win Vista/7 provide a default AHCI driver. If there is only one SSD, I do not think installing the driver is necessary.

    I had an nvidia chipset and a driver was not required for the SATA controller. TRIM worked fine as long as I had AHCI selected in my BIOS and the same goes for my current 1156 setup.

    Also, isn't GC only needed for those who have an OS/controller that doesn't support TRIM or if they are running a RAID setup?

  10. #10
    V3 Xeons coming soon!
    Join Date
    Nov 2005
    Location
    New Hampshire
    Posts
    36,363
    Or, if it's just a dedicated cruncher buy a old used 36 gig raptor and watch it crunch for 3-5 years..
    Bought 3 a while ago for $55.00 total shipped..
    Can't beat that with a stick..
    Crunch with us, the XS WCG team
    The XS WCG team needs your support.
    A good project with good goals.
    Come join us,get that warm fuzzy feeling that you've done something good for mankind.

    Quote Originally Posted by Frisch View Post
    If you have lost faith in humanity, then hold a newborn in your hands.

  11. #11
    Xtreme Member
    Join Date
    Feb 2007
    Location
    St. Louis
    Posts
    477
    Quote Originally Posted by Movieman View Post
    Or, if it's just a dedicated cruncher buy a old used 36 gig raptor and watch it crunch for 3-5 years..
    Bought 3 a while ago for $55.00 total shipped..
    Can't beat that with a stick..
    Indeed, I think for dedicated crunchers an SSD is not worth the investment since you can get a hard drive or a flash drive for much less. I think laptop drives are probably one of the better choices since they consume less power, are the same size as SSDs and a 5400rpm 2.5" drive is quiet.

    I only have an SSD because it is in my daily use rig.

  12. #12
    Back from the Dead
    Join Date
    Oct 2007
    Location
    Stuttgart, Germany
    Posts
    6,602
    Quote Originally Posted by kjeldoran View Post
    Oh no, I just didn't see it mentioned for the 2nd generation of SSDs.



    True, GC probably needs the driver to run on XP/Mac/Linux and RAID. I didn't know it was for AHCI, but I think Win Vista/7 provide a default AHCI driver. If there is only one SSD, I do not think installing the driver is necessary.

    I had an nvidia chipset and a driver was not required for the SATA controller. TRIM worked fine as long as I had AHCI selected in my BIOS and the same goes for my current 1156 setup.

    Also, isn't GC only needed for those who have an OS/controller that doesn't support TRIM or if they are running a RAID setup?
    You got a few things mixed up there. GC does NOT work in Raid, neither does TRIM. Only way to re-set the performance on RAIDed SSDs is wiping them.
    Using the default Windows 7 driver, GC does run on Win7's stock driver, but it's horribly slow. With that driver it only takes a few seconds to complete.
    GC can actually be used as a supplement to TRIM to keep your Indilinx drive performance optimal. I run it once a month on my Supertalent Ultradrive in my laptop (on Win7 with TRIM enabled as well), and performance hasn't degraded one bit for over a year.
    World Community Grid - come join a great team and help us fight for a better tomorrow![size=1]


  13. #13
    Xtreme Member
    Join Date
    Mar 2009
    Location
    So. Burlington, VT
    Posts
    267
    That write-up cleared up a lot of questions I had about SSD's. Thank you
    Heh. Ahhhhh........ heh. HEH.

    AMD 1055T
    2x4GB GSkill Ripjaws DDR3-1333
    Gigabyte 890GPA-UD3H
    EVGA GTS 450
    Corsair 550VX
    Buncha disks
    Mouse
    Keyboard

  14. #14
    Back from the Dead
    Join Date
    Oct 2007
    Location
    Stuttgart, Germany
    Posts
    6,602
    Glad you like it
    I'll try and add some more info on GC and the likes later. Now I need to catch some sleep
    World Community Grid - come join a great team and help us fight for a better tomorrow![size=1]


  15. #15
    Xtreme Member
    Join Date
    Feb 2007
    Location
    St. Louis
    Posts
    477
    Quote Originally Posted by jcool View Post
    Glad you like it
    I'll try and add some more info on GC and the likes later. Now I need to catch some sleep
    Yeah, that would be great because I am confused on garbage collection. I thought the indilinx controllers have on board GC so it would work in RAID. Is GC controller related?

  16. #16
    Xtreme Cruncher
    Join Date
    Apr 2007
    Location
    Western Canada
    Posts
    1,004
    Holy smokes now that helps to explain a lot of things lol

    It is mentioned that the Kingston SSDNow V Series Drive do not support trim, however from Kingstons site "Supports TRIM — ensures maximum performance on compatible Operating Systems".

    Biker- does the attached pic indicate my drive is not aligned "31K-Bad" ? If so then the rest of my hard drives are bad as well !!!


  17. #17
    XS WCG Hamster Herder
    Join Date
    Mar 2007
    Location
    Pacific Northwest, USA
    Posts
    2,389
    ....and just for the record, I have jcools entire post, with codes and all, copied into a notepad doc on my garage rig. We KNOW what happened to the XS servers last time jcool posted this good of a write-up. We were all refugees at TPU...

    So, if we lose the server this time, we can re-construct the content...

    Thx j, I still have to read it all and comprehend. I have read many articles on this, and honestly, I understand it for a little while, then quickly forget....

    Best,
    Bob
    If You ain't Crunching, you ain't Xtreme enough. Go Here
    Help cure CANCER, MS, AIDS, and other diseases.
    ....and don't let your GPU sit there bored...Crunch or Fold on it!!
    Go Here, Or Here

  18. #18
    Back from the Dead
    Join Date
    Oct 2007
    Location
    Stuttgart, Germany
    Posts
    6,602
    ..Back-up by Bob!
    I _will_ draw a backup of this myself as soon as it's finished.. but who knows, that may be too late

    @Johnmark: 31k offset looks like you are running Windows XP (OR, you crated this partition using WIndows XP Setup), am I correct?
    That offset is indeed rather bad for an SSD. How bad is determined by the "class" of SSD you are running, as we have established earlier.
    If class 1 (old Jmicron), such an offset will cause stuttering and shorten drive life considerably. For class 2, it will affect performance and maybe drive life a little, but nothing too dramatical. For class 3, it shouldn't affect drive life, and performance losses will be minimal.

    Now, from your screenshot, it looks like you're running a Kingston SSDNow V-Series G2 with 128GB, that's a JMF618 based drive, so it should be doing fine.

    If you do want to change your offset while keeping your current install, you'll need to draw an image of your OS install ujsing drive snapshot and create a new partition manually. What you need to do is written down here - I have never worked with Drive snapshot myself though (it's free I think).

    Otherwise just save your Data, kill the partition and set up a fresh Windows 7 - you won't regret it if coming from XP
    Don't forget you have to delete the old partitions and let Win7 setup create new ones!

    @kjeldoran: In order for GC to work, the GC Tool needs to "see" the drives as individual drives, which is NOT the case while running a RAID array. Same issue as with TRIM here, the ATA pass through command is not forwarded through the raid controller to the disks.

    By the way, in case anyone was still wondering WHY you'd run Raid 0 despite the disadvantages for SSDs.. here's why

    Last edited by jcool; 10-17-2010 at 04:12 AM.
    World Community Grid - come join a great team and help us fight for a better tomorrow![size=1]


  19. #19
    Worlds Fastest F5
    Join Date
    Aug 2006
    Location
    Room 101, Ministry of Truth
    Posts
    1,615
    Quote Originally Posted by Johnmark View Post
    Biker- does the attached pic indicate my drive is not aligned "31K-Bad" ? If so then the rest of my hard drives are bad as well !!!
    Yes 31k BAD is the standard Windows XP offset which is not good for any SSD.

    Drive Snapshot is a great tool and last time I checked it was free for the first month then it will restore only and not create new images for you.

    If you first stick the SSD in another PC so it is not the boot drive then create an image with drive snapshot to another drive and then follow my alignment proceedure above you will have an aligned drive.

    Now check the alignment with AS SSD to make sure it is correct.

    If you are getting a Green then restore the snapshot image to it.

    The great thing about drive snapshot is that when you restore an image it respects the partition offset you have already set up!
    Last edited by Biker; 10-17-2010 at 05:54 AM.
    X5670 B1 @175x24=4.2GHz @1.24v LLC on
    Rampage III Extreme Bios 0003
    G.skill Eco @1600 (7-7-7-20 1T) @1.4v
    EVGA GTX 580 1.5GB
    Auzen X-FI Prelude
    Seasonic X-650 PSU
    Intel X25-E SLC RAID 0
    Samsung F3 1TB
    Corsair H70 with dual 1600 rpm fan
    Corsair 800D
    3008WFP A00



  20. #20
    Xtreme Cruncher
    Join Date
    Apr 2007
    Location
    Western Canada
    Posts
    1,004
    Quote Originally Posted by jcool View Post
    ..Back-up by Bob!
    I _will_ draw a backup of this myself as soon as it's finished.. but who knows, that may be too late

    @Johnmark: 31k offset looks like you are running Windows XP (OR, you crated this partition using WIndows XP Setup), am I correct?
    That offset is indeed rather bad for an SSD. How bad is determined by the "class" of SSD you are running, as we have established earlier.
    If class 1 (old Jmicron), such an offset will cause stuttering and shorten drive life considerably. For class 2, it will affect performance and maybe drive life a little, but nothing too dramatical. For class 3, it shouldn't affect drive life, and performance losses will be minimal.

    Now, from your screenshot, it looks like you're running a Kingston SSDNow V-Series G2 with 128GB, that's a JMF618 based drive, so it should be doing fine.

    If you do want to change your offset while keeping your current install, you'll need to draw an image of your OS install ujsing drive snapshot and create a new partition manually. What you need to do is written down here - I have never worked with Drive snapshot myself though (it's free I think).

    Otherwise just save your Data, kill the partition and set up a fresh Windows 7 - you won't regret it if coming from XP
    Don't forget you have to delete the old partitions and let Win7 setup create new ones!

    @kjeldoran: In order for GC to work, the GC Tool needs to "see" the drives as individual drives, which is NOT the case while running a RAID array. Same issue as with TRIM here, the ATA pass through command is not forwarded through the raid controller to the disks.

    By the way, in case anyone was still wondering WHY you'd run Raid 0 despite the disadvantages for SSDs.. here's why

    Nope, running Win7 Pro x64 and it was a fresh install on a new 300GB Raptor, many months ago now. But the partition was transferd using Actonis True Image Home a couple days ago.
    Used v2 of the Paragon Alignment tool on this drive, it did its thing rebooted and still the same offset? Tried it a couple more times with the same results?

    A fresh install! I've got over a hundred programs installed on this machine so a fresh install is needed, but not until I have some time off.

    I'll try the procedure you and biker provided me above to transfer the partition with snapshot.

    P.S. Is it an issue that 4 of 5 of the HD's all show an offset as well? I know some of those drives where formatted with XP. But I know for sure the two WD 1TB blacks where both formatted with Win7, one shows an offset of 31k in red the other 1024k in green.

    Thank You guys!
    Last edited by Johnmark; 10-17-2010 at 11:51 AM.

  21. #21
    Xtreme Cruncher
    Join Date
    Apr 2007
    Location
    Western Canada
    Posts
    1,004
    Quote Originally Posted by Biker View Post
    Yes 31k BAD is the standard Windows XP offset which is not good for any SSD.

    Drive Snapshot is a great tool and last time I checked it was free for the first month then it will restore only and not create new images for you.

    If you first stick the SSD in another PC so it is not the boot drive then create an image with drive snapshot to another drive and then follow my alignment proceedure above you will have an aligned drive.

    Now check the alignment with AS SSD to make sure it is correct.

    If you are getting a Green then restore the snapshot image to it.

    The great thing about drive snapshot is that when you restore an image it respects the partition offset you have already set up!
    Dang that didn't work very well. Got to the green light, but after copying the snapshot image the drive wouldn't boot, it just hung. Tried a couple of times to no avail.
    Got the partition aligned one final time then used Acronis to copy it's image and the drive booted, but got the same misalignment I started with.

  22. #22
    Worlds Fastest F5
    Join Date
    Aug 2006
    Location
    Room 101, Ministry of Truth
    Posts
    1,615


    Occasionally Snapshot misbehaves...

    Are you using the latest version?

    Is it just the .exe or are you using the installer?

    Whatever version you are using try the other one and use the verify option when making the image...(sounds nuts but worked for me when I had an issue on a slow client machine)

    Sadly Arconis does not leave offsets intact during a restore...

    Like I said Snapshot is one of a very few image / restore apps that respects preset offsets...

    I hope you can get it working...

    Good luck.
    X5670 B1 @175x24=4.2GHz @1.24v LLC on
    Rampage III Extreme Bios 0003
    G.skill Eco @1600 (7-7-7-20 1T) @1.4v
    EVGA GTX 580 1.5GB
    Auzen X-FI Prelude
    Seasonic X-650 PSU
    Intel X25-E SLC RAID 0
    Samsung F3 1TB
    Corsair H70 with dual 1600 rpm fan
    Corsair 800D
    3008WFP A00



  23. #23
    Xtreme Cruncher
    Join Date
    Apr 2007
    Location
    Western Canada
    Posts
    1,004
    Quote Originally Posted by Biker View Post


    Occasionally Snapshot misbehaves...

    Are you using the latest version?

    Is it just the .exe or are you using the installer?

    Whatever version you are using try the other one and use the verify option when making the image...(sounds nuts but worked for me when I had an issue on a slow client machine)

    Sadly Arconis does not leave offsets intact during a restore...

    Like I said Snapshot is one of a very few image / restore apps that respects preset offsets...

    I hope you can get it working...

    Good luck.
    I probably should have made two snapshots, but I wan't an Ancronis image just in case, which I'm glad I had Yes I used the latest version, but did not verify the image.
    Used the .exe vr. instead of the installer.

    When I went to put the snapshot back onto the drive I received a warning there was an offset between the image and partition size and asked if I wanted to fix it, one time I said yes the other time I said no. When I said no the image would not copy at all?
    Also interesting was the latest version of Pargon alignment tool would not realign any of my drives? It would do its thing, reboot and the alignment error was still there in all cases? Reading the Paragon forum, a lot of users have complained about this ?

    Think I'll do more reading before I make anymore attempts to realign my drives. But at least now I know there is a way to make all drives faster by ensuring they are aligned. Before this thread I didn't even know this issue existed.

    Thanks for your help Biker

  24. #24
    Xtreme Member
    Join Date
    May 2008
    Location
    Sydney, Australia
    Posts
    242
    My 2c worth ...
    • I don't know whether the BOINC time-between-disc-writes setting has any effect. The HDD activity LEDs on most of my crunchers often blink every second a lot of the time. Also, it may be up to the WCG science program to choose when to write checkpoint info, and it may ignore the BOINC setting.
    • Some WCG sciences seem to treat the swap partition/file/pagefile as extended RAM, and access it very often, so it might be wise to move this partition/file onto a magnetic or RAM drive. In particular DDDT-2, which runs the QCHEMM program, does this. I suspect that the forthcoming Windows version of CEP-2 will do the same, as during the recent beta test, crunchers were experiencing the same symptoms of tasks crashing with timeouts on disc waits as happened to me with DDDT-2/XP/WD Caviar Green w 32MB onboard buffer. My workaround was to upgrade the system disk to a 10-yo 8.4GB Seagate IDE drive that gets off its a*se and writes sectors to disc as soon as requests arrive. No apparent speed penalty as the OS disc cache, interrupt-processing and DMA take care of things. Slow to boot up? Crunchers don't have to boot up - they never turn their machines off. And the drive just went prmp, prmp, prmp, every second, writing the updates, ignoring the BOINC setting. I don't think I'd see a work throughput improvement with an SSD.
    • Sorry, jcool, but I don't understand partition "alignment". With a mag. drive, one normally aligns to cylinder boundaries, tho this probably has no advantages as far as the hardware is concerned. Is your magic number the SSD equivalent? Are there any other sizes? What would the DOS or *nix fdisk program say about an "aligned" partition?
    • The Intel RAID driver software has a function even if you do not run RAID - it enables and is necessary for running SATA drives in AHCI mode (XP). You can install it with XP post OS-installation, but you need to patch the registry with a chipset-dependent magic number. I found info at http://forum.msi.com.tw/index.php?topic=106575.0 but that's not online right now. (I might have saved a copy somewhere. Also, the location of the Intel software has changed).

    PS: @jcool - I can't read the yellow text in your 1st post, against the yellow background used by the XS forum, unless I select the text so it shows white against blue. Bad choice of colour, mate.
    Last edited by BlindFreddie; 10-19-2010 at 09:34 PM.

  25. #25
    Back from the Dead
    Join Date
    Oct 2007
    Location
    Stuttgart, Germany
    Posts
    6,602
    Quote Originally Posted by BlindFreddie View Post
    My 2c worth ...
    • I don't know whether the BOINC time-between-disc-writes setting has any effect. The HDD activity LEDs on most of my crunchers often blink every second a lot of the time. Also, it may be up to the WCG science program to choose when to write checkpoint info, and it may ignore the BOINC setting.
    • Actually yeah, it does have an effect. How do I know this? Well.. I blew out two JMF602-based SSDs within 2 or 3 months. They became slow as hell, had bad sectors showing with MHDD and finally it became impossible to install a new OS to them. Since I changed that setting, that same rig has been up & running with the 3rd JMF602-based SSD (a Patriot Warp V2) for over 4 months now without a hiccup. All I did change was that one setting, so no - I don't believe that's a coincidence.

    • Some WCG sciences seem to treat the swap partition/file/pagefile as extended RAM, and access it very often, so it might be wise to move this partition/file onto a magnetic or RAM drive. In particular DDDT-2, which runs the QCHEMM program, does this. I suspect that the forthcoming Windows version of CEP-2 will do the same, as during the recent beta test, crunchers were experiencing the same symptoms of tasks crashing with timeouts on disc waits as happened to me with DDDT-2/XP/WD Caviar Green w 32MB onboard buffer. My workaround was to upgrade the system disk to a 10-yo 8.4GB Seagate IDE drive that gets off its a*se and writes sectors to disc as soon as requests arrive. No apparent speed penalty as the OS disc cache, interrupt-processing and DMA take care of things. Slow to boot up? Crunchers don't have to boot up - they never turn their machines off. And the drive just went prmp, prmp, prmp, every second, writing the updates, ignoring the BOINC setting. I don't think I'd see a work throughput improvement with an SSD.
    Good point - I generally move the Swap file off an SSD simply for space reasons anyway, or disable it completely if I have enough ram. Will add that to the 1st post when I get a chance

  26. Sorry, jcool, but I don't understand partition "alignment". With a mag. drive, one normally aligns to cylinder boundaries, tho this probably has no advantages as far as the hardware is concerned. Is your magic number the SSD equivalent? Are there any other sizes? What would the DOS or *nix fdisk program say about an "aligned" partition?
  27. The Intel RAID driver software has a function even if you do not run RAID - it enables and is necessary for running SATA drives in AHCI mode (XP). You can install it with XP post OS-installation, but you need to patch the registry with a chipset-dependent magic number. I found info at http://forum.msi.com.tw/index.php?topic=106575.0 but that's not online right now. (I might have saved a copy somewhere. Also, the location of the Intel software has changed).
It's been awhile since I've read into that alignment stuff, and frankly, I don't really remember the how's and why's simply because it has become unneccessary to do ever since Windows Vista. I do know it makes a difference though. Reason is that SSDs somehow use different block sizes than HDDs, so the file system needs to be adjusted (the written block size needs to match the block size that the SSDs controller uses internally or something). I recommend reading that link to OCZ forums I posted, it explains it a bit better IIRC.

PS: @jcool - I can't read the yellow text in your 1st post, against the yellow background used by the XS forum, unless I select the text so it shows white against blue. Bad choice of colour, mate.
No problems here - my background is XS standard grey though. Not sure why yours is yellow?
World Community Grid - come join a great team and help us fight for a better tomorrow![size=1]

Reply With Quote Reply With Quote

Page 1 of 2 12 LastLast

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •