NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

ONTAP Discussions

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

ONTAP Discussions

Ask a Question

"controller failover of PRO-BACKUP-SPB not possible: unsynchronized log "

xiatian
‎2020-12-24 07:01 PM
3,696 Views

hI, ALL

 could anyone help me for the following the error messages, what's wrong for the error messages? how to solve it ?

the  hardware environmet, 

 NetApp Release 8.2.4P1 7-Mode: Wed Dec 23 18:32:25 PST 2015
System ID: 2015179694 (PRO-FAS3220-SPB); partner ID: 2017755174 (PRO-FAS3220-SPA)
System Rev: B2

 

Mon Dec 21 15:16:12 CST [PRO-BACKUP-SPA:monitor.globalStatus.critical:CRITICAL]: Controller failover of PRO-BACKUP-SPB is not possible: unsynchronized log. /vol/LLDB is full (using or reserving 99% of space and 0% of inodes, using 99% of reserve).
Mon Dec 21 15:17:14 CST [PRO-BACKUP-SPA:monitor.globalStatus.nonCritical:warning]: /vol/LLDB is full (using or reserving 99% of space and 0% of inodes, using 99% of reserve).
Mon Dec 21 15:25:01 CST [PRO-BACKUP-SPA:disk.healthTrigger:warning]: Disk 4b.05.10 received NHT health trigger (0x1 0xb 0x5d 0x10)

0 Kudos
3 REPLIES 3

paul_stejskal
NetApp
‎2020-12-25 07:20 AM
3,650 Views

I don't see that in this month's ASUP.

 

Possibly a bad disk?

0 Kudos

xiatian
‎2020-12-30 10:22 PM
In response to paul_stejskal
3,585 Views

hi, expert: badly disk  ？ actually  i dont  found a bad disk. 

0 Kudos

paul_stejskal
NetApp
‎2020-12-31 07:31 AM
In response to xiatian
3,569 Views

It is a bad mailbox disk it looks like:

[?] Sat Dec 12 05:06:04 CST [BOC-FAS3220-SPB: pmcsas_intrd_2: sas.adapter.debug:info]: params: {'debug_string': 'BAD destination on OPEN (0x14) -- delaying: dev 0a.01.2, cdb 0x28:44626e28:0008 (0/117310435), NDU 0x0', 'adapterName': '0a'}
[?] Sat Dec 12 05:06:04 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: sas.adapter.debug:info]: params: {'debug_string': 'BAD destination on OPEN (0x14) -- delaying: dev 4c.01.2, cdb 0x28:44626e28:0008 (0/117310435), NDU 0x0', 'adapterName': '4c'}
[?] Sat Dec 12 05:06:05 CST [BOC-FAS3220-SPB: pmcsas_asyncd_0: sas.adapter.debug:info]: params: {'debug_string': 'DISCOVERY: REPORT GENERAL on expander 5:0050cc:105006f:bf: Configing 2 -- continuing (0)', 'adapterName': '4c'}
[?] Sat Dec 12 05:06:05 CST [BOC-FAS3220-SPB: pmcsas_asyncd_0: sas.adapter.debug:info]: params: {'debug_string': 'Device 4c.01.2 invalidate debounce - 40', 'adapterName': '4c'}
[?] Sat Dec 12 05:06:05 CST [BOC-FAS3220-SPB: pmcsas_asyncd_0: sas.adapter.debug:info]: params: {'debug_string': 'Asyncd device scan done.', 'adapterName': '4c'}
[?] Sat Dec 12 05:06:05 CST [BOC-FAS3220-SPB: pmcsas_asyncd_2: sas.adapter.debug:info]: params: {'debug_string': 'Device 0a.01.2 invalidate debounce - 40', 'adapterName': '0a'}
[?] Sat Dec 12 05:06:05 CST [BOC-FAS3220-SPB: pmcsas_asyncd_2: sas.adapter.debug:info]: params: {'debug_string': 'Asyncd device scan done.', 'adapterName': '0a'}
[?] Sat Dec 12 05:06:09 CST [BOC-FAS3220-SPB: pmcsas_asyncd_0: sas.adapter.debug:info]: params: {'debug_string': 'DISCOVERY: REPORT GENERAL on expander 5:0050cc:105006f:bf: Configing 2 -- continuing (1)', 'adapterName': '4c'}
[?] Sat Dec 12 05:06:09 CST [BOC-FAS3220-SPB: pmcsas_asyncd_0: sas.adapter.debug:info]: params: {'debug_string': 'DISCOVERY: REPORT GENERAL on expander 5:0050cc:1050155:bf: Configing 2 -- continuing (0)', 'adapterName': '4c'}
[?] Sat Dec 12 05:06:09 CST [BOC-FAS3220-SPB: pmcsas_asyncd_0: sas.adapter.debug:info]: params: {'debug_string': 'DISCOVERY: REPORT GENERAL on expander 5:0050cc:10500ca:bf: Configing 2 -- continuing (0)', 'adapterName': '4c'}
[?] Sat Dec 12 05:06:09 CST [BOC-FAS3220-SPB: pmcsas_asyncd_0: sas.adapter.debug:info]: params: {'debug_string': 'Device 4c.01.2 came back.', 'adapterName': '4c'}
[?] Sat Dec 12 05:06:09 CST [BOC-FAS3220-SPB: pmcsas_asyncd_0: sas.adapter.debug:info]: params: {'debug_string': 'Asyncd device scan done.', 'adapterName': '4c'}
[?] Sat Dec 12 05:06:09 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: sas.adapter.debug:info]: params: {'debug_string': 'BAD destination on OPEN (0x14) -- delaying: dev 4c.01.2, cdb 0x28:44626638:0008 (0/5), NDU 0x0', 'adapterName': '4c'}
[?] Sat Dec 12 05:06:09 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: sas.adapter.debug:info]: params: {'debug_string': 'BAD destination on OPEN (0x14) -- delaying: dev 4c.01.2, cdb 0x28:44626e28:0008 (1/0), NDU 0x0', 'adapterName': '4c'}
[?] Sat Dec 12 05:06:10 CST [BOC-FAS3220-SPB: pmcsas_asyncd_2: sas.adapter.debug:info]: params: {'debug_string': 'Device 0a.01.2 came back.', 'adapterName': '0a'}
[?] Sat Dec 12 05:06:10 CST [BOC-FAS3220-SPB: pmcsas_asyncd_2: sas.adapter.debug:info]: params: {'debug_string': 'Asyncd device scan done.', 'adapterName': '0a'}
[?] Sat Dec 12 05:06:11 CST [BOC-FAS3220-SPB: cf_main: cf.fsm.takeoverOfPartnerDisabled:error]: Failover monitor: takeover of BOC-FAS3220-SPA disabled (status of backup mailbox is uncertain).
[?] Sat Dec 12 05:06:12 CST [BOC-FAS3220-SPB: pmcsas_asyncd_2: sas.adapter.debug:info]: params: {'debug_string': 'Asyncd device scan done.', 'adapterName': '0a'}
[?] Sat Dec 12 05:06:13 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: scsi.cmd.notReadyCondition:notice]: Disk device 4c.01.2: Device returns not yet ready: CDB 0x28:44626e28:0008: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x0)(8834).
[?] Sat Dec 12 05:06:13 CST [BOC-FAS3220-SPB: pmcsas_asyncd_0: sas.adapter.debug:info]: params: {'debug_string': 'Asyncd device scan done.', 'adapterName': '4c'}
[?] Sat Dec 12 05:06:14 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: scsi.cmd.notReadyCondition:notice]: Disk device 4c.01.2: Device returns not yet ready: CDB 0x28:44626e28:0008: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x0)(9833).
[?] Sat Dec 12 05:06:14 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: scsi.cmd.notReadyCondition:notice]: Disk device 4c.01.2: Device returns not yet ready: CDB 0x28:44626638:0008: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x0)(8714).
[?] Sat Dec 12 05:06:14 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: disk.ioRecoveredError.retry:info]: Recovered error on disk 4c.05.11: op 0x28:1d5a7cd0:0008 sector 0 SCSI:recovered error - Disk used internal retry algorithm to obtain data (1 b 5d 5) (3) [NETAPP   X412_S15K7560A15 NA04] S/N [6SL7308V0000N40913ZH]
[?] Sat Dec 12 05:06:14 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: disk.IO.status:debug]: params: {'deviceName': '4c.05.11', 'returnCode': '5', 'pathRetryCount': '0', 'adapterStatus': '0x0', 'cdb': '0x28:1d5a7cd0:0008', 'basicTimeout': '5', 'iASCQ': '0x5d', 'iSenseKey': '0x1', 'sSenseCode': '', 'ETime': '3', 'iASC': '0xb', 'victimRetryCount': '0', 'sSenseKey': 'SCSI:recovered error', 'targetStatus': '0x2', 'disk_information': '[NETAPP   X412_S15K7560A15 NA04] S/N [6SL7308V0000N40913ZH]', 'retryCount': '0', 'pathsTried': '1', 'timeoutRetryCount': '0'}
[?] Sat Dec 12 05:06:15 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: scsi.cmd.notReadyCondition:notice]: Disk device 4c.01.2: Device returns not yet ready: CDB 0x28:44626e28:0008: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x0)(10833).
[?] Sat Dec 12 05:06:15 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: scsi.cmd.notReadyCondition:notice]: Disk device 4c.01.2: Device returns not yet ready: CDB 0x28:44626638:0008: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x0)(9713).
[?] Sat Dec 12 05:06:16 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: scsi.cmd.notReadyCondition:notice]: Disk device 4c.01.2: Device returns not yet ready: CDB 0x28:44626e28:0008: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x0)(11833).
[?] Sat Dec 12 05:06:16 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: scsi.cmd.notReadyCondition:notice]: Disk device 4c.01.2: Device returns not yet ready: CDB 0x28:44626638:0008: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x0)(10713).
[?] Sat Dec 12 05:06:17 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: scsi.cmd.notReadyCondition:notice]: Disk device 4c.01.2: Device returns not yet ready: CDB 0x28:44626e28:0008: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x0)(12833).
[?] Sat Dec 12 05:06:17 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: scsi.cmd.notReadyCondition:notice]: Disk device 4c.01.2: Device returns not yet ready: CDB 0x28:44626638:0008: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x0)(11713).
[?] Sat Dec 12 05:06:18 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: scsi.cmd.retrySuccess:info]: Disk device 4c.01.2: request successful after retry #0/#4: cdb 0x28:44626638:0008 (12713).
[?] Sat Dec 12 05:06:18 CST [BOC-FAS3220-SPB: pmcsas_intrd_0: scsi.cmd.retrySuccess:info]: Disk device 4c.01.2: request successful after retry #0/#5: cdb 0x28:44626e28:0008 (13849).
[?] Sat Dec 12 05:06:18 CST [BOC-FAS3220-SPB: cf_main: cf.fsm.takeoverOfPartnerEnabled:notice]: Failover monitor: takeover of BOC-FAS3220-SPA enabled
0 Kudos
Announcements
All Community Forums
Public