{"id":970,"date":"2013-01-30T12:30:14","date_gmt":"2013-01-30T12:30:14","guid":{"rendered":"http:\/\/www.kozeniauskas.com\/itblog\/?p=970"},"modified":"2013-02-06T12:18:09","modified_gmt":"2013-02-06T12:18:09","slug":"fsm-unable-to-find-storage-controller-device-for-syschassis-4blade-2boardstorage-sas-1-to-perform-image-update","status":"publish","type":"post","link":"http:\/\/www.kozeniauskas.com\/itblog\/2013\/01\/30\/fsm-unable-to-find-storage-controller-device-for-syschassis-4blade-2boardstorage-sas-1-to-perform-image-update\/","title":{"rendered":"UCS: FSM: Unable to find Storage Controller Device for sys\/chassis-4\/blade-2\/board\/storage-SAS-1 to perform Image update"},"content":{"rendered":"

Here is a strange error that popped up recently.
\nAfter server reboot the blade got stuck on 47% of associating service profile.
\nHere is the error:<\/p>\n

Remote Result: Service Unavailable
\nRemote Error Code: 4106
\nRemote Error Description: Unable to find Storage Controller Device for sys\/chassis-4\/blade-2\/storage-SAS-1 to perform Image update<\/em><\/em><\/em><\/p>\n

\"1\"<\/a><\/p>\n

 <\/p>\n

When looking in the KVM Console for the blade I can see that it was sitting in the screen below:
\n\"2\"<\/a><\/p>\n

Here are the things that I’ve tried to fix this and none of these worked:
\n1. As it was saying about the image update for Storage adapter I though I’ll remove Host firmware policy from the service profile.
\n2. Next I created a new Host firmware policy but only added firmware SAS storage controller and chose different version than it had.
\n3. Remove and add service profile back<\/p>\n

Here is what worked though:
\nRemoved service profile from blade, re-acknowledged the blade added service profile back. After this the error was gone and the blade was booting normally.
\nThe last step was to add old Hast firmware policy to the service profile and check if that brakes it again, but all worked as expected.
\nSo I’m happy that the blade is back but cannot explain how and why this has happened.<\/p>\n","protected":false},"excerpt":{"rendered":"

Here is a strange error that popped up recently. After server reboot the blade got stuck on 47% of associating service profile. Here is the error: Remote Result: Service Unavailable Remote Error Code: 4106 Remote Error Description: Unable to find Storage Controller Device for sys\/chassis-4\/blade-2\/storage-SAS-1 to perform Image update   When looking in the KVM […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[380,381],"tags":[443,497,441,440,498,442],"_links":{"self":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts\/970"}],"collection":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/comments?post=970"}],"version-history":[{"count":4,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts\/970\/revisions"}],"predecessor-version":[{"id":976,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts\/970\/revisions\/976"}],"wp:attachment":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/media?parent=970"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/categories?post=970"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/tags?post=970"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}