August 27, 201015 yr Hello, I captured some logs of my server crashing. My server has been crashing every week or so, unfortunately I don't have a screen attached to it and the server is tucked away in the crawl space, afte a reboot though i kept the following log file in my cache drive and i'm hoping someone can udnerstand what it means. Aug 26 11:03:16 kenny kernel: BUG: unable to handle kernel paging request at f83ce000 Aug 26 11:03:16 kenny kernel: IP: [<f83c48e4>] md_cmd_proc_read+0x41/0x54 [md_mod] Aug 26 11:03:16 kenny kernel: *pdpt = 0000000001447001 *pde = 0000000037410067 *pte = 0000000000000000 Aug 26 11:03:16 kenny kernel: Oops: 0000 [#1] SMP Aug 26 11:03:16 kenny kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.1/ide0/0.1/block/hdb/stat Aug 26 11:03:16 kenny kernel: Modules linked in: md_mod xor ide_gd_mod i2c_i801 i2c_core ata_piix piix sata_mv r8169 Aug 26 11:03:16 kenny kernel: Aug 26 11:03:16 kenny kernel: Pid: 14732, comm: egrep Not tainted (2.6.32.9-unRAID #5) Aug 26 11:03:16 kenny kernel: EIP: 0060:[<f83c48e4>] EFLAGS: 00010207 CPU: 1 Aug 26 11:03:16 kenny kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod] Aug 26 11:03:16 kenny kernel: EAX: c6ccbf38 EBX: fffffe1e ECX: 3ffff1f2 EDX: fffffe1e Aug 26 11:03:16 kenny kernel: ESI: f83ce000 EDI: c701d654 EBP: c6ccbf04 ESP: c6ccbef4 Aug 26 11:03:16 kenny kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Aug 26 11:03:16 kenny kernel: Process egrep (pid: 14732, ti=c6cca000 task=f777f020 task.ti=c6cca000) Aug 26 11:03:16 kenny kernel: Stack: Aug 26 11:03:16 kenny kernel: c6ccbf38 f83c48a3 00001000 c701a000 c6ccbf4c c109d5f5 00000c00 c6ccbf3c Aug 26 11:03:16 kenny kernel: <0> 00000000 00008000 00000000 00007400 0806bc00 f6e95c60 00000c00 f6e95c60 Aug 26 11:03:16 kenny kernel: <0> 00000c00 c701a000 00000001 f6e95c60 c109d4ea fffffffb c6ccbf70 c1099f72 Aug 26 11:03:16 kenny kernel: Call Trace: Aug 26 11:03:16 kenny kernel: [<f83c48a3>] ? md_cmd_proc_read+0x0/0x54 [md_mod] Aug 26 11:03:16 kenny kernel: [<c109d5f5>] ? proc_file_read+0x10b/0x22d Aug 26 11:03:16 kenny kernel: [<c109d4ea>] ? proc_file_read+0x0/0x22d Aug 26 11:03:17 kenny kernel: [<c1099f72>] ? proc_reg_read+0x56/0x6a Aug 26 11:03:17 kenny kernel: [<c1099f1c>] ? proc_reg_read+0x0/0x6a Aug 26 11:03:17 kenny kernel: [<c106cbd8>] ? vfs_read+0x8a/0x114 Aug 26 11:03:17 kenny kernel: [<c106cf6f>] ? sys_read+0x3b/0x60 Aug 26 11:03:17 kenny kernel: [<c1002935>] ? syscall_call+0x7/0xb Aug 26 11:03:17 kenny kernel: Code: 55 f0 e8 6a 22 d7 c8 8d 50 01 29 f2 39 d3 7c 0b 8b 45 0c 89 d3 c7 00 01 00 00 00 8b 45 f0 89 d9 81 c6 ac 9d 3c f8 c1 e9 0 2 89 38 <f3> a5 89 d9 83 e1 03 74 02 f3 a4 5a 89 d8 5b 5e 5f 5d c3 55 89 Aug 26 11:03:17 kenny kernel: EIP: [<f83c48e4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c6ccbef4 Aug 26 11:03:17 kenny kernel: CR2: 00000000f83ce000 Aug 26 11:03:17 kenny kernel: ---[ end trace dc172b4b33f36fba ]--- Aug 26 11:03:23 kenny kernel: BUG: unable to handle kernel NULL pointer dereference at (null) Aug 26 11:03:23 kenny kernel: IP: [<c1078a5b>] __d_find_alias+0x1b/0x7c Aug 26 11:03:23 kenny kernel: *pdpt = 000000002668b001 *pde = 0000000000000000
August 29, 201015 yr I'd start with an overnight memory test. If it is successful, then a check of each of the disk file-systems using reiserfsck as described in the wiki. Joe L.
September 14, 201015 yr Author Hi Joe, i did the memtest overnight and everythng checked out. I'm about to do the reiserfck but it will be a long process so maybe over the weekend. In the meantime though here are more logs that might help.... one thing I have noticed before the crash I get a lot of "spindown" requests; Sep 13 14:19:05 kenny kernel: mdcmd (20665): spindown 1 Sep 13 14:19:25 kenny kernel: mdcmd (20669): spindown 1 Sep 13 14:20:06 kenny kernel: mdcmd (20675): spindown 1 Sep 13 14:20:26 kenny kernel: mdcmd (20679): spindown 1 Sep 13 14:20:57 kenny kernel: mdcmd (20685): spindown 1 Sep 13 14:21:17 kenny kernel: mdcmd (20689): spindown 1 Sep 13 14:21:30 kenny kernel: mdcmd (20691): spindown 1 Sep 13 14:21:51 kenny kernel: mdcmd (20695): spindown 1 Sep 13 14:22:32 kenny kernel: mdcmd (20702): spindown 1 Sep 13 14:22:52 kenny kernel: mdcmd (20706): spindown 1 Sep 13 14:23:23 kenny kernel: mdcmd (20711): spindown 1 Sep 13 14:23:44 kenny kernel: mdcmd (20715): spindown 1 Sep 13 14:24:05 kenny kernel: mdcmd (20719): spindown 1 Sep 13 14:24:25 kenny kernel: mdcmd (20723): spindown 1 Sep 13 14:24:45 kenny kernel: mdcmd (20726): spindown 1 Sep 13 14:25:06 kenny kernel: mdcmd (20730): spindown 1 Sep 13 14:25:26 kenny kernel: mdcmd (20734): spindown 1 Sep 13 14:25:46 kenny kernel: mdcmd (20738): spindown 1 Sep 13 14:26:07 kenny kernel: mdcmd (20742): spindown 1 Sep 13 14:26:48 kenny kernel: mdcmd (20749): spindown 1 Sep 13 14:27:09 kenny kernel: mdcmd (20753): spindown 1 Sep 13 14:27:29 kenny kernel: mdcmd (20757): spindown 1 Sep 13 14:27:49 kenny kernel: mdcmd (20761): spindown 1 Sep 13 14:28:10 kenny kernel: mdcmd (20764): spindown 1 Sep 13 14:28:30 kenny kernel: mdcmd (20768): spindown 1 Sep 13 14:28:50 kenny kernel: mdcmd (20772): spindown 1 Sep 13 14:29:10 kenny kernel: mdcmd (20776): spindown 1 Sep 13 14:29:41 kenny kernel: mdcmd (20781): spindown 1 Sep 13 14:30:01 kenny kernel: mdcmd (20785): spindown 1 Sep 13 14:30:21 kenny kernel: mdcmd (20789): spindown 1 Sep 13 14:31:13 kenny kernel: mdcmd (20797): spindown 1 Sep 13 14:31:34 kenny kernel: mdcmd (20801): spindown 1 Sep 13 14:31:54 kenny kernel: mdcmd (20805): spindown 1 Sep 13 14:32:14 kenny kernel: mdcmd (20809): spindown 1 Sep 13 14:33:05 kenny kernel: mdcmd (20817): spindown 1 Sep 13 14:33:25 kenny kernel: mdcmd (20821): spindown 1 Sep 13 14:33:45 kenny kernel: mdcmd (20825): spindown 1 Sep 13 14:34:16 kenny kernel: mdcmd (20830): spindown 1 Sep 13 14:34:37 kenny kernel: mdcmd (20834): spindown 1 Sep 13 14:34:57 kenny kernel: mdcmd (20838): spindown 1 Sep 13 14:35:17 kenny kernel: mdcmd (20842): spindown 1 Sep 13 14:35:48 kenny kernel: mdcmd (20847): spindown 1 Sep 13 14:36:19 kenny kernel: mdcmd (20853): spindown 1 Sep 13 14:36:40 kenny kernel: mdcmd (20857): spindown 1 Sep 13 14:37:00 kenny kernel: mdcmd (20861): spindown 1 Sep 13 14:37:21 kenny kernel: mdcmd (20864): spindown 1 Sep 13 14:37:41 kenny kernel: mdcmd (20868): spindown 1 Sep 13 14:38:01 kenny kernel: mdcmd (20872): spindown 1 Sep 13 14:38:23 kenny kernel: mdcmd (20876): spindown 1 Sep 13 14:38:44 kenny kernel: mdcmd (20880): spindown 1 Sep 13 14:39:04 kenny kernel: mdcmd (20884): spindown 1 Sep 13 14:39:24 kenny kernel: mdcmd (20888): spindown 1 Sep 13 14:39:54 kenny kernel: mdcmd (20893): spindown 1 Sep 13 14:40:46 kenny kernel: mdcmd (20901): spindown 1 Sep 13 14:41:06 kenny kernel: mdcmd (20905): spindown 1 Sep 13 14:41:27 kenny kernel: mdcmd (20909): spindown 1 Sep 13 14:41:48 kenny kernel: mdcmd (20913): spindown 1 Sep 13 14:42:19 kenny kernel: mdcmd (20918): spindown 1 Sep 13 14:42:39 kenny kernel: mdcmd (20922): spindown 1 Sep 13 14:43:00 kenny kernel: mdcmd (20926): spindown 1 Sep 13 14:43:30 kenny kernel: mdcmd (20931): spindown 1 Sep 13 14:43:50 kenny kernel: mdcmd (20935): spindown 1 Sep 13 14:59:48 kenny kernel: mdcmd (21067): spindown 2 Sep 13 15:00:09 kenny kernel: mdcmd (21071): spindown 1 Sep 13 15:00:50 kenny kernel: mdcmd (21077): spindown 1 Sep 13 15:01:11 kenny kernel: mdcmd (21081): spindown 1 Sep 13 15:01:31 kenny kernel: mdcmd (21085): spindown 1 Sep 13 15:01:51 kenny kernel: mdcmd (21089): spindown 1 Sep 13 15:02:11 kenny kernel: mdcmd (21092): spindown 1 Sep 13 15:02:31 kenny kernel: mdcmd (21096): spindown 1 Sep 13 15:03:23 kenny kernel: mdcmd (21104): spindown 1 Sep 13 15:03:44 kenny kernel: mdcmd (21108): spindown 1 Sep 13 15:04:04 kenny kernel: mdcmd (21112): spindown 1 Sep 13 15:04:24 kenny kernel: mdcmd (21116): spindown 1 Sep 13 15:04:45 kenny kernel: mdcmd (21120): spindown 1 Sep 13 15:05:05 kenny kernel: mdcmd (21124): spindown 1 Sep 13 15:05:26 kenny kernel: mdcmd (21127): spindown 1 Sep 13 15:05:46 kenny kernel: mdcmd (21131): spindown 1 Sep 13 15:06:08 kenny kernel: mdcmd (21135): spindown 1 Sep 13 15:06:59 kenny kernel: mdcmd (21143): spindown 1 Sep 13 15:07:19 kenny kernel: mdcmd (21147): spindown 1 Sep 13 15:07:40 kenny kernel: mdcmd (21151): spindown 1 Sep 13 15:08:00 kenny kernel: mdcmd (21155): spindown 1 Sep 13 15:08:41 kenny kernel: mdcmd (21161): spindown 1 Sep 13 15:09:01 kenny kernel: mdcmd (21165): spindown 1 Sep 13 15:09:22 kenny kernel: mdcmd (21169): spindown 1 Sep 13 15:10:13 kenny kernel: mdcmd (21177): spindown 1 Sep 13 15:10:13 kenny kernel: mdcmd (21177): spindown 1 Sep 13 15:10:33 kenny kernel: mdcmd (21181): spindown 1 Sep 13 15:10:54 kenny kernel: mdcmd (21185): spindown 1 Sep 13 15:11:14 kenny kernel: mdcmd (21189): spindown 1 Sep 13 15:12:37 kenny kernel: mdcmd (21201): spindown 1 Sep 13 15:12:57 kenny kernel: mdcmd (21205): spindown 1 Sep 13 15:13:27 kenny kernel: mdcmd (21210): spindown 1 Sep 13 15:13:48 kenny kernel: mdcmd (21214): spindown 1 Sep 13 15:14:08 kenny kernel: mdcmd (21218): spindown 1 Sep 13 15:14:29 kenny kernel: mdcmd (21222): spindown 1 Sep 13 15:14:50 kenny kernel: mdcmd (21226): spindown 1 Sep 13 15:15:10 kenny kernel: mdcmd (21230): spindown 1 Sep 13 15:15:30 kenny kernel: mdcmd (21234): spindown 1 Sep 13 15:15:43 kenny kernel: mdcmd (21236): spindown 1 Sep 13 15:16:04 kenny kernel: mdcmd (21240): spindown 1 Sep 13 15:16:24 kenny kernel: mdcmd (21243): spindown 1 Sep 13 15:16:44 kenny kernel: mdcmd (21247): spindown 1 Sep 13 15:17:05 kenny kernel: mdcmd (21251): spindown 1 Sep 13 15:17:25 kenny kernel: mdcmd (21255): spindown 1 Sep 13 15:17:46 kenny kernel: mdcmd (21259): spindown 1 Sep 13 15:18:06 kenny kernel: mdcmd (21262): spindown 1 Sep 13 15:18:26 kenny kernel: mdcmd (21266): spindown 1 Sep 13 15:18:47 kenny kernel: mdcmd (21270): spindown 1 Sep 13 15:18:57 kenny kernel: BUG: unable to handle kernel paging request at f83ce000 Sep 13 15:18:57 kenny kernel: IP: [<f83c48e4>] md_cmd_proc_read+0x41/0x54 [md_mod] Sep 13 15:18:58 kenny kernel: *pdpt = 0000000001447001 *pde = 0000000037410067 *pte = 0000000000000000 Sep 13 15:18:58 kenny kernel: Oops: 0000 [#1] SMP Sep 13 15:18:58 kenny kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.1/ide0/0.1/block/hdb/stat Sep 13 15:18:58 kenny kernel: Modules linked in: md_mod xor ide_gd_mod i2c_i801 i2c_core ata_piix piix sata_mv r8169 Sep 13 15:18:58 kenny kernel: Sep 13 15:18:58 kenny kernel: Pid: 17009, comm: cat Not tainted (2.6.32.9-unRAID #5) Sep 13 15:18:58 kenny kernel: EIP: 0060:[<f83c48e4>] EFLAGS: 00010202 CPU: 1 Sep 13 15:18:58 kenny kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod] Sep 13 15:18:58 kenny kernel: EAX: f0fa5f38 EBX: fffff924 ECX: 3ffff0b4 EDX: fffff924 Sep 13 15:18:58 kenny kernel: ESI: f83ce000 EDI: c62f2654 EBP: f0fa5f04 ESP: f0fa5ef4 Sep 13 15:18:58 kenny kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Sep 13 15:18:58 kenny kernel: Process cat (pid: 17009, ti=f0fa4000 task=f76146e0 task.ti=f0fa4000) Sep 13 15:18:58 kenny kernel: Stack: Sep 13 15:18:58 kenny kernel: f0fa5f38 f83c48a3 00001000 c62ef000 f0fa5f4c c109d5f5 00000400 f0fa5f3c Sep 13 15:18:58 kenny kernel: <0> 00000000 00001000 00000000 00000400 0804ec00 f6d99c60 00000c00 f6d99c60 Sep 13 15:18:58 kenny kernel: <0> 00000400 c62ef000 00000001 f6d99c60 c109d4ea fffffffb f0fa5f70 c1099f72 Sep 13 15:18:58 kenny kernel: Call Trace: Sep 13 15:18:58 kenny kernel: [<f83c48a3>] ? md_cmd_proc_read+0x0/0x54 [md_mod] Sep 13 15:18:58 kenny kernel: [<c109d5f5>] ? proc_file_read+0x10b/0x22d Sep 13 15:18:58 kenny kernel: [<c109d4ea>] ? proc_file_read+0x0/0x22d Sep 13 15:18:58 kenny kernel: [<c1099f72>] ? proc_reg_read+0x56/0x6a Sep 13 15:18:58 kenny kernel: [<c1099f1c>] ? proc_reg_read+0x0/0x6a Sep 13 15:18:58 kenny kernel: [<c106cbd8>] ? vfs_read+0x8a/0x114 Sep 13 15:18:58 kenny kernel: [<c106cf6f>] ? sys_read+0x3b/0x60 Sep 13 15:18:58 kenny kernel: [<c1002935>] ? syscall_call+0x7/0xb Sep 13 15:18:58 kenny kernel: Code: 55 f0 e8 6a 22 d7 c8 8d 50 01 29 f2 39 d3 7c 0b 8b 45 0c 89 d3 c7 00 01 00 00 00 8b 45 f0 89 d9 81 c6 ac 9d 3c f8 c1 e9 02 89 38 <f3> a5 89 d9 83 e1 03 74 02 f3 a4 5a 89 d8 5b 5e 5f 5d c3 55 89 Sep 13 15:18:58 kenny kernel: EIP: [<f83c48e4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:f0fa5ef4 Sep 13 15:18:58 kenny kernel: CR2: 00000000f83ce000 Sep 13 15:18:58 kenny kernel: ---[ end trace fd001779b3dd0b2d ]---
September 15, 201015 yr Author Hi Joe, I ran the reiserfs on all my hard drives (including the cache) and everything came back with no errors. Anything else you can recommend to help fix my crashing problems?
September 15, 201015 yr Anything else you can recommend to help fix my crashing problems? Posting your complete hardware is a start in the right direction
September 15, 201015 yr Sep 13 15:18:26 kenny kernel: mdcmd (21266): spindown 1 Sep 13 15:18:47 kenny kernel: mdcmd (21270): spindown 1 Sep 13 15:18:57 kenny kernel: BUG: unable to handle kernel paging request at f83ce000 Sep 13 15:18:57 kenny kernel: IP: [<f83c48e4>] md_cmd_proc_read+0x41/0x54 [md_mod] Sep 13 15:18:58 kenny kernel: *pdpt = 0000000001447001 *pde = 0000000037410067 *pte = 0000000000000000 Sep 13 15:18:58 kenny kernel: Oops: 0000 [#1] SMP Sep 13 15:18:58 kenny kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.1/ide0/0.1/block/hdb/stat Sep 13 15:18:58 kenny kernel: Modules linked in: md_mod xor ide_gd_mod i2c_i801 i2c_core ata_piix piix sata_mv r8169 Sep 13 15:18:58 kenny kernel: Sep 13 15:18:58 kenny kernel: Pid: 17009, comm: cat Not tainted (2.6.32.9-unRAID #5) Sep 13 15:18:58 kenny kernel: EIP: 0060:[<f83c48e4>] EFLAGS: 00010202 CPU: 1 Sep 13 15:18:58 kenny kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod] Sep 13 15:18:58 kenny kernel: EAX: f0fa5f38 EBX: fffff924 ECX: 3ffff0b4 EDX: fffff924 Sep 13 15:18:58 kenny kernel: ESI: f83ce000 EDI: c62f2654 EBP: f0fa5f04 ESP: f0fa5ef4 Sep 13 15:18:58 kenny kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Sep 13 15:18:58 kenny kernel: Process cat (pid: 17009, ti=f0fa4000 task=f76146e0 task.ti=f0fa4000) Sep 13 15:18:58 kenny kernel: Stack: Sep 13 15:18:58 kenny kernel: f0fa5f38 f83c48a3 00001000 c62ef000 f0fa5f4c c109d5f5 00000400 f0fa5f3c Sep 13 15:18:58 kenny kernel: <0> 00000000 00001000 00000000 00000400 0804ec00 f6d99c60 00000c00 f6d99c60 Sep 13 15:18:58 kenny kernel: <0> 00000400 c62ef000 00000001 f6d99c60 c109d4ea fffffffb f0fa5f70 c1099f72 Sep 13 15:18:58 kenny kernel: Call Trace: Sep 13 15:18:58 kenny kernel: [<f83c48a3>] ? md_cmd_proc_read+0x0/0x54 [md_mod] Sep 13 15:18:58 kenny kernel: [<c109d5f5>] ? proc_file_read+0x10b/0x22d Sep 13 15:18:58 kenny kernel: [<c109d4ea>] ? proc_file_read+0x0/0x22d Sep 13 15:18:58 kenny kernel: [<c1099f72>] ? proc_reg_read+0x56/0x6a Sep 13 15:18:58 kenny kernel: [<c1099f1c>] ? proc_reg_read+0x0/0x6a Sep 13 15:18:58 kenny kernel: [<c106cbd8>] ? vfs_read+0x8a/0x114 Sep 13 15:18:58 kenny kernel: [<c106cf6f>] ? sys_read+0x3b/0x60 Sep 13 15:18:58 kenny kernel: [<c1002935>] ? syscall_call+0x7/0xb Sep 13 15:18:58 kenny kernel: Code: 55 f0 e8 6a 22 d7 c8 8d 50 01 29 f2 39 d3 7c 0b 8b 45 0c 89 d3 c7 00 01 00 00 00 8b 45 f0 89 d9 81 c6 ac 9d 3c f8 c1 e9 02 89 38 <f3> a5 89 d9 83 e1 03 74 02 f3 a4 5a 89 d8 5b 5e 5f 5d c3 55 89 Sep 13 15:18:58 kenny kernel: EIP: [<f83c48e4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:f0fa5ef4 Sep 13 15:18:58 kenny kernel: CR2: 00000000f83ce000 Sep 13 15:18:58 kenny kernel: ---[ end trace fd001779b3dd0b2d ]--- It looks to me your problem is same as this one. http://lime-technology.com/forum/index.php?topic=6302.0 May 7 03:20:45 Tower kernel: mdcmd (26): spindown 0 May 7 03:20:46 Tower kernel: mdcmd (27): spindown 1 May 7 03:20:47 Tower kernel: mdcmd (28): spindown 2 May 7 03:20:48 Tower kernel: mdcmd (30): spindown 3 May 7 03:20:48 Tower kernel: BUG: unable to handle kernel paging request at f8ac8000 May 7 03:20:48 Tower kernel: IP: [<f8abe8c4>] md_cmd_proc_read+0x41/0x54 [md_mod] May 7 03:20:48 Tower kernel: *pdpt = 0000000001443001 *pde = 00000000039fe067 *pte = 0000000000000000 May 7 03:20:48 Tower kernel: Oops: 0000 [#1] SMP May 7 03:20:48 Tower kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.5/host5/target5:0:0/5:0:0:0/block/sdi/stat May 7 03:20:48 Tower kernel: Modules linked in: md_mod xor ata_piix e1000e mvsas libsas scst scsi_transport_sas [last unloaded: md_mod] May 7 03:20:48 Tower kernel: Pid: 1920, comm: emhttp Not tainted (2.6.32.9-unRAID #1) X7SPA-HF May 7 03:20:48 Tower kernel: EIP: 0060:[<f8abe8c4>] EFLAGS: 00210203 CPU: 1 May 7 03:20:48 Tower kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod] May 7 03:20:48 Tower kernel: EAX: c3979f38 EBX: fffff24a ECX: 3fffef6f EDX: fffff24a May 7 03:20:48 Tower kernel: ESI: f8ac7ffe EDI: f727948c EBP: c3979f04 ESP: c3979ef4 May 7 03:20:48 Tower kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 May 7 03:20:48 Tower kernel: Process emhttp (pid: 1920, ti=c3978000 task=f6ca0000 task.ti=c3978000) May 7 03:20:48 Tower kernel: Stack: May 7 03:20:48 Tower kernel: c3979f38 f8abe883 00000000 f7276000 c3979f4c c109d56d 00000400 c3979f3c May 7 03:20:48 Tower kernel: <0> 00000000 00000400 00000000 00000400 b78c7000 f6dab9c0 00000000 f6dab9c0 May 7 03:20:48 Tower kernel: <0> 00000400 f7276000 00000001 f6dab9c0 c109d462 fffffffb c3979f70 c1099eea May 7 03:20:48 Tower kernel: Call Trace: May 7 03:20:48 Tower kernel: [<f8abe883>] ? md_cmd_proc_read+0x0/0x54 [md_mod] May 7 03:20:48 Tower kernel: [<c109d56d>] ? proc_file_read+0x10b/0x22d May 7 03:20:48 Tower kernel: [<c109d462>] ? proc_file_read+0x0/0x22d May 7 03:20:48 Tower kernel: [<c1099eea>] ? proc_reg_read+0x56/0x6a May 7 03:20:48 Tower kernel: [<c1099e94>] ? proc_reg_read+0x0/0x6a May 7 03:20:48 Tower kernel: [<c106cb60>] ? vfs_read+0x8a/0x114 May 7 03:20:48 Tower kernel: [<c106cef7>] ? sys_read+0x3b/0x60 May 7 03:20:48 Tower kernel: [<c1002935>] ? syscall_call+0x7/0xb May 7 03:20:48 Tower kernel: Code: 55 f0 e8 da 47 67 c8 8d 50 01 29 f2 39 d3 7c 0b 8b 45 0c 89 d3 c7 00 01 00 00 00 8b 45 f0 89 d9 81 c6 a0 3d ac f8 c1 e9 02 89 38 <f3> a5 89 d9 83 e1 03 74 02 f3 a4 5a 89 d8 5b 5e 5f 5d c3 55 89 May 7 03:20:48 Tower kernel: EIP: [<f8abe8c4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c3979ef4 May 7 03:20:48 Tower kernel: CR2: 00000000f8ac8000 May 7 03:20:48 Tower kernel: ---[ end trace 21bf876656a0f23e ]---
September 16, 201015 yr Author Anything else you can recommend to help fix my crashing problems? Posting your complete hardware is a start in the right direction This is my setup; Supermicro AOC-SAT2-MV8 8 Port SATA Card Pcix 64BIT 133MHZ RAID Intel BOXD945GCLF2 MINI-ITX Kingston ValueRAM KVR667D2N5/2G PC2-5300 2GB 1X2GB DDR2-667 6 Hard drives 1 parity drive 1 cache drive the cache drive has a 2 GB swap file enabled. The packages I run are; Unmenu unraidweb unraid notify cache_dirs monthly parity checker Clean powerdown unrar & infozip Rtorrent I also have a flash drive outside of the array mounted and a cron setup to copy the contents of that flash drive every day. Thanks GK20, i'm going to keep an eye on that thread but it doesn't seem like much has hapenned in the last 4 days.
September 16, 201015 yr Author Here are more logs. Again there is an abnormal amount of spindown 1 attempts. So one thing I noticed is that I get emails telling me that my disk 1 is overheating (this is not abnormal, i have it on a low threshold for now), but everytime i go into the unraid interface it shows that my disk 1 is sleeping... and it should be. All of my content goes to disk 4, it's the only one awake unless I try to access some archived items in the other drives. So, how can I find out what wakes up disk 1? (if anything wakes it up for that matter) and why is it having such a hard time spinning it down? Sep 16 15:59:30 kenny kernel: mdcmd (3869): spindown 1 Sep 16 15:59:50 kenny kernel: mdcmd (3873): spindown 1 Sep 16 16:00:11 kenny kernel: mdcmd (3877): spindown 1 Sep 16 16:00:31 kenny kernel: mdcmd (3881): spindown 1 Sep 16 16:00:52 kenny kernel: mdcmd (3885): spindown 1 Sep 16 16:01:12 kenny kernel: mdcmd (3889): spindown 1 Sep 16 16:01:32 kenny kernel: mdcmd (3893): spindown 1 Sep 16 16:01:52 kenny kernel: mdcmd (3897): spindown 1 Sep 16 16:02:12 kenny kernel: mdcmd (3901): spindown 1 Sep 16 16:02:25 kenny kernel: mdcmd (3903): spindown 1 Sep 16 16:02:46 kenny kernel: mdcmd (3907): spindown 1 Sep 16 16:03:16 kenny kernel: mdcmd (3912): spindown 1 Sep 16 16:03:36 kenny kernel: mdcmd (3916): spindown 1 Sep 16 16:04:07 kenny kernel: mdcmd (3921): spindown 1 Sep 16 16:04:27 kenny kernel: mdcmd (3925): spindown 1 Sep 16 16:04:37 kenny kernel: BUG: unable to handle kernel paging request at f83ce000 Sep 16 16:04:37 kenny kernel: IP: [<f83c48e4>] md_cmd_proc_read+0x41/0x54 [md_mod] Sep 16 16:04:37 kenny kernel: *pdpt = 0000000001447001 *pde = 0000000037410067 *pte = 0000000000000000 Sep 16 16:04:37 kenny kernel: Oops: 0000 [#1] SMP Sep 16 16:04:37 kenny kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1f.1/ide0/0.1/block/hdb/stat Sep 16 16:04:38 kenny kernel: Modules linked in: md_mod xor ide_gd_mod i2c_i801 i2c_core ata_piix piix sata_mv r8169 Sep 16 16:04:38 kenny kernel: Sep 16 16:04:39 kenny kernel: Pid: 4470, comm: cat Not tainted (2.6.32.9-unRAID #5) Sep 16 16:04:39 kenny kernel: EIP: 0060:[<f83c48e4>] EFLAGS: 00010203 CPU: 1 Sep 16 16:04:39 kenny kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod] Sep 16 16:04:39 kenny kernel: EAX: c1fe7f38 EBX: fffff85b ECX: 3ffff081 EDX: fffff85b Sep 16 16:04:39 kenny kernel: ESI: f83ce000 EDI: f0045654 EBP: c1fe7f04 ESP: c1fe7ef4 Sep 16 16:04:39 kenny kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Sep 16 16:04:39 kenny kernel: Process cat (pid: 4470, ti=c1fe6000 task=f24c3700 task.ti=c1fe6000) Sep 16 16:04:39 kenny kernel: Stack: Sep 16 16:04:39 kenny kernel: c1fe7f38 f83c48a3 00001000 f0042000 c1fe7f4c c109d5f5 00000400 c1fe7f3c Sep 16 16:04:39 kenny kernel: <0> 00000000 00001000 00000000 00000400 0804ec00 f7656d20 00000c00 f7656d20 Sep 16 16:04:39 kenny kernel: <0> 00000400 f0042000 00000001 f7656d20 c109d4ea fffffffb c1fe7f70 c1099f72 Sep 16 16:04:39 kenny kernel: Call Trace: Sep 16 16:04:39 kenny kernel: [<f83c48a3>] ? md_cmd_proc_read+0x0/0x54 [md_mod] Sep 16 16:04:39 kenny kernel: [<c109d5f5>] ? proc_file_read+0x10b/0x22d Sep 16 16:04:39 kenny kernel: [<c109d4ea>] ? proc_file_read+0x0/0x22d Sep 16 16:04:39 kenny kernel: [<c1099f72>] ? proc_reg_read+0x56/0x6a Sep 16 16:04:39 kenny kernel: [<c1099f1c>] ? proc_reg_read+0x0/0x6a Sep 16 16:04:39 kenny kernel: [<c106cbd8>] ? vfs_read+0x8a/0x114 Sep 16 16:04:39 kenny kernel: [<c106cf6f>] ? sys_read+0x3b/0x60 Sep 16 16:04:39 kenny kernel: [<c1002935>] ? syscall_call+0x7/0xb Sep 16 16:04:39 kenny kernel: Code: 55 f0 e8 6a 22 d7 c8 8d 50 01 29 f2 39 d3 7c 0b 8b 45 0c 89 d3 c7 00 01 00 00 00 8b 45 f0 89 d9 81 c6 ac 9d 3c f8 c1 e9 02 89 38 <f3> a5 89 d9 83 e1 03 74 02 f3 a4 5a 89 d8 5b 5e 5f 5d c3 55 89 Sep 16 16:04:39 kenny kernel: EIP: [<f83c48e4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:c1fe7ef4 Sep 16 16:04:39 kenny kernel: CR2: 00000000f83ce000 Sep 16 16:04:39 kenny kernel: ---[ end trace 5a9b18981de91adc ]--- Sep 16 16:04:57 kenny kernel: mdcmd (3930): spindown 1 Sep 16 16:05:17 kenny kernel: mdcmd (3934): spindown 1 Sep 16 16:05:37 kenny kernel: mdcmd (3938): spindown 1 Sep 16 16:06:08 kenny kernel: mdcmd (3944): spindown 1 Sep 16 16:06:28 kenny kernel: mdcmd (3947): spindown 1 Sep 16 16:06:48 kenny kernel: mdcmd (3951): spindown 1 Sep 16 16:07:08 kenny kernel: mdcmd (3955): spindown 1 Sep 16 16:07:29 kenny kernel: mdcmd (3959): spindown 1 Sep 16 16:07:49 kenny kernel: mdcmd (3963): spindown 1 Sep 16 16:08:09 kenny kernel: mdcmd (3967): spindown 1 Sep 16 16:08:30 kenny kernel: mdcmd (3971): spindown 1 Sep 16 16:08:50 kenny kernel: mdcmd (3975): spindown 1 Sep 16 16:09:10 kenny kernel: mdcmd (3979): spindown 1 Sep 16 16:09:30 kenny kernel: mdcmd (3983): spindown 1 Sep 16 16:09:51 kenny kernel: mdcmd (3986): spindown 1
September 16, 201015 yr flixxx- Please send an email to me, [email protected] so that I can give you a patched release that may fix this problem.
September 16, 201015 yr Anything else you can recommend to help fix my crashing problems? Posting your complete hardware is a start in the right direction This is my setup; Supermicro AOC-SAT2-MV8 8 Port SATA Card Pcix 64BIT 133MHZ RAID Intel BOXD945GCLF2 MINI-ITX Kingston ValueRAM KVR667D2N5/2G PC2-5300 2GB 1X2GB DDR2-667 6 Hard drives 1 parity drive 1 cache drive This is not your complete setup. The power supply and the case (especially for someone using mini-ITX board) are very important too. I believe that not many will buy a brand new mini-ITX MB with only 2 SATA ports for Unraid as they are usually way more expensive compared to the regular uATX. Obviously you used this in HTPC and no one will buy a big case and reasonable powered PSU for that - instead they will use a tiny case and a small psu as the noise is a big NONO. Then you probably got a dedicated player and decided to reuse the parts you had - nothing wrong with that too, but did you change the case and the power supply - we do not know. And the syslog does not show these. We only know that you have overheating problems (possible cause is a tiny and not adequate case) and your server crashes "every week or so" which can be due to a small, non adequate PS or not clean power (ripples) if you used some 'house brand" that came with your case. Now the hard drives - you have 8 in total but... are the Seagate's - some of them are with buggy firmware and they may cause you the problems you have; are they WD's and are they the advanced formatting, were they jumpered,,, Pay attention if you have newer WD and they were overheating as there is a rare report from a Russian data recovery lab that shows that the heads of the newer WD HDs are very heat sensitive and prolonged use above 45C may cause a failure. See- it may not be a bug in Unraid but hardware problem.
September 16, 201015 yr Author Anything else you can recommend to help fix my crashing problems? Posting your complete hardware is a start in the right direction This is my setup; Supermicro AOC-SAT2-MV8 8 Port SATA Card Pcix 64BIT 133MHZ RAID Intel BOXD945GCLF2 MINI-ITX Kingston ValueRAM KVR667D2N5/2G PC2-5300 2GB 1X2GB DDR2-667 6 Hard drives 1 parity drive 1 cache drive This is not your complete setup. The power supply and the case (especially for someone using mini-ITX board) are very important too. I believe that not many will buy a brand new mini-ITX MB with only 2 SATA ports for Unraid as they are usually way more expensive compared to the regular uATX. Obviously you used this in HTPC and no one will buy a big case and reasonable powered PSU for that - instead they will use a tiny case and a small psu as the noise is a big NONO. Then you probably got a dedicated player and decided to reuse the parts you had - nothing wrong with that too, but did you change the case and the power supply - we do not know. And the syslog does not show these. We only know that you have overheating problems (possible cause is a tiny and not adequate case) and your server crashes "every week or so" which can be due to a small, non adequate PS or not clean power (ripples) if you used some 'house brand" that came with your case. Now the hard drives - you have 8 in total but... are the Seagate's - some of them are with buggy firmware and they may cause you the problems you have; are they WD's and are they the advanced formatting, were they jumpered,,, Pay attention if you have newer WD and they were overheating as there is a rare report from a Russian data recovery lab that shows that the heads of the newer WD HDs are very heat sensitive and prolonged use above 45C may cause a failure. See- it may not be a bug in Unraid but hardware problem. No no, i bought the mobo for power saving reasons. it's in a full tower and i have approximately 5 fans. My hard drive avg at about 30Celsius and i get an overheat email at 35. They only overheat if 2 hard drives on top of each other are spun up. I also ran smart reports and all the drives past. I'm going to try Tom's patch and see how it goes.
September 17, 201015 yr Author Here is something else I just noticed. I did a tail on my syslog and watched it do a spindown; Sep 16 20:14:57 kenny kernel: mdcmd (2454): spindown 0 Sep 16 20:14:57 kenny kernel: mdcmd (2455): spindown 1 Sep 16 20:14:57 kenny kernel: mdcmd (2456): spindown 2 Sep 16 20:14:58 kenny kernel: mdcmd (2457): spindown 3 Sep 16 20:14:58 kenny kernel: mdcmd (2458): spindown 4 Sep 16 20:14:59 kenny kernel: mdcmd (2459): spindown 5 Sep 16 20:14:59 kenny emhttp: shcmd (42): /usr/sbin/hdparm -y /dev/hdb >/dev/null Sep 16 20:15:01 kenny kernel: mdcmd (2460): spindown 6 But then every 20 seconsd i get this; Sep 16 20:15:26 kenny kernel: mdcmd (2466): spindown 1 Sep 16 20:15:47 kenny kernel: mdcmd (2470): spindown 1 Sep 16 20:16:07 kenny kernel: mdcmd (2474): spindown 1 Sep 16 20:16:27 kenny kernel: mdcmd (2477): spindown 1 Sep 16 20:16:58 kenny kernel: mdcmd (2483): spindown 1 It's infinite, until it crashes.
September 17, 201015 yr They only overheat if 2 hard drives on top of each other are spun up. What happens during a parity check when all drives are spun up?
September 17, 201015 yr Author They only overheat if 2 hard drives on top of each other are spun up. What happens during a parity check when all drives are spun up? It's not an overheat problem, at the most they get to 40 degrees which for me is not even close to a danger zone. Only 3 hard drives are close together, the others are spaced well enough in my case and they never go above 35. besides at this point i'm noticing an unlimited amount of spindown attempts that seems to be crashing the server, i'll wait for Tom's patch to see if it solves the problem.
September 20, 201015 yr Author Hello everyone, i'm waiting for the patch that Tom said he'll send but in the meantime can anyone suggest what might be causing this unlimited "spindown" on disk1? it only happens on "disk 1", if I turn off spin down for that disk then i don't get the spindown requests every 20 seconds in the logs. I ran a long smart test and it passed, it's an IDE Hard drive that's on there. Any suggestions would be helpful.
Archived
This topic is now archived and is closed to further replies.