Jump to content

Recommended Posts

Posted

Black cats, ladders, mirrors and bad numbers... all seemed a tad silly to me until this Friday the 13th. One dirty MS patch that forced a reboot despite settings and that changed. Three blown server hard drives later I may now be a tad superstitious.

 

Next time I may well just shut everything down on thursday the 13th and not boot anything back up till saturday the 15th in order to avoid the day all together.

 

MS is lucky that I have not yet mailed their security team a box of dog leavings to show them how I feel.

  • Thanks 1
Posted (edited)

FFFFFFFFFFFF!!! - as a lovely follow up while going through a door I managed to drop my own portable hard drive onto the concrete below. I seem to have contracted a hard drive killing diesease and obviously need to be quarenteened on a nice island somewhere far away from rotating platters.

 

Edit, the machine I am writing this on now is just a basic workstation so if the hd in this dies I simply don't care :)

Edited by SYNACK
Posted

I hope for your sake Synack those three hard drives weren't in a RAID array. That would be rather unfortunate!

 

I'm generally not superstitious but weirdly I remember years ago, everytime I look at the time it would read 1:13, 2:13, 3:13... it did become a little annoying, but then like magic it stopped.

  • Thanks 1
Posted
I hope for your sake Synack those three hard drives weren't in a RAID array. That would be rather unfortunate!

 

I'm generally not superstitious but weirdly I remember years ago, everytime I look at the time it would read 1:13, 2:13, 3:13... it did become a little annoying, but then like magic it stopped.

No such luck I'm afraid, lukily its school holidays here or the excrement would have hit the rotating propeller much harder. Two of the drives were in a 1+0 of 6 drives but statisticly were very unkind in the order of failure and the third was luckilly in a raid 5 array but the hold in the reboot - press f1 to continue - caused the failure of the DFS namespace servers services on reboot dropping the DFS shares for the whole domain untill I tracked down the fault - moral, don't migrate DFS roots from 2000 to 2008 and expect them to follow the rules.

Posted
One dirty MS patch that forced a reboot despite settings and that changed.

MS is lucky that I have not yet mailed their security team a box of dog leavings to show them how I feel.

 

Well that explains the MS Security Bulletin amendment email I got this morning.....

Posted
Share??

 

********************************************************************

Title: Microsoft Security Bulletin Minor Revisions

Issued: March 13, 2012

********************************************************************

 

Summary

=======

The following bulletins have undergone a minor revision increment.

Please see the appropriate bulletin for more details.

 

* MS11-030 - Critical

* MS11-025 - Important

* MS11-067 - Important

 

 

Bulletin Information:

=====================

 

 

* MS11-030 - Critical

 

- Microsoft Security Bulletin MS11-030 - Critical : Vulnerability in DNS Resolution Could Allow Remote Code Execution (2509553)

- Reason for Revision: V1.1 (March 13, 2012): Added a link to

Microsoft Knowledge Base Article 2509553 under Known Issues

in the Executive Summary.

- Originally posted: April 12, 2011

- Updated: March 13, 2012

- Bulletin Severity Rating: Critical

- Version: 1.1

 

* MS11-025 - Important

 

- Microsoft Security Bulletin MS11-025 - Important : Vulnerability in Microsoft Foundation Class (MFC) Library Could Allow Remote Code Execution (2500212)

- Reason for Revision: V4.3 (March 13, 2012): Added an entry to

the update FAQ to announce a detection change for KB2565063

and KB2565057 to correct an installation issue. This is a

detection change only. There were no changes to the security

update files. Customers who have already successfully updated

their systems do not need to take any action.

- Originally posted: April 12, 2011

- Updated: March 13, 2012

- Bulletin Severity Rating: Important

- Version: 4.3

 

* MS11-067 - Important

 

- Microsoft Security Bulletin MS11-067 - Important : Vulnerability in Microsoft Report Viewer Could Allow Information Disclosure (2578230)

- Reason for Revision: V1.1 (March 13, 2012): Added an entry to the

update FAQ to announce a detection change for KB2548826 to correct

an installation issue. This is a detection change only. There were

no changes to the security update files. Customers who have already

successfully updated their systems do not need to take any action.

- Originally posted: August 9, 2011

- Updated: March 13, 2012

- Bulletin Severity Rating: Important

- Version: 1.1

  • Thanks 1
Posted
FFFFFFFFFFFF!!! - as a lovely follow up while going through a door I managed to drop my own portable hard drive onto the concrete below. I seem to have contracted a hard drive killing diesease and obviously need to be quarenteened on a nice island somewhere far away from rotating platters.

 

Edit, the machine I am writing this on now is just a basic workstation so if the hd in this dies I simply don't care :)

 

Not sure if this is the silver lining but at a guess said hard drive wasn't a 'what data' drive he he, if it wasn't , it is now :D

Posted
Not sure if this is the silver lining but at a guess said hard drive wasn't a 'what data' drive he he, if it wasn't , it is now :D

 

No to my suprise those drives and the two that died earlier in the week were all Seagate/HP rebranded Seagate. I don't know if they had some kind of kill switch built in or what but in total five drives have died in very short succession.

 

I knew that all the drives reliability ratings had gone down but this is insane, they are dropping like late 90s floppy disks at the moment. I'm half expecting to have to buy replacements in packs of ten.

 

Moving production to thailand seems to have been the worst decision that the HD makers could have made, their product was that bad that even nature tried to put a stop to it.

Posted
No to my suprise those drives and the two that died earlier in the week were all Seagate/HP rebranded Seagate. I don't know if they had some kind of kill switch built in or what but in total five drives have died in very short succession.

 

I knew that all the drives reliability ratings had gone down but this is insane, they are dropping like late 90s floppy disks at the moment. I'm half expecting to have to buy replacements in packs of ten.

 

Moving production to thailand seems to have been the worst decision that the HD makers could have made, their product was that bad that even nature tried to put a stop to it.

 

There way of saying that we should move onto Solid State / Flash Storage ie PCI - E SSD's etc or even just SATA 3 SSD's ??

Posted
There way of saying that we should move onto Solid State / Flash Storage ie PCI - E SSD's etc or even just SATA 3 SSD's ??

 

If so its seems a silly business plan for them as they don't make any of those things.

  • Thanks 1
Posted
Originally Posted by plexer

Trying to avoid Friday the 14th in that case?

 

Ben

Clarification?[/Quote]

 

Think he means this bit :)

 

Next time I may well just shut everything down on thursday the 13th and not boot anything back up till saturday the 15th in order to avoid the day all together.

  • Thanks 1
Posted

I swapped over our core switch (8206zl with another 8206zl on friday 13th)........went without a hitch in just 30minutes :D

 

Just thought i'd show off how well my friday went lol

Posted
Think he means this bit :)

 

Yikes, even my maths is broken.

 

Further, one of the servers decided to fail to reboot thanks to a cooked stick of RAM but I only found out about it a day later (dirty Acer).

 

Next time I am going to shelter in a nuclear bunker, that may be the only safe place for me.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...