Saturday, May 16, 2015

RAID whoops

IT horror story of the day from a friend in the US –


Corporation’s large RAID array drops disk 1.  They don’t have a new spare, so under protest and on direct order of the IT manager, they insert a used disk.  The array rebuild starts.


5 minutes later, they’ve got a flood of tickets from users unable to access network shares, and alarms going off from applications that have dependencies on them.


Investigation showed that the particular RAID controller will rebuild the array from NVRAM configuration… unless it finds a working schema on disk 1, then it uses that by default.  Which is a problem if your disk 1 used to be disk 1 in another array with a different schema.



No comments:

Post a Comment

Please be aware that all comments are moderated so if you're a scumbag spammer then I suggest not wasting your time. Your spam will not be seen by anyone.

Note: Only a member of this blog may post a comment.