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.

Big Trouble, no not in Little China, but in Erica, NL. Stalling CPU or OOM?

Featured Replies

I run 5.0RC11 in 4 GB mode.

 

After starting a Parity Check I see the following in my syslog:

 

Feb 23 11:13:47 Tower1 kernel: INFO: rcu_sched self-detected stall on CPU { 0}  (t=6000 jiffies)

Feb 23 11:13:47 Tower1 kernel: Pid: 9369, comm: unraidd Not tainted 3.4.26-unRAID #2

Feb 23 11:13:47 Tower1 kernel: Call Trace:

Feb 23 11:13:47 Tower1 kernel:  [<c1057bca>] print_cpu_stall+0x6d/0xe5

Feb 23 11:13:47 Tower1 kernel:  [<c1057c7d>] __rcu_pending+0x3b/0x138

Feb 23 11:13:47 Tower1 kernel:  [<c1057df0>] rcu_check_callbacks+0x76/0xa1

Feb 23 11:13:47 Tower1 kernel:  [<c102c982>] update_process_times+0x2d/0x58

Feb 23 11:13:47 Tower1 kernel:  [<c104b11b>] tick_periodic+0x63/0x65

Feb 23 11:13:47 Tower1 kernel:  [<c104b136>] tick_handle_periodic+0x19/0x6f

Feb 23 11:13:47 Tower1 kernel:  [<c10180d0>] smp_apic_timer_interrupt+0x6d/0x7f

Feb 23 11:13:47 Tower1 kernel:  [<c1342652>] apic_timer_interrupt+0x2a/0x30

Feb 23 11:13:47 Tower1 kernel:  [<c1342040>] ? _raw_spin_unlock_irqrestore+0x8/0xa

Feb 23 11:13:47 Tower1 kernel:  [<f988bc8f>] unraid_end_request+0x64/0x6b [md_mod]

Feb 23 11:13:47 Tower1 kernel:  [<c10a965f>] bio_endio+0x25/0x27

Feb 23 11:13:47 Tower1 kernel:  [<c11a052c>] req_bio_endio+0x80/0x88

Feb 23 11:13:47 Tower1 kernel:  [<c1224f90>] ? put_device+0xf/0x11

Feb 23 11:13:47 Tower1 kernel:  [<c11a0676>] blk_update_request+0x142/0x302

Feb 23 11:13:47 Tower1 kernel:  [<c11a0844>] blk_update_bidi_request+0xe/0x4f

Feb 23 11:13:47 Tower1 kernel:  [<c11a1144>] blk_end_bidi_request+0x1d/0x53

Feb 23 11:13:47 Tower1 kernel:  [<c11a11b9>] blk_end_request+0x12/0x14

Feb 23 11:13:47 Tower1 kernel:  [<c12459d5>] scsi_end_request+0x1f/0x70

Feb 23 11:13:47 Tower1 kernel:  [<c1245d3b>] scsi_io_completion+0x1a9/0x3fd

Feb 23 11:13:47 Tower1 kernel:  [<c1245ad9>] ? scsi_device_unbusy+0x7c/0x82

Feb 23 11:13:47 Tower1 kernel:  [<c1240bfa>] scsi_finish_command+0x9d/0xa3

Feb 23 11:13:47 Tower1 kernel:  [<c1246063>] scsi_softirq_done+0xc5/0xcd

Feb 23 11:13:47 Tower1 kernel:  [<c11a5652>] blk_done_softirq+0x4a/0x57

Feb 23 11:13:47 Tower1 kernel:  [<c102862d>] __do_softirq+0x6b/0xfa

Feb 23 11:13:47 Tower1 kernel:  [<c10285c2>] ? irq_enter+0x41/0x41

Feb 23 11:13:47 Tower1 kernel:  <IRQ>  [<c1028476>] ? irq_exit+0x32/0x58

Feb 23 11:13:47 Tower1 kernel:  [<c1003713>] ? do_IRQ+0x87/0x9b

Feb 23 11:13:47 Tower1 kernel:  [<c1342fa9>] ? common_interrupt+0x29/0x30

