| View previous topic :: View next topic |
| Author |
Message |
kbzium
Tux's lil' helper
Joined: 31 Jul 2012
Posts: 146
|
 Posted: Thu Feb 28, 2013 10:02 pm Post subject: Test if SSD is using SataIII? |
 |
|
Hello,
how to be absolutelly sure that an SSD runs on SataIII, not II? It may be a huge loss, you know.
Thanks! |
|
| Back to top |
|
 |
eccerr0r
Watchman
Joined: 01 Jul 2004
Posts: 9891
Location: almost Mile High in the USA
|
| Posted: Thu Feb 28, 2013 11:16 pm Post subject: |
|
|
It should be fairly obvious in read benchmarks... If you have a decent disk getting less than 300MB/sec, likely you're not using SATA III.
The dmesg log should report a 6Gbps link to the disk too.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
| Back to top |
|
|
kbzium
Tux's lil' helper
Joined: 31 Jul 2012
Posts: 146
|
| Posted: Sat Mar 02, 2013 9:24 am Post subject: |
|
|
Ok so what are other things that I should be aware of using ssd on gentoo? Just bumped into AHCI... turned in on in bios (Windows 8 gets blue screen after that  )
but Gentoo works. When i do
| Code: |
grep AHCI /var/log/dmesg
ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode |
And:
| Code: | | /dev/sdb1 / ext4 discard,noatime 0 1 |
Is it good or not? Some options in Kernel I should enable? Moreover:
| Code: | Disk /dev/sdb: 128.0 GB, 128035676160 bytes
255 heads, 63 sectors/track, 15566 cylinders, total 250069680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000037a7
Device Boot Start End Blocks Id System
/dev/sdb1 4096 167776255 83886080 83 Linux
/dev/sdb2 * 167776256 250069679 41146712 7 HPFS/NTFS/exFAT
|
Is it good partition placement? I figured out that my vertex 4 has 2MB erase block size with 8k blocks. Ext4 supports only 4k so I left 4k.
I've used H128 + S32 option but I don't know why its 255 heads, 63 sectors/track now...
Thanks! |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54834
Location: 56N 3W
|
| Posted: Sat Mar 02, 2013 11:19 am Post subject: |
|
|
kbzium,
Looks good.
With the discard option, you should never need to wait the erase time prior to a write, unless your SSD is very full.
On the other hand, the erase happens soon after space is freed, so don't expect to recover any deleted files either.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
kbzium
Tux's lil' helper
Joined: 31 Jul 2012
Posts: 146
|
| Posted: Sat Mar 02, 2013 1:32 pm Post subject: |
|
|
One last thing that bothers me is that I've actually set stride=512, stripe-width=512, -b 4096 (which is max) as I'm using vertex 4 with:
| Code: | 2MB erase block size
8kb block
which gives
256 stripes/erase block |
I've used -H128 -S32 in fdisk when partitioning (that is 128*32 = 4096)
This means that there are 2 data units in one 8kb block "row", is that correct too? Is there any tool on linux that could give me actually some results to be absolutely sure that everything works just fine too?
Thanks man! |
|
| Back to top |
|
|
|
Kernel & Hardware
