prtsmgr

Members
  • Posts

    196
  • Joined

  • Last visited

Posts posted by prtsmgr

  1. Using unRAID Server Plus v5.0-rc8a

    I have Monthly Parity Check setup in unMENU.

    I see forum posts referring to average parity speed and I don't see that reported on my server.

    Am I missing an add-on to report average parity speeds?

     

    When Monthly Parity Check finishes, I see this on the unMENU Main page:

    Array Status

    STARTED, 4 disks in array.    Parity is Valid:.  Last parity check < 1 day ago with no sync errors.

     

    I see this on this on the unRAID Main page:

    Last checked on Mon Oct 1 06:46:51 2012 PDT, finding 0 errors.

     

    I see this in the syslog:

    Oct  1 00:00:01 Tower kernel: mdcmd (49): check NOCORRECT (unRAID engine)

    Oct  1 00:00:01 Tower kernel:  (Routine)

    Oct  1 00:00:01 Tower kernel: md: recovery thread woken up ... (unRAID engine)

    Oct  1 00:00:01 Tower kernel: md: recovery thread checking parity... (unRAID engine)

    Oct  1 00:00:02 Tower kernel: md: using 1536k window, over a total of 2930266532 blocks. (unRAID engine)

    Oct  1 06:46:51 Tower kernel: md: sync done. time=24410sec (unRAID engine)

    Oct  1 06:46:51 Tower kernel: md: recovery thread sync completion status: 0 (unRAID engine)

     

    How can I get something like this:

    Last checked on Mon Oct 1 10:41:25 2012 SGT (today), finding 0 errors.

    * Duration: 9 hours, 41 minutes, 24 seconds. Average speed: 57.3 MB/sec

     

  2. Rockdawg,

     

    Glad to hear you got it working.

    In reference to an earlier part of this thread, has this changed?

    The reason I ask is because my syslog looks the same as you had posted earlier.

    Thanks

     

    I have noticed one difference in the syslogs between straight unRAID and unRAID through ESXi:

     

    Straight unRAID

    Sep  3 09:17:29 Tower kernel: mpt2sas2: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (16608336 kB)
    

     

    unRAID through ESXi

    Sep  2 02:18:43 Tower kernel: mpt2sas2: 32 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (2074648 kB)

     

    Why wouldn't they both be 64 BIT?

  3. Up for sale is a Supermicro X7SPE-HF-D525-O Motherboard with 8GB Kingston Ram.

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

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

     

    This board was in my server for 6 months before I decided to upgrade so that I could try out ESXi.

    I am offering it here for $200 US including US Shipping.

    International buyers need to contact me regarding shipping charges.

    Please send a PM if interested.

     

    Mark

  4. What is the best format for my video content?

     

    There isn't a single definitive answer to this question as it can depend on which Plex client you're using to access your content as well as how you plan on accessing that content (locally on the computer, local across your network, or remotely from outside your network). That said, we can recommend some general guidelines that most people find useful:

     

        MKV and MP4/M4V are popular file formats/containers that both generally work well.

        Video encoded as H.264 is the most broadly compatible, can often take advantage of hardware acceleration, and tends to give small filesizes for the quality you get.

        AAC and AC-3 are popular audio formats to use with video. DTS is also popular if your playback hardware supports it.

        VIDEO_TS (as well as ISO, IMG, dvdmedia, and other "disc image" format) content is generally not recommended as it is not compatible with most Plex clients and usually can't be streamed.

        SRT format subtitles are the best supported. VOBSUB/PSG format subtitles may not work with all clients and particularly with streaming.

  5. this will look crazy but I can't get my VM to auto-start  :'(

     

    I am interested in this as well. I read that auto-start was broken in the 5.0 Update 1

    http://blogs.vmware.com/vsphere/2012/03/free-esxi-hypervisor-auto-start-breaks-with-50-update-1.html

     

    THANK YOU, I may not be crazy! I'm effectively running 5.0 Update 1 (VMware-VMvisor-Installer-5.0.0.update01-623860.x86_64.iso)

     

    Update 1 was released in March, more than 3 months ago... Why isn't this fixed yet? It's kind of ridiculous!?

     

    I can't revert back as explained in the Blog post as I have a 5.0 Update 1 clean install. There's a sketchy workaround in the comments but I would prefer not to mess with that. So I guess that I will have to start all over from scratch with a 5.0 install (VMware-VMvisor-Installer-5.0.0-469512.x86_64.iso)

     

    Should I be careful about anything in doing this? (except for unplugging every drives when re-installing ESXi)

     

    Looking at the Update 1 release notes, I should be fine downgrading; my OSX VM wasn't working anyway..

     

    And then VMware is gonna release Update 2 / a fix in a week haha

     

    You were right, the fix has been released http://blogs.vmware.com/vsphere/2012/07/vsphere-hypervisor-auto-start-bug-fixed.html