Zeron

Community Developer
  • Posts

    175
  • Joined

  • Last visited

Everything posted by Zeron

  1. Yes - the latest version do this. Something is preventing the custom shutdown script from executing.
  2. There is a shutdown script included that cleanly shuts down the array when you press the shutdown guest button. It works on my ESXi 5.0 system, but appears to be ignored under 5.1. I have updated my development system to ESXi 5.1 so hopefully I can find out why the script no longer works.
  3. New version uploaded for 5.0rc8/8a Update to: open_vm_tools-2012.10.14.874563 Work around shutdown error on ESXi 5.1 (You no longer need to add ifup from your go file)
  4. 5rc6-r8168-test has fixed this issue.
  5. Files for 5.0rc6r8168test posted.
  6. It should work if you set the type to VMXNET3 instead of flexible.
  7. Version for 5.0rc4 is posted.
  8. Ths file is on kernel.org, just not linked form the front page yet: http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.0.33.tar.gz
  9. I tried upgrading from beta-6a to 5c3 and get the panic below at boot just as the mpt2sas driver is detecting the drives. It appears that this bug is fixed by a patch on 3.0.33 (see below) Is ther any cahnce of 5.0rc4 using 3.0.33? Panic: BUG: unable to handle kernel NULL pointer dereference at (null) IP: [<c101f8dd>] __wake_up_common+0x17/0x5c *pdpt = 000000000c934001 *pde = 0000000000000000 Oops: 0000 [#1] SMP Modules linked in: e1000 mpt2sas(+) scsi_transport_sas raid_class piix(+) Pid: 833, comm: modprobe Not tainted 3.0.31-unRAID #1 VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform EIP: 0060:[<c101f8dd>] EFLAGS: 00010093 CPU: 0 EIP is at __wake_up_common+0x17/0x5c EAX: dd6c84e8 EBX: fffffff4 ECX: 00000001 EDX: 00000003 ESI: 00000092 EDI: 00000003 EBP: dd40ff4c ESP: dd40ff34 DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Process modprobe (pid: 833, ti=dd40e000 task=cc9014a0 task.ti=d911e000) Stack: c14c9600 dd6d3fa8 00000001 dd6c84e4 00000092 dd6c84e0 dd40ff68 c10202e5 00000000 00000000 dd6c837c d9800020 dd602620 dd40ff78 e0869c9e d9708000 0000000d dd40ffb8 e086a720 19800000 19800000 dd40ffa4 dd6c8390 00000000 Call Trace: [<c10202e5>] complete+0x2b/0x3e [<e0869c9e>] mpt2sas_base_done+0x6e/0x74 [mpt2sas] [<e086a720>] _base_interrupt+0x133/0x2f8 [mpt2sas] [<c104e61b>] handle_irq_event_percpu+0x24/0x100 [<c105038e>] ? irq_set_chip_and_handler_name+0x24/0x24 [<c104e71b>] handle_irq_event+0x24/0x3b [<c105038e>] ? irq_set_chip_and_handler_name+0x24/0x24 [<c105043c>] handle_edge_irq+0xae/0xce <IRQ> [<c1003622>] ? do_IRQ+0x37/0x90 [<c130fa69>] ? common_interrupt+0x29/0x30 [<e086858c>] ? _base_event_notification+0xef/0x1af [mpt2sas] [<e0868b0a>] ? _base_make_ioc_operational+0x2f1/0x36e [mpt2sas] [<e086bb47>] ? mpt2sas_base_attach+0x447/0x558 [mpt2sas] [<e08703a5>] ? _scsih_probe+0x310/0x3fe [mpt2sas] [<c11af52a>] ? local_pci_probe+0x3e/0x81 [<c11afc89>] ? pci_device_probe+0x43/0x66 [<c1207e52>] ? really_probe+0x72/0xed [<c1207ef9>] ? driver_probe_device+0x2c/0x41 [<c1207f51>] ? __driver_attach+0x43/0x5f [<c1207838>] ? bus_for_each_dev+0x3d/0x67 [<c1207d19>] ? driver_attach+0x14/0x16 [<c1207f0e>] ? driver_probe_device+0x41/0x41 [<c12072cb>] ? bus_add_driver+0x9d/0x1cd [<c12083ca>] ? driver_register+0x7c/0xe3 [<c11ff477>] ? misc_register+0x91/0xe6 [<c11afe4e>] ? __pci_register_driver+0x38/0x95 [<e088610c>] ? _scsih_init+0x10c/0x12d [mpt2sas] [<c1001159>] ? do_one_initcall+0x71/0x113 [<e0886000>] ? 0xe0885fff [<c104cae6>] ? sys_init_module+0x61/0x18b [<c130ed05>] ? syscall_call+0x7/0xb Code: 7e 08 01 5a 30 11 72 34 eb 06 01 5a 28 11 72 2c 5b 5e 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 EIP: [<c101f8dd>] __wake_up_common+0x17/0x5c SS:ESP 0068:dd40ff34 CR2: 0000000000000000 ---[ end trace 22b2c2d4edffda35 ]--- Kernel panic - not syncing: Fatal exception in interrupt Pid: 833, comm: modprobe Tainted: G D 3.0.31-unRAID #1 Call Trace: [<c130ce2f>] panic+0x50/0x13a [<c100490a>] oops_end+0x6e/0x7c [<c101b2d9>] no_context+0xac/0xb6 [<c101b3cb>] __bad_area_nosemaphore+0xe8/0xf0 [<c101b582>] ? mm_fault_error+0x129/0x129 [<c101b3e0>] bad_area_nosemaphore+0xd/0x10 [<c101b6d2>] do_page_fault+0x150/0x332 [<c10202ee>] ? complete+0x34/0x3e [<c107ace1>] ? dma_pool_free+0xcd/0xd5 [<c101b582>] ? mm_fault_error+0x129/0x129 [<c130f302>] error_code+0x5a/0x60 [<c103007b>] ? task_ns_capable+0x1/0x16 [<c101b582>] ? mm_fault_error+0x129/0x129 [<c101f8dd>] ? __wake_up_common+0x17/0x5c [<c10202e5>] complete+0x2b/0x3e [<e0869c9e>] mpt2sas_base_done+0x6e/0x74 [mpt2sas] [<e086a720>] _base_interrupt+0x133/0x2f8 [mpt2sas] [<c104e61b>] handle_irq_event_percpu+0x24/0x100 [<c105038e>] ? irq_set_chip_and_handler_name+0x24/0x24 [<c104e71b>] handle_irq_event+0x24/0x3b [<c105038e>] ? irq_set_chip_and_handler_name+0x24/0x24 [<c105043c>] handle_edge_irq+0xae/0xce <IRQ> [<c1003622>] ? do_IRQ+0x37/0x90 [<c130fa69>] ? common_interrupt+0x29/0x30 [<e086858c>] ? _base_event_notification+0xef/0x1af [mpt2sas] [<e0868b0a>] ? _base_make_ioc_operational+0x2f1/0x36e [mpt2sas] [<e086bb47>] ? mpt2sas_base_attach+0x447/0x558 [mpt2sas] [<e08703a5>] ? _scsih_probe+0x310/0x3fe [mpt2sas] [<c11af52a>] ? local_pci_probe+0x3e/0x81 [<c11afc89>] ? pci_device_probe+0x43/0x66 [<c1207e52>] ? really_probe+0x72/0xed [<c1207ef9>] ? driver_probe_device+0x2c/0x41 [<c1207f51>] ? __driver_attach+0x43/0x5f [<c1207838>] ? bus_for_each_dev+0x3d/0x67 [<c1207d19>] ? driver_attach+0x14/0x16 [<c1207f0e>] ? driver_probe_device+0x41/0x41 [<c12072cb>] ? bus_add_driver+0x9d/0x1cd [<c12083ca>] ? driver_register+0x7c/0xe3 [<c11ff477>] ? misc_register+0x91/0xe6 [<c11afe4e>] ? __pci_register_driver+0x38/0x95 [<e088610c>] ? _scsih_init+0x10c/0x12d [mpt2sas] [<c1001159>] ? do_one_initcall+0x71/0x113 [<e0886000>] ? 0xe0885fff [<c104cae6>] ? sys_init_module+0x61/0x18b [<c130ed05>] ? syscall_call+0x7/0xb Fix from 3.0.33 commit 35d73fe5e3d8c72a41c2eaf285a9bfb7b6c66aee Author: [email protected] <[email protected]> Date: Tue Mar 20 12:10:01 2012 +0530 SCSI: mpt2sas: Fix for panic happening because of improper memory allocation commit e42fafc25fa86c61824e8d4c5e7582316415d24f upstream. The ioc->pfacts member in the IOC structure is getting set to zero following a call to _base_get_ioc_facts due to the memset in that routine. So if the ioc->pfacts was read after a host reset, there would be a NULL pointer dereference. The routine _base_get_ioc_facts is called from context of host reset. The problem in _base_get_ioc_facts is the size of Mpi2IOCFactsReply is 64, whereas the sizeof "struct mpt2sas_facts" is 60, so there is a four byte overflow resulting from the memset. Also, there is memset in _base_get_port_facts using the incorrect structure, it should be "struct mpt2sas_port_facts" instead of Mpi2PortFactsReply. Signed-off-by: Nagalakshmi Nandigama <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
  10. Version for 5.0rc3 is posted.
  11. The 5.0rc2test version will also work in 5.0rc2
  12. A version for 5.0RC2test has been posted.
  13. I have not been able to reporduce issues using a LSI card under ubuntu 12.04 (Kernel 3.2.14). It appears that the issue is related to the drive going through the driver in unraid or the way unraid puts the drive in spindown. Can anyone else with a LSI card test this?
  14. A version for 5.0RC1 has been posted.
  15. If I recally correctly, b12a wouls segfault on shutdown on some systems. Perhaps that is what is happening to yours.
  16. I have seen the same when I mount the share when logged in a root on another system. Having force user force group force create mode and force directory mode set in the samba configuration for public shares would avoid this issue.
  17. Zeron

    Move News

    That is absolutley not true. The bug IS in Tom's code, which was derrived from the linux MD drive long ago. No recent linux MD drivers ahve had this issue. That's akin to installing an engine you purchased into a chassis you built yourself and then someone blaming the chassis because the engine has a bad gasket. Version 4.7 was built using the faulty md drivers - they ALL were faulty at that time. Current betas use newer md drivers that the issue was resolved. Tom forked the MD5 md driver way back tomake the unRAId MD driver and does NOT track the changed that are put in to the standard Linux MD code. If he did track it, the "explicit block device plugging" bug that he references in the Beta-12 release notes would not have been there as the standard linux MD code was updated when explicit block device plugging was added. If you want to check this for your self, the code for unRAID driver is in /usr/src/linux/drivers/md on your unRAID server and teh standard linux md code can be seen here: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=tree;f=drivers/md
  18. Zeron

    Move News

    That is absolutley not true. The bug IS in Tom's code, which was derrived from the linux MD drive long ago. No recent linux MD drivers ahve had this issue.
  19. try setting pciPassthru0.msiEnabled = "FALSE" pciPassthru1.msiEnabled = "FALSE"
  20. May people have used these: http://www.ebay.com/itm/ws/eBayISAPI.dll?ViewItem&item=280429470355 They work well.
  21. I have been running P12 on my IBM M1015 for about a week now. No issues so far. I have a zip file with all the files to upgrade from DOS here: http://unraid.zeron.ca/other/upgrade-M1015-P12.zip
  22. You can achieve this already if you are willing to do a little bit of work. I have it on one of my development machines. I have two unraid virtual machines - each using vt-d to access sata controllers directly. I have one further VM that mounts the shares from the two unRAID vm's, combines them using a union filesystem (AUFS I think) and then shares that back via samba. How are writes handled with that setup? What determines which unRAID server it is written to? Are there any mirroring features in the union filesystem, such that your ultra important stuff will be mirrored between the two unRAID servers but only presented once? I do like the idea a lot. Have one unified filesystem while using more unRAID servers with fewer number of drives to keep the parity calc and rebuild time down. I recall reading about how you can control writes in AUFS, but I was just creating a read-only share. I write to my diskx shares directly.