new case - started seeing errors in syslog

[joyless]

hello,

i have replaced my old case with new one, 4 bay hot swap NAS type of case.

everything works fine, but i'm seeing some errors in syslog, that i have never seen before:

Jan 28 08:54:05 lilmofo kernel: ------------[ cut here ]------------
Jan 28 08:54:05 lilmofo kernel: WARNING: CPU: 1 PID: 16375 at ./arch/x86/include/asm/thread_info.h:236 SyS_rt_sigsuspend+0x8f/0x9e()
Jan 28 08:54:05 lilmofo kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod kvm_amd kvm k10temp r8169 mii i2c_piix4 i2c_core pata_atiixp ahci libahci wmi acpi_cpufreq
Jan 28 08:54:05 lilmofo kernel: CPU: 1 PID: 16375 Comm: Threadpool work Not tainted 4.4.30-unRAID #2
Jan 28 08:54:05 lilmofo kernel: Hardware name: System manufacturer System Product Name/C60M1-I, BIOS 0205 04/06/2012
Jan 28 08:54:05 lilmofo kernel: 0000000000000000 ffff8801397fbee0 ffffffff8136f79f 0000000000000000
Jan 28 08:54:05 lilmofo kernel: 00000000000000ec ffff8801397fbf18 ffffffff8104a4ab ffffffff8105569b
Jan 28 08:54:05 lilmofo kernel: fffffffffffffdfe 00000000000021b0 000000000000000d 000000000000a0c4
Jan 28 08:54:05 lilmofo kernel: Call Trace:
Jan 28 08:54:05 lilmofo kernel: [<ffffffff8136f79f>] dump_stack+0x61/0x7e
Jan 28 08:54:05 lilmofo kernel: [<ffffffff8104a4ab>] warn_slowpath_common+0x8f/0xa8
Jan 28 08:54:05 lilmofo kernel: [<ffffffff8105569b>] ? SyS_rt_sigsuspend+0x8f/0x9e
Jan 28 08:54:05 lilmofo kernel: [<ffffffff8104a568>] warn_slowpath_null+0x15/0x17
Jan 28 08:54:05 lilmofo kernel: [<ffffffff8105569b>] SyS_rt_sigsuspend+0x8f/0x9e
Jan 28 08:54:05 lilmofo kernel: [<ffffffff81629c2e>] entry_SYSCALL_64_fastpath+0x12/0x6d
Jan 28 08:54:05 lilmofo kernel: ---[ end trace 6792b1b072408542 ]---

 

and this one after mover:

Jan 28 03:49:05 lilmofo kernel: ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x400000 action 0x6 frozen
Jan 28 03:49:05 lilmofo kernel: ata3.00: irq_stat 0x08000000, interface fatal error
Jan 28 03:49:05 lilmofo kernel: ata3: SError: { Handshk }
Jan 28 03:49:05 lilmofo kernel: ata3.00: failed command: WRITE DMA EXT
Jan 28 03:49:05 lilmofo kernel: ata3.00: cmd 35/00:18:d8:d7:54/00:05:48:00:00/e0 tag 7 dma 667648 out
Jan 28 03:49:05 lilmofo kernel:         res 50/00:00:d7:d7:54/00:00:48:00:00/e0 Emask 0x10 (ATA bus error)
Jan 28 03:49:05 lilmofo kernel: ata3.00: status: { DRDY }
Jan 28 03:49:05 lilmofo kernel: ata3: hard resetting link
Jan 28 03:49:05 lilmofo kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jan 28 03:49:05 lilmofo kernel: ata3.00: configured for UDMA/133
Jan 28 03:49:05 lilmofo kernel: ata3: EH complete

 

i tried googling and searching forum, but didnt find much info.

any ideas? should i be worried?

 

[RobJ]

The 2 issues are different, unrelated.  I suspect the second one (a drive interface issue) is from the reconnecting of the drives in the new case.  Make sure all the power connections are tight.  And if you don't have a single rail power supply, make sure there aren't too many drives on any one power cable.

 

We have seen the second issue a few times before, but without a known and clear cause or solution.  The usual advice is to make sure you have the latest BIOS for your motherboard (yours is from 2012), latest firmware for any controller cards installed, and keep upgrading to the latest unRAID releases (currently 6.3.0-rc9), so you have the latest Linux kernel.

[joyless]

RobJ, thanks for your reply!

I have single rail power supply. I'll open the case and make sure the power connection is tight (it was very hard to push it all the way in) and will replace sata cables just to be sure (they are way to long and make a mess anyway).

I'll also update the BIOS.

I think I experienced a random shutdown yesterday Woke up and the server was powered off, and I really don't recall shutting it down (I pretty much run my NAS powered 24/7)

[testdasi]

When you turn the server back on, did unRAID complain about an unclean shutdown?

If it does then I think something isnt right with the PSU.

[joyless]

When you turn the server back on, did unRAID complain about an unclean shutdown?

If it does then I think something isnt right with the PSU.

unfortunately there is no way to tell, i currently have no parity drive installed