XavierMace
Diamond Member
- Apr 20, 2013
- 4,307
- 450
- 126
Well, I am not familiar with that particular metric when it comes to drives. I guess I will scrap those drives from the build then, or at least from the ZIL/L2ARC portion. Would the Agility 3's be sufficient in Raid 0 for the OS do you think?
The other 2 drives that I have are Toshiba Q Series HDTS225XZSTA. Would these suffice for L2ARC and ZIL partitions?
Don't RAID0 an OS drive, that's just asking for avoidable issues. Honestly 60GB is more than plenty for a Linux server OS (hell an 8GB SD card is enough).
Those drives would work, but are super pricy. I would strongly consider the Intel SSD Pro 2500 240GB at $135. You pay about a $35 premium over a drive like an MX100, but you get high, consistent IO performance. The MX100 is consistent too, and would save you some money, but has lower steady state performance. You really can't go wrong either way.
The Toshiba drives that I linked are a zero cost, because I already own 2. One of them is in my gaming laptop, but it makes no sense for an SSD in that one, still takes forever to boot with an SSD. The twin to that drive is the one that is in my PS3. That doesn't need to be in there, as I want a larger drive in there, and have a 1TB 2.5" drive to replace it. Just a matter of backing up the PS3 and replacing it, but that is an issue since the dumb thing won't recognize any external drives I have.
I messed with the order of the cables on the motherboard connectors until I got the drive arrangement that I wanted, so that sda is boot, sdb will be boot backup, sdc and sdd will be LOG and L2ARC drives. The good news is that all 8 of the hot swap drives in place are all seen as well.
<putty image>
I want the bezel on there so that I can have some filter media between it and the chassis (hopefully) to hopefully keep all of the fans and heat sinks free from dust and getting clogged.
ziggidy@Ziggidy-VH:~$ sudo zpool status
pool: Storage
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
Storage ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1304884 ONLINE 0 0 0
ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1344552 ONLINE 0 0 0
ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1344610 ONLINE 0 0 0
ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1324763 ONLINE 0 0 0
ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1380342 ONLINE 0 0 0
ata-WDC_WD40EFRX-68WT0N0_WD-WCC4EFUL6XA9 ONLINE 0 0 0
logs
ata-TOSHIBA_THNSNH256GBST_83IS10JLTE8Y-part1 ONLINE 0 0 0
ata-TOSHIBA_THNSNH256GBST_83JS106NTE8Y-part1 ONLINE 0 0 0
cache
ata-TOSHIBA_THNSNH256GBST_83IS10JLTE8Y-part2 ONLINE 0 0 0
ata-TOSHIBA_THNSNH256GBST_83JS106NTE8Y-part2 ONLINE 0 0 0
errors: No known data errors
ziggidy@Ziggidy-VH:~$
ziggidy@Ziggidy-VH:~$
ziggidy@Ziggidy-VH:~$ sudo zfs list
NAME USED AVAIL REFER MOUNTPOINT
Storage 1.80M 14.3T 272K /Storage
Storage/Backups 272K 14.3T 272K /mnt/Storage/Backups
Storage/Media 272K 14.3T 272K /mnt/Storage/Media
ziggidy@Ziggidy-VH:~$
ziggidy@Ziggidy-VH:~$
ziggidy@Ziggidy-VH:~$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +29.0°C (high = +85.0°C, crit = +95.0°C)
Core 1: +29.0°C (high = +85.0°C, crit = +95.0°C)
Core 9: +29.0°C (high = +85.0°C, crit = +95.0°C)
Core 10: +26.0°C (high = +85.0°C, crit = +95.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 0: +23.0°C (high = +85.0°C, crit = +95.0°C)
Core 1: +25.0°C (high = +85.0°C, crit = +95.0°C)
Core 9: +24.0°C (high = +85.0°C, crit = +95.0°C)
Core 10: +30.0°C (high = +85.0°C, crit = +95.0°C)
w83627hf-isa-0a00
Adapter: ISA adapter
in0: +3.84 V (min = +0.00 V, max = +4.08 V)
in1: +3.86 V (min = +0.00 V, max = +4.08 V)
in2: +3.84 V (min = +2.82 V, max = +3.79 V) ALARM
in3: +3.06 V (min = +4.08 V, max = +4.08 V) ALARM
in4: +3.09 V (min = +4.08 V, max = +4.08 V) ALARM
in5: +3.14 V (min = +4.08 V, max = +4.08 V) ALARM
in6: +3.15 V (min = +4.08 V, max = +4.08 V) ALARM
in7: +3.31 V (min = +4.08 V, max = +4.08 V) ALARM
in8: +3.25 V (min = +4.08 V, max = +4.08 V) ALARM
fan1: 0 RPM (min = 0 RPM, div = 8)
fan2: 0 RPM (min = 0 RPM, div = 8)
fan3: 0 RPM (min = 0 RPM, div = 8)
temp1: -48.0°C (high = -1.0°C, hyst = -1.0°C) sensor = thermistor
temp2: -48.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
temp3: -48.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
cpu0_vid: +1.419 V
beep_enable: enabled
ziggidy@Ziggidy-VH:~$
Yeah, i'd run vmware ESXi on that guy, then run whatever I want and attach those raids as data stores, using the SSD's are C drives for boot of the VPS's.
I am digging the command Line. It isn't foreign as I am in Cisco and Juniper router command lines all day at work, just different commands. Sometimes Unix jumper servers too, nothing other than creating router configs with vi, changing permissions, searching, and copying files though with those.
Code:ziggidy@Ziggidy-VH:~$ sudo zpool status pool: Storage state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM Storage ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1304884 ONLINE 0 0 0 ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1344552 ONLINE 0 0 0 ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1344610 ONLINE 0 0 0 ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1324763 ONLINE 0 0 0 ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1380342 ONLINE 0 0 0 ata-WDC_WD40EFRX-68WT0N0_WD-WCC4EFUL6XA9 ONLINE 0 0 0 logs ata-TOSHIBA_THNSNH256GBST_83IS10JLTE8Y-part1 ONLINE 0 0 0 ata-TOSHIBA_THNSNH256GBST_83JS106NTE8Y-part1 ONLINE 0 0 0 cache ata-TOSHIBA_THNSNH256GBST_83IS10JLTE8Y-part2 ONLINE 0 0 0 ata-TOSHIBA_THNSNH256GBST_83JS106NTE8Y-part2 ONLINE 0 0 0
zpool remove Storage ata-TOSHIBA_THNSNH256GBST_83IS10JLTE8Y-part1
zpool remove Storage ata-TOSHIBA_THNSNH256GBST_83JS106NTE8Y-part1
zpool add Storage log mirror ata-TOSHIBA_THNSNH256GBST_83IS10JLTE8Y-part1 ata-TOSHIBA_THNSNH256GBST_83JS106NTE8Y-part1
ziggidy@Ziggidy-VH:~$ sudo zpool remove Storage ata-TOSHIBA_THNSNH256GBST_83IS10JLTE8Y-part1
ziggidy@Ziggidy-VH:~$ sudo zpool remove Storage ata-TOSHIBA_THNSNH256GBST_83JS106NTE8Y-part1
ziggidy@Ziggidy-VH:~$ sudo zpool add Storage log mirror ata-TOSHIBA_THNSNH256GBST_83IS10JLTE8Y-part1 ata-TOSHIBA_THNSNH256GBST_83JS106NTE8Y-part1
ziggidy@Ziggidy-VH:~$
ziggidy@Ziggidy-VH:~$
ziggidy@Ziggidy-VH:~$ sudo zpool status
pool: Storage
state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(5) for details.
scan: none requested
config:
NAME STATE READ WRITE CKSUM
Storage ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1304884 ONLINE 0 0 0
ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1344552 ONLINE 0 0 0
ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1344610 ONLINE 0 0 0
ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1324763 ONLINE 0 0 0
ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1380342 ONLINE 0 0 0
ata-WDC_WD40EFRX-68WT0N0_WD-WCC4EFUL6XA9 ONLINE 0 0 0
logs
mirror-1 ONLINE 0 0 0
ata-TOSHIBA_THNSNH256GBST_83IS10JLTE8Y-part1 ONLINE 0 0 0
ata-TOSHIBA_THNSNH256GBST_83JS106NTE8Y-part1 ONLINE 0 0 0
cache
ata-TOSHIBA_THNSNH256GBST_83IS10JLTE8Y-part2 ONLINE 0 0 0
ata-TOSHIBA_THNSNH256GBST_83JS106NTE8Y-part2 ONLINE 0 0 0
errors: No known data errors
ziggidy@Ziggidy-VH:~$
I would definitely not run ESXi on a machine that is meant to be a storage server. You either have to give up the performance and flexibility of ZFS to go with hardware RAID or try to virtualize ZFS and lose the performance and reliability features built into ZFS.
I would definitely not run ESXi on a machine that is meant to be a storage server. You either have to give up the performance and flexibility of ZFS to go with hardware RAID or try to virtualize ZFS and lose the performance and reliability features built into ZFS.
Thank you for the heads up on that. Totally forgot. I had to alter the commands from zfs to zpool, but it worked like a champ!!