Roger C

Members
  • Posts

    32
  • Joined

  • Last visited

Posts posted by Roger C

  1. I currently have 4 super micro 5 in 3's and I was just wondering if they would fit in an antec 1200? The motherboard in using is a super micro X9SCM-F-O. I did a quick search and get mixed answers as to if they will hit the motherboard.

     

    Thanks

  2. Hello.  Woke up this morning to find Unraid doing a parity check. It doesn't show any errors that I see but its completing it at less then 1MB/sec with over a month to complete it. My hardware is as follows

     

    MB : Supermicro X9SCM-F

    HDD : 6 WD 2 TB green drives

    1 AOC-SASLP-MV8

    Unraid 4.7

     

    I have 4 HDD connected to the MB sata 2 ports and the other 2 on the AOC-SASLP-MV8

    Can someone please have a look at my syslog to see if anything stands out as to what could be causing this.

    I did noticed in unmenu there were a couple lines that were red

    Sep  3 08:51:24 Tower kernel: irq 16: nobody cared (try booting with the "irqpoll" option) (Errors)

    Sep  3 08:51:24 Tower kernel: Pid: 0, comm: swapper Not tainted 2.6.32.9-unRAID #8 (Errors)

    Sep  3 08:51:24 Tower kernel: Call Trace: (Errors)

    Sep  3 08:51:24 Tower kernel:  [<c10451cf>] __report_bad_irq+0x2e/0x6f (Errors)

    Sep  3 08:51:24 Tower kernel:  [<c1045305>] note_interrupt+0xf5/0x13c (Errors)

    Sep  3 08:51:24 Tower kernel:  [<c1045a14>] handle_fasteoi_irq+0x5f/0x9d (Errors)

    Sep  3 08:51:24 Tower kernel:  [<c1004a82>] handle_irq+0x1a/0x24 (Errors)

    Sep  3 08:51:24 Tower kernel:  [<c1004285>] do_IRQ+0x40/0x96 (Errors)

    Sep  3 08:51:24 Tower kernel:  [<c1002f29>] common_interrupt+0x29/0x30 (Errors)

    Sep  3 08:51:24 Tower kernel:  [<c116d019>] ? acpi_idle_enter_bm+0x216/0x23f (Errors)

    Sep  3 08:51:24 Tower kernel:  [<c12108e8>] cpuidle_idle_call+0x63/0x9b (Errors)

    Sep  3 08:51:24 Tower kernel:  [<c1001a14>] cpu_idle+0x3a/0x4e (Errors)

    Sep  3 08:51:24 Tower kernel:  [<c128a8bf>] rest_init+0x53/0x55 (Errors)

    Sep  3 08:51:24 Tower kernel:  [<c13f580c>] start_kernel+0x27b/0x280 (Errors)

    Sep  3 08:51:24 Tower kernel:  [<c13f5091>] i386_start_kernel+0x91/0x96 (Errors)

     

    But I have no idea what these mean.

    Thanks for the help.

    syslog.txt

  3. I think your right the computer was off all day so it was cool. It seems as its doing the parity check now the southbridge is getting hot as hell and it's slowing down. Im even noticing when I refresh the web GUI its taking a lot longer to reload it. Im also seeing big speed changes when I push on the motherboard which makes me think the board is toast. I have an XFX Nforce 680i LT laying around. Does anyone know if that board works with Unraid before I rip everything all apart?

     

    Thanks

  4. Figured out what the problem was. The case and hot swap rack I have puts the drives on there side. I was going to try a new motherboard to see if that would fix it and when I turned the case on its side I figured I would try one more time and was surprised to see 63,563 KB/s. As soon as I turn the case back up it drops back to 8500 KB/s. Guess these green WD drives dont like being on there side.

  5. Im having a problem with my new unraid build. I have 6 WD green drives that pre cleared fine with 4k alignment. When I setup my array parity sync took 3 days to complete at an average speed of 8500 KB/s which i thought was rather slow. After finishing parity sync I noticed one drive had smart errors for raw read errors so i took the drive back and got another one and put it in. The array is now rebuilding but im still sitting around 8500 KB/s for 2 days now. Does anyone know why it might be going so slow? This is driving my crazy. My specs are as follows

     

    M/B:  Gigabyte GA-G41M-ES2L

    CPU: Core 2 Duo 2.66

    2 GB Ram

    6 WD Green EARS

    Supermicro AOC-SASLP-MV8 with 2 drives on it

    Unraid 4.7

     

    Im at work right now so I can't post my syslog but can do that as soon as I get home.

     

    Thanks