I asked what the community thought was too simple. Here is the link. And yes it has been voted down and closed. I am happy with that. I am just surprised at the tone of some comments. Does it help the community by using terms like "crap" on genuine queries? Honestly?
But the question was crap; if my hand is lying on the floor, blood is spurting from my wrist and I'm losing consciousness I don't ask my Doctor what's up, it's beyond obvious.
Serverfault is for professional sysadmins, who tend to read and comprehend error messages.
As the others have pointed out, "crap question" is an accepted term in the StackExchange world.
Beyond that, SF - like the other SE sites - is a community and has some community norms, including a dislike of poor quality questions. Things that go against those norms will sometimes get harsh treatment. Most of the regulars are pretty easy-going most of the time, but any given bad question might happen to get a harsher response. There are no long-term consequences, you're welcome to ask a more appropriate question any time and no-one is going to remember that they thought an earlier question was less on-topic.
There are two other issues in play here:
Question migration is a complicated topic for the community.
The "crap" reference comes from Jeff's answer on this topic.
Poorly researched/asked questions are not warmly received here.
Your question reads as though you've invested zero effort in writing it, or finding resolution. You may want to learn more about how to ask better questions prior to your next posting.
I was merely quoting Jeff Atwood (one of the founders of Stack Exchange) who will often be caught spouting don't migrate crap, and I happen to strongly agree with his opinion.
The reason I voted down and voted to close your question was because it practically contained the answer inside of it. In my very humble opinion you wasted your time posting it and everyone else's time who decided to read it.
The 'crap' comment refers to the principal of 'Not migrating crap'. Your question was deemed off topic for SF and early voters suggested it should be migrated to SU. As the answer to your question was contained in the error message you posted then it was deemed a crap question and dealt with accordingly.
Sorry, if an end user can't figure out what an absurdly obvious error message like this means they should be taking the machine to someone who knows something about computers, rather than asking for help in an inappropriate place. As such there's just no way it belongs or SU, let alone SF.
If you feel offended by how we view the question just imagine how we feel every time we see such questions. What you've done is the equivalent of taking your personal computer to work and asking the IT department to fix it for you. Please do us the courtesy of reading the FAQ before posting again.
I wouldn't consider this question crap in a user context. A message like “smart failure predicted on hard disk 0” (or even “SMART failure predicted on hard disk 0”) is absolutely not clear to an end user. So the question would be ok on Super User.
But Server Fault is intended for professionals. Professionals are expected to know what SMART is already; or if they don't they're at least expected to realize that it's a technical term that they need to look up.
So from an SF perspective, this question is crap. From an SU perspective, it's a valid question. Ideally the question should have been migrated, but in this case it's perfectly understandable that closers would take the safe path and not migrate a question that doesn't look good to them.