Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Error in sys log

Lou
in General Support (V5 and Older)

Featured Replies

I just updated my mother board all seems to run fine but I have a new error message in the syslog.

Could someone tell me what this error is and what has to be done to correct it.

 

Jan  1 14:16:14 Unraid kernel: ------------[ cut here ]------------

Jan  1 14:16:14 Unraid kernel: WARNING: at fs/proc/generic.c:590 proc_register+0x11c/0x14b()

Jan  1 14:16:14 Unraid kernel: Hardware name: C2SEA

Jan  1 14:16:14 Unraid kernel: proc_dir_entry 'scsi_tgt/mvst_scst' already registered

Jan  1 14:16:14 Unraid kernel: Modules linked in: mvsas(+) libsas scst scsi_transport_sas

Jan  1 14:16:14 Unraid kernel: Pid: 803, comm: modprobe Not tainted 2.6.32.9-unRAID #8

Jan  1 14:16:14 Unraid kernel: Call Trace:

Jan  1 14:16:14 Unraid kernel:  [<c102449e>] warn_slowpath_common+0x60/0x77

Jan  1 14:16:14 Unraid kernel:  [<c10244e9>] warn_slowpath_fmt+0x24/0x27

Jan  1 14:16:14 Unraid kernel:  [<c109cf0e>] proc_register+0x11c/0x14b

Jan  1 14:16:14 Unraid kernel:  [<c109d0cc>] proc_mkdir_mode+0x2f/0x43

Jan  1 14:16:14 Unraid kernel:  [<c109d0ef>] proc_mkdir+0xf/0x11

Jan  1 14:16:14 Unraid kernel:  [<f83e1a36>] scst_build_proc_target_dir_entries+0x55/0xdc [scst]

Jan  1 14:16:14 Unraid kernel:  [<f83c8ca9>] __scst_register_target_template+0x16c/0x3af [scst]

Jan  1 14:16:14 Unraid kernel:  [<f8446d5d>] mvst_init+0x3b/0x5b [mvsas]

Jan  1 14:16:14 Unraid kernel:  [<f844b895>] mvs_pci_init+0xaa5/0xaf7 [mvsas]

Jan  1 14:16:14 Unraid kernel:  [<c10062d9>] ? dma_generic_alloc_coherent+0x0/0xdb

Jan  1 14:16:14 Unraid kernel:  [<c1142050>] local_pci_probe+0xe/0x10

Jan  1 14:16:14 Unraid kernel:  [<c11426ad>] pci_device_probe+0x48/0x66

Jan  1 14:16:14 Unraid kernel:  [<c1194956>] driver_probe_device+0x79/0xed

Jan  1 14:16:14 Unraid kernel:  [<c1194a0d>] __driver_attach+0x43/0x5f

Jan  1 14:16:14 Unraid kernel:  [<c11940a7>] bus_for_each_dev+0x39/0x5a

Jan  1 14:16:14 Unraid kernel:  [<f8453000>] ? mvs_init+0x0/0x45 [mvsas]

Jan  1 14:16:14 Unraid kernel:  [<c119482f>] driver_attach+0x14/0x16

Jan  1 14:16:14 Unraid kernel:  [<c11949ca>] ? __driver_attach+0x0/0x5f

Jan  1 14:16:14 Unraid kernel:  [<c119451c>] bus_add_driver+0x9f/0x1c5

Jan  1 14:16:14 Unraid kernel:  [<f8453000>] ? mvs_init+0x0/0x45 [mvsas]

Jan  1 14:16:14 Unraid kernel:  [<c1194ccf>] driver_register+0x7b/0xd7

Jan  1 14:16:14 Unraid kernel:  [<f8453000>] ? mvs_init+0x0/0x45 [mvsas]

Jan  1 14:16:14 Unraid kernel:  [<c1142882>] __pci_register_driver+0x39/0x8c

Jan  1 14:16:14 Unraid kernel:  [<f8453000>] ? mvs_init+0x0/0x45 [mvsas]

Jan  1 14:16:14 Unraid kernel:  [<f8453030>] mvs_init+0x30/0x45 [mvsas]

Jan  1 14:16:14 Unraid kernel:  [<c1001139>] do_one_initcall+0x4c/0x131

Jan  1 14:16:14 Unraid kernel:  [<c1042e6e>] sys_init_module+0xa7/0x1dd

Jan  1 14:16:14 Unraid kernel:  [<c1002935>] syscall_call+0x7/0xb

Jan  1 14:16:14 Unraid kernel: ---[ end trace efdfc04c4fa60a41 ]---

thanks

