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.

Kernel panic - not syncing

Featured Replies

Woke this morning to a crashed server.  Console displayed the following (see attached pic of console).

 

Kernel panic - not syncing: Timeout: Not all CPUs entered broadcast exception handler

Shutting down cpus with NMI

Kernel Offset: disable

Rebooting in 30 secs...

 

I had backups running and I can tell it crashed around 4AM.  It never rebooted in spite of the message (Rebooting in 30 secs...).  I had to do a hard reset.

 

I've notice a couple of interesting things in the log.  Namespace lookup failure?  Could this be the source?  A couple disks failing?  I didn't see anything in the smart logs...

 

Sep  2 23:06:40 HunterNAS kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff880607451410), AE_NOT_FOUND (20160831/psparse-543)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8806074512a8), AE_NOT_FOUND (20160831/psparse-543)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff880607451230), AE_NOT_FOUND (20160831/psparse-543)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff880607451398), AE_NOT_FOUND (20160831/psparse-543)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff880607451320), AE_NOT_FOUND (20160831/psparse-543)
Sep  2 23:06:40 HunterNAS kernel: ata1.00: ATA-8: Hitachi HDS5C3020ALA632,       ML0220F30YS4XD, ML6OA580, max UDMA/133
Sep  2 23:06:40 HunterNAS kernel: ata1.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Sep  2 23:06:40 HunterNAS kernel: ata5.00: ATA-8: Hitachi HDS5C3020ALA632,       ML0220F311GHND, ML6OA580, max UDMA/133
Sep  2 23:06:40 HunterNAS kernel: ata5.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Sep  2 23:06:40 HunterNAS kernel: ata4.00: ATA-8: Hitachi HUA723030ALA640,       MK0371YVG9PYUA, MKAOA8P0, max UDMA/133
Sep  2 23:06:40 HunterNAS kernel: ata4.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Sep  2 23:06:40 HunterNAS kernel: ata3.00: ATA-8: Hitachi HUA723030ALA640,       MK0361YHJ0N8JD, MKAOAA50, max UDMA/133
Sep  2 23:06:40 HunterNAS kernel: ata3.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff880607451230), AE_NOT_FOUND (20160831/psparse-543)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT4._GTF] (Node ffff880607451410), AE_NOT_FOUND (20160831/psparse-543)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT3._GTF] (Node ffff880607451398), AE_NOT_FOUND (20160831/psparse-543)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff880607451320), AE_NOT_FOUND (20160831/psparse-543)
Sep  2 23:06:40 HunterNAS kernel: ata1.00: configured for UDMA/133
Sep  2 23:06:40 HunterNAS kernel: ata4.00: configured for UDMA/133
Sep  2 23:06:40 HunterNAS kernel: ata5.00: configured for UDMA/133
Sep  2 23:06:40 HunterNAS kernel: ata3.00: configured for UDMA/133
Sep  2 23:06:40 HunterNAS kernel: scsi 2:0:0:0: Direct-Access     ATA      Hitachi HDS5C302 A580 PQ: 0 ANSI: 5
Sep  2 23:06:40 HunterNAS kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff880607451488), AE_NOT_FOUND (20160831/psparse-543)
Sep  2 23:06:40 HunterNAS kernel: ata6.00: ATA-8: Hitachi HUA723030ALA640,       MK0373YVHH0A4C, MKAOAA50, max UDMA/133
Sep  2 23:06:40 HunterNAS kernel: ata6.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT5._GTF] (Node ffff880607451488), AE_NOT_FOUND (20160831/psparse-543)
Sep  2 23:06:40 HunterNAS kernel: ata6.00: configured for UDMA/133
Sep  2 23:06:40 HunterNAS kernel: ata8: SATA link down (SStatus 0 SControl 300)
Sep  2 23:06:40 HunterNAS kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep  2 23:06:40 HunterNAS kernel: sd 2:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Sep  2 23:06:40 HunterNAS kernel: sd 2:0:0:0: Attached scsi generic sg1 type 0
Sep  2 23:06:40 HunterNAS kernel: sd 2:0:0:0: [sdb] Write Protect is off
Sep  2 23:06:40 HunterNAS kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Sep  2 23:06:40 HunterNAS kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep  2 23:06:40 HunterNAS kernel: ata11: SATA link down (SStatus 0 SControl 300)
Sep  2 23:06:40 HunterNAS kernel: ata12: SATA link down (SStatus 0 SControl 300)
Sep  2 23:06:40 HunterNAS kernel: ata9: SATA link down (SStatus 0 SControl 300)
Sep  2 23:06:40 HunterNAS kernel: ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Sep  2 23:06:40 HunterNAS kernel: ata10: SATA link down (SStatus 0 SControl 300)
Sep  2 23:06:40 HunterNAS kernel: ata13: SATA link down (SStatus 0 SControl 300)
Sep  2 23:06:40 HunterNAS kernel: ata14.00: ATAPI: MARVELL VIRTUALL, , 1.09, max UDMA/66
Sep  2 23:06:40 HunterNAS kernel: ata14.00: configured for UDMA/66
Sep  2 23:06:40 HunterNAS kernel: ata7.00: ATA-8: OCZ-AGILITY3, OCZ-2W4T6Y3445O71DAW, 2.22, max UDMA/133
Sep  2 23:06:40 HunterNAS kernel: ata7.00: 468862128 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Sep  2 23:06:40 HunterNAS kernel: ata7.00: configured for UDMA/133
Sep  2 23:06:40 HunterNAS kernel: ata2.00: NCQ Send/Recv Log not supported
Sep  2 23:06:40 HunterNAS kernel: ata2.00: ATA-9: ST5000DM000-1FK178,             W4J0YEEN, CC48, max UDMA/133
Sep  2 23:06:40 HunterNAS kernel: ata2.00: 9767541168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
Sep  2 23:06:40 HunterNAS kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8806074512a8), AE_NOT_FOUND (20160831/psparse-543)
Sep  2 23:06:40 HunterNAS kernel: ata2.00: NCQ Send/Recv Log not supported
Sep  2 23:06:40 HunterNAS kernel: ata2.00: configured for UDMA/133

 

Any thoughts?

 

2017-09-02 15.00.07.jpg

hunternas-diagnostics-20170902-2321.zip

  • Author

A bit more data.  There's a loop in the attached diagnostics related to plex and a memory issue.  Does this indicate a memory module problem?  Could that be the source of the server locking up all the time?

hunternas-diagnostics-20170903-1558.zip

  • 1 year later...

I'm having the same issue. Were you able to resolve this problem?

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.