X25-E strip size test results

Printable View

03-02-2009, 03:41 PM
Ao1

1 Attachment(s)

X25-E strip size test results

Set up: Adaptec 5405, X25-E x 2 in raid 0. Win 7, no tweaks.

The raid strip sizes were reconfigured online using Adaptec Storage Manager without rebooting or formatting the drives. The raid strip that the OS was installed on originally was configured at 128K, from here it was changed to 16K, then 1024K, then 512K then 256K and then back to 128K.

Reconfiguring the strip size online with the Adaptec Storage Manager seemed like an easy option to save time testing various strip sizes on freshly formatted drives, but may well have skewed the results in the process, albeit that would be an interesting result in itself.

The easy option actually ended up taking more time as a fresh install of Windows 7 takes around 10 minutes and reconfiguring the strip size took around 20 minutes. Next I may try the same exercise but with a reformatted drive for each strip size.

Before the first reconfiguration ATTO produced the following result with a 128K strip. (Didn't think to run CrystalMark)
03-02-2009, 03:42 PM
Ao1

1 Attachment(s)

Results with a 16K strip
03-02-2009, 03:43 PM
Ao1

1 Attachment(s)

Results with a 1024K strip
03-02-2009, 03:46 PM
Ao1

1 Attachment(s)

Results with a 512K strip
03-02-2009, 03:47 PM
Ao1

1 Attachment(s)

Results with a 256K strip
03-02-2009, 03:49 PM
Ao1

1 Attachment(s)

Back to a 128K strip.
03-02-2009, 03:56 PM
alfaunits

WEll, let me give you a hint - you wasted time with all these "tests". ATTO is the most worthless HD test around, even more useless than HDTach really ;)
03-02-2009, 03:56 PM
Ao1

Seems like the 256K strip is best, although I'm really kicking myself for not testing the original 128K strip with CrystalMark before I started reconfiguring the strip sizes.
03-02-2009, 03:57 PM
Ao1

Quote:

Originally Posted by alfaunits

WEll, let me give you a hint - you wasted time with all these "tests". ATTO is the most worthless HD test around, even more useless than HDTach really ;)

Thats why I used CrystalMark as well. What would you test with?
03-02-2009, 04:09 PM
n0shutz

only show the first one next time lol =)
03-03-2009, 12:54 AM
Ao1

1 Attachment(s)

Quote:

Originally Posted by n0shutz

only show the first one next time lol =)

I guess it depends on which benchmark programme you can believe. ;)

Changing the array with HDD takes hours.

With the X25-E the best case was 8 minutes, worst case 37 minutes. The time got progressively worse, which makes me think that the drives were affected by the tests. Intel apparently asked reviewers to format the drives after each benchmark test because the drives adapt to usage patterns.

I chose to do the test this way for two reasons, one to find the best strip size and two to see what happened to the drive, which was never going to give a conclusive result either way, however I'm still inclined to think that a 256 strip is fastest.

These tests were undertaken on drives that have been used for two months following an OS install. The drives were 50% full during the test but that have been used at 95% i.e. 60GB of written data on 64GB array.

If nothing else it shows these drives can take a hammering and at no time have I noticed the slightest drop in perceived performance.
03-03-2009, 01:58 AM
spazoid

Quote:

Originally Posted by alfaunits

WEll, let me give you a hint - you wasted time with all these "tests". ATTO is the most worthless HD test around, even more useless than HDTach really ;)

I beg to differ. CrystalMark is the worst of the worst.

@ OP

Go download IOmeter.
03-03-2009, 02:30 AM
Ao1

If certain benchmarks are useless maybe someone could explain why that is the case. Every benchmark out there has been slated by someone at one time or another, but no one is explaining why. It sounds like it should be a new thread, but hopefully someone can give an explanation as to why a benchmark is a waste of time. :up:
03-03-2009, 02:37 AM
spazoid

First off, both Atto and Crystalmark in this case basically just test the linear performance of the cache on your controller. Crystalmark does test random to some extend, but with IOmeter you can specify which usage patterns you wish to test down to very specific patterns. Mixing random writes with linear reads for example is a very effective way at testing if the setup can/will generate stutters.
03-03-2009, 03:01 AM
Marios

Try this under Vista or Seven
Make a batch flie bnch.bat
Edit
Copy paste the following

Code:

winsat disk -ran -read -drive %1 -count 1 -iocount 256 -ransize 16384 winsat disk -ran -read -drive %1 -count 1 -iocount 256 -ransize 32768 winsat disk -ran -read -drive %1 -count 1 -iocount 256 -ransize 65536 winsat disk -ran -read -drive %1 -count 1 -iocount 256 -ransize 131072 winsat disk -ran -read -drive %1 -count 1 -iocount 256 -ransize 262144 winsat disk -ran -read -drive %1 -count 1 -iocount 256 -ransize 524288 winsat disk -ran -read -drive %1 -count 1 -iocount 256 -ransize 1048576 winsat disk -ran -write -drive %1 -count 1 -iocount 256 -ransize 16384 winsat disk -ran -write -drive %1 -count 1 -iocount 256 -ransize 32768 winsat disk -ran -write -drive %1 -count 1 -iocount 256 -ransize 65536 winsat disk -ran -write -drive %1 -count 1 -iocount 256 -ransize 131072 winsat disk -ran -write -drive %1 -count 1 -iocount 256 -ransize 262144 winsat disk -ran -write -drive %1 -count 1 -iocount 256 -ransize 524288 winsat disk -ran -write -drive %1 -count 1 -iocount 256 -ransize 1048576 winsat disk -seq -read -drive %1 -count 1 -iocount 256 -seqsize 65536 winsat disk -seq -read -drive %1 -count 1 -iocount 256 -seqsize 131072 winsat disk -seq -read -drive %1 -count 1 -iocount 256 -seqsize 262144 winsat disk -seq -read -drive %1 -count 1 -iocount 256 -seqsize 524288 winsat disk -seq -read -drive %1 -count 1 -iocount 256 -seqsize 1048576 winsat disk -seq -write -drive %1 -count 1 -iocount 256 -seqsize 65536 winsat disk -seq -write -drive %1 -count 1 -iocount 256 -seqsize 131072 winsat disk -seq -write -drive %1 -count 1 -iocount 256 -seqsize 262144 winsat disk -seq -write -drive %1 -count 1 -iocount 256 -seqsize 524288 winsat disk -seq -write -drive %1 -count 1 -iocount 256 -seqsize 1048576

Save it under c:\user\yourname\
Start run cmd and type "bnch c"
You may change "c" with any partition you want to check.
In case you have a small partition you get better results.
In case you have formated the whole disk as one partition you get reliable results for the whole disk or raid.
Though we may change the parameter -drive %1 with -n %1 (not applied in raid) to check the whole disk or raid %1 no matter how many partitions we have.
In this case we type bnch 0 or bnch 1 to check the first or the second disk respectively
The numbers at the end are IO sizes. I have used the full IO size range, but we may add any IO size we want to check as follows
-seqsize <65536-1048576> bytes
-ransize <16384-1048576> bytes
The iocount set at 256 produces quick results.
-iocount <256-5000>

In a cmd window you might also copy past the following to get results similar to HDTach.
winsat disk -seq -read -drive c -count 1 -iocount 256 -seqsize 65536 -v
03-03-2009, 03:45 AM
Ao1

@ spazoid & Marios,

Thanks guys. :up:

So if I understand correctly the benchmark results distorted by cache, which I guess is the same regardless if it is on a dedicated raid card or if it is built into the SSD itself (?) Does that mean that benchmarks are OK if there is no cache in the equation?

If the benchmarks are written for HDD and are accurate for HDD that use cache are those results also not affected in the same way?

@ Marios, thanks for this. I will try it out.

I'm using hard raid for two reasons, first for capacity and second because I find it is much more stable than onboard raid. All I'm really bothered about is finding the optimum strip size.
03-03-2009, 04:08 AM
alfaunits

Quote:

Originally Posted by audienceofone

So if I understand correctly the benchmark results distorted by cache, which I guess is the same regardless if it is on a dedicated raid card or if it is built into the SSD itself (?) Does that mean that benchmarks are OK if there is no cache in the equation?

Right on both counts. However, if there is no cache in the test (on the controller, drive, volume level OS), you can't compare it to the test with cache.
ATTO in other words gives no useful numbers whatsoever (except for marketing tidbits).
HDTach at least gives you a number that has some (albeit very limited) meaning. At least in file copying it is useful - ATTO is not!

Quote:

If the benchmarks are written for HDD and are accurate for HDD that use cache are those results also not affected in the same way?

They are affected - read again: ATTO is useless ;)
03-03-2009, 04:23 AM
Ao1

Thinking about this more I guess it was my mistake to benchmark without making it clear what I was trying to achieve.

