chetebrown

Members
  • Posts

    9
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

chetebrown's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Finally got my setup completed running beta 8c on my ESXi box with vmdirectpath on a BR10i and the Plop VM. It's running great, spindown and temperature are flawless as mentioned before me and it's been running like a dream. Thank you all in the thread for your inputs, comments and being the innovators among the innovators who tested the hardware first ! I was curious as to if anyone had their setup running on a UPS and who they had it done. I've been looking and so far it seems the most common implementation is using an APC UPC with parachute and having it summon a batch file or script that would send the kill signal to the VM's and then ESXi. Anyone else running something like this ?
  2. I've decided to take the plunge and try consolidating my physical unraid to ESXi after the reports of working spindown in the latest beta with the br10i. I did see some posts of returns from eBay vendors so I was looking for recommendations on where to get one reliable and relatively affordable br10i.
  3. Good to know, will probably run sun tests late next week !
  4. I'm just about ready to get started building my new esxi box, just waiting for the supermicro X8DTI-F mobo to get here (hopefully Monday), so i've re-read the whole thread, but it's still unclear to me.... I see Zeron and Drealit posting that they got direct hardware passthrough / vmdirectpath up and running on their SATA adapter with esxi 4.1 (and 4.1U1 in some instance), but is there confirmation that temperature display and spindown are working properly ? I got confused because the other thread about the Br10i support seemed to point that was still an issue....
  5. Everything seemed ok with jason's config but it seems the dependencies package should read installpkg /boot/custom/SABnzbdDependencies-2.0-i486-unRAID.tgz
  6. In my case I've noticed that hdparm -y does end up working when manually triggered via console (although it errors out): # hdparm -C /dev/sdc issuing standby command SG_IO: bad/missing ATA_16 sense data:: 70 00 00 00 00 00 00 18 00 00 00 00 0 00 00 00 00 09 0c 00 00 00 00 00 00 00 00 00 00 40 50 SG_IO: bad/missing ATA_16 sense data:: 70 00 00 00 00 00 00 18 00 00 00 00 0 00 00 00 00 09 0c 00 00 00 00 00 00 00 00 00 00 40 50 HDIO_DRIVE_CMD(standby) failed: Input/output error PRIOR TO COOL DOWN: # smartctl -A /dev/sda | grep 194 ; smartctl -A /dev/sdbrep 194; smartctl -A /dev/sdc | grep 194 194 Temperature_Celsius 0x0022 112 107 000 Old_age Always 38 194 Temperature_Celsius 0x0022 109 105 000 Old_age Always 41 194 Temperature_Celsius 0x0022 108 104 000 Old_age Always 39 AFTER COOL DOWN: # smartctl -A /dev/sda | grep 194 ; smartctl -A /dev/sdb | grep 194; smartctl -A /dev/sdc | grep 194 194 Temperature_Celsius 0x0022 120 107 000 Old_age Always - 23 194 Temperature_Celsius 0x0022 118 105 000 Old_age Always - 22 194 Temperature_Celsius 0x0022 116 104 000 Old_age Always - 22 hdparm -S however is still yielding no results... So I'm currently looking for a way to have something else monitor drive idle time and then input the commands to spin down my drives.
  7. I can speak to the drive with the smartctl commands from unraid and it does give out the temperature readings (their all around 40C). Been poking around the sagetv forum and it seems I'm not the only one coming up with that hurdle.
  8. I had just started playing around with Unraid last week-end with the free 3 server license to see if I liked it, and I was very pleased except at the idea of having to sacrifice a box to unraid alone or having to resort to getting it setup on dev environment with VMware server.... Needless to say, when I saw this thread I was jumping around as this is exactly what I was looking for. I have ESXi 4.1 up and running just fine thanks to Bryanr's greatly detailed setup and I also have my unraid vm working just fine to. Here is my setup: ASUS P5K Deluxe 6 GB RAM 2 * 1 TB WD caviar black 1 * 500 GB WD (500AKS series) 1 * 250 GB WD (this one is the one that is being used as the data store) Initial parity sync was at ~58000K I was wondering if anybody else has come across what I am seeing: the unraid console does not display the Hard Drive temperatures, and although they are marked as "spinned down" I have my doubts that they are and was wondering how to check that. (the doubt is based on the physical heat I feel the drives emiting, as well as the fact I don't hear them spin up or down when I request it via the console). Initially I had my SATA adapter in the BIOS set as IDE rather than AHCI, and the drive temperature was showing up as "*", when I changed it to AHCI the drive temperature now shows up as "0 C". I was under the impression that via pass through the drives would be communicating directly with the VM. I've been looking around to see if I can get does details directly from the vSphere console but it seems to only give me data on read/write outputs and other measures that aren't linked to the temperature or the current drive state (spinned down or not). Any thoughts ?