I hit the stop button on my server last night and it went to unmounting the drives but that's it.  I could telnet in but the webpage just said unmounting.  I waited about 15 min.  I captured a syslog but it doesn't show anything.

 

I've also attached a syslog of the sever after the reboot it went straight to a parity check since it wasn't a clean shutdown.

capture_from_telnet_after_stop_command_syslog.txt

after_rebootsyslog-2010-04-30.txt

You had a kernel oops when it went to un-mount the file-system on one of your disks.

pr 20 18:34:03 Backup kernel: BUG: unable to handle kernel NULL pointer dereference at 00000010

Apr 20 18:34:03 Backup kernel: IP: [<c1030b21>] wq_per_cpu+0x1/0x19

Apr 20 18:34:03 Backup kernel: *pdpt = 00000000046e1001 *pde = 0000000000000000

Apr 20 18:34:03 Backup kernel: Oops: 0000 [#1] SMP

Apr 20 18:34:03 Backup kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1c.0/0000:05:00.0/host5/target5:0:0/5:0:0:0/block/sdd/stat

Apr 20 18:34:03 Backup kernel: Modules linked in: md_mod xor r8169 pata_jmicron jmicron ahci sata_mv

Apr 20 18:34:03 Backup kernel:

Apr 20 18:34:03 Backup kernel: Pid: 2427, comm: emhttp Not tainted (2.6.32.9-unRAID #1) System Product Name

Apr 20 18:34:03 Backup kernel: EIP: 0060:[<c1030b21>] EFLAGS: 00210246 CPU: 3

Apr 20 18:34:03 Backup kernel: EIP is at wq_per_cpu+0x1/0x19

Apr 20 18:34:03 Backup kernel: EAX: 00000000 EBX: f8512134 ECX: f8512134 EDX: 00000003

Apr 20 18:34:03 Backup kernel: ESI: f8512144 EDI: 00000000 EBP: f6b25e1c ESP: f6b25e04

Apr 20 18:34:03 Backup kernel:  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068

Apr 20 18:34:03 Backup kernel: Process emhttp (pid: 2427, ti=f6b24000 task=c47e06e0 task.ti=f6b24000)

Apr 20 18:34:03 Backup kernel: Stack:

Apr 20 18:34:03 Backup kernel:  f6b25e1c c103134e ffffffff f76428d4 f7642880 c148d000 f6b25e28 c10313cc

Apr 20 18:34:03 Backup kernel: <0> 0000000a f6b25eb0 c10c0203 03115048 f6b25e50 c4541200 f6b25ed0 00000010

Apr 20 18:34:03 Backup kernel: <0> 00000000 f8502000 c730e000 f79e3000 f7271ec0 00000001 00000000 00000004

Apr 20 18:34:03 Backup kernel: Call Trace:

Apr 20 18:34:03 Backup kernel:  [<c103134e>] ? queue_delayed_work_on+0x44/0x94

Apr 20 18:34:03 Backup kernel:  [<c10313cc>] ? queue_delayed_work+0x1b/0x1e

Apr 20 18:34:03 Backup kernel:  [<c10c0203>] ? do_journal_end+0x935/0xb33

Apr 20 18:34:03 Backup kernel:  [<c10c045c>] ? journal_end_sync+0x5b/0x63

Apr 20 18:34:03 Backup kernel:  [<c10b4133>] ? reiserfs_sync_fs+0x32/0x4f

Apr 20 18:34:03 Backup kernel:  [<c10850d4>] ? __sync_filesystem+0x38/0x49

Apr 20 18:34:03 Backup kernel:  [<c108522b>] ? sync_filesystem+0x2c/0x41

Apr 20 18:34:03 Backup kernel:  [<c106da13>] ? do_remount_sb+0x45/0xab

Apr 20 18:34:03 Backup kernel:  [<c107e7b8>] ? do_mount+0x1c9/0x5f9

Apr 20 18:34:03 Backup kernel:  [<c1016e90>] ? do_page_fault+0x0/0x1e4

Apr 20 18:34:03 Backup kernel:  [<c1054f19>] ? strndup_user+0x40/0x5f

Apr 20 18:34:03 Backup kernel:  [<c107ec49>] ? sys_mount+0x61/0x94

Apr 20 18:34:03 Backup kernel:  [<c1002935>] ? syscall_call+0x7/0xb

Apr 20 18:34:03 Backup kernel: Code: 18 a6 43 c1 89 e5 85 c0 75 04 0f 0b eb fe 8b 14 95 64 ff 3e c1 8b 00 64 8b 0d 54 a4 43 c1 3b 4c 10 20 5d 0f 94 c0 0f b6 c0 c3 55 <83> 78 10 00 89 e5 0f 45 15 5c 00 3f c1 8b 00 5d 03 04 95 64 ff

Apr 20 18:34:03 Backup kernel: EIP: [<c1030b21>] wq_per_cpu+0x1/0x19 SS:ESP 0068:f6b25e04

Apr 20 18:34:03 Backup kernel: CR2: 0000000000000010

Apr 20 18:34:03 Backup kernel: ---[ end trace 877d523ce9087eed ]---

 

It appears as if emhttp crashed at that point. 

You might have been able to regain control by typing

killall emhttp

emhttp &

 

I don't see evidence of the disks being unmounted after emhttp crashed.

 

You might want to perform a file-system check on each of your file-systems.  In the past, it is often file-system corruption that results in invalid pointers and attempts to reference invalid memory locations.  Instructions are here in the wiki:

http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

 

You may also want to forward a copy of the "oops" to lime-technology, in case it gives them a clue as to what might have happened.

 

Joe L.

 

Thanks for the recommendation Joe.  I ran the check on all my data drives and there are no errors.  Since then I've stopped and started the array with no problems.