Hello Guys,

 

Just received this trace in my syslog and I am quite concerned as to the gravity of it. Perhaps someone could shed some light on this dump.

 

Running 4.5.6 (plus license) on a dfi lanparty nf4 sli-dr with 6/8 sata slots being used.

 

Nov  2 13:46:34 Clara-Belle kernel: BUG: unable to handle kernel paging request at f82c0000

Nov  2 13:46:34 Clara-Belle kernel: IP: [<f82b68e4>] md_cmd_proc_read+0x41/0x54 [md_mod]

Nov  2 13:46:34 Clara-Belle kernel: *pdpt = 0000000001447001 *pde = 0000000037410067 *pte = 0000000000000000

Nov  2 13:46:34 Clara-Belle kernel: Oops: 0000 [#1] SMP

Nov  2 13:46:34 Clara-Belle kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:09.0/0000:01:08.0/host6/target6:0:0/6:0:0:0/block/sdf/stat

Nov  2 13:46:34 Clara-Belle kernel: Modules linked in: ntfs md_mod xor forcedeth skge sata_sil sata_nv amd74xx

Nov  2 13:46:34 Clara-Belle kernel:

Nov  2 13:46:34 Clara-Belle kernel: Pid: 1568, comm: emhttp Not tainted (2.6.32.9-unRAID #5)

Nov  2 13:46:34 Clara-Belle kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:09.0/0000:01:08.0/host6/target6:0:0/6:0:0:0/block/sdf/stat

Nov  2 13:46:34 Clara-Belle kernel: Modules linked in: ntfs md_mod xor forcedeth skge sata_sil sata_nv amd74xx

Nov  2 13:46:34 Clara-Belle kernel:

Nov  2 13:46:34 Clara-Belle kernel: Pid: 1568, comm: emhttp Not tainted (2.6.32.9-unRAID #5)

Nov  2 13:46:34 Clara-Belle kernel: EIP: 0060:[<f82b68e4>] EFLAGS: 00210212 CPU: 0

Nov  2 13:46:34 Clara-Belle kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod]

Nov  2 13:46:34 Clara-Belle kernel: EAX: f6f75f38 EBX: fffffa0c ECX: 3ffff075 EDX: fffffa0c

Nov  2 13:46:34 Clara-Belle kernel: ESI: f82bfffe EDI: c5cca838 EBP: f6f75f04 ESP: f6f75ef4

Nov  2 13:46:34 Clara-Belle kernel:  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Nov  2 13:46:34 Clara-Belle kernel: <0> 00000400 c5cc7000 00000001 f75803c0 c109d4ea fffffffb f6f75f70 c1099f72

Nov  2 13:46:34 Clara-Belle kernel: Call Trace:

Nov  2 13:46:34 Clara-Belle kernel:  [<f82b68a3>] ? md_cmd_proc_read+0x0/0x54 [md_mod]

Nov  2 13:46:34 Clara-Belle kernel:  [<c109d5f5>] ? proc_file_read+0x10b/0x22d

Nov  2 13:46:34 Clara-Belle kernel:  [<c109d4ea>] ? proc_file_read+0x0/0x22d

Nov  2 13:46:34 Clara-Belle kernel:  [<c1099f72>] ? proc_reg_read+0x56/0x6a

Nov  2 13:46:34 Clara-Belle kernel:  [<c1099f1c>] ? proc_reg_read+0x0/0x6a

Nov  2 13:46:34 Clara-Belle kernel:  [<c106cbd8>] ? vfs_read+0x8a/0x114

Nov  2 13:46:34 Clara-Belle kernel:  [<c106cf6f>] ? sys_read+0x3b/0x60

Nov  2 13:46:34 Clara-Belle kernel:  [<c1002935>] ? syscall_call+0x7/0xb

Nov  2 13:46:34 Clara-Belle kernel: Code: 55 f0 e8 6a 02 e8 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 bd 2b 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

Nov  2 13:46:34 Clara-Belle kernel: EIP: [<f82b68e4>] md_cmd_proc_read+0x41/0x54 [md_mod] SS:ESP 0068:f6f75ef4

Nov  2 13:46:34 Clara-Belle kernel: CR2: 00000000f82c0000

Nov  2 13:46:34 Clara-Belle kernel: ---[ end trace 9966278a603ae92c ]---

 

sdf appears to be my sixth disk in the array.

 

disk5 device: pci-0000:01:08.0-scsi-1:0:0:0 host6 (sdf) WDC_WD10EAVS-00D7B0_WD-WCAU48521540

 

Subsequently after I got this dump, the system hung completely and I was not able to ssh or log in via the console. I had to force a restart and disks are currently being checked for parity on reboot as I type this.

 

The first line: "BUG: unable to handle kernel paging request at f82c0000" could this be due to a lack of swap space? I have not allocated any swap space for the server. Perhaps next move would be to add a cache drive / swap file.

 

Any help would be greatly appreciated.

 

Thanks.

 

^

^

 

http://lime-technology.com/forum/index.php?topic=8027.0

GK20, thanks for your reply.

 

Looks like this bug has been around forever, with no solution in sight. Nonetheless, I just added a swapfile to the server.

 

Part of the Oops club, huh? How honored...

GK20, thanks for your reply.

 

Looks like this bug has been around forever, with no solution in sight. Nonetheless, I just added a swapfile to the server.

 

Part of the Oops club, huh? How honored...

Don't forget, unless the swap file is on a disk not assigned to the array, the array will not stop when you press the "Stop" button.

 

You must FIRST disable the swap file, then stop the array.

Thanks Joe L.

 

I'm assuming that the Clean Powerdown package takes care of this on a powerdown, correct?

Thanks Joe L.

 

I'm assuming that the Clean Powerdown package takes care of this on a powerdown, correct?

It does nothing to disable swap, therefore, if your swap file is on your data disk, or on the cache disk, the array will not stop.

 

You can try it yourself.  Press the "Stop" button.  It will sit there waiting, saying something like "Unmounting..."

 

You'll need to add a swapoff command to the powerdown package, or locate your swap file elsewhere.

Tried that after I posted. Had to stop sickbeard, sabnzbd, mysqld and swap before I was able to see the array as stopped. Guess I have to modify the powerdown package for this four processes.