Lou

  • Quote

    I just updated my mother board all seems to run fine but I have a new error message in the syslog.

    Could someone tell me what this error is and what has to be done to correct it.

     

    Jan  1 14:16:14 Unraid kernel: ------------[ cut here ]------------

    Jan  1 14:16:14 Unraid kernel: WARNING: at fs/proc/generic.c:590 proc_register+0x11c/0x14b()

    Jan  1 14:16:14 Unraid kernel: Hardware name: C2SEA

    Jan  1 14:16:14 Unraid kernel: proc_dir_entry 'scsi_tgt/mvst_scst' already registered

    Jan  1 14:16:14 Unraid kernel: Modules linked in: mvsas(+) libsas scst scsi_transport_sas

    Jan  1 14:16:14 Unraid kernel: Pid: 803, comm: modprobe Not tainted 2.6.32.9-unRAID #8

    Jan  1 14:16:14 Unraid kernel: Call Trace:

    Jan  1 14:16:14 Unraid kernel:  [<c102449e>] warn_slowpath_common+0x60/0x77

    Jan  1 14:16:14 Unraid kernel:  [<c10244e9>] warn_slowpath_fmt+0x24/0x27

    Jan  1 14:16:14 Unraid kernel:  [<c109cf0e>] proc_register+0x11c/0x14b

    Jan  1 14:16:14 Unraid kernel:  [<c109d0cc>] proc_mkdir_mode+0x2f/0x43

    Jan  1 14:16:14 Unraid kernel:  [<c109d0ef>] proc_mkdir+0xf/0x11

    Jan  1 14:16:14 Unraid kernel:  [<f83e1a36>] scst_build_proc_target_dir_entries+0x55/0xdc [scst]

    Jan  1 14:16:14 Unraid kernel:  [<f83c8ca9>] __scst_register_target_template+0x16c/0x3af [scst]

    Jan  1 14:16:14 Unraid kernel:  [<f8446d5d>] mvst_init+0x3b/0x5b [mvsas]

    Jan  1 14:16:14 Unraid kernel:  [<f844b895>] mvs_pci_init+0xaa5/0xaf7 [mvsas]

    Jan  1 14:16:14 Unraid kernel:  [<c10062d9>] ? dma_generic_alloc_coherent+0x0/0xdb

    Jan  1 14:16:14 Unraid kernel:  [<c1142050>] local_pci_probe+0xe/0x10

    Jan  1 14:16:14 Unraid kernel:  [<c11426ad>] pci_device_probe+0x48/0x66

    Jan  1 14:16:14 Unraid kernel:  [<c1194956>] driver_probe_device+0x79/0xed

    Jan  1 14:16:14 Unraid kernel:  [<c1194a0d>] __driver_attach+0x43/0x5f

    Jan  1 14:16:14 Unraid kernel:  [<c11940a7>] bus_for_each_dev+0x39/0x5a

    Jan  1 14:16:14 Unraid kernel:  [<f8453000>] ? mvs_init+0x0/0x45 [mvsas]

    Jan  1 14:16:14 Unraid kernel:  [<c119482f>] driver_attach+0x14/0x16

    Jan  1 14:16:14 Unraid kernel:  [<c11949ca>] ? __driver_attach+0x0/0x5f

    Jan  1 14:16:14 Unraid kernel:  [<c119451c>] bus_add_driver+0x9f/0x1c5

    Jan  1 14:16:14 Unraid kernel:  [<f8453000>] ? mvs_init+0x0/0x45 [mvsas]

    Jan  1 14:16:14 Unraid kernel:  [<c1194ccf>] driver_register+0x7b/0xd7

    Jan  1 14:16:14 Unraid kernel:  [<f8453000>] ? mvs_init+0x0/0x45 [mvsas]

    Jan  1 14:16:14 Unraid kernel:  [<c1142882>] __pci_register_driver+0x39/0x8c

    Jan  1 14:16:14 Unraid kernel:  [<f8453000>] ? mvs_init+0x0/0x45 [mvsas]

    Jan  1 14:16:14 Unraid kernel:  [<f8453030>] mvs_init+0x30/0x45 [mvsas]

    Jan  1 14:16:14 Unraid kernel:  [<c1001139>] do_one_initcall+0x4c/0x131

    Jan  1 14:16:14 Unraid kernel:  [<c1042e6e>] sys_init_module+0xa7/0x1dd

    Jan  1 14:16:14 Unraid kernel:  [<c1002935>] syscall_call+0x7/0xb

    Jan  1 14:16:14 Unraid kernel: ---[ end trace efdfc04c4fa60a41 ]---

    thanks

    Lou

    It is a WARNING, not an error.

    It simply indicates the mvsas driver was already loaded.  (You probably have two of the same SATA cards that use the same driver.  This message occurs when the hardware detects the second of the two cards.)

     

    On yes... you cannot do anything about it.  (other than to remove one of the SATA cards) ;)

     

     

  • Quote
    • Author

    Thanks Joe

    I did install a second super micro card.

    So it sounds like the system and 2 cards will work fine other than getting the warning messages right?

    Lou

  • Quote

    Correct. Others have systems that have been running on two or more SuperMicro cards for at least 6 months now with close to the maximum drive limit without issues (other than the Warnings).

  • Quote
    • Author

    Great

    Thanks Brit

    Lou

  • Quote

    • Archived

    This topic is now archived and is closed to further replies.

    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.