Feb 23 11:13:47 Tower1 kernel:  [<f872ca49>] ? xor_sse_5+0x2b4/0x3d9 [xor]

Feb 23 11:13:47 Tower1 kernel:  [<c103cdfd>] ? check_preempt_curr+0x39/0x64

Feb 23 11:13:47 Tower1 kernel:  [<f872d8cc>] ? xor_blocks+0x74/0x7c [xor]

Feb 23 11:13:47 Tower1 kernel:  [<f988ac94>] ? check_parity+0x96/0xcc [md_mod]

Feb 23 11:13:47 Tower1 kernel:  [<f988b8de>] ? handle_stripe+0xb30/0xdc1 [md_mod]

Feb 23 11:13:47 Tower1 kernel:  [<c102849a>] ? irq_exit+0x56/0x58

Feb 23 11:13:47 Tower1 kernel:  [<c103d051>] ? __wake_up+0x3b/0x42

Feb 23 11:13:47 Tower1 kernel:  [<f988bbe7>] ? unraidd+0x78/0xbc [md_mod]

Feb 23 11:13:47 Tower1 kernel:  [<f9888b31>] ? md_thread+0xcc/0xe3 [md_mod]

Feb 23 11:13:47 Tower1 kernel:  [<c10379b5>] ? wake_up_bit+0x5b/0x5b

Feb 23 11:13:47 Tower1 kernel:  [<f9888a65>] ? import_device+0x166/0x166 [md_mod]

Feb 23 11:13:47 Tower1 kernel:  [<c10376bc>] ? kthread+0x67/0x6c

Feb 23 11:13:47 Tower1 kernel:  [<c1037655>] ? kthread_freezable_should_stop+0x49/0x49

Feb 23 11:13:47 Tower1 kernel:  [<c1342fb6>] ? kernel_thread_helper+0x6/0xd

Feb 23 11:17:47 Tower1 kernel: INFO: rcu_sched self-detected stall on CPU { 0}  (t=6000 jiffies)

Feb 23 11:17:47 Tower1 kernel: Pid: 9369, comm: unraidd Not tainted 3.4.26-unRAID #2

 

Has something bad happened to the array? Are there memory problems? What does all of this mean?

I have only SABNZBD, APCUPSD and SNAP running.

Please help!!!

 

Full syslog is attached.

syslog-2013-02-23.zip

  • Author

Rebooted the server and gave it the full 16 GB memory.

 

The messages came back in the syslog after restarting the parity check.

 

syslog-2013-02-23a.zip

No OOM as far as I can see... try and run without plugins to see where the issue lies.

  • Author

Disabled the plugins but same happens again. Any more options?

 

 

Funny thing is that during a parity rebuild last night I didn't see these errors, but now approx. 10 minutes after beginning a parity check they appear.

syslog-2013-02-23b.zip

  • Author

A parity sync/rebuild finished overnight again without problems.

 

After starting the parity check the same errors in the syslog turned up.

 

All addons are disabled and running with 16 GB memory.

 

I don't know how this turns up, öut of the blue"

 

Can it be an hardware error?

 

Running baremetal now.

 

Even when running stock like described in dgaschk's sig.

 

latest syslog is attached

 

syslog.zip

Try a memtest maybe ?

 

Check the flashdrive for corruption also.

  • Author

As of 14:47 the errors stopped appearing in the syslog. Don't know what caused this, just let the parity check run.

 

One thing I noticed was that the unraidd process appeared at the top of top-screen with ove 50 %CPU.

 

Don't see anything special in the latest syslog though.

syslog2.zip

Sorry but there is way to much in there for me to understand... If its gone then be happy :-)  Still think a memtest might be a good idea though.. Something weird was definately going on..

Try a memtest maybe ?

 

Check the flashdrive for corruption also.

 

Run memtest overnight. Run checkdisk on the flash in a PC or Mac. Does the problem occur when running bare-metal?

  • Author

Try a memtest maybe ?

 

Check the flashdrive for corruption also.

 

Run memtest overnight. Run checkdisk on the flash in a PC or Mac. Does the problem occur when running bare-metal?

 

Like stated previously: I am running baremetal.

 

chkdsk found no problems

 

Archived

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

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.