<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I agree with Phil’s assessment. Time
to replace the drive, if you want to try something before that, do a complete
image backup, then reformat the drive and re run the app to see if you still
have errors. I’ve known of a single sector that caused the entire system
to seem like it failed. However, with the cost of drives these days, it’s
best to replace the drive.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Jon<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
plug-bounces@plug.org.au [mailto:plug-bounces@plug.org.au] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Phillip Bennett<br>
<b><span style='font-weight:bold'>Sent:</span></b> Monday, 28 March 2011 10:15
AM<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">plug@plug.org.au</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [plug] error trying
to boot into ubuntu 10</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Hi David,<br>
<br>
>From reading the log you posted, this part seems the most important to me;<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
<br>
[ 490.196216] ata3.00: status: { DRDY ERR }<br>
[ 490.196219] ata3.00: error: { UNC }<br>
[ 490.198376] ata3.00: configured for UDMA/133<br>
[ 490.198386] ata3: EH complete<br>
[ 494.543476] ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0<br>
[ 494.543483] ata3.00: irq_stat 0x40000008<br>
[ 494.543489] ata3.00: failed command: READ FPDMA QUEUED<br>
[ 494.543500] ata3.00: cmd 60/00:00:97:01:de/01:00:16:00:<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>00/40 tag 0 ncq 131072 in<br>
[ 494.543502] res
41/40:00:1b:02:de/00:00:16:00:00/40 Emask 0x409 (media error) <F><br>
[ 494.543507] ata3.00: status: { DRDY ERR }<o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>From, this you can see the DRDY ERR (Drive Ready, Error) and the
UNC error (UNCorrectable error) which has meant physical errors for me in the
past. This is also stated as a physical error at <a
href="https://ata.wiki.kernel.org/index.php/Libata_error_messages"
target="_blank">https://ata.wiki.kernel.org/index.php/Libata_error_messages</a>.
<br>
<br>
I can see the error on the second last line there says "media
error". It looks to me as though it gets the error and resets to try
again, only to hit the same error again, and does this for a little
while. I think this is definitely a hardware error that will need fixing.<br>
<br>
I fixed mine by formatting the drive and having it mark the bad sectors as
such. I don't really trust bad sector mapping that much, so would
recommend a replacement.<br>
<br>
Hope this helps,<br>
Phil.<o:p></o:p></span></font></p>
</div>
</body>
</html>