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

unRaid 4.7 - weird error in syslog

rick.p
in General Support (V5 and Older)

Featured Replies

Have a 4.7 server that's been running peacefully for months, no errors, no glitches.. nothing.

 

Until past couple days...

now the entire log is starts on sept 30, so it's long....

 

all pretty dull and boring till a couple days ago... when this sort of thing popped up

 

Dec 30 19:47:01 BURBANK sSMTP[16386]: Creating SSL connection to host
Dec 30 19:47:01 BURBANK sSMTP[16386]: SSL connection using RC4-SHA
Dec 30 19:47:07 BURBANK sSMTP[16386]: Sent mail for root@[email protected] (221 2.0.0 closing connection vs4sm28511985obb.14) uid=0 username=root outbytes=1486
Dec 30 20:47:01 BURBANK sSMTP[16475]: Creating SSL connection to host
Dec 30 20:47:02 BURBANK sSMTP[16475]: SSL connection using RC4-SHA
Dec 30 20:47:06 BURBANK sSMTP[16475]: Sent mail for root@[email protected] (221 2.0.0 closing connection aw4sm29203622oec.9) uid=0 username=root outbytes=1486
Dec 30 21:15:57 BURBANK kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Dec 30 21:15:57 BURBANK kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x100000 action 0x6 frozen
Dec 30 21:15:57 BURBANK kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Dec 30 21:15:57 BURBANK kernel: ata3: edma_err_cause=00000020 pp_flags=00000000, SError=00100000
Dec 30 21:15:57 BURBANK kernel: ata4: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Dec 30 21:15:57 BURBANK kernel: ata3: SError: { Dispar }
Dec 30 21:15:57 BURBANK kernel: ata4: SError: { 10B8B Dispar }
Dec 30 21:15:57 BURBANK kernel: ata1: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Dec 30 21:15:57 BURBANK kernel: ata3: hard resetting link
Dec 30 21:15:57 BURBANK kernel: ata4: hard resetting link
Dec 30 21:15:57 BURBANK kernel: ata1: SError: { 10B8B Dispar }
Dec 30 21:15:57 BURBANK kernel: ata1: hard resetting link
Dec 30 21:15:58 BURBANK kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 30 21:15:58 BURBANK kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 30 21:15:58 BURBANK kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 30 21:15:58 BURBANK kernel: ata1.00: configured for UDMA/133
Dec 30 21:15:58 BURBANK kernel: ata1: EH complete
Dec 30 21:15:58 BURBANK kernel: ata3.00: configured for UDMA/133
Dec 30 21:15:58 BURBANK kernel: ata3: EH complete
Dec 30 21:15:58 BURBANK kernel: ata4.00: configured for UDMA/133
Dec 30 21:15:58 BURBANK kernel: ata4: EH complete
Dec 30 21:16:50 BURBANK kernel: ata9: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen
Dec 30 21:16:50 BURBANK kernel: ata9: irq_stat 0x00400000, PHY RDY changed
Dec 30 21:16:50 BURBANK kernel: ata9: SError: { RecovComm Persist PHYRdyChg 10B8B }
Dec 30 21:16:50 BURBANK kernel: ata9: hard resetting link
Dec 30 21:16:50 BURBANK kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Dec 30 21:16:50 BURBANK kernel: ata1: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Dec 30 21:16:50 BURBANK kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Dec 30 21:16:50 BURBANK kernel: ata10: exception Emask 0x10 SAct 0x0 SErr 0x90202 action 0xe frozen
Dec 30 21:16:50 BURBANK kernel: ata2: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Dec 30 21:16:50 BURBANK kernel: ata10: irq_stat 0x00400000, PHY RDY changed
Dec 30 21:16:50 BURBANK kernel: ata2: SError: { 10B8B Dispar }
Dec 30 21:16:50 BURBANK kernel: ata10: SError: { RecovComm Persist PHYRdyChg 10B8B }
Dec 30 21:16:50 BURBANK kernel: ata1: SError: { 10B8B Dispar }
Dec 30 21:16:50 BURBANK kernel: ata2: hard resetting link
Dec 30 21:16:50 BURBANK kernel: ata10: hard resetting link
Dec 30 21:16:50 BURBANK kernel: ata1: hard resetting link
Dec 30 21:16:50 BURBANK kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Dec 30 21:16:50 BURBANK kernel: ata4: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Dec 30 21:16:50 BURBANK kernel: ata4: SError: { 10B8B Dispar }
Dec 30 21:16:50 BURBANK kernel: ata4: hard resetting link
Dec 30 21:16:50 BURBANK kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Dec 30 21:16:50 BURBANK kernel: ata3: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Dec 30 21:16:50 BURBANK kernel: ata3: SError: { 10B8B Dispar }
Dec 30 21:16:50 BURBANK kernel: ata3: hard resetting link
Dec 30 21:16:51 BURBANK kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 30 21:16:51 BURBANK kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 30 21:16:51 BURBANK kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 30 21:16:51 BURBANK kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 30 21:16:51 BURBANK kernel: ata2.00: configured for UDMA/133
Dec 30 21:16:51 BURBANK kernel: ata2: EH complete
Dec 30 21:16:51 BURBANK kernel: ata1.00: configured for UDMA/133
Dec 30 21:16:51 BURBANK kernel: ata1: EH complete
Dec 30 21:16:51 BURBANK kernel: ata3.00: configured for UDMA/133
Dec 30 21:16:51 BURBANK kernel: ata3: EH complete
Dec 30 21:16:51 BURBANK kernel: ata4.00: configured for UDMA/133
Dec 30 21:16:51 BURBANK kernel: ata4: EH complete
Dec 30 21:16:51 BURBANK kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x100000 action 0x6 frozen
Dec 30 21:16:51 BURBANK kernel: ata2: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Dec 30 21:16:51 BURBANK kernel: ata3: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Dec 30 21:16:51 BURBANK kernel: ata2: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Dec 30 21:16:51 BURBANK kernel: ata3: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Dec 30 21:16:51 BURBANK kernel: ata2: SError: { 10B8B Dispar }
Dec 30 21:16:51 BURBANK kernel: ata3: SError: { 10B8B Dispar }
Dec 30 21:16:51 BURBANK kernel: ata1: edma_err_cause=00000020 pp_flags=00000000, SError=00100000
Dec 30 21:16:51 BURBANK kernel: ata2: hard resetting link
Dec 30 21:16:51 BURBANK kernel: ata3: hard resetting link
Dec 30 21:16:51 BURBANK kernel: ata1: SError: { Dispar }
Dec 30 21:16:51 BURBANK kernel: ata1: hard resetting link
Dec 30 21:16:51 BURBANK kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Dec 30 21:16:51 BURBANK kernel: ata4: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Dec 30 21:16:51 BURBANK kernel: ata4: SError: { 10B8B Dispar }
Dec 30 21:16:51 BURBANK kernel: ata4: hard resetting link
Dec 30 21:16:51 BURBANK kernel: ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 30 21:16:51 BURBANK kernel: ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 30 21:16:51 BURBANK kernel: ata9.00: configured for UDMA/133
Dec 30 21:16:51 BURBANK kernel: ata10.00: configured for UDMA/133
Dec 30 21:16:51 BURBANK kernel: ata9: EH complete
Dec 30 21:16:51 BURBANK kernel: ata10: EH complete
Dec 30 21:16:51 BURBANK kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 30 21:16:51 BURBANK kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 30 21:16:51 BURBANK kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 30 21:16:51 BURBANK kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Dec 30 21:16:51 BURBANK kernel: ata3.00: configured for UDMA/133
Dec 30 21:16:51 BURBANK kernel: ata3: EH complete
Dec 30 21:16:51 BURBANK kernel: ata4.00: configured for UDMA/133
Dec 30 21:16:51 BURBANK kernel: ata4: EH complete
Dec 30 21:16:51 BURBANK kernel: ata2.00: configured for UDMA/133
Dec 30 21:16:51 BURBANK kernel: ata2: EH complete
Dec 30 21:16:51 BURBANK kernel: ata1.00: configured for UDMA/133
Dec 30 21:16:51 BURBANK kernel: ata1: EH complete
Dec 30 21:21:46 BURBANK kernel: ata1: limiting SATA link speed to 1.5 Gbps
Dec 30 21:21:46 BURBANK kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
Dec 30 21:21:46 BURBANK kernel: ata4: limiting SATA link speed to 1.5 Gbps
Dec 30 21:21:46 BURBANK kernel: ata1: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
Dec 30 21:21:46 BURBANK kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x100000 action 0x6 frozen
Dec 30 21:21:46 BURBANK kernel: ata4: edma_err_cause=00000020 pp_flags=00000000, SError=00100000
Dec 30 21:21:46 BURBANK kernel: ata4: SError: { Dispar }
Dec 30 21:21:46 BURBANK kernel: ata1: SError: { 10B8B Dispar }
Dec 30 21:21:46 BURBANK kernel: ata1: hard resetting link
Dec 30 21:21:46 BURBANK kernel: ata4: hard resetting link
Dec 30 21:21:46 BURBANK kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Dec 30 21:21:46 BURBANK kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Dec 30 21:21:46 BURBANK kernel: ata1.00: configured for UDMA/133
Dec 30 21:21:46 BURBANK kernel: ata1: EH complete
Dec 30 21:21:46 BURBANK kernel: ata4.00: configured for UDMA/133
Dec 30 21:21:46 BURBANK kernel: ata4: EH complete
Dec 30 21:47:01 BURBANK sSMTP[16564]: Creating SSL connection to host
Dec 30 21:47:02 BURBANK sSMTP[16564]: SSL connection using RC4-SHA
Dec 30 21:47:07 BURBANK sSMTP[16564]: Sent mail for root@[email protected] (221 2.0.0 closing connection e1sm29312948oef.4) uid=0 username=root outbytes=1486

 

any thoughts, concerns, worries? (parity check is a-coming!) the array was IDLE at the time nothing accessing, stats show no errors on any drive.

weirdlog.zip

  • Quote

    are these drives all connected to MB ports ?

     

    it looks like they all had errors at the same time (within a minute or so). which points to a common issue (MB or Power) ?

  • Quote
    • Author

    6 on the MB, 4 on a controller, OCZ ZT Series 650W Fully-Modular PS bought back in April. Plugged into an APC 1500. No power 'crashes', just those blips in the log

  • 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.