<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Disk on sigtar.com</title>
		<link>https://sigtar.com/tags/disk/</link>
		<description>Recent content in Disk on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Tue, 30 Jun 2020 00:00:00 +1200</lastBuildDate>
		
			<atom:link href="https://sigtar.com/tags/disk/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>HEVC media optimization</title>
				<link>https://sigtar.com/2020/06/30/hevc-media-optimization/</link>
				<pubDate>Tue, 30 Jun 2020 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2020/06/30/hevc-media-optimization/</guid>
				<description>&lt;p&gt;&lt;img src=&#34;https://sigtar.com/wp-content/uploads/hevc_logo.png&#34; alt=&#34;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Do you have a large collection of video media files not using HEVC (H265) yet? There is a massive amount of disk space coming your way if you flick over to the new video codec format.&lt;/p&gt;&#xA;&lt;p&gt;HEVC definitely lives up to its name, for most media you can expect a 70% or more disk savings from transcoding from an old codec. There are some catches though&amp;hellip; If you want your TV to play it direct (i.e. straight off the file) the codec will need to be supported by it. You can of course get around this by using a media server such as Plex or Emby which will transcode from HEVC back to a compatible format.&lt;/p&gt;</description>
			</item>
			<item>
				<title>unraid smart check - dead WD green drive</title>
				<link>https://sigtar.com/2014/10/30/unraid-smart-check/</link>
				<pubDate>Thu, 30 Oct 2014 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2014/10/30/unraid-smart-check/</guid>
				<description>&lt;p&gt;errors on unraid GUI - sometimes its a loose cable, sometimes its an issue with the drive.&lt;/p&gt;&#xA;&lt;p&gt;Run this command to check smart status&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;smartctl -a -d ata /dev/sda&lt;/strong&gt; or if you are using a newer SATA controller &lt;strong&gt;smartctl -a -A /dev/sda&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;http://lime-technology.com/wiki/index.php/Troubleshooting&#34;&gt;http://lime-technology.com/wiki/index.php/Troubleshooting&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;unfortunately in my case, looks like drive is pretty much dead&amp;hellip; not too bad for a drive almost 5 years old.&lt;/p&gt;&#xA;&lt;p&gt;its pretty typical of a WD green drive in its default config to die in this type of environment, no plans to replace it with a similar type drive. You can see below the incredibly high LCC count which indicates the drive header has parked this many times over its life. This is probably part of the problem - there is a tool you can run (check this vid, link for  WDIDDLE3 also in comments - &lt;a href=&#34;http://www.youtube.com/watch?v=J2eYyRI_F98&#34;&gt;http://www.youtube.com/watch?v=J2eYyRI_F98&lt;/a&gt;) which disables the intellipark feature of the green drive. I never disabled the park timeout before this drive died (which defaults to 8 seconds!) &amp;ndash; note: i have disabled it completely on my other green drives.&lt;/p&gt;</description>
			</item>
			<item>
				<title>vmware : IDE to SCSI</title>
				<link>https://sigtar.com/2011/04/27/vmware-ide-to-scsi/</link>
				<pubDate>Wed, 27 Apr 2011 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2011/04/27/vmware-ide-to-scsi/</guid>
				<description>&lt;p&gt;I&amp;rsquo;ve found that vmware converter (this may be fixed in newer verions) creates vmware guests with an IDE controller. There can be performance issues if you choose to remain with this particular controller&amp;hellip; Best bet is to change it to one of the various vmware SCSI controllers&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;Depending on which windows operating system you are running depends on which controller you use&amp;hellip;.  &lt;a href=&#34;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1006621&#34;&gt;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=1006621&lt;/a&gt;&lt;/p&gt;&#xA;&lt;table&gt;&#xA;&#x9;&lt;thead&gt;&#xA;&#x9;&#x9;&#x9;&lt;tr&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;th&gt;&lt;strong&gt;Guest Operating System&lt;/strong&gt;&lt;/th&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;th&gt;&lt;strong&gt;Adapter Type&lt;/strong&gt;&lt;/th&gt;&#xA;&#x9;&#x9;&#x9;&lt;/tr&gt;&#xA;&#x9;&lt;/thead&gt;&#xA;&#x9;&lt;tbody&gt;&#xA;&#x9;&#x9;&#x9;&lt;tr&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;td&gt;Windows 2003, 2008, Vista&lt;/td&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;td&gt;lsilogic&lt;/td&gt;&#xA;&#x9;&#x9;&#x9;&lt;/tr&gt;&#xA;&#x9;&#x9;&#x9;&lt;tr&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;td&gt;Windows NT, 2000, XP&lt;/td&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;td&gt;buslogic&lt;/td&gt;&#xA;&#x9;&#x9;&#x9;&lt;/tr&gt;&#xA;&#x9;&#x9;&#x9;&lt;tr&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;td&gt;Linux&lt;/td&gt;&#xA;&#x9;&#x9;&#x9;&#x9;&#x9;&lt;td&gt;lsilogic&lt;/td&gt;&#xA;&#x9;&#x9;&#x9;&lt;/tr&gt;&#xA;&#x9;&lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;p&gt; &lt;/p&gt;</description>
			</item>
			<item>
				<title>vmware - measuring iscsi write performance</title>
				<link>https://sigtar.com/2010/05/07/vmware-measuring-iscsi-write-performance/</link>
				<pubDate>Fri, 07 May 2010 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2010/05/07/vmware-measuring-iscsi-write-performance/</guid>
				<description>&lt;p&gt;I picked this trick up off vmware support. If you&amp;rsquo;ve got your iscsi all setup you can drop to the shell (either ssh or console) and do this to measure your average write throughput.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;time vmkfstools -c 10G /vmfs/volumes/san_vmfs/my_vm/fat_disk.vmdk -d eagerzeroedthick&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Try larger a larger disk if this is too quick (free space permitting)&lt;/p&gt;&#xA;&lt;p&gt;Essentially this will initiate the host to create a fat disk in the location above. You will then get a time recorded on how long it takes to execute this command. Then you can use your maths skill to work out the transfer rate&amp;hellip;&lt;/p&gt;</description>
			</item>
			<item>
				<title>zfs - checking your zpool throughput</title>
				<link>https://sigtar.com/2009/02/18/zfs-checking-your-zpool-throughput/</link>
				<pubDate>Wed, 18 Feb 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/02/18/zfs-checking-your-zpool-throughput/</guid>
				<description>&lt;p&gt;This is quite a good diagnostic for checking your disk throughput. Try copying data to and from your zpool while your running this command on the host&amp;hellip;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;zpool iostat -v unprotected 2&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;capacity     operations    bandwidth&#xA;pool         used  avail   read  write   read  write&#xA;----------  -----  -----  -----  -----  -----  -----&#xA;unprotected  1.39T   668G     18      7  1.35M   161K&#xA;c7d0       696G   403M      1      2  55.1K  21.3K&#xA;c9d0       584G   112G      8      2   631K  69.3K&#xA;c7d1       141G   555G      8      2   697K  70.0K&#xA;----------  -----  -----  -----  -----  -----  -----&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The above command will keep displaying the above output every 2 seconds (average during that time). I&amp;rsquo;ve used it a few times to ensure that all disks are being used (in write operations) where needed. Of course read op&amp;rsquo;s may not be typically across all disks as it will depend where the data is&amp;hellip;&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
