I have a little nettop that I'm using as a test unraid box (to work on development of packages/plugins/test things with).

Using a fresh install of unraid 0.5rc16c. The machine is a MSI MS-7618/Wind Board D510(MS-7618) with Intel® Atom CPU D510 with 1gb ram.  It has only one harddrive connected (intel 40gb ssd), there is no array or anything built.

 

If I power on the machine, it boots to unraid and works as normal. On reboot the machine appears to 'hang' but it eventually boots.. but is ungodly slow to do anything.

 

When its running normal (cold boot), you can see that the bootup takes 1 sec:

Aug 18 17:24:24 testtower syslogd 1.4.1: restart.
...
Aug 18 17:24:25 testtower emhttp: auto start disabled

 

When its slow (reboot), its a different story 2min 12 secs:

Aug 18 02:40:01 testtower syslogd 1.4.1: restart.
...
Aug 18 02:42:13 testtower emhttp: auto start disabled

 

So you can only imagine how slow it is to do anything when its in this state.

 

Notable things that stood out when comparing the syslogs

Aug 18 02:40:07 testtower kernel: smpboot: Booting Node   0, Processors  #1
Aug 18 02:40:07 testtower kernel: TSC synchronization [CPU#0 -> CPU#1]:
Aug 18 02:40:07 testtower kernel: Measured 40 cycles TSC warp between CPUs, turning off TSC clock.
Aug 18 02:40:07 testtower kernel: tsc: Marking TSC unstable due to check_tsc_sync_source failed

 

Aug 18 02:40:09 testtower kernel: Unpacking initramfs...
Aug 18 02:40:09 testtower kernel: INFO: rcu_sched self-detected stall on CPU { 2}  (t=6001 jiffies g=240 c=239 q=5)
Aug 18 02:40:09 testtower kernel: Pid: 1, comm: swapper/0 Not tainted 3.9.6p-unRAID #23
Aug 18 02:40:09 testtower kernel: Call Trace:
Aug 18 02:40:09 testtower kernel:  [<c1062ba6>] print_cpu_stall+0xbc/0x107
Aug 18 02:40:09 testtower kernel: INFO: rcu_sched detected stalls on CPUs/tasks:
Aug 18 02:40:09 testtower kernel:  [<c1062e36>] __rcu_pending+0x4f/0x12a
Aug 18 02:40:09 testtower kernel:  [<c1062f84>] rcu_check_callbacks+0x73/0x9b
Aug 18 02:40:09 testtower kernel:  [<c1032ead>] update_process_times+0x2d/0x53
Aug 18 02:40:09 testtower kernel:  [<c1055167>] tick_sched_timer+0x77/0xa1
Aug 18 02:40:09 testtower kernel:  [<c1040d86>] ? __remove_hrtimer+0x25/0x7a
Aug 18 02:40:09 testtower kernel:  [<c1040ec9>] __run_hrtimer+0x45/0xaf
Aug 18 02:40:09 testtower kernel:  [<c1041231>] hrtimer_interrupt+0xf1/0x1e7
Aug 18 02:40:09 testtower kernel:  [<c101c43a>] smp_apic_timer_interrupt+0x6d/0x7f
Aug 18 02:40:09 testtower kernel:  [<c14033f9>] apic_timer_interrupt+0x2d/0x34
Aug 18 02:40:09 testtower kernel:  [<c126d23c>] ? lzma_main+0xd8/0x22d
Aug 18 02:40:09 testtower kernel:  [<c126d5d9>] lzma2_lzma+0x146/0x1a3
Aug 18 02:40:09 testtower kernel:  [<c126d93d>] xz_dec_lzma2_run+0x307/0x4b2
Aug 18 02:40:09 testtower kernel:  [<c126e176>] xz_dec_bcj_run+0x76/0x190
Aug 18 02:40:09 testtower kernel:  [<c126c291>] dec_block+0x39/0x174
Aug 18 02:40:09 testtower kernel:  [<c1096e11>] ? sys_write+0x43/0x6e
Aug 18 02:40:09 testtower kernel:  [<c126c552>] dec_main+0x125/0x3da
Aug 18 02:40:09 testtower kernel:  [<c126c831>] xz_dec_run+0x2a/0x81
Aug 18 02:40:09 testtower kernel:  [<c1590234>] unxz+0x129/0x1df
Aug 18 02:40:09 testtower kernel:  [<c159010b>] ? unlzo+0x30b/0x30b
Aug 18 02:40:09 testtower kernel:  [<c157558e>] unpack_to_rootfs+0x16d/0x293
Aug 18 02:40:09 testtower kernel:  [<c157526c>] ? do_reset+0xb0/0xb0
Aug 18 02:40:09 testtower kernel:  [<c1575095>] ? initrd_load+0x47/0x47
Aug 18 02:40:09 testtower kernel:  [<c1575dfa>] populate_rootfs+0x49/0x93
Aug 18 02:40:09 testtower kernel:  [<c100116f>] do_one_initcall+0x87/0x134
Aug 18 02:40:09 testtower kernel:  [<c1575db1>] ? do_header+0x23f/0x23f
Aug 18 02:40:09 testtower kernel:  [<c1574475>] do_basic_setup+0x87/0xa4
Aug 18 02:40:09 testtower kernel:  [<c1574588>] ? kernel_init_freeable+0xf6/0xf6
Aug 18 02:40:09 testtower kernel:  [<c15744fe>] kernel_init_freeable+0x6c/0xf6
Aug 18 02:40:09 testtower kernel:  [<c13f6ba5>] kernel_init+0xb/0xbe
Aug 18 02:40:09 testtower kernel:  [<c1403837>] ret_from_kernel_thread+0x1b/0x28
Aug 18 02:40:09 testtower kernel:  [<c13f6b9a>] ? rest_init+0x5a/0x5a
Aug 18 02:40:09 testtower kernel:  { 2} (detected by 0, t=6007 jiffies, g=240, c=239, q=5)

 

Attached syslogs below for review.

5.0rc16c-normal-syslog.txt

5.0rc16c-slow-syslog.txt

I know, this is rather old, but in the absence of any other comment, I thought I would post my own thought.  I found this by accident, looking (found "comparing the syslogs") for more syslog comparison tools, and rather amazed at the dearth online!

 

Your nettop appears to have either a buggy motherboard or bad CPU or buggy BIOS, with timer related issues and/or CPU sync issues.  The 'normal' syslog appears fine, but included the following...

 

Aug 18 17:24:24 testtower kernel: APIC calibration not consistent with PM-Timer: 109ms instead of 100ms

Aug 18 17:24:24 testtower kernel: APIC delta adjusted to PM-Timer: 1041651 (1145816)

 

A 9ms difference at the machine level is obviously ENORMOUS!  But the kernel detected it and applied a workaround.  Neither happened on the warm boot, and when CPU timing was checked and found to be wrong, the TSC clock was disabled.  However it does appear there were delays already, even before that.

 

Your BIOS appears to be from 2010, and since that's the only potentially fixable option, I'd check for a newer one.  Hopefully, that will make this machine more usable?

thanks for the post, sadly this is just a old nettop i had laying unused..  there is 0 support for anything getting updated so ill just have to toss this up to a lost cause with regards to unraid.. but what is odd is that it works fine on first boot but reboots dont.. which made me think it was something software wise