Got some errors after rebooting tonight. Are these something to be worried about? Any ideas about the cause?

 

It took about 5 minutes for the webpage to go from "Starting..." to "Started", much longer than normal. Meanwhile Disk 11 stayed as "Unmounted", which normally doesn't happen.

 

 

Feb 24 20:30:02 MEDIA kernel: ------------[ cut here ]------------

Feb 24 20:30:02 MEDIA kernel: WARNING: at fs/proc/generic.c:590 proc_register+0x11c/0x14b() (Minor Issues)

Feb 24 20:30:02 MEDIA kernel: Hardware name: X8SIA

Feb 24 20:30:02 MEDIA kernel: proc_dir_entry 'scsi_tgt/mvst_scst' already registered (Drive related)

Feb 24 20:30:02 MEDIA kernel: Modules linked in: mvsas(+) libsas scst scsi_transport_sas (Drive related)

Feb 24 20:30:02 MEDIA kernel: Pid: 912, comm: modprobe Not tainted 2.6.32.9-unRAID #5 (Errors)

Feb 24 20:30:02 MEDIA kernel: Call Trace: (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c10244e9>] warn_slowpath_fmt+0x24/0x27 (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c109cf0e>] proc_register+0x11c/0x14b (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c109d0cc>] proc_mkdir_mode+0x2f/0x43 (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c109d0ef>] proc_mkdir+0xf/0x11 (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<f83f4a36>] scst_build_proc_target_dir_entries+0x55/0xdc [scst] (Routine)

Feb 24 20:30:02 MEDIA kernel:  [<f83dbca9>] __scst_register_target_template+0x16c/0x3af [scst] (Routine)

Feb 24 20:30:02 MEDIA kernel:  [<f8459d5d>] mvst_init+0x3b/0x5b [mvsas] (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<f845e895>] mvs_pci_init+0xaa5/0xaf7 [mvsas] (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c10062d9>] ? dma_generic_alloc_coherent+0x0/0xdb (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c1142050>] local_pci_probe+0xe/0x10 (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c11426ad>] pci_device_probe+0x48/0x66 (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c1194956>] driver_probe_device+0x79/0xed (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c1194a0d>] __driver_attach+0x43/0x5f (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c11940a7>] bus_for_each_dev+0x39/0x5a (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<f8466000>] ? mvs_init+0x0/0x45 [mvsas] (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c119482f>] driver_attach+0x14/0x16 (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c11949ca>] ? __driver_attach+0x0/0x5f (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c119451c>] bus_add_driver+0x9f/0x1c5 (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<f8466000>] ? mvs_init+0x0/0x45 [mvsas] (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c1194ccf>] driver_register+0x7b/0xd7 (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<f8466000>] ? mvs_init+0x0/0x45 [mvsas] (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c1142882>] __pci_register_driver+0x39/0x8c (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<f8466000>] ? mvs_init+0x0/0x45 [mvsas] (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<f8466030>] mvs_init+0x30/0x45 [mvsas] (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c1001139>] do_one_initcall+0x4c/0x131 (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c1042e6e>] sys_init_module+0xa7/0x1dd (Errors)

Feb 24 20:30:02 MEDIA kernel:  [<c1002935>] syscall_call+0x7/0xb (Errors)

Feb 24 20:30:02 MEDIA kernel: ---[ end trace 6cedeea1497b3070 ]---

nothing to worry about.  Basically you have 2 of the SASLP cards in your server.  The first one was seen and the driver was loaded, the second one was seen and the driver tried to load again... it failed because it was already loaded.

Thanks for the response. Is the long time to go from "Starting..." to "Started" something to be concerned about? An indication of a failing hard drive or something?

Thanks for the response. Is the long time to go from "Starting..." to "Started" something to be concerned about? An indication of a failing hard drive or something?

The management console does not self refresh.  It will say "Starting" forever until you refresh the browser.

This problem is persisting. I clicked "Stop" to stop the array, and the web server has yet to respond to multiple refresh requests. Pulling the plug and rebooting seems like a bad idea mid-array-stop, but at some point I guess I may need to.

 

For a few minutes after clicking "Stop" I was able to log in via ssh, but that isn't responding anymore either.

 

Any ideas on what to do now? Pull the plug? Any ideas on how to troubleshoot the continually slow/no responses?

 

>The management console does not self refresh

Thanks, but I know that. Refreshing did not cause the status to change.

Once again, stopping the array has caused the system to stop responding. This time it sent some text to my SSH session before dying:

 

Message from syslogd@MEDIA at Fri Mar 11 00:03:03 2011 ...

MEDIA kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1c.0/0000:05:00.0/host2/port-2:0/end_device-2:0/target2:0:0/2:0:0:0/block/sdf/stat

 

Message from syslogd@MEDIA at Fri Mar 11 00:03:03 2011 ...

MEDIA kernel: Stack:

 

Message from syslogd@MEDIA at Fri Mar 11 00:03:03 2011 ...

MEDIA kernel: Process emhttp (pid: 18230, ti=e56ba000 task=f7467a70 task.ti=e56ba000)

 

Message from syslogd@MEDIA at Fri Mar 11 00:03:03 2011 ...

MEDIA kernel: Call Trace:

 

Message from syslogd@MEDIA at Fri Mar 11 00:03:03 2011 ...

MEDIA kernel: Oops: 0000 [#1] SMP

 

Message from syslogd@MEDIA at Fri Mar 11 00:03:03 2011 ...

MEDIA kernel: Code: 00 8b 02 8b 72 10 85 c0 89 45 e0 75 18 52 8b 55 ec 83 c9 ff ff 75 e8 89 f8 e8 84 fb ff ff 89 45 e0 58 5a eb 0b 8b 4d e0 8b 42 0c <8b> 04 81 89 02 53 9d 66 83 7d ec 00 79 21 83 7d e0 00 74 1b 89

 

Message from syslogd@MEDIA at Fri Mar 11 00:03:03 2011 ...

MEDIA kernel: EIP: [<c1068767>] kmem_cache_alloc+0x64/0x9e SS:ESP 0068:e56bbae4

 

Message from syslogd@MEDIA at Fri Mar 11 00:03:03 2011 ...

MEDIA kernel: CR2: 0000000000000005

 

Anyone have any ideas? Is there any more data I should get that would a diagnosis?

 

Any input is much appreciated.

How do I attach my syslog? It is post-reboot, so probably not too helpful, but I'm getting

 

>The message exceeds the maximum allowed length (20000 characters).

zip the syslog