October 18, 201015 yr Seeing a kernel bug when adding a 16th drive to the array. This drive (a Seagate ST31500341AS firmware CC1H sent to me from Seagate a couple weeks ago) has been pre-cleared and I was attempting to add it to a SuperMicro AOC-SASLP-MV8 card. When connected, the system will crash within hours. I've since disconnected it and the server has been stable for over 72 hours and has passed parity check. Oct 15 10:38:03 saraswati kernel: BUG: unable to handle kernel paging request at 67726184 Oct 15 10:38:03 saraswati kernel: IP: [<c1133ec9>] radix_tree_delete+0x76/0x175 Oct 15 10:38:03 saraswati kernel: *pdpt = 0000000032276001 *pde = 0000000000000000 Oct 15 10:38:03 saraswati kernel: Oops: 0000 [#2] SMP Oct 15 10:38:03 saraswati kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/port-1:5/end_device-1:5/target1:0:5/1:0:5:0/block/sdg/stat Oct 15 10:38:03 saraswati kernel: Modules linked in: md_mod xor i2c_i801 i2c_core ahci e1000 sata_sil24 mvsas libsas scst scsi_transport_sas Oct 15 10:38:03 saraswati kernel: Oct 15 10:38:03 saraswati kernel: Pid: 319, comm: kswapd0 Tainted: G D (2.6.32.9-unRAID #5) EP45-UD3P Oct 15 10:38:03 saraswati kernel: EIP: 0060:[<c1133ec9>] EFLAGS: 00010046 CPU: 1 Oct 15 10:38:03 saraswati kernel: EIP is at radix_tree_delete+0x76/0x175 Oct 15 10:38:03 saraswati kernel: EAX: 00000000 EBX: da8f02c8 ECX: 00000000 EDX: 00000000 Oct 15 10:38:03 saraswati kernel: ESI: 67726174 EDI: f764dd18 EBP: f764dd3c ESP: f764dcf0 Oct 15 10:38:03 saraswati kernel: DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Oct 15 10:38:03 saraswati kernel: Process kswapd0 (pid: 319, ti=f764c000 task=f74525d0 task.ti=f764c000) Oct 15 10:38:03 saraswati kernel: Stack: Oct 15 10:38:03 saraswati kernel: 00003000 67726174 00000000 c13f1840 d9024a68 00000000 d9024b90 00000003 Oct 15 10:38:03 saraswati kernel: <0> d213a250 00000000 67726174 00000000 c13f18c0 f764dd4c 00000202 00000001 Oct 15 10:38:03 saraswati kernel: <0> c73fdd40 da8f02c4 c73fdd40 f764dd4c c1049ad4 c73fdd40 da8f02c4 f764dd60 Oct 15 10:38:03 saraswati kernel: Call Trace: Oct 15 10:38:03 saraswati kernel: [<c1049ad4>] ? __remove_from_page_cache+0x15/0x94 Oct 15 10:38:03 saraswati kernel: [<c10505e8>] ? __remove_mapping+0x82/0x98 Oct 15 10:38:03 saraswati kernel: [<c1050d7f>] ? shrink_page_list+0x47e/0x57b Oct 15 10:38:03 saraswati kernel: [<c1050030>] ? isolate_pages_global+0x7c/0x1bf Oct 15 10:38:03 saraswati kernel: [<c104f16a>] ? ____pagevec_lru_add+0xe7/0xf5 Oct 15 10:38:03 saraswati kernel: [<c1051420>] ? shrink_zone+0x5a4/0x8ba Oct 15 10:38:03 saraswati kernel: [<c1036edf>] ? sched_clock_local+0x11/0x135 Oct 15 10:38:03 saraswati kernel: [<c101c7f4>] ? update_curr+0x60/0xa4 Oct 15 10:38:03 saraswati kernel: [<c10daa27>] ? nfs_access_cache_shrinker+0x1f/0x1a5 Oct 15 10:38:03 saraswati kernel: [<c1051def>] ? kswapd+0x2c7/0x456 Oct 15 10:38:03 saraswati kernel: [<c104ffb4>] ? isolate_pages_global+0x0/0x1bf Oct 15 10:38:03 saraswati kernel: [<c103391d>] ? autoremove_wake_function+0x0/0x30 Oct 15 10:38:03 saraswati kernel: [<c1051b28>] ? kswapd+0x0/0x456 Oct 15 10:38:03 saraswati kernel: [<c1033869>] ? kthread+0x61/0x68 Oct 15 10:38:03 saraswati kernel: [<c1033808>] ? kthread+0x0/0x68 Oct 15 10:38:03 saraswati kernel: [<c100339f>] ? kernel_thread_helper+0x7/0x1a Oct 15 10:38:03 saraswati kernel: Code: 8d 7d bc c7 45 bc 00 00 00 00 8d 48 fa 83 7d b8 00 0f 84 06 01 00 00 8b 45 b4 83 c7 08 d3 e8 83 e0 3f 4a 89 47 04 8b 75 b8 89 37 <8b> 44 86 10 89 45 b8 74 05 83 e9 06 eb d4 83 7d b8 00 0f 84 da Oct 15 10:38:03 saraswati kernel: EIP: [<c1133ec9>] radix_tree_delete+0x76/0x175 SS:ESP 0068:f764dcf0 Oct 15 10:38:03 saraswati kernel: CR2: 0000000067726184 Oct 15 10:38:03 saraswati kernel: ---[ end trace 32fe8f7fb013f79c ]--- Edit: Strong possibility of hardware failure. See http://lime-technology.com/forum/index.php?action=post;topic=8510.0
Archived
This topic is now archived and is closed to further replies.