SL150 - "Unable to Sense Robotic Device" Reported in System Messages (Doc ID 1536488.1)

Last updated on JULY 25, 2022

Applies to:

Symptoms

Having issues with all the drives going up and down intermittently.

messages(58): Mar  6 06:13:52 betuat01 tldd[6210]: [ID 615307 daemon.error] TLD(1) [6210] timed out after waiting 860 seconds for ready, drive 8
messages(77): Mar  6 06:31:03 betuat01 tldd[6527]: [ID 552616 daemon.error] TLD(1) [6527] timed out after waiting 860 seconds for ready, drive 7
messages(294): Mar  6 18:19:55 betuat01 tldd[17404]: [ID 324735 daemon.error] TLD(1) unavailable: initialization failed: Unable to sense robotic device
messages(306): Mar  6 18:22:50 betuat01 tldd[17404]: [ID 324735 daemon.error] TLD(1) unavailable: initialization failed: Unable to sense robotic device
messages(308): Mar  6 18:26:58 betuat01 tldd[17404]: [ID 324735 daemon.error] TLD(1) unavailable: initialization failed: Unable to sense robotic device
messages(315): Mar  6 20:02:24 betuat01 tldd[18908]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages(339): Mar  6 20:06:44 betuat01 tldd[19708]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages(659): Mar  7 15:56:13 betuat01 tldd[6028]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages(2086): Mar  7 17:22:33 betuat01 tldd[5445]: [ID 324735 daemon.error] TLD(1) unavailable: initialization failed: Unable to sense robotic device
messages(2103): Mar  7 17:24:39 betuat01 tldd[5445]: [ID 324735 daemon.error] TLD(1) unavailable: initialization failed: Unable to sense robotic device
messages(2104): Mar  7 17:26:42 betuat01 tldd[5445]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages(3602): Mar  7 17:47:37 betuat01 tldd[5444]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages(5071): Mar  7 18:51:17 betuat01 tldd[5454]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages(5159): Mar  7 19:02:33 betuat01 tldd[10234]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages(5174): Mar  7 19:09:53 betuat01 tldcd[11197]: [ID 133939 daemon.notice] Skipping TLD(1), it's controlled by another host (sr71)
messages(5182): Mar  7 19:12:45 betuat01 tldd[11847]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages(5203): Mar  7 19:23:55 betuat01 tldd[12632]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages.0(8427): Mar  1 19:08:59 betuat01 tldd[11543]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages.0(8472): Mar  1 19:18:14 betuat01 tldd[12284]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages.0(8485): Mar  1 19:46:54 betuat01 tldd[13144]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages.0(8500): Mar  1 19:53:34 betuat01 tldd[13858]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages.0(8628): Mar  3 07:13:37 betuat01 tldd[24417]: [ID 193470 daemon.error] TLD(1) [24417] timed out after waiting 852 seconds for ready, drive 8
messages.0(8645): Mar  3 07:56:35 betuat01 tldd[25015]: [ID 568650 daemon.error] TLD(1) [25015] timed out after waiting 856 seconds for ready, drive 7
messages.0(8684): Mar  3 13:19:11 betuat01 tldd[226]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages.0(9979): Mar  3 14:06:18 betuat01 tldd[5828]: [ID 947741 daemon.notice] TLD(1) going to UP state
messages.0(10025): Mar  3 14:09:39 betuat01 tldd[10485]: [ID 947741 daemon.notice] TLD(1) going to UP state

SL150 appears to be working functionally with the drives.  No hardware issues seen.

Changes

 New Install.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.