My objective was not to find out how the X25-E performs. My objective was to find the best stripe size using 2 X25-E's in raid 0 with the 5405, so cache is an important factor to the equation.

That said are the benchmarks still useless and if so is IOmeter still the best for establishing this?

And I guess I should also add what I am using the drives for! General OS use, games & photoshop. I am not copying large files all day.
03-03-2009, 06:05 AM
alfaunits

ATTO is ueeless any way you put it! (except marketing again)
ATTO numbers will not equate to anything in real-world, be it simple OS stuff or power use.
03-03-2009, 06:35 AM
Marios

audienceofone
Please check the post with the bench file again, since I made a few corrections.
I think this is a reliable test to compare different stripe sizes so that you may get better results from your Intel X25-E SSD x 2 RAID-0.
03-03-2009, 08:57 AM
Ao1

1 Attachment(s)

Quote:

Originally Posted by Marios

audienceofone
Please check the post with the bench file again, since I made a few corrections.
I think this is a reliable test to compare different stripe sizes so that you may get better results from your Intel X25-E SSD x 2 RAID-0.

Thanks Marios, I really appreciate the time you have spent to help me.

First result below with a 128K strip. Now I'm changing to a 256 strip to retest. Again I am changing the strip online with the Adaptec Storage Manager without reformatting.

Maybe I'm being thick but I'm still confused about why benchmarks are not valid. Why can't anyone seem to agree on a valid benchmark for SSD? I hear spazoid loud and clear, but I have also seem other posters (non marketing in origin) that have said the opposite. :shrug:
03-03-2009, 09:09 AM
Ao1

1 Attachment(s)

Results for a 256 Strip. I'm going to put them in an excel table to make comparison easier.
03-03-2009, 11:17 AM
Marios

1 Attachment(s)

OMG those are GREAT results from two hard disks in RAID-0!!!
You got a 7.7 (128 strip) and 7.8 (256 strip) Disk Bench Rate on Seven!! Unbelievable ... LOL
Do you think it is because of your Adaptec controller?
Did you use one partition for both your disks or did you make more partitions?
I think it's time for me to get two of those diamonds.

You might also copy the results instead of making a snapshot.

Just select mark, then select what you want to copy and press enter
Then paste in notepad.

For Excell use three columns. The first is the following. Then add as many columns as you want with your results.
Then make a chart.

Random Read 16KB
Random Read 32KB
Random Read 64KB
Random Read 128KB
Random Read 256KB
Random Read 512KB
Random Read 1024KB
Random Write 16KB
Random Write 32KB
Random Write 64KB
Random Write 128KB
Random Write 256KB
Random Write 512KB
Random Write 1024KB
Sequencial Read 64KB
Sequencial Read 128KB
Sequencial Read 256KB
Sequencial Read 512KB
Sequencial Read 1024KB
Sequencial Write 64KB
Sequencial Write 128KB
Sequencial Write 256KB
Sequencial Write 512KB
Sequencial Write 1024KB

You may also try the long form with -v for the two most important results (measured by Seven) which are random read 16K and sequential read 64K.
This way you see results from all the areas of your disk and you may also make a graph like HDTach with excel.
03-03-2009, 11:50 AM
alfaunits

I think the test is mostly ran in the cache, as those write speeds cannot be achieved otherwise even with 4 of those babies.
03-03-2009, 01:03 PM
Marios

It is very difficult to reliably measure ssd disks.
I have one more idea. This is easy.
Could you please shrink your partition to the actual data size and run again the same test on drive C?
Something like a drive C 98% full with available disk space at about 2% should be OK.
Leave the rest of the raid-0 without any partitions.
03-03-2009, 02:13 PM
Ao1

2 Attachment(s)

Marios,

To answer your questions:

I guess the Adaptec controller is only helping, however One Hertz has looked into the 5405 and his testing has shown that access/ latency times suffer on the 5405 in comparison to onboard.

I started off with a single X25-E but it quickly transpired that it was not going to be big enough. Unfortunately I didn't test it, but I can say that I have not noticed any perceivable difference in performance since I went to raid 0 on the Adaptec. I only went to the Adaptec because I got fed up with onboard raid failures.

The X25-e's are on a single partition giving a capacity of 63.7GB currently around 50% used.

I didn't read your post until I had finished the testing and didn't save the results directly from CDM as I didn't know you could extract the results. Dooh. (Actually I got the last test on a 64K strip)

