January 13, 201115 yr Jan 13 01:14:51 Tower kernel: ------------[ cut here ]------------ Jan 13 01:14:51 Tower kernel: kernel BUG at drivers/md/unraid.c:780! Jan 13 01:14:51 Tower kernel: invalid opcode: 0000 [#1] SMP Jan 13 01:14:51 Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:11.0/host6/target6:0:0/6:0:0:0/block/sdf/stat Jan 13 01:14:51 Tower kernel: Modules linked in: md_mod xor atiixp ahci r8169 Jan 13 01:14:51 Tower kernel: Jan 13 01:14:51 Tower kernel: Pid: 1425, comm: unraidd Not tainted (2.6.32.9-unRAID #5) System Product Name Jan 13 01:14:51 Tower kernel: EIP: 0060:[] EFLAGS: 00010246 CPU: 0 Jan 13 01:14:51 Tower kernel: EIP is at handle_stripe+0xdb/0xbc9 [md_mod] Jan 13 01:14:51 Tower kernel: EAX: 00000009 EBX: c2d5cc10 ECX: 00000001 EDX: c2d5cc28 Jan 13 01:14:51 Tower kernel: ESI: 00000001 EDI: c2d5cb00 EBP: c2051f9c ESP: c2051f24 Jan 13 01:14:51 Tower kernel: DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Jan 13 01:14:51 Tower kernel: Process unraidd (pid: 1425, ti=c2050000 task=f75a25d0 task.ti=c2050000) Jan 13 01:14:51 Tower kernel: Stack: Jan 13 01:14:51 Tower kernel: c4543ac0 f75a25d0 c13ce774 c1442240 f75a25d0 c2051f9c c4543a80 00000006 Jan 13 01:14:51 Tower kernel: <0> 00000002 00000001 00000000 00000002 00000000 00000000 00000000 00000000 Jan 13 01:14:51 Tower kernel: <0> 00000000 00000003 c2bc3840 00000001 f75a25d0 c2051f8c f82c2601 00000000 Jan 13 01:14:51 Tower kernel: Call Trace: Jan 13 01:14:51 Tower kernel: [] ? _release_stripe+0xb8/0xdc [md_mod] Jan 13 01:14:51 Tower kernel: [] ? unraidd+0x8f/0xb0 [md_mod] Jan 13 01:14:51 Tower kernel: [] ? unraidd+0x0/0xb0 [md_mod] Jan 13 01:14:51 Tower kernel: [] ? kthread+0x61/0x68 Jan 13 01:14:51 Tower kernel: [] ? kthread+0x0/0x68 Jan 13 01:14:51 Tower kernel: [] ? kernel_thread_helper+0x7/0x1a Jan 13 01:14:51 Tower kernel: Code: 75 a8 68 55 52 2c f8 e8 07 24 d6 c8 83 c4 18 3e 0f ba 73 04 0d 19 c0 85 c0 0f 84 a9 00 00 00 f6 43 05 02 8d 53 18 8b 43 28 75 04 <0f> 0b eb fe 89 c6 83 e6 01 83 7a 14 00 75 47 8b 45 88 e8 58 d9 Jan 13 01:14:51 Tower kernel: EIP: [] handle_stripe+0xdb/0xbc9 [md_mod] SS:ESP 0068:c2051f24 Jan 13 01:14:51 Tower kernel: ---[ end trace b47a0968a00b2b7e ]---
January 14, 201115 yr Author Was transferring files to the server.. power went out... Turned it back on, did a parity check had a fair amount of errors... wanted to double check nothing was wrong 1 more time.. so before I went to bed did another check.. When I woke up in the morning.. it was scanning at like 400kb/s? Pretty Much Froze... Checked the syslog and it gave me 3 parity incorrect errors.. followed by that line, so I copied that... I pressed stop parity check... and system went down.. couldn't access remote or direct.. restarted and it booted up no problem...
January 20, 201115 yr Was transferring files to the server.. power went out... Turned it back on, did a parity check had a fair amount of errors... wanted to double check nothing was wrong 1 more time.. so before I went to bed did another check.. You mean parity sync errors? Did you restart file transfer to the server? When I woke up in the morning.. it was scanning at like 400kb/s? Pretty Much Froze... [/quote Should've just stayed in bed Checked the syslog and it gave me 3 parity incorrect errors.. followed by that line, so I copied that... I pressed stop parity check... and system went down.. couldn't access remote or direct.. restarted and it booted up no problem... Do you still have that syslog? Can you make it happen again?
January 21, 201115 yr Author Do you still have that syslog? Can you make it happen again? No.... sadly I don't and I haven't been able to replicate the problem... I'm not worried about anything, just curious... was hoping that line from the syslog would be enough... next time I have to grab it all
Archived
This topic is now archived and is closed to further replies.