December 10, 201015 yr Hello all, I'm trying to get out of this vicious cycle of crashing and restarting, parity checking and reiserfsck'ing, but I now have something new to report. Within the last week or so, I've been experiencing Kernel Panics (two in a row actually) while attempting to perform reiserfsck --check's. Most recently, I tried to do a --check on disk3, and here's what unraid spits back out: AJs_Unraid kernel: Oops: 0000 [#1] SMP Message from syslogd@AJs_Unraid at Thu Dec 9 22:50:35 2010 ... AJs_Unraid kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:11.0/host5/target5:0:0/5:0:0:0/block/sdf/stat Message from syslogd@AJs_Unraid at Thu Dec 9 22:50:35 2010 ... AJs_Unraid kernel: Process kswapd0 (pid: 342, ti=f76fa000 task=f7791ef0 task.ti=f76fa000) Message from syslogd@AJs_Unraid at Thu Dec 9 22:50:35 2010 ... AJs_Unraid kernel: Stack: Message from syslogd@AJs_Unraid at Thu Dec 9 22:50:35 2010 ... AJs_Unraid kernel: Call Trace: Message from syslogd@AJs_Unraid at Thu Dec 9 22:50:35 2010 ... AJs_Unraid kernel: Code: 1c 5b 5e 5f 5d c3 55 89 e5 56 89 d6 53 8b 08 89 c3 8b 50 10 f6 c1 01 75 04 0f 0b eb fe 31 c0 80 e5 20 75 1d 85 d2 74 12 8b 42 38 <8b> 48 28 85 c9 74 08 89 f2 89 d8 ff d1 eb 07 89 d8 e8 b6 d9 03 Message from syslogd@AJs_Unraid at Thu Dec 9 22:50:35 2010 ... AJs_Unraid kernel: EIP: [<c10483b9>] try_to_release_page+0x25/0x3f SS:ESP 0068:f76fbd58 Message from syslogd@AJs_Unraid at Thu Dec 9 22:50:35 2010 ... AJs_Unraid kernel: CR2: 0000000000000983 finished Comparing bitmaps..finished Checking Semantic tree: /Hot Rod/Media/TV Shows/Band of Brothers/Season 1/05 Crossroads.mp4 Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... AJs_UnraidAJs_Unraid Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... kernel: EIP: [<c10483b9>] try_to_release_page+0x25/0x3f SS:ESP 0068:c202fb34kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:11.0/host5/target5:0:0/5:0:0:0/block/sdf/stat AJs_Unraid kernel: Oops: 0000 [#2] SMP Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... AJs_Unraid kernel: Stack: Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... AJs_Unraid kernel: Call Trace: Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... AJs_Unraid kernel: Code: 1c 5b 5e 5f 5d c3 55 89 e5 56 89 d6 53 8b 08 89 c3 8b 50 10 f6 c1 01 75 04 0f 0b eb fe 31 c0 80 e5 20 75 1d 85 d2 74 12 8b 42 38 <8b> 48 28 85 c9 74 08 89 f2 89 d8 ff d1 eb 07 89 d8 e8 b6 d9 03 Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... AJs_UnraidAJs_Unraid kernel: CR2: 000000000ce77cabkernel: Process reiserfsck (pid: 13309, ti=c202e000 task=f74f4000 task.ti=c202e000) Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... AJs_Unraid kernel: Oops: 0000 [#3] SMP Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... AJs_Unraid kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:11.0/host5/target5:0:0/5:0:0:0/block/sdf/stat Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... AJs_Unraid kernel: Process reiserfsck (pid: 13309, ti=c202e000 task=f74f4000 task.ti=c202e000) Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... AJs_Unraid kernel: Stack: Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... AJs_Unraid kernel: Call Trace: Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... AJs_Unraid kernel: Code: c0 5d c3 55 89 e5 0f ae f0 66 90 f6 40 02 01 8b 50 10 74 07 ba 74 5d 3d c1 eb 09 f6 c2 01 75 14 85 d2 74 10 8b 52 38 85 d2 74 09 <8b> 52 08 85 d2 74 02 ff d2 e8 85 67 25 00 31 c0 5d c3 55 89 e5 Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... AJs_Unraid kernel: EIP: [<c1048c19>] sync_page+0x28/0x3a SS:ESP 0068:c202f8a0 Message from syslogd@AJs_Unraid at Fri Dec 10 00:44:47 2010 ... AJs_Unraid kernel: CR2: 000000000ce77c8b Any thoughts on how I should proceed? I have posted my syslog, in case anyone can glean some good info from it thanks! -alex syslog-2010-12-10.txt.zip
December 10, 201015 yr Author I'd like to pose an alternative series of questions. If I were to stop the array, and then pre_clear 1 disk, would unRAID recognize and allow me to rebuild from parity when the array is restarted? If possible, would that be any use or would it just put the "corruptions" back onto my newly pre_cleared disk? thanks -alex
December 11, 201015 yr I'd like to pose an alternative series of questions. If I were to stop the array, and then pre_clear 1 disk, would unRAID recognize and allow me to rebuild from parity when the array is restarted? If possible, would that be any use or would it just put the "corruptions" back onto my newly pre_cleared disk? thanks -alex It would put back whatever corruptions currently exist.
Archived
This topic is now archived and is closed to further replies.