Main Area and Open Discussion > Living Room

Ground Hog Day - failed system image restoring yet again

<< < (2/3) > >>

nudone:
This does not necessarily meet the criteria for incompetence. Incompetence is knowing how to do a job, but failing to do it anyway.
This case looks more like either ignorance or a lack of adequate training (or both) is what got you here.

If that is the case, then it is a management failure (and grossly unfair) to put someone into a a job - a position of responsibility for something - without ensuring that they are adequately equipped to properly execute that job/responsibility to the best of their ability. - paraphrased from W.Edwards Deming.

If you had known better, but still took the risk anyway, then that would probably be a different matter.

Good luck with the recovery.
-IainB (December 13, 2011, 03:20 PM)
--- End quote ---

Oh, I do know better. I've been using system backups since Ghost was made available to me (before Norton picked it up) when it took away the pain of reinstalling Windows off of floppy disks. So, I've simply become lazy and happy to pretend that I don't have time to test backups - because they've GOT to work, they can't fail, I haven't time for them to fail, that's just not an option.

So, like I say, I'm incompetent. I ought to hand in my resignation and start basket weaving for a job or something. But I'm self-employed so I'm stuck with my own IT Dept. run by a total arrogant sod who believes testing is for losers.

edit:
Just thought I'd better add. Now I'm not even sure if did or did not test the first backup I made for this new system. I'm beginning to think I did test it as I've had issues with Paragon before. So, if I DID test it, that means I can't even trust it when it works. Which then implies that one method of backup isn't enough. Looks like I've just got to start taking matters seriously if I want things to remain reliable. It's all a bit of a game at the moment; gambling on whether the computer will work or not. And I can't afford that - so I'm being more stupid than I first thought.

Stoic Joker:
It might help if you mentioned what code the BSOD contained.

The behavior does sound vaguely (I emphasize vague due to a lack of detail :)) familiar. I had a batch of new Dells that exhibited much the same behavior, until I uninstalled the ATI Catalyst Control Center. No more BSODS after 2 month of 24/7 running after removal of the CCC.

Just a thought - Shit drove me (and the client) nutz for 3 months.

nudone:
Adding a bit more, for what it's worth...

...looking around the web, people are reporting that the OCZ ssd likes to bluescreen and freeze - which is exactly what this new machine does, and yep, I have a OCZ ssd. This is what I suspected but didn't want to believe (I had to return the previous "new" machine because the ssd in that one died after 5 days).

If I do anything with all this testing rigmarole, I'll first just rip out the ssd and stick a proper drive in its place. In fact, I think I'll just order a small drive tomorrow and try putting the windows backup onto it.

nudone:
It might help if you mentioned what code the BSOD contained.
-Stoic Joker (December 13, 2011, 04:36 PM)
--- End quote ---

I'll start paying more attention to what it is and write it down - but, as I've just posted before I saw your post above, the machine also likes to freeze so no bluescreen codes there.

One pattern (I think) to these problems is that they tend to happen in the afternoon - perhaps when the ssd is getting too hot???

nudone:
Okay, having read about even more people with OCZ vertex 3 ssd problems it now seems very, very likely that this is the problem with my machine. And it also sounds like OCZ haven't resolved the problem regardless of the firmware updates they released.

Looks like I can resolve this problem very quickly by hammering a 6" nail through the ssd.

Navigation

[0] Message Index

[#] Next page

[*] Previous page