Jump to content

Writing to drive crashes system


Shigo_Naito

Recommended Posts

Posted

Hello,

I just recently got a red X on one of my drives.  I replaced old 2TB drive with a newer 4TB drive I had for a spare, array rebuilt and Parity-Check came out clear.  Now it seems when ever Plex or myself access a file from the disk I get the error below and the system starts running slow and any shares with the drive start not responding.  Also when trying to stop the array it hangs on sync filesystems and I have to hard shutdown and reboot.

 

Any help you can give would be wonderful.

 

Thank you

 

Oct 14 16:53:43 IronMan kernel: REISERFS panic: vs-6030 check_internal_block_head: invalid item number level=2, nr_items=174, free_space=65424 rdkey 
Oct 14 16:53:43 IronMan kernel: ------------[ cut here ]------------
Oct 14 16:53:43 IronMan kernel: kernel BUG at fs/reiserfs/prints.c:371!
Oct 14 16:53:43 IronMan kernel: invalid opcode: 0000 [#1] PREEMPT SMP 
Oct 14 16:53:43 IronMan kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables iptable_filter ip_tables kvm_intel kvm vhost_net vhost macvtap macvlan tun md_mod igb e1000e i2c_algo_bit ahci i2c_i801 libahci mpt2sas ptp raid_class scsi_transport_sas pps_core [last unloaded: md_mod]
Oct 14 16:53:43 IronMan kernel: CPU: 0 PID: 8620 Comm: smbd Not tainted 4.0.4-unRAID #5
Oct 14 16:53:43 IronMan kernel: Hardware name: ASUS All Series/Z87-WS, BIOS 1803 04/16/2014
Oct 14 16:53:43 IronMan kernel: task: ffff88040b5cec10 ti: ffff8800d5eac000 task.ti: ffff8800d5eac000
Oct 14 16:53:43 IronMan kernel: RIP: 0010:[] [] __reiserfs_panic+0xb6/0xb8
Oct 14 16:53:43 IronMan kernel: RSP: 0018:ffff8800d5eaf568 EFLAGS: 00010296
Oct 14 16:53:43 IronMan kernel: RAX: 0000000000000075 RBX: ffffffff81754937 RCX: 0000000000000000
Oct 14 16:53:43 IronMan kernel: RDX: ffff88041fa0e601 RSI: ffff88041fa0e0b8 RDI: ffff88041fa0e0b8
Oct 14 16:53:43 IronMan kernel: RBP: ffff8800d5eaf5d8 R08: 0000000000000400 R09: 0000000000000000
Oct 14 16:53:43 IronMan kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Oct 14 16:53:43 IronMan kernel: R13: ffffffff81621020 R14: ffff8803ec887958 R15: 0000000000000068
Oct 14 16:53:43 IronMan kernel: FS: 00002b7ae240c380(0000) GS:ffff88041fa00000(0000) knlGS:0000000000000000
Oct 14 16:53:43 IronMan kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 14 16:53:43 IronMan kernel: CR2: 0000000000660968 CR3: 00000000d42c4000 CR4: 00000000001407f0
Oct 14 16:53:43 IronMan kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 14 16:53:43 IronMan kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct 14 16:53:43 IronMan kernel: Stack:
Oct 14 16:53:43 IronMan kernel: 0000000000000202 0000000000000028 ffff8800d5eaf5e8 ffff8800d5eaf588
Oct 14 16:53:43 IronMan kernel: ffff88041fa13ac0 0000000000000000 ffff8800d5eaf5b8 ffffffff8115b840
Oct 14 16:53:43 IronMan kernel: ffff8803ec887958 00000000000000ae ffff8800d5eaf6a8 0000000000000005
Oct 14 16:53:43 IronMan kernel: Call Trace:
Oct 14 16:53:43 IronMan kernel: [] ? reiserfs_schedule_old_flush+0x70/0x75
Oct 14 16:53:43 IronMan kernel: [] check_internal+0x78/0xaf
Oct 14 16:53:43 IronMan kernel: [] internal_move_pointers_items+0x17c/0x216
Oct 14 16:53:43 IronMan kernel: [] internal_shift_left+0x8e/0x97
Oct 14 16:53:43 IronMan kernel: [] balance_internal+0x2e1/0xba1
Oct 14 16:53:43 IronMan kernel: [] ? leaf_insert_into_buf+0x159/0x1a5
Oct 14 16:53:43 IronMan kernel: [] ? balance_leaf+0x1813/0x2084
Oct 14 16:53:43 IronMan kernel: [] do_balance+0xd6/0x16c
Oct 14 16:53:43 IronMan kernel: [] reiserfs_insert_item+0x229/0x290
Oct 14 16:53:43 IronMan kernel: [] add_save_link+0x19e/0x1ef
Oct 14 16:53:43 IronMan kernel: [] reiserfs_unlink+0x1d2/0x23f
Oct 14 16:53:43 IronMan kernel: [] vfs_unlink+0xc5/0x165
Oct 14 16:53:43 IronMan kernel: [] do_unlinkat+0x107/0x22f
Oct 14 16:53:43 IronMan kernel: [] ? SyS_newstat+0x25/0x2e
Oct 14 16:53:43 IronMan kernel: [] SyS_unlink+0x11/0x13
Oct 14 16:53:43 IronMan kernel: [] system_call_fastpath+0x12/0x17
Oct 14 16:53:43 IronMan kernel: Code: 48 c7 c2 55 ed 78 81 eb 0a 48 c7 c2 1d fa 74 81 48 89 d6 49 c7 c0 30 72 9f 81 4c 89 e9 31 c0 48 c7 c7 03 45 75 81 e8 ec e0 49 00 <0f> 0b 55 48 89 e5 41 54 49 89 f4 53 48 8d 45 10 48 89 fb 48 8d 
Oct 14 16:53:43 IronMan kernel: RIP [] __reiserfs_panic+0xb6/0xb8
Oct 14 16:53:43 IronMan kernel: RSP 
Oct 14 16:53:43 IronMan kernel: ---[ end trace 1ca580c1a47f1c58 ]---

Posted

Sorry looking over my post it does not give much information.  I am running version 6.1.3 and I did downgrade to 6.0.1 and the problem still continued.  I am trying to get a full syslog of the issue now, if there is any other information you need please let me know.

 

Thx

Posted

Did a file system check and yes it does look like there where some corruption.  The check said to rebuild the tree and after that it looks like most of the data is still there, need to do some reorganizing but things are working normal again.  Thanks for the suggestion,  this was only my 2nd drive failure for me over the 5+ years of running this array.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...