July 9, 20169 yr Anyone have any idea what causes this? Just started happening... Using 6.1.9 Diagnostics attached... Jul 9 04:35:29 Angband kernel: REISERFS panic: vs-6030 check_internal_block_head: invalid item number level=2, nr_items=170, free_space=65520 rdkey Jul 9 04:35:29 Angband kernel: ------------[ cut here ]------------ Jul 9 04:35:29 Angband kernel: kernel BUG at fs/reiserfs/prints.c:371! Jul 9 04:35:29 Angband kernel: invalid opcode: 0000 [#1] PREEMPT SMP Jul 9 04:35:29 Angband kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables kvm_amd kvm vhost_net vhost macvtap macvlan tun xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat it87 hwmon_vid md_mod k10temp fam15h_power i2c_piix4 ahci libahci mvsas libsas r8169 mii scsi_transport_sas acpi_cpufreq Jul 9 04:35:29 Angband kernel: CPU: 6 PID: 2088 Comm: shfs Not tainted 4.1.18-unRAID #1 Jul 9 04:35:29 Angband kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A97 R2.0, BIOS 2201 12/10/2013 Jul 9 04:35:29 Angband kernel: task: ffff880837520860 ti: ffff88079c440000 task.ti: ffff88079c440000 Jul 9 04:35:29 Angband kernel: RIP: 0010:[<ffffffff8116422d>] [<ffffffff8116422d>] __reiserfs_panic+0xb6/0xb8 Jul 9 04:35:29 Angband kernel: RSP: 0018:ffff88079c443408 EFLAGS: 00010296 Jul 9 04:35:29 Angband kernel: RAX: 0000000000000075 RBX: ffffffff817416c6 RCX: 0000000000000000 Jul 9 04:35:29 Angband kernel: RDX: ffff88085ed90a01 RSI: ffff88085ed8e438 RDI: ffff88085ed8e438 Jul 9 04:35:29 Angband kernel: RBP: ffff88079c443478 R08: 0000000000000400 R09: 0000000000000000 Jul 9 04:35:29 Angband kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 Jul 9 04:35:29 Angband kernel: R13: ffffffff81610140 R14: ffff8805e4746750 R15: 0000000000000008 Jul 9 04:35:29 Angband kernel: FS: 00002b552a979700(0000) GS:ffff88085ed80000(0000) knlGS:0000000000000000 Jul 9 04:35:29 Angband kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jul 9 04:35:29 Angband kernel: CR2: 00002b61113771c8 CR3: 000000080ef7a000 CR4: 00000000000406e0 Jul 9 04:35:29 Angband kernel: Stack: Jul 9 04:35:29 Angband kernel: ffff88079c443468 ffffffff00000028 ffff88079c443488 ffff88079c443428 Jul 9 04:35:29 Angband kernel: 0000000000000002 ffffea00178807c0 ffff88079c443468 ffff8805de7d0e58 Jul 9 04:35:29 Angband kernel: ffff8805e4746750 00000000000000aa ffff88079c443548 0000000000000001 Jul 9 04:35:29 Angband kernel: Call Trace: Jul 9 04:35:29 Angband kernel: [<ffffffff81164947>] check_internal+0x78/0xaf Jul 9 04:35:29 Angband kernel: [<ffffffff81167589>] internal_move_pointers_items+0x17c/0x216 Jul 9 04:35:29 Angband kernel: [<ffffffff811676b1>] internal_shift_left+0x8e/0x97 Jul 9 04:35:29 Angband kernel: [<ffffffff81167b20>] balance_internal+0x2e1/0xba1 Jul 9 04:35:29 Angband kernel: [<ffffffff811568b0>] ? balance_leaf+0x1f34/0x2084 Jul 9 04:35:29 Angband kernel: [<ffffffff81156ad6>] do_balance+0xd6/0x16c Jul 9 04:35:29 Angband kernel: [<ffffffff8116ae4c>] reiserfs_paste_into_item+0x19c/0x200 Jul 9 04:35:29 Angband kernel: [<ffffffff8115bbb5>] reiserfs_get_block+0xc0c/0xecc Jul 9 04:35:29 Angband kernel: [<ffffffff81124450>] __block_write_begin+0x159/0x321 Jul 9 04:35:29 Angband kernel: [<ffffffff8115afa9>] ? reiserfs_commit_write+0x169/0x169 Jul 9 04:35:29 Angband kernel: [<ffffffff810b9212>] ? wait_for_stable_page+0x15/0x34 Jul 9 04:35:29 Angband kernel: [<ffffffff81159d70>] reiserfs_write_begin+0x100/0x1bc Jul 9 04:35:29 Angband kernel: [<ffffffff810b1990>] generic_perform_write+0xd1/0x185 Jul 9 04:35:29 Angband kernel: [<ffffffff810b2a1f>] __generic_file_write_iter+0x9f/0x147 Jul 9 04:35:29 Angband kernel: [<ffffffff810b2bd9>] generic_file_write_iter+0x112/0x17d Jul 9 04:35:29 Angband kernel: [<ffffffff810fd986>] __vfs_write+0x8f/0xb8 Jul 9 04:35:29 Angband kernel: [<ffffffff810fdf05>] vfs_write+0xad/0x165 Jul 9 04:35:29 Angband kernel: [<ffffffff810fe76a>] SyS_pwrite64+0x50/0x81 Jul 9 04:35:29 Angband kernel: [<ffffffff815f7b2e>] system_call_fastpath+0x12/0x71 Jul 9 04:35:29 Angband kernel: Code: 48 c7 c2 ec 97 77 81 eb 0a 48 c7 c2 19 c7 73 81 48 89 d6 49 c7 c0 80 93 9e 81 4c 89 e9 31 c0 48 c7 c7 92 12 74 81 e8 9a a2 48 00 <0f> 0b 55 48 89 e5 41 54 49 89 f4 53 48 8d 45 10 48 89 fb 48 8d Jul 9 04:35:29 Angband kernel: RIP [<ffffffff8116422d>] __reiserfs_panic+0xb6/0xb8 Jul 9 04:35:29 Angband kernel: RSP <ffff88079c443408> Jul 9 04:35:29 Angband kernel: ---[ end trace 323e898dea17fd6f ]--- angband-diagnostics-20160709-0439.zip
July 9, 20169 yr Community Expert Only now had a chance to look at your SMART reports and you may have problems on multiple disks: Device Model: WDC WD20EARS-00J99B0 Serial Number: WD-WCAWZ0156791 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 5 Device Model: WDC WD20EARX-00PASB0 Serial Number: WD-WCAZAD207818 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 Device Model: WDC WD20EARX-00PASB0 Serial Number: WD-WMAZA9532045 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 64 One or more could be false positives, you may want to do an extended SMART test on each before deciding how to proceed.
July 10, 20169 yr Author All three drives passed extended SMART without errors. Not sure what to try next.
July 11, 20169 yr Author New diags... FSCK is going to take some time... 24 drives, most 4TB... ugh. angband-diagnostics-20160709-0439.zip
July 11, 20169 yr Author Ok, so it turns out I had to rebuild-tree on 4 drives... yikes! I have done this (according to the Wiki) now I should be able to just run a parity check to correct anything that's out, or is there something else I should do first? The ones that re-built, I ran the --check on them again and they showed OK.
July 12, 20169 yr Community Expert If you followed the wiki and repaired the mdX devices parity was updated and is in sync, although you should always run periodic parity checks. I still would like to see the SMART reports post extended tests, the diagnostics you posted above is the same as the first one, pre extended tests.
Archived
This topic is now archived and is closed to further replies.