mikejp

Members
  • Posts

    234
  • Joined

  • Last visited

Everything posted by mikejp

  1. Good choice on the Seasonic!! I don't use anything but Seasonic anymore...never had one fail... I don't own the X760, but.... My modular ones, (2) X650s & (2) X750s, all have 5 outputs for peripheral connections. None of my cables have over 3 SATA connectors... sooo... 15. Hope that helps... YMMV!
  2. NICE !!! Check these out... http://www.amazon.com/gp/product/B00632FL8A/ref=ox_sc_act_title_2?ie=UTF8&smid=A23NVCSO4PYH3S $.24 more than the ones you linked to... & an extra 200 RPMs to boot
  3. Tom... Sorry for that last post... the system still had the powerdown-1.02, & a s3 sleep script running I didn't loose the web interface, or have to force a shut down this time... The Call Trace remains... Started a NOCORRECT parity check. Both of my systems exhibit the same behavior. Both are running w/no addons. (now) Configs for both systems are in my sig. Syslogs attached. syslog-LOGO.zip syslog-THOR.zip
  4. Seem to have a problem... The system was running great until this showed up... Quote Aug 6 23:46:37 THOR kernel: Call Trace: Aug 6 23:46:37 THOR kernel: [<c1055180>] print_cpu_stall+0x59/0xd1 Aug 6 23:46:37 THOR kernel: [<c1055233>] __rcu_pending+0x3b/0x125 Aug 6 23:46:37 THOR kernel: [<c1055393>] rcu_check_callbacks+0x76/0xa1 Aug 6 23:46:37 THOR kernel: [<c102b11b>] update_process_times+0x2d/0x58 Aug 6 23:46:37 THOR kernel: [<c1048dfe>] tick_periodic+0x63/0x65 Aug 6 23:46:37 THOR kernel: [<c1048e19>] tick_handle_periodic+0x19/0x6c Aug 6 23:46:37 THOR kernel: [<c10173f2>] smp_apic_timer_interrupt+0x67/0x7a Aug 6 23:46:37 THOR kernel: [<c131f3fa>] apic_timer_interrupt+0x2a/0x30 Aug 6 23:46:37 THOR kernel: [<f853a6e0>] ? xor_sse_4+0x262/0x338 [xor] Aug 6 23:46:37 THOR kernel: [<f853b8cd>] xor_blocks+0x55/0x71 [xor] Aug 6 23:46:37 THOR kernel: [<f853b8cd>] ? xor_blocks+0x55/0x71 [xor] Aug 6 23:46:37 THOR kernel: [<f8618951>] check_parity+0xb3/0xc3 [md_mod] Aug 6 23:46:37 THOR kernel: [<f86194b5>] handle_stripe+0xa7d/0xcfb [md_mod] Aug 6 23:46:37 THOR kernel: [<f86197aa>] unraidd+0x77/0xb8 [md_mod] Aug 6 23:46:37 THOR kernel: [<f8616925>] md_thread+0xcc/0xe3 [md_mod] Aug 6 23:46:37 THOR kernel: [<c1035e9c>] ? wake_up_bit+0x5b/0x5b Aug 6 23:46:37 THOR kernel: [<f8616859>] ? import_device+0x147/0x147 [md_mod] Aug 6 23:46:37 THOR kernel: [<c1035ba4>] kthread+0x67/0x6c Aug 6 23:46:37 THOR kernel: [<c1035b3d>] ? kthread_freezable_should_stop+0x49/0x49 Aug 6 23:46:37 THOR kernel: [<c131fd76>] kernel_thread_helper+0x6/0xd Aug 6 23:49:37 THOR kernel: INFO: rcu_sched self-detected stall on CPU { 2} (t=96015 jiffies) Aug 6 23:49:37 THOR kernel: Pid: 2389, comm: unraidd Not tainted 3.4.4-unRAID #2 Aug 6 23:49:37 THOR kernel: Call Trace: Aug 6 23:49:37 THOR kernel: [<c1055180>] print_cpu_stall+0x59/0xd1 Aug 6 23:49:37 THOR kernel: [<c1055233>] __rcu_pending+0x3b/0x125 Aug 6 23:49:37 THOR kernel: [<c1055393>] rcu_check_callbacks+0x76/0xa1 Aug 6 23:49:37 THOR kernel: [<c102b11b>] update_process_times+0x2d/0x58 Aug 6 23:49:37 THOR kernel: [<c1048dfe>] tick_periodic+0x63/0x65 Aug 6 23:49:37 THOR kernel: [<c1048e19>] tick_handle_periodic+0x19/0x6c Aug 6 23:49:37 THOR kernel: [<c10173f2>] smp_apic_timer_interrupt+0x67/0x7a Aug 6 23:49:37 THOR kernel: [<c131f3fa>] apic_timer_interrupt+0x2a/0x30 Aug 6 23:49:37 THOR kernel: [<f853a903>] ? xor_sse_5+0x14d/0x3d8 [xor] Aug 6 23:49:37 THOR kernel: [<c10161a3>] ? native_smp_send_reschedule+0x3f/0x41 Aug 6 23:49:37 THOR kernel: [<f853b8de>] xor_blocks+0x66/0x71 [xor] Aug 6 23:49:37 THOR kernel: [<f853b8de>] ? xor_blocks+0x66/0x71 [xor] Aug 6 23:49:37 THOR kernel: [<f861892b>] check_parity+0x8d/0xc3 [md_mod] Aug 6 23:49:37 THOR kernel: [<f86194b5>] handle_stripe+0xa7d/0xcfb [md_mod] Aug 6 23:49:37 THOR kernel: [<f86197aa>] unraidd+0x77/0xb8 [md_mod] Aug 6 23:49:37 THOR kernel: [<f8616925>] md_thread+0xcc/0xe3 [md_mod] Aug 6 23:49:37 THOR kernel: [<c1035e9c>] ? wake_up_bit+0x5b/0x5b Aug 6 23:49:37 THOR kernel: [<f8616859>] ? import_device+0x147/0x147 [md_mod] Aug 6 23:49:37 THOR kernel: [<c1035ba4>] kthread+0x67/0x6c Aug 6 23:49:37 THOR kernel: [<c1035b3d>] ? kthread_freezable_should_stop+0x49/0x49 Aug 6 23:49:37 THOR kernel: [<c131fd76>] kernel_thread_helper+0x6/0xd Aug 6 23:49:46 THOR in.telnetd[31505]: connect from 192.168.1.2 (192.168.1.2) Aug 6 23:49:52 THOR login[31506]: ROOT LOGIN on '/dev/pts/1' from '192.168.1.2' Aug 6 23:50:36 THOR in.telnetd[31521]: connect from 192.168.1.2 (192.168.1.2) Aug 6 23:50:42 THOR login[31522]: ROOT LOGIN on '/dev/pts/2' from '192.168.1.2' Aug 6 23:52:37 THOR kernel: INFO: rcu_sched self-detected stall on CPU { 2} (t=114018 jiffies) Aug 6 23:52:37 THOR kernel: Pid: 2389, comm: unraidd Not tainted 3.4.4-unRAID #2 Aug 6 23:52:37 THOR kernel: Call Trace: Aug 6 23:52:37 THOR kernel: [<c1055180>] print_cpu_stall+0x59/0xd1 Aug 6 23:52:37 THOR kernel: [<c1055233>] __rcu_pending+0x3b/0x125 Aug 6 23:52:37 THOR kernel: [<c1055393>] rcu_check_callbacks+0x76/0xa1 Aug 6 23:52:37 THOR kernel: [<c102b11b>] update_process_times+0x2d/0x58 Aug 6 23:52:37 THOR kernel: [<c1048dfe>] tick_periodic+0x63/0x65 Aug 6 23:52:37 THOR kernel: [<c1048e19>] tick_handle_periodic+0x19/0x6c Aug 6 23:52:37 THOR kernel: [<c10173f2>] smp_apic_timer_interrupt+0x67/0x7a Aug 6 23:52:37 THOR kernel: [<c131f3fa>] apic_timer_interrupt+0x2a/0x30 Aug 6 23:52:37 THOR kernel: [<c119103f>] ? blk_update_request+0x112/0x2e4 Aug 6 23:52:37 THOR kernel: [<c119121f>] blk_update_bidi_request+0xe/0x4f Aug 6 23:52:37 THOR kernel: [<c1191ad5>] blk_end_bidi_request+0x18/0x50 Aug 6 23:52:37 THOR kernel: [<c1191b41>] blk_end_request+0xa/0xc Aug 6 23:52:37 THOR kernel: [<c1230818>] scsi_end_request+0x1f/0x70 Aug 6 23:52:37 THOR kernel: [<c1230b7e>] scsi_io_completion+0x1a9/0x3e0 Aug 6 23:52:37 THOR kernel: [<c123091c>] ? scsi_device_unbusy+0x7c/0x82 Aug 6 23:52:37 THOR kernel: [<c122bca2>] scsi_finish_command+0x97/0x9d Aug 6 23:52:37 THOR kernel: [<c1230e7e>] scsi_softirq_done+0xba/0xc2 Aug 6 23:52:37 THOR kernel: [<c1195e26>] blk_done_softirq+0x4a/0x57 Aug 6 23:52:37 THOR kernel: [<c1027046>] __do_softirq+0x6b/0xe5 Aug 6 23:52:37 THOR kernel: [<c1026fdb>] ? irq_enter+0x41/0x41 Aug 6 23:52:37 THOR kernel: <IRQ> [<c1026e8f>] ? irq_exit+0x32/0x58 Aug 6 23:52:37 THOR kernel: [<c1003506>] ? do_IRQ+0x7c/0x90 Aug 6 23:52:37 THOR kernel: [<c131fd69>] ? common_interrupt+0x29/0x30 Aug 6 23:52:37 THOR kernel: [<c11a65bc>] ? memcmp+0x15/0x25 Aug 6 23:52:37 THOR kernel: [<f86194d9>] ? handle_stripe+0xaa1/0xcfb [md_mod] Aug 6 23:52:37 THOR kernel: [<f86197aa>] ? unraidd+0x77/0xb8 [md_mod] Aug 6 23:52:37 THOR kernel: [<f8616925>] ? md_thread+0xcc/0xe3 [md_mod] Aug 6 23:52:37 THOR kernel: [<c1035e9c>] ? wake_up_bit+0x5b/0x5b Aug 6 23:52:37 THOR kernel: [<f8616859>] ? import_device+0x147/0x147 [md_mod] Aug 6 23:52:37 THOR kernel: [<c1035ba4>] ? kthread+0x67/0x6c Aug 6 23:52:37 THOR kernel: [<c1035b3d>] ? kthread_freezable_should_stop+0x49/0x49 Aug 6 23:52:37 THOR kernel: [<c131fd76>] ? kernel_thread_helper+0x6/0xd I started a parity check, & a few minutes later went to refresh the web GUI... The GUI would no longer come up... I had access via putty & the terminal though. Tried everything I could find to get the system to shut down... no go I captured the syslog, changed the 2 files back to rc5 & hard reset it... Running parity now...showed 128 errors right off... 95% done now with no further errors. syslog.zip
  5. Dimensions are listed as mm: 482.6 x 673.1 x 177.8 inches: 19 x 26.5 x 7 Can anyone that has received their server verify this, please? That is exactly what my AMD setup measures... Same case... different motherboard http://www.ebay.com/itm/Custom-Dual-Core-AMD-Opteron-2-0GHz-8GB-DDR2-160GB-IDE-Server-/170762230144?pt=LH_DefaultDomain_0&hash=item27c238d980
  6. Check out this thread... same thing with AMD instead of Intel http://lime-technology.com/forum/index.php?topic=18610.0
  7. I get the same thing happening every time I load Simple Features... If I don't load SF... no such entries...
  8. Got them yesterday... THX Today I flashed them (without loading the bios) to LSI w/firmware 13... Tonight they are installed & running great
  9. You're right... my bad ... these are for the other server
  10. http://www.ebay.com/itm/230623850977?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649
  11. All issues are fixed in RC3....3tb support, disks spin up and down properly, hdd temps are reported properly......my cards are flashed to LSI9211-8i P13 FW. +1
  12. http://www.wiredzone.com/Supermicro-AOC-SAS2LP-MV8-8-port-SAS-SATA-Controller-Card~10021085~0.htm
  13. I hope that we get a solid, stable, release - how ever many betas or RCs it takes. We just need faults ironed out - even if that simply means published work-arounds ... more delays are being caused by feature-creep! +1
  14. RC2 seems to be working great... for me anyway Over a SMB gigabit LAN, Intel NICS , Windows7 (reading & writing to a SSD), moving Blu-Ray MKVs, I get read from share ~80 MB/S write to share (no cache drive) ~40 MB/S write to share (w/cache drive) ~73MB/S Parity Check(correct) run through at 88.3 MB/S The results are from my backup/test server using 13) 1.5 WD Blacks on 2) flashed M1015s... ;D No errors in the system log after multiple spin up/downs, & numerous read/writes. Thanks Tom !!!
  15. According to the webui. the drive doesn't spin down... Syslog attached. syslog.txt
  16. Here's a sample output from the terminal session: When I restarted the array, the 3 drives I ran those commands on, came up unformatted showing 2 errors each. Syslog attached. syslog.zip
  17. Please post a link to the best thread that describes the problem. The post BRiT refers you to above pretty much covers it...
  18. Have to get back to you on a specific thread... What happened is, as soon as the drives spun down, error messages started filling the system log & then a drive red balled. At that point I didn't go any further... I shut the array down, copied my backup to the flash, & rebooted back to 12a... I'll go looking through threads to find some specifics that relate to the problem I'm having.
  19. The Br10i on my test array has the same problems as before... I'm assuming the M1015s won't work either...
  20. 4.7 doesn't support 3TB drives... Beta Support for 3T Drives in 5.0-beta8 or later.
  21. Excuse me, but you sir are ignorant to the situation at hand. What you said is so far from the truth. The troubled hardware people are using makes up the most popular of all SATA controllers. According to the past Gartner reports, LSI ranks No. 1 overall in worldwide host bus RAID controller unit market share. (Reference) You might look at my sig... Besides LOGOPOLIS, I have THOR with a M1015 & a Br10i, & TOWER, with a single M1015. I doubt I'm "ignorant to the situation at hand" Just sayin'...