{"id":69,"date":"2008-07-22T20:26:14","date_gmt":"2008-07-22T20:26:14","guid":{"rendered":"https:\/\/www.bishnet.net\/tim\/blog\/?p=69"},"modified":"2010-11-11T13:01:42","modified_gmt":"2010-11-11T13:01:42","slug":"a-solution-its-all-suns-fault","status":"publish","type":"post","link":"https:\/\/www.bishnet.net\/tim\/blog\/2008\/07\/22\/a-solution-its-all-suns-fault\/","title":{"rendered":"A solution? It’s all Sun’s fault."},"content":{"rendered":"

I’ve made a couple<\/a> of posts<\/a> lately about the problems we’ve been having with one of our Sun 3511 disk arrays. Sun got back to me today with what they thought the problem was. Here’s the gory detail (slightly truncated to fit this blog post):<\/p>\n

* SES\r\n\r\nCh\u00c2\u00a0 Id Chassis Vendor\/Product ID\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 Rev\u00c2\u00a0 PLD\r\n-------------------------------------------------\r\n\u00c2\u00a02\u00c2\u00a0 28 092131\u00c2\u00a0 SUN StorEdge 3511F A\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 0430 1000\r\n\u00c2\u00a03\u00c2\u00a0 28 092131\u00c2\u00a0 SUN StorEdge 3511F D\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 0420 1100*\r\n\r\n* indicates SES or PLD firmware mismatch.<\/pre>\n
This appears in a few places, so I’ve only quoted the one Sun spotted. It boils down to the components in the array having inconsistent firmware revisions. This could very well have caused the crash we saw yesterday<\/a>.<\/p>\n
This is something I blame Sun for. Firstly, they shipped out a controller with mismatched firmwares on it. I guess this sort of thing might happen though, but the field engineer should really have spotted the mistake when he was onsite and getting the replacement controller configured.<\/p>\n
Today Sun wanted to send out another engineer to get the firmware updated, and when I came back from shifting some stuff around I had a voicemail from dispatch. It’s good to see them being so proactive at fixing the issue, although I wonder if it’s because they realised it was their fault?<\/p>\n
However, being as I am a sysadmin,\u00c2\u00a0I figured I could save everyone a lot of time and hassle if I did the upgrade myself. Sun gave me the link and a couple of hours later it was all sorted (and I even managed to shift some furniture around the building in the middle of it). We’ve agreed with Sun to wait until next week to ensure things are working as they should, then we’ll close the case.<\/p>\n
In the meantime I have our largest volume resyncing, but have some familiar looking problems cropping up with the other. Somehow I fear this saga isn’t quite over yet…<\/p>\n","protected":false},"excerpt":{"rendered":"
I’ve made a couple of posts lately about the problems we’ve been having with one of our Sun 3511 disk arrays. Sun got back to me today with what they thought the problem was. Here’s the gory detail (slightly truncated to fit this blog post): * SES Ch\u00c2\u00a0 Id Chassis Vendor\/Product ID\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0\u00c2\u00a0 Rev\u00c2\u00a0 PLD ————————————————- \u00c2\u00a02\u00c2\u00a0 28 092131\u00c2\u00a0 SUN StorEdge …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-69","post","type-post","status-publish","format-standard","hentry","category-work"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t