I did however put the results in an excel sheet as below. Seems that the X25-E's don't like the 16K strip and the sweet spot is between 128K & 256K.

The test results are in order of the strip changes that I made. Looking at the results it does not seem that read results suffered from repeated testing, despite the hammering. Just to be sure that read speeds were not affected I'm going to switch back to a 128K strip to see if I get the same results as the original test.

Again my sincere thanks for your help.
03-03-2009, 02:15 PM
Ao1

Quote:

Originally Posted by Marios

It is very difficult to reliably measure ssd disks.
I have one more idea. This is easy.
Could you please shrink your partition to the actual data size and run again the same test on drive C?
Something like a drive C 98% full with available disk space at about 2% should be OK.
Leave the rest of the raid-0 without any partitions.

No problem. What strip size though? Currently it's set at 64K. If I need to change it I will post tomorrow if not I may get back tonight if you reply quickly.....it's getting late in the UK
03-03-2009, 02:49 PM
Marios

No need to change the stripe size.
Nice job. Thank you for your info and your efforts.
03-03-2009, 03:17 PM
One_Hertz

should have really turned off the cache before all that testing :(
03-03-2009, 04:54 PM
Ao1

Quote:

Originally Posted by One_Hertz

should have really turned off the cache before all that testing :(

Specially for you One Hertz as I like your posts...albeit this gem could have come a bit earlier. ;)

Remember I'm not testing the X25-E here, I'm testing the combination of the X25-E and 5405 so I'm not going to test each strip size again unless someone really wants to see it.

Seems that 128K works best with the 5405 as you said in the first place. :up:

Strip back at 128K. Write & read cache disabled in Adaptec Storage Manager:

Microsoft Windows [Version 6.1.7000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\richard>bnch c

C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
16384
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 16384'
> Run Time 00:00:00.28
> Disk Random 16.0 Write 196.80 MB/s
> Total Run Time 00:00:00.87

C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
65536
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 65536'
> Run Time 00:00:00.36
> Disk Random 64.0 Write 304.22 MB/s
> Total Run Time 00:00:00.95

C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
524288
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 524288'
> Run Time 00:00:01.04
> Disk Random 512.0 Write 283.23 MB/s
> Total Run Time 00:00:01.70

C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
1048576
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 1048576'
> Run Time 00:00:01.45
> Disk Random 1024.0 Write 272.44 MB/s
> Total Run Time 00:00:02.14

C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
16384
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 16384'
> Run Time 00:00:00.34
> Disk Random 16.0 Read 137.68 MB/s 7.4
> Total Run Time 00:00:01.00

C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
65536
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 65536'
> Run Time 00:00:00.37
> Disk Random 64.0 Read 246.02 MB/s
> Total Run Time 00:00:00.98

C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
524288
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 524288'
> Run Time 00:00:00.51
> Disk Random 512.0 Read 489.61 MB/s
> Total Run Time 00:00:01.12

C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
1048576
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 1048576'
> Run Time 00:00:00.87
> Disk Random 1024.0 Read 425.14 MB/s
> Total Run Time 00:00:01.53

C:\Users\richard>winsat disk -seq -write -drive c -count 1 -iocount 256 -seqsize
65536
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -write -drive c -count 1 -iocount 2
56 -seqsize 65536'
> Run Time 00:00:00.31
> Disk Sequential 64.0 Write 751.38 MB/s
> Total Run Time 00:00:00.97

C:\Users\richard>winsat disk -seq -write -drive c -count 1 -iocount 256 -seqsize
524288
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -write -drive c -count 1 -iocount 2
56 -seqsize 524288'
> Run Time 00:00:00.76
> Disk Sequential 512.0 Write 314.88 MB/s
> Total Run Time 00:00:01.39

C:\Users\richard>winsat disk -seq -write -drive c -count 1 -iocount 256 -seqsize
1048576
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -write -drive c -count 1 -iocount 2
56 -seqsize 1048576'
> Run Time 00:00:01.36
> Disk Sequential 1024.0 Write 316.33 MB/s
> Total Run Time 00:00:01.95

C:\Users\richard>winsat disk -seq -read -drive c -count 1 -iocount 256 -seqsize
65536
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -read -drive c -count 1 -iocount 25
6 -seqsize 65536'
> Run Time 00:00:02.53
> Disk Sequential 64.0 Read 392.34 MB/s 7.9
> Total Run Time 00:00:03.28

C:\Users\richard>winsat disk -seq -read -drive c -count 1 -iocount 256 -seqsize
524288
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -read -drive c -count 1 -iocount 25
6 -seqsize 524288'
> Run Time 00:00:04.57
> Disk Sequential 512.0 Read 449.34 MB/s
> Total Run Time 00:00:05.21

C:\Users\richard>winsat disk -seq -read -drive c -count 1 -iocount 256 -seqsize
1048576
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -read -drive c -count 1 -iocount 25
6 -seqsize 1048576'
> Run Time 00:00:06.32
> Disk Sequential 1024.0 Read 467.71 MB/s
> Total Run Time 00:00:06.91

C:\Users\richard>
03-03-2009, 06:48 PM
One_Hertz

Quote:

Originally Posted by audienceofone

Seems that 128K works best with the 5405 as you said in the first place. :up:

I've tested it myself on real world apps and found 128k the best for all scenarios, which is why I recommended you that size back when you first asked. Just wanted to confirm my findings :).
03-03-2009, 09:15 PM
Marios

1 Attachment(s)

The Intel SSD controller is very efficient by using various techniques, like combining many small files to a larger one, so that writes are almost sequential. There are other techniques involved which no one knows.
Shrinking the partition volume usually gives better results.
Is this the case with Intel SSDs?
Can we shrink the Voolume on Seven with SSDs?

To shrink the volume we do the following.
Right click computer - Manage - Storage - Disk management
Next to disk 0 there is a representation of the RAID (C:) partition.
This should have the size of two Intel SSD disks.
Right click on this partition and select shrink volume.
03-04-2009, 05:09 AM
Ao1

1 Attachment(s)

Hi Marios,

As you can see below the drive is 50% full, but I can only shrink the disk by approx 1GB. My guess is this is because the drive is badly fragmented and Windows is seeing partly written blocks as being full. If true this is not really surprising. The drives have been running for a couple of months and have been subject to numerous tests, including IOmeter, which actually filled the drive completely with data at one stage.

If correct the results in the tests are the worst case performance of these drives.

To find out for sure I'm going to do a secure erase and then check to see if I can shrink the partition and then follow up with a new test with a 128K strip with and without cache.
03-04-2009, 06:25 AM
Marios

Hi audienceofone,

I thought you might not be able to shrink the disk because of the way SSDs write all over the disk to prevent wear. Thank you for your info.
Seven have no way to consolidate the drive (erase blocks and re write them elsewhere to make room, since there is no standard about SSD controllers yet.
The second thing I suspect is that on an almost full drive, SSDs give worse results.
I do not mean to put you in trouble, but I think it is important to bench on an almost full partition for SSDs.
To do it you might have to create the partition first.
Shrinking it afterwards, might not work, even with a fresh install on a revived SSD.
So in case you really want to check both situations (fragmentation and worst case bench), I agree that the way you proposed is the best.
On the other hand you might find that benching on a full partition gives results closer to the perception you have about the speed of your SSDs in everyday usage.
There is a very nice small utility HDDErase_3.3 to erase your disk.
You may find it here.

Thank you again.
03-04-2009, 08:10 AM
Ao1

Hi Marios

OK, drives formatted with HDDErase level 1. OS installed back from an image. Benchmarks below are on a 128K strip. First test is with cache, second is without.

Benchmarks show improvements so it seems that previously results have suffered from fragmentation.

I was still not able to shrink the volume after the format so in SDD terms it seems it was full. I'm therefore wondering if reducing the partition size would make any difference. Reducing the partition is going to involve a fresh format and a fresh install, which is going to be a lot of work, especially as I will then have to do it all again on a full partition.

I can do it if you really think it would be worthwhile, but I'm inclined to think that all of the previously posted tests were effectively on a full drive.

128 Strip - With Cache
Microsoft Windows [Version 6.1.7000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\richard>bnch c
C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
16384
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 16384'
> Run Time 00:00:00.25
> Disk Random 16.0 Read 214.51 MB/s 7.8
> Total Run Time 00:00:00.90

C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
32768
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 32768'
> Run Time 00:00:00.28
> Disk Random 32.0 Read 155.79 MB/s
> Total Run Time 00:00:00.92
C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
65536
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 65536'
> Run Time 00:00:00.26
> Disk Random 64.0 Read 366.56 MB/s
> Total Run Time 00:00:00.86
C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
131072
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 131072'
> Run Time 00:00:00.28
> Disk Random 128.0 Read 362.86 MB/s
> Total Run Time 00:00:00.84
C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
262144
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 262144'
> Run Time 00:00:00.36
> Disk Random 256.0 Read 495.89 MB/s
> Total Run Time 00:00:01.00
C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
524288
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 524288'
> Run Time 00:00:00.50
> Disk Random 512.0 Read 495.22 MB/s
> Total Run Time 00:00:01.15
C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
1048576
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 1048576'
> Run Time 00:00:00.73
> Disk Random 1024.0 Read 487.14 MB/s
> Total Run Time 00:00:01.34
C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
16384
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 16384'
> Run Time 00:00:00.25
> Disk Random 16.0 Write 503.01 MB/s
> Total Run Time 00:00:00.83
C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
32768
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 32768'
> Run Time 00:00:00.26
> Disk Random 32.0 Write 566.24 MB/s
> Total Run Time 00:00:00.89

C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
65536
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 65536'
> Run Time 00:00:00.25
> Disk Random 64.0 Write 617.30 MB/s
> Total Run Time 00:00:00.89
C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
131072
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 131072'
> Run Time 00:00:00.28
> Disk Random 128.0 Write 822.24 MB/s
> Total Run Time 00:00:00.87
C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
262144
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 262144'
> Run Time 00:00:00.25
> Disk Random 256.0 Write 883.89 MB/s
> Total Run Time 00:00:00.83
C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
524288
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 524288'
> Run Time 00:00:00.42
> Disk Random 512.0 Write 841.58 MB/s
> Total Run Time 00:00:01.04
C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
1048576
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 1048576'
> Run Time 00:00:00.51
> Disk Random 1024.0 Write 919.79 MB/s
> Total Run Time 00:00:01.15
C:\Users\richard>winsat disk -seq -read -drive c -count 1 -iocount 256 -seqsize
65536
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -read -drive c -count 1 -iocount 25
6 -seqsize 65536'
> Run Time 00:00:01.92
> Disk Sequential 64.0 Read 495.42 MB/s 7.9
> Total Run Time 00:00:02.53
C:\Users\richard>winsat disk -seq -read -drive c -count 1 -iocount 256 -seqsize
131072
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -read -drive c -count 1 -iocount 25
6 -seqsize 131072'
> Run Time 00:00:02.03
> Disk Sequential 128.0 Read 500.33 MB/s
> Total Run Time 00:00:02.61
C:\Users\richard>winsat disk -seq -read -drive c -count 1 -iocount 256 -seqsize
262144
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -read -drive c -count 1 -iocount 25
6 -seqsize 262144'
> Run Time 00:00:03.17
> Disk Sequential 256.0 Read 457.04 MB/s
> Total Run Time 00:00:03.81

C:\Users\richard>winsat disk -seq -read -drive c -count 1 -iocount 256 -seqsize
524288
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -read -drive c -count 1 -iocount 25
6 -seqsize 524288'
> Run Time 00:00:03.98
> Disk Sequential 512.0 Read 496.07 MB/s
> Total Run Time 00:00:04.60
C:\Users\richard>winsat disk -seq -read -drive c -count 1 -iocount 256 -seqsize
1048576
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -read -drive c -count 1 -iocount 25
6 -seqsize 1048576'
> Run Time 00:00:05.84
> Disk Sequential 1024.0 Read 487.97 MB/s
> Total Run Time 00:00:06.41
C:\Users\richard>winsat disk -seq -write -drive c -count 1 -iocount 256 -seqsize
65536
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -write -drive c -count 1 -iocount 2
56 -seqsize 65536'
> Run Time 00:00:00.25
> Disk Sequential 64.0 Write 862.28 MB/s
> Total Run Time 00:00:00.86
C:\Users\richard>winsat disk -seq -write -drive c -count 1 -iocount 256 -seqsize
131072
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -write -drive c -count 1 -iocount 2
56 -seqsize 131072'
> Run Time 00:00:00.26
> Disk Sequential 128.0 Write 869.26 MB/s
> Total Run Time 00:00:00.90
C:\Users\richard>winsat disk -seq -write -drive c -count 1 -iocount 256 -seqsize
262144
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -write -drive c -count 1 -iocount 2
56 -seqsize 262144'
> Run Time 00:00:00.31
> Disk Sequential 256.0 Write 913.64 MB/s
> Total Run Time 00:00:00.95
C:\Users\richard>winsat disk -seq -write -drive c -count 1 -iocount 256 -seqsize
524288
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -write -drive c -count 1 -iocount 2
56 -seqsize 524288'
> Run Time 00:00:00.41
> Disk Sequential 512.0 Write 739.18 MB/s
> Total Run Time 00:00:00.98
C:\Users\richard>winsat disk -seq -write -drive c -count 1 -iocount 256 -seqsize
1048576
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -write -drive c -count 1 -iocount 2
56 -seqsize 1048576'
> Run Time 00:00:00.84
> Disk Sequential 1024.0 Write 497.46 MB/s
> Total Run Time 00:00:01.45
C:\Users\richard>

128 Strip - Without Cache
Microsoft Windows [Version 6.1.7000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\richard>bnch c
C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
16384
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 16384'
> Run Time 00:00:00.26
> Disk Random 16.0 Read 227.08 MB/s 7.9
> Total Run Time 00:00:00.92
C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
32768
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 32768'
> Run Time 00:00:00.23
> Disk Random 32.0 Read 314.70 MB/s
> Total Run Time 00:00:00.81
C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
65536
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 65536'
> Run Time 00:00:00.28
> Disk Random 64.0 Read 375.29 MB/s
> Total Run Time 00:00:00.90
C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
131072
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 131072'
> Run Time 00:00:00.33
> Disk Random 128.0 Read 423.32 MB/s
> Total Run Time 00:00:00.98
C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
262144
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 262144'
> Run Time 00:00:00.39
> Disk Random 256.0 Read 482.48 MB/s
> Total Run Time 00:00:01.03
C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
524288
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 524288'
> Run Time 00:00:00.47
> Disk Random 512.0 Read 493.05 MB/s
> Total Run Time 00:00:01.04
C:\Users\richard>winsat disk -ran -read -drive c -count 1 -iocount 256 -ransize
1048576
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -read -drive c -count 1 -iocount 25
6 -ransize 1048576'
> Run Time 00:00:00.76
> Disk Random 1024.0 Read 481.65 MB/s
> Total Run Time 00:00:01.40
C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
16384
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 16384'
> Run Time 00:00:00.28
> Disk Random 16.0 Write 195.55 MB/s
> Total Run Time 00:00:00.92
C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
32768
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 32768'
> Run Time 00:00:00.28
> Disk Random 32.0 Write 271.13 MB/s
> Total Run Time 00:00:00.92
C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
65536
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 65536'
> Run Time 00:00:00.27
> Disk Random 64.0 Write 294.58 MB/s
> Total Run Time 00:00:00.84

C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
131072
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 131072'
> Run Time 00:00:00.34
> Disk Random 128.0 Write 337.70 MB/s
> Total Run Time 00:00:00.98
C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
262144
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 262144'
> Run Time 00:00:00.41
> Disk Random 256.0 Write 396.62 MB/s
> Total Run Time 00:00:01.06
C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
524288
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 524288'
> Run Time 00:00:00.61
> Disk Random 512.0 Write 390.93 MB/s
> Total Run Time 00:00:01.20
C:\Users\richard>winsat disk -ran -write -drive c -count 1 -iocount 256 -ransize
1048576
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-ran -write -drive c -count 1 -iocount 2
56 -ransize 1048576'
> Run Time 00:00:00.90
> Disk Random 1024.0 Write 399.77 MB/s
> Total Run Time 00:00:01.50
C:\Users\richard>winsat disk -seq -read -drive c -count 1 -iocount 256 -seqsize
65536
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -read -drive c -count 1 -iocount 25
6 -seqsize 65536'
> Run Time 00:00:02.31
> Disk Sequential 64.0 Read 470.80 MB/s 7.9
> Total Run Time 00:00:02.95

C:\Users\richard>winsat disk -seq -read -drive c -count 1 -iocount 256 -seqsize
131072
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -read -drive c -count 1 -iocount 25
6 -seqsize 131072'
> Run Time 00:00:02.56
> Disk Sequential 128.0 Read 492.77 MB/s
> Total Run Time 00:00:03.20
C:\Users\richard>winsat disk -seq -read -drive c -count 1 -iocount 256 -seqsize
262144
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -read -drive c -count 1 -iocount 25
6 -seqsize 262144'
> Run Time 00:00:03.06
> Disk Sequential 256.0 Read 488.43 MB/s
> Total Run Time 00:00:03.70
C:\Users\richard>winsat disk -seq -read -drive c -count 1 -iocount 256 -seqsize
524288
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -read -drive c -count 1 -iocount 25
6 -seqsize 524288'
> Run Time 00:00:04.15
> Disk Sequential 512.0 Read 489.95 MB/s
> Total Run Time 00:00:04.79
C:\Users\richard>winsat disk -seq -read -drive c -count 1 -iocount 256 -seqsize
1048576
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -read -drive c -count 1 -iocount 25
6 -seqsize 1048576'
> Run Time 00:00:06.30
> Disk Sequential 1024.0 Read 487.26 MB/s
> Total Run Time 00:00:06.94
C:\Users\richard>winsat disk -seq -write -drive c -count 1 -iocount 256 -seqsize
65536
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -write -drive c -count 1 -iocount 2
56 -seqsize 65536'
> Run Time 00:00:00.26
> Disk Sequential 64.0 Write 923.00 MB/s
> Total Run Time 00:00:00.83
C:\Users\richard>winsat disk -seq -write -drive c -count 1 -iocount 256 -seqsize
131072
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -write -drive c -count 1 -iocount 2
56 -seqsize 131072'
> Run Time 00:00:00.30
> Disk Sequential 128.0 Write 598.48 MB/s
> Total Run Time 00:00:00.90
C:\Users\richard>winsat disk -seq -write -drive c -count 1 -iocount 256 -seqsize
262144
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -write -drive c -count 1 -iocount 2
56 -seqsize 262144'
> Run Time 00:00:00.41
> Disk Sequential 256.0 Write 467.50 MB/s
> Total Run Time 00:00:01.04
C:\Users\richard>winsat disk -seq -write -drive c -count 1 -iocount 256 -seqsize
524288
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -write -drive c -count 1 -iocount 2
56 -seqsize 524288'
> Run Time 00:00:00.59
> Disk Sequential 512.0 Write 423.42 MB/s
> Total Run Time 00:00:01.22
C:\Users\richard>winsat disk -seq -write -drive c -count 1 -iocount 256 -seqsize
1048576
Windows System Assessment Tool
> Running: Feature Enumeration v1.0.0.0 ''
> Run Time 00:00:00.00
> Running: Storage Assessment v2.0.0.0 '-seq -write -drive c -count 1 -iocount 2
56 -seqsize 1048576'
> Run Time 00:00:00.86
> Disk Sequential 1024.0 Write 421.25 MB/s
> Total Run Time 00:00:01.45
C:\Users\richard>
03-04-2009, 09:35 PM
Marios

Hi audienceofone,

You got impressive results on your revived disks.
It would be very interesting to know if something changes dramatically in case of a full partition.
It involves a lot of time to check it, so it is up to you to do it or not.

Marios
03-05-2009, 12:02 PM
Ao1

I'm intrigued as well, so I will play with it over the weekend and post results.
03-07-2009, 12:39 AM
Ao1

Hi Marios

I created a 8GB partition in raid 0 from the Adaptec BIOS, no problem. Tried a fresh 7 install and it would not install. Not enough space....hmm. I deleted the raid and created another one with a 9GB partition and tried a fresh install again. Not enough space....something is not right.

I did a secure erase with HDDErase.....I got a message to say not all sectors could be erased. At this stage a mild sweat began to develop.

I created a full raid 0 array and tried a fresh install and it would not install. I tried another secure erase with HDDErase.....I got the same message to say not all sectors could be erased. Now I'm beginning to :banana::banana::banana::banana: bricks.

I tried an image install. Whew....it worked.

Somehow the image install cleared/ reset the partition when HDD Erase could not.

Call me a sucker but I tried it all again with a 10GB partition, but this time the drive could not even been seen for a fresh install. I could see the raid 1 HDD array so this was nothing to do with drivers.

Back to the image install. No problem.

Adaptec don't support SDD. 7 is a beta. Could be one or the other or both, or much more likely I don't think SDD's like anything less than a full partition.

Sorry about that, but it seems that just as you can't shrink an SDD you can't create small partitions.

Has anyone else had any luck creating a small partition on an SSD?
03-07-2009, 08:15 AM
One_Hertz

AFAIK my windows 7 took 14GB. So yes, 8,9,10 won't work.
03-07-2009, 09:05 AM
Griff805

You need at least around 24-26GB I think for Windows 7 install. After install, it takes up around 14-16GB. You can Vlite the install and get it down to less than 2GB install. I had to do this to get Windows 7 on a 16GB SSD.

http://www.multimolti.de/blog/2009/0...ee-pc-4gb-sdd/

http://www.multimolti.de/blog/2008/1...us-eee-pc-900/