gvers

Members
  • Posts

    38
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

gvers's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Upgraded 6.7.2 - 6.8.2 no issues all VM's start fine
  2. @jonp @limetech yet another RFS cpu stall issue to add to the growing list. By RFS I take it you mean ReiserFS. That's interesting because all my drives are XFS. I have added a system log and wanted to add it does not happen on B14a.
  3. Just tried a parity check on this beta and it was going very slow. The system log is filled with these Feb 26 21:25:07 Tower kernel: mdcmd (61): check CORRECT Feb 26 21:25:07 Tower kernel: md: recovery thread woken up ... Feb 26 21:25:07 Tower kernel: md: recovery thread checking parity... Feb 26 21:25:07 Tower kernel: md: using 1536k window, over a total of 2930266532 blocks. Feb 26 21:26:01 Tower sSMTP[11098]: Creating SSL connection to host Feb 26 21:26:02 Tower sSMTP[11098]: SSL connection using RC4-SHA Feb 26 21:26:03 Tower sSMTP[11098]: Sent mail for ####### (221 know-smtprelay-4-imp bizsmtp closing connection) uid=0 username=root outbytes=746 Feb 26 21:26:09 Tower kernel: INFO: rcu_sched self-detected stall on CPU { 2} (t=6001 jiffies g=10526 c=10525 q=90297) Feb 26 21:26:09 Tower kernel: Task dump for CPU 2: Feb 26 21:26:09 Tower kernel: unraidd R running task 0 3155 2 0x00000008 Feb 26 21:26:09 Tower kernel: 0000000000000000 ffff88030fc83da8 ffffffff8105e0b5 0000000000000002 Feb 26 21:26:09 Tower kernel: 0000000000000002 ffff88030fc83dc8 ffffffff81060780 0000000000000004 Feb 26 21:26:09 Tower kernel: ffffffff81834400 ffff88030fc83df8 ffffffff8107845f ffffffff81834400 Feb 26 21:26:09 Tower kernel: Call Trace: Feb 26 21:26:09 Tower kernel: [] sched_show_task+0xbe/0xc3 Feb 26 21:26:09 Tower kernel: [] dump_cpu_task+0x35/0x39 Feb 26 21:26:09 Tower kernel: [] rcu_dump_cpu_stacks+0x6a/0x8c Feb 26 21:26:09 Tower kernel: [] rcu_check_callbacks+0x1db/0x4f9 Feb 26 21:26:09 Tower kernel: [] ? tick_sched_handle+0x34/0x34 Feb 26 21:26:09 Tower kernel: [] update_process_times+0x3a/0x64 Feb 26 21:26:09 Tower kernel: [] tick_sched_handle+0x32/0x34 Feb 26 21:26:09 Tower kernel: [] tick_sched_timer+0x37/0x61 Feb 26 21:26:09 Tower kernel: [] __run_hrtimer.isra.29+0x57/0xb0 Feb 26 21:26:09 Tower kernel: [] hrtimer_interrupt+0xd9/0x1c0 Feb 26 21:26:09 Tower kernel: [] local_apic_timer_interrupt+0x50/0x54 Feb 26 21:26:09 Tower kernel: [] smp_apic_timer_interrupt+0x3c/0x4e Feb 26 21:26:09 Tower kernel: [] apic_timer_interrupt+0x6d/0x80 Feb 26 21:26:09 Tower kernel: [] ? xor_sse_5_pf64+0xc3/0x3c0 Feb 26 21:26:09 Tower kernel: [] ? xor_sse_5_pf64+0x57/0x3c0 Feb 26 21:26:09 Tower kernel: [] xor_blocks+0x49/0x4b Feb 26 21:26:09 Tower kernel: [] handle_stripe+0xd84/0x120f [md_mod] Feb 26 21:26:09 Tower kernel: [] unraidd+0xda/0x194 [md_mod] Feb 26 21:26:09 Tower kernel: [] md_thread+0xd2/0xe8 [md_mod] Feb 26 21:26:09 Tower kernel: [] ? __wake_up_sync+0xd/0xd Feb 26 21:26:09 Tower kernel: [] ? 0xffffffffa00c9000 Feb 26 21:26:09 Tower kernel: [] kthread+0xd6/0xde Feb 26 21:26:09 Tower kernel: [] ? kthread_create_on_node+0x172/0x172 Feb 26 21:26:09 Tower kernel: [] ret_from_fork+0x7c/0xb0 Feb 26 21:26:09 Tower kernel: [] ? kthread_create_on_node+0x172/0x172 I have added a system log and wanted to add it does not happen on B14a. All my drives are XFS. syslog.zip
  4. Mine show the same but in Windows it says the adaptor speed is 10G so it may just be an error displaying the setting. I tried speedtest.net and got 60Mbps which is what I would expect. I also tried changing the speed from 10G to 1G and got the same results.
  5. I had that. Delete the downloaded GUI from the plugin folder.
  6. Thanks Tom upgraded without any issues - using stock web gui 18 disk array
  7. gvers

    Status

    Thanks for the update fingers crossed
  8. Just like to say thanks for the update. Looking forward to 5 finals.
  9. Just a quick update. Upgraded both cards to P14 and copied a couple of large file to the array. All seem good at this point and a bit faster the the previous RC's. Aug 1 19:37:32 Tower kernel: mpt2sas0: LSISAS2008: FWVersion(14.00.00.00), ChipRevision(0x03), BiosVersion(07.27.00.00) (Drive related) I can post a syslog if anyone want's it.
  10. After reading this thread I though I'd give this release a try but thing did not go well. 2 x M1015's flashed to IT mode Jul 31 21:41:01 Tower kernel: Pid: 912, comm: scsi_eh_10 Tainted: G O 3.4.4-unRAID #2 Gigabyte Technology Co., Ltd. GA-890GPA-UD3H/GA-890GPA-UD3H Jul 31 21:41:01 Tower kernel: EIP: 0060:[<c103ad1e>] EFLAGS: 00010093 CPU: 0 Jul 31 21:41:01 Tower kernel: EIP is at __wake_up_common+0x17/0x5c Jul 31 21:41:01 Tower kernel: EAX: f2fe0564 EBX: fffffff4 ECX: 00000001 EDX: 00000003 Jul 31 21:41:01 Tower kernel: ESI: 00000246 EDI: 00000003 EBP: f2f75eb4 ESP: f2f75e9c Jul 31 21:41:01 Tower kernel: DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Jul 31 21:41:01 Tower kernel: CR0: 8005003b CR2: 00000000 CR3: 361a5000 CR4: 000007f0 Jul 31 21:41:01 Tower kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 Jul 31 21:41:01 Tower kernel: DR6: ffff0ff0 DR7: 00000400 Jul 31 21:41:01 Tower kernel: Process scsi_eh_10 (pid: 912, ti=f2f74000 task=f3541e60 task.ti=f2f74000) Jul 31 21:41:01 Tower kernel: Stack: Jul 31 21:41:01 Tower kernel: 00000246 00000282 00000001 f2fe0560 00000246 f2fe055c f2f75ed0 c103b2ca Jul 31 21:41:01 Tower kernel: 00000000 00000000 f2fe03b4 00000002 00000001 f2f75ee0 f853c379 f2fe03b4 Jul 31 21:41:01 Tower kernel: 00000000 f2f75efc f853de89 f2fe04c0 f2fe04d4 f2fe03b4 00002002 f2fe03b4 Jul 31 21:41:01 Tower kernel: Call Trace: Jul 31 21:41:01 Tower kernel: [<c103b2ca>] complete+0x2b/0x3e Jul 31 21:41:01 Tower kernel: [<f853c379>] _base_reset_handler+0x11a/0x178 [mpt2sas] Jul 31 21:41:01 Tower kernel: [<f853de89>] mpt2sas_base_hard_reset_handler+0x12d/0x1e9 [mpt2sas] Jul 31 21:41:01 Tower kernel: [<f8546f71>] mpt2sas_scsih_issue_tm+0xd8/0x445 [mpt2sas] Jul 31 21:41:01 Tower kernel: [<f85428a3>] ? _scsih_tm_display_info+0x13f/0x147 [mpt2sas] Jul 31 21:41:01 Tower kernel: [<f85476b0>] _scsih_abort+0x120/0x15f [mpt2sas] Jul 31 21:41:01 Tower kernel: [<c122f125>] scsi_unjam_host+0xab/0x14e Jul 31 21:41:01 Tower kernel: [<c122f252>] scsi_error_handler+0x8a/0xdc Jul 31 21:41:01 Tower kernel: [<c122f1c8>] ? scsi_unjam_host+0x14e/0x14e Jul 31 21:41:01 Tower kernel: [<c1035ba4>] kthread+0x67/0x6c Jul 31 21:41:01 Tower kernel: [<c1035b3d>] ? kthread_freezable_should_stop+0x49/0x49 Jul 31 21:41:01 Tower kernel: [<c131fd76>] kernel_thread_helper+0x6/0xd Jul 31 21:41:01 Tower kernel: Code: db 01 42 30 11 5a 34 eb 08 31 db 01 42 28 11 5a 2c 5b 5d c3 55 89 e5 57 89 d7 56 53 83 ec 0c 89 4d f0 8b 58 04 83 c0 04 83 eb 0c <8b> 73 0c 89 45 e8 83 ee 0c eb 2a 8b 03 89 fa ff 75 0c 8b 4d 08 Jul 31 21:41:01 Tower kernel: EIP: [<c103ad1e>] __wake_up_common+0x17/0x5c SS:ESP 0068:f2f75e9c Jul 31 21:41:01 Tower kernel: CR2: 0000000000000000 Jul 31 21:41:01 Tower kernel: ---[ end trace 17137aaa2e86c242 ]--- syslog-2012-07-31.txt
  11. Any reason why you are on B14. RC5 had fixes for permissions.
  12. I got this error today trying to delete a directory. Once the drive had spun up it deleted on my next attempt. I also have another issue running RC3 but had it with b12a as well. When mounting and ISO with VCD via a user share I get and error that it is unable to mount. I have to use a disk share to mount the ISO. This happens on all of my PC's. http://lime-technology.com/forum/index.php?topic=16870.msg153854#msg153854 http://lime-technology.com/forum/index.php?topic=14664.msg138449#msg138449 Appart from that it seems to be working fine on my 2 M1015's flashed to IT mode.
  13. I had similar problems with my GA-890GPA-UD3H in ACHI mode and the AOC SASLP. In the end I flashed mine up to .21 and installed it in the second PCIe slot. I Moved my IBM M1015 (flashed to IT mode) to the first PCIe slot. With this configuration I have ACHI on and the machine boots.
  14. Lots of people get these when preclearing on the AOC-SASLP-MV8 card. It's nothing to worry about and should preclear fine.