So since I have posted the following over on the xbox forums and seem to get back quite a bit of feedback that it has solved several others RROD August 11 System Update deaths, I figured I would post it here as well before MS decides to pull the whole thread to make sure they don’t admit that they had anything to do with everyone’s consoles dying!

So my console was completely dead after working with MS support related to the Aug 11 update failure on my 3 year old Pro console. They basically wanted me to send it in saying I had a hardware failure (even though initially didn’t have RROD) and wanted the 100 bucks to repair since it was long past its warranty.

Since I wasn’t going to pay for any old hardware to be fixed that was broken by their software, I figured I would find a solution on my own since their support was pretty useless on the phone.

Since the console was working fine before the update I started to see what options to clear the system of the update. Since mine was not even getting past the 360 startup logo before it completely froze and then showed RROD recently, I had nothing to lose. It was going to meet the dumpster at this point!

First thing I did was use the sync clear method stated early on in the post and several others places in the forums and web:

1. Held the sync button (on the console to the right of the 2nd memory module port).
2. Pressed the power button (still holding down sync button the whole time) until it was at the dashboard.

Mine didn’t say anything, but oddly enough it got me past the logo and I actually could see the NXE dash now. I have not seen this for days (say the last 8 tries of starting the console). That was positive.

---

Next I used the 360 Clear Cache method (the new method, since the August 11 update was still in place at this point apparently). Not the long (X,X,LB,RB,X,X) combo.

I quickly navigated to the system blade (thinking I had less than 30 seconds before it RROD on me):

1. Selected Memory.
2. Selected Hard Drive.
3. Selected Y for device options.
4. Selected Clear Cache (3rd Choice).

In my case it freed up about 5 gigs worth of disk space by clearing out the “cache”. Dang all those software updates for games!

Restarted the console to be safe and see if everything still worked. Sure enough it started up, the lag I noticed after the August 11 update was not there and I actually was able to play two XBL games and even some Fable II. All of which was impossible the previous days.

Does this solve all my problems, probably not, but things are working again until the next failure or RROD. I find it interesting that MS doesn’t force these kinds of clearing of the cache if they can be problems with system updates.

Since both of these steps together has currently (and maybe only temporarily) fixed my RROD. This leads me to believe it is really not hardware failure! Does anyone else see something wrong with this if my console lives on and MS was going to take my 100 bucks to just clear the cache on my box and send it back to me!!! Or is there really changes to the latest system code that is taking a border line stable console and sending it over the edge?

This was the first time I ever had any failures on my 360, which would lead one to believe something not right with this system update. I wonder if these steps works for anyone else out there with the Aug 11 failures!?”

I have verified that this has worked on my console (still working many gaming sessions later) and at least 8 reported instances of others consoles (ranging from 3+ years old to not even a month old elite) being fixed by these steps above. Even with complete RROD’s. Of course I can’t guarantee this will work for anyone else’s 360 or that it will last, but it has worked on ours at this point.
Thanks for nothing Microsoft, maybe you would like to test your stuff before releasing. All for new avatar and netflix junk!? Dang, what happens come fall with the Twitter and Fackebook stuff piled on top of this… I smell smoke in them there hills?

So the console gets updated with the fabulous new August 11 auto update on XBL.  Cause I need new avatar clothes right! NOT

Installs, reboots, gets to the “new” NXE updates and you notice everything is jerky and slow.  Think to one’s self, must be that everyone and their dog is on and updating so the tubes are full (right Mr Gore).  Tried to watch a vid or two, locks up each time at different points.  Forced shutdown each time.  Not real happy with the “new” features yet MS.

Try to play a little Fable II… don’t even get past the menu when the whole console locks again.  Still no ROR either.

Try it several more times over the course of several days each time it actually seems to get worse and worse.  Taking less and less time from startup for it to lock up.

Figure I would see what the fanboys and XBOX forums say… what do you know, top of the XBOX forums general discussion list:

Installed the latest Aug. 11 Update and 360 has stopped working

Entry after entry sounds similar to mine.  Figured, heck I am out of warranty so lets call MS support and see what line they sale me.  “I have a hardware failure.”  Really, I would of never guessed.

Since I am out of warranty, that would be 99 to fix broken hardware that you have been making money off of for years and the public/media knows!

Needless to say since it wasn’t a RROD, I was years past my warranty period and MS is currently ignoring the issue and not an issue.  So good customer service.

The best part of the story is that after getting off the support call, and the console is down to mere seconds before freezing now, it RROD the last time I cycle it.

I should just sale everything 360 related and go to the horrible PS3 or worse yet a Weeeeeee!

MS stinks tonight on the East coast.  I write software for a living and if I developed something that destroyed hardware, boy I would be out of a job!

So now what to do.. maybe it is time to hang up the gaming hat.

I have to say that Verizon FIOS is one of the best moves we have made.

Switching from Comcast to FIOS is like night and day. These are our personal experience so far and YMMV.

• Cost Less
• Get More
• Better Service
• HD Quality is incredible (getting HD for less than the cost of SD on Comcast)
• Internet pipe is not shared with my neighbors!
• Incredible net speed
• Really nice router

The last one I have to admit I was shocked about.  I have always had my own firewall and network gear, but Verizon has really done a nice job on their router (but that is another post).

Internet speed:

The tech that showed up to install the service was awesome.   Really nice guy that called before showing up to tell me when he would be there (was 1 minute early from when he said he would be there).  Did everything that I had ordered in a very timely matter and it all just worked!  Took under 3 hours for us to get all new Internet and two TV receivers.  All working better than expected.

Just sweet!

More to come.

It’s always interesting to see what other developers use as their real workspace when they have control over it.  (Unlike cubical heck).

Once such sweet space is something Mitch Haile built.  I stumbled across it in one of me RSS feed consumption extravaganas and have to admit the space is really, really nice, but I have to say the screen real estate and mini server room/closet is very nice for a home build.

Just had to share the nerd eye candy for others to consume!

http://www.biscade.com/office/

Snaps on Flickr:

http://www.flickr.com/photos/bwa32/sets/72157607284828899/

Very nice work Mitch!  Kudos

If you own a Seagate drive that is fairly new, you might want to check if it is ticking data time bomb.

I thought I was safe until I realized a recently replaced 500G drive was replaced with one of their newer / quieter / cooler drives that is on their “potential” failure list.

In theory, even if the drive firmware does die, your data in theory is all there, but would have to send it back to Seagate to get it fixed and hopefully get your data back.

So for those Seagate users, head over to their site and see if you have a possible issue:

Firmware Recommendations for Seagate Drives [KB 207931]

I was able to use their Seagate Drive Detect tool (patience here, since it almost acted like it crashed the first time I used it).

It will report what drive Model, Serial and Firmware you have like this:

This way you will be able to see what Model and Firmware version you have.

As of this afternoon, their Firmware update page was scrambled (lack of better words) and could not provide the much needed information.

Next came contacting their discsupport@seagate.com email address.  Got a quick replay, that said they were working on it (once again, I think.. not really clear if they referred to the page or the firmware).  Had to send a reply and ask if the drive I was emailing them about (sent Model, Serial and Firmware version) actually needed an update since it fell between the two firmware version I heard are the issue.

Waiting on the official reply now, will update soon.

UPDATE: 2009-01-24:

Well finally got an email back from seagate support:

Thank you for contacting Seagate Support.

A firmware issue has been identified that affects a small  number of
Seagate Barracuda 7200.11 hard drive models  which may result in data
becoming inaccessible after a power-off/on operation.  The affected
products are Barracuda 7200.11, Barracuda ES.2 SATA, and DiamondMax 22.
Based on the low risk as determined by an analysis of actual field return
data, Seagate believes that the affected drives can be used as is.
However, as part of our commitment to customer satisfaction, Seagate is
offering a free firmware upgrade.

Please follow this link
(http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931)
to enter the Knowledge Base article(s) detailing the steps to update your
drive.

In the unlikely event your drive is affected and you cannot access your
data, the data still resides on the drive and there is no data loss
associated with this issue. If your drive is no longer accessible, contact
us directly for further assistance at
http://www.seagate.com/www/en-us/about/contact_us/.

NOTE:  If you have contacted Seagate Support regarding a separate issue or
about another product, please visit
http://www.seagate.com/www/en-us/about/contact_us/ to submit an email.
Thank you.

Seagate Support

So once I downloaded the correct ISO for my drive in question (Model: ST3640323AS) and went to try and apply it in the actual machine it was in, got nothing but sector read errors like 5 times and then the whole image boot failed.  That was not very reassuring that this was going to work.   Downloaded the ISO again to just make sure it was not a failed iso or burn.  Same results.

Figured I would take the drive out and put it on my test bench skeleton machine and see if I get the same error.  Nope… worked as expected.  FreeDOS boot loader started right up.  Saw their instruction readme.txt file show up.  Then prompted with a screen to upload firmware, scan drives on machine or quit basically.  I tried the SeagateEnum (scan) first to verify that it saw my Seagate drive fine (remember it is just the CD and single Seagate drive on the chain).  It saw it, saw the firmware version everything looked good.

Uploaded the new firmware binary to the drive (after some really funky fairly load clicking… I assume parking of the heads or something), took about 30 seconds.  Then it said it uploaded fine and that I had to POWER CYCLE the machine (no 3 finger salute here).  Did that, heard some extra (not normally heard) noise from the drive and but it spun up fine.  Booted to the CD again and verified via the SeagateEnum drive chain scanner to see that indeed the drive was reporting new firmware.  Yep, it was now at version: SD1B.

Everything seems to be working fine, since I am typing this update on the machine with the flashed drive in it.  Not that I had problems before with the drive, but since the problem appears when you power off and back on.  The drives never come back online.  Thankfully that did not happen and hopefully will not happen now!

There is a great Coding Horror write up by Jeff which gives a interesting perspective (most likely management.. but still the same) on the trade off of what your developer costs you and what new more powerful hardware costs you.

Hardware is Cheap, Programmers are Expensive

The post eludes to several key points, many of which I try to get management on numerous efforts to understand all the time.  Some hold true, but there is a point of no return.  Sometimes just throwing iron at it will only make more of mess (especially in the energy conscious era we have stepped into these recent years.)

Remember the quote, “To make money, you have to spend money.”… well the spin I see here is, “To save money, you have to spend money, sometimes.”

This directly ties into the The Programmer’s Bill of Rights.

I remember the days of Windows development that I heard that they did not want to give the development team too fast of machines, since then the code they wrote would never perform well on “normal” hardware that end users would have.  That was some what true, but much less important (excluding fancy fancy stuff) in a web centric world.  Now it has to deal with the size of the pipe and not the engine.

Over the years I have seen more times than not, is not about optimizing (as eluded to by Jeff) but cleaning and/or refactoring.  I usually find 9 out of 10 times if I refactor code when trying to make more out of it I get more bang for the buck.  But that also means you live a life of refactoring (which all good developer should).  This helps with:

• Stop the code decay / erosion.  All code dies over time.  (Try to get management to understand that one right?  Some developers don’t even understand it sadly enough.)
• Make the code more clear and concise for future developers who will have to read it.  (If it doesn’t you probably refactored wrong).
• Enhance the current functionality with less code (more bang for the buck).  Yes Virgina, there is a Santa Claus and this can happen to you too.
• Evolve the code to newer library/standards/technology.

The last bullet point is something I have found very important in the Java world.  You find that you have (or someone else) has written code for a project 5,6,10 years ago based upon JDK, lib, etc at the time.  If you evolve the code to use more modern JDK run-time libraries or even specific 3rd party libs/projects that didn’t exist back then, you can get some great windfall.  (Of course done with great scrutiny).

As always, there is not just black and white.  There is not just one solution to all problems.  Find the right shoe and make sure it fits.