NVMe: 2.5" SFF drives working in a normal desktop

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
C

Chuntzu

Active Member
Jun 30, 2013
383
98
28
@Patrick it would be sick to put 12 in one chassis with 12 sas3 12.0 drives. Bet that would be one heck of a speed deamon. Possibly the next dirtcheap data warehouse, what do you say @dba ? Might need quad socket to utilize all those 8k iops.
 
Patrick

Patrick

Administrator
Staff member
Dec 21, 2010
12,535
5,862
113
Chuntzu said:
@Patrick it would be sick to put 12 in one chassis with 12 sas3 12.0 drives. Bet that would be one heck of a speed deamon. Possibly the next dirtcheap data warehouse, what do you say @dba ? Might need quad socket to utilize all those 8k iops.
Click to expand...
I think @dba and I have discussed something similar. NVMe drives are not an issue at this point. Just need more places to put them!

Also - the Asus Hyper Kit arrived yesterday. Unfortunately the adapter size is in-between the two post mounting points on the X10SDV-TLN4F so that is not likely to work. Total bummer!
 
Hank C

Hank C

Active Member
Jun 16, 2014
644
66
28
Patrick said:
I think @dba and I have discussed something similar. NVMe drives are not an issue at this point. Just need more places to put them!

Also - the Asus Hyper Kit arrived yesterday. Unfortunately the adapter size is in-between the two post mounting points on the X10SDV-TLN4F so that is not likely to work. Total bummer!
Click to expand...
why not get the conversion kit?
 
Patrick

Patrick

Administrator
Staff member
Dec 21, 2010
12,535
5,862
113
I just wanted to see if I could fit it in the m.2 slot. Odds are I can fit this with some electrical tape.
 
D

dba

Moderator
Feb 20, 2012
1,477
184
63
San Francisco Bay Area, California, USA
Chuntzu said:
@Patrick it would be sick to put 12 in one chassis with 12 sas3 12.0 drives. Bet that would be one heck of a speed deamon. Possibly the next dirtcheap data warehouse, what do you say @dba ? Might need quad socket to utilize all those 8k iops.
Click to expand...
I keep waiting for a chassis that can deliver 16+ NVMe drives. It would be a not-so-dirt-cheap data warehouse, but man would it fly! We're talking 40,000MB/s, or a bit less than double what I have now.
 
  • Like
Reactions: ehorn and Chuntzu
Patrick

Patrick

Administrator
Staff member
Dec 21, 2010
12,535
5,862
113
dba said:
I keep waiting for a chassis that can deliver 16+ NVMe drives. It would be a not-so-dirt-cheap data warehouse, but man would it fly! We're talking 40,000MB/s, or a bit less than double what I have now.
Click to expand...
I actually think that with these Intel kits, that is not a completely unreasonable goal. 4 kits would be around $2k alone though. You would also need 64 lanes just for those drives.
 
  • Like
Reactions: Chuntzu
Patrick

Patrick

Administrator
Staff member
Dec 21, 2010
12,535
5,862
113
Biren78 said:
Did you get a chance to try the Intel in a normal desktop case?
Click to expand...
Great question. I tried in a spare SC732 and it fit width wise but not height wise. I am going to install the unit in the DC today so I did not want to Dremel but the rear 1/2" fit fine before all of the extruded parts hit the chassis. Seems doable except for one aspect. The sides of the cage are perfectly smooth. No holes for mounting it into a standard desktop chassis.

On the Supermicro X10SDV-TLN4F only the first SSD showed up :-/ That one works no problem but the others did not show up. Total bummer!
 
Patrick

Patrick

Administrator
Staff member
Dec 21, 2010
12,535
5,862
113
Installed the new carrier in the datacenter. Added 4x Samsung SM1625 200GB SAS drives also. It at least booted back into Ubuntu which is nice.

Ended up adding:
4x Samsung SM1625 200GB SAS
1x Intel P3700 400GB AIC
1x Intel P3600 400GB AIC
2x Samsung XS1715 800GB
1x Intel P3700 800GB SFF
1x Intel P3600 400GB SFF
additional 128GB RAM for a total of 256GB

Removed:
2x Fusion-io ioDrive 353GB MLC

The Fusion-io cards could have stayed but I wanted to have more OS flexibility. They will likely go into the Supermicro 2U if I can find full height brackets for the cards. There is already a 160GB SLC one in there so that will need to stay on a supported Ubuntu distribution.

Total time to install the cage: ~15 minutes. I did re-install the riser as well which was really easy.
 
Last edited:
neo

neo

Well-Known Member
Mar 18, 2015
672
364
63
Patrick said:
The Fusion-io cards could have stayed but I wanted to have more OS flexibility. They will likely go into the Supermicro 2U if I can find full height brackets for the cards.
Click to expand...
Unless there was a revision, it should be the same as the commonly found LSI 9211-8i brackets on eBay.
 
Patrick

Patrick

Administrator
Staff member
Dec 21, 2010
12,535
5,862
113
neo said:
Unless there was a revision, it should be the same as the commonly found LSI 9211-8i brackets on eBay.
Click to expand...
The issue is more that it would cover up the LED lights. Oh well!

Also as an update... minor mistake on the install (d'oh)! Will post later.
 
Patrick

Patrick

Administrator
Staff member
Dec 21, 2010
12,535
5,862
113
OK well now:
Code: 
Disk /dev/sda: 372.6 GiB, 400088457216 bytes, 781422768 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
Disklabel type: dos
Disk identifier: 0x77bb2b9e

Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1        2048 781420543 781418496 372.6G  7 HPFS/NTFS/exFAT

Disk /dev/sdc: 745.2 GiB, 800166076416 bytes, 1562824368 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
Disklabel type: dos
Disk identifier: 0xce3010e0


Disk /dev/sdb: 372.6 GiB, 400088457216 bytes, 781422768 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
Disklabel type: gpt
Disk identifier: E07461BD-779E-456F-9ECE-E852E05C2595


Disk /dev/sdd: 745.2 GiB, 800166076416 bytes, 1562824368 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
Disklabel type: dos
Disk identifier: 0x7833f945

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdd1          63 1562822319 1562822257 745.2G 42 SFS

Disk /dev/sdf: 447.1 GiB, 480103981056 bytes, 937703088 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
Disklabel type: dos
Disk identifier: 0xd631d380

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdf1  *     2048 703320063 703318016 335.4G fd Linux raid autodetect

Disk /dev/sde: 447.1 GiB, 480103981056 bytes, 937703088 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
Disklabel type: dos
Disk identifier: 0xf547de26

Device     Boot Start       End   Sectors   Size Id Type
/dev/sde1  *     2048 703320063 703318016 335.4G fd Linux raid autodetect

Disk /dev/sdg: 370.7 GiB, 397999603712 bytes, 777342976 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 /dev/nvme0n1: 745.2 GiB, 800166076416 bytes, 1562824368 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
Disklabel type: gpt
Disk identifier: 1A4202BA-8382-4B00-9A69-4E5EC59FC244

Device          Start        End    Sectors   Size Type
/dev/nvme0n1p1     34     262177     262144   128M Microsoft reserved
/dev/nvme0n1p2 264192 1562822655 1562558464 745.1G Microsoft basic data

Disk /dev/md0: 335.2 GiB, 359964606464 bytes, 703055872 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 /dev/nvme1n1: 372.6 GiB, 400088457216 bytes, 781422768 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 /dev/nvme2n1: 745.2 GiB, 800166076416 bytes, 1562824368 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 /dev/nvme3n1: 745.2 GiB, 800166076416 bytes, 1562824368 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 /dev/nvme4n1: 372.6 GiB, 400088457216 bytes, 781422768 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
Disklabel type: dos
Disk identifier: 0x9b01e099

Device         Boot Start       End   Sectors   Size Id Type
/dev/nvme4n1p1       2048 781420543 781418496 372.6G  7 HPFS/NTFS/exFAT

Disk /dev/nvme5n1: 372.6 GiB, 400088457216 bytes, 781422768 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
Hello 6x NVMe drives in the system! Looks like one still had the Windows FS on it.
 
  • Like
Reactions: T_Minus
You must log in or register to reply here.
Top Bottom