jimwhite

Members
  • Posts

    597
  • Joined

  • Last visited

Posts posted by jimwhite

  1. I purchased one of these for a new build I'm in the middle of now.  It's going to be an ESXi 4.1 box with a total of 16 drives ( maybe 18?).  Six on the Intel Southbridge, 8 on the onboard LSI 2008, and 2 or 4 on the E-Bay LSI plug in card I'm awaiting delivery on.  My case, a Thermaltake Armour, has 4 3-in-2 Hot Swap cages and one 4-in-3, all from Kingwin.  The case also has an internal mount for 2 more drives which I may or may not use.  The intention is to use 2 drives in raid-0 on the plug-in card as data store for the ESXi layer.  Maybe these will go in the internal mount, allowing use of all 16 front slots for unraid.  Still gelling that config in my mind.  Other specs are few... a Corsair 750 watt supply, 16 Samsung 2tb 204 drives for unraid, and 2 Seagate 7200 rpm 1tb drives for the raid0 datastore, 16 gb of ecc ddr3, Xeon E3-1230  ...

     

    I've been playing with the board quite a bit at the esxi level, learning how to migrate VM's back and forth between host and client, and such.  The board runs great and I'm absolutely thrilled with the ip based KVM functionality... being able to totally power-down the server and the turn it back on from my desktop is the bees-knees...

     

  2. Can someone please help me re-enable the linux r8169 driver into this beta10 release?

     

    I tried copying the .ko across from beta9 but modprobe in beta10 doesn't accept it (I'm guessing because the kernel is now 2.6.39.3).

    I tried downloading r8169 driver source code from Realtek site, but I can't build ('make clean modules') the driver because of an error (the 'build' folder is allegedly not found, even though when I 'ls' that folder it does, in fact exist).

     

    I assume you want to do this because you are having problems with beta10 and the Realtek driver now included.

    yes exactly: http://lime-technology.com/forum/index.php?topic=14158.msg134153#msg134153

    I'm going to get rid of r8168 and restore r8169 in -beta10a.  So much for Realtek being able to support their own NIC's  ::)

     

    When do you think 5.0 will be final?  ;)

     

    when it's done....  :D

     

  3. Things marked as copy once should only be playable the machine that recorded it

    The copy once flag basically means you cannot move it off the machine that it was originally recorded onto.  So you can't record it to your WMC HTPC and then move it onto your unRAID server.  Major suck factor there.  If the file is marked copy freely you can move it to any PC you want - just like any other unencrypted content.

     

    I don't believe this to be true...

     

  4. Any chance this could be used to see / re-format a ReiserFS HDD that I pulled from unRaid and would like to re-purpose for the Windows environment?

    I'm not trying to save any of the data on the drive, I just want to wipe and format as NTFS so that I can use in Windows.

    no need.... just:

    hook the drive up to the windows machine

    go to disk management (right click the [My]Computer icon and pick Manage)

    select the correct drive in the lower graphical window and right click

    delete the existing partition

    create & format a new partition

    done

    :D

     

     

     

  5. why not make a VM of unRaid running on a full-slackware distro?

     

     

    I think the issue with that is the drives aren't exposed to unRAID inside the VM.

    As far as VM of unRAID running on full-slackware distro - my preference for unRAID VM is to keep it as small as possible and just do storage piece and leave other functionality for other VMs running on better suited OS distros such ubuntu, centos, windows and so on.

     

     

    Good Point.  :o

     

  6. http://www.newegg.com/Product/Product.aspx?Item=N82E16822148413

     

    How are these in terms of write speed in unraid vs the 7200 rpm models? I need 3 or 4 of them to replace a huge stack of 500gb 7200rpm drives. If I can save 30 bucks a drive... I'd be happy.

    They will be, at best, 5900/7200ths ( 81% ) of the speed of a write where both the parity and data disk are spinning at 7200 RPM.    If the parity disk is also spinning at 5900 RPM then you'll probably not notice any slower write speed, as it was already limited by the slower spinning parity disk. 

     

    Read speeds are unaffected, so playing movies from your server are unchanged.  Same with parity "checks" as those are read-only operations.

     

     

    This is assuming the same areal density.  The 2 tb drives, I believe, are using higher areal density disks.