NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-macppc/59014: Shutdown -r now often freezes on macppc b&w G3
The following reply was made to PR port-macppc/59014; it has been noted by GNATS.
From: Chris Tucker <capa150%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost, port-macppc-maintainer%netbsd.org@localhost,
gnats-admin%netbsd.org@localhost
Cc:
Subject: Re: port-macppc/59014: Shutdown -r now often freezes on macppc b&w G3
Date: Wed, 5 Feb 2025 21:33:29 -0800
--000000000000a7016b062d7295fe
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Modifying the kernel to turn off UDMA and even DMA did not resolve the
problem when running the drive off the motherboard UDMA port.
(Also, as an aside, I got no rndctl crashes when I ran the drive off
the "IDE" port on the Mac's motherboard, which is normally used for the
CDROM and different from the UDMA port)
I purchased a Sonnet ATA Tempo 133 IDE controller and connected the drive
to it.
This eliminated the rndctl problem entirely when using the unaltered
GENERIC kernel. I ran a script to test rndctl 250 times for both load and
save. The Mac never crashed.
However, there was a new problem: I got well over 100 repeated
warnings/errors:
wd0: error reading fsbn ... xfer f70, retry 0
wd0: (aborted command, interface CRC error)
wd0: soft error (corrected) xfer f70
These errors occur during the installer process, making it difficult to
read. It does successfully install, however.
The errors also occur during boot and normal operation.
I am using a short UDMA cable.
According to https://mail-index.netbsd.org/tech-kern/2005/08/24/0000.html
CRC errors are harmless as long as they do not occur often:
[quote]
"This is harmless as long as it doesn't occur often. This means that
the data got corrupted during transfers on the IDE bus, and this was
detected by the Ultra-DMA CRC function (in this case the driver just redo
the
transfers). It's expected to see occasionnal CRC errors on Ultra-DMA IDE
busses, this bus just can't do reliable data transmission at this speed
(PATA Ultra-DMA could be called a hardware hack :)"
I also noted that during boot there was a message along the lines
of "transfer error downgrading to udma mode 3"
This blue and white G3 officially only does UDMA mode 2. So the system was
trying initially to use udma mode 4, then dropped down to mode 3, causing
errors along the way.
Taking that as a clue, I modified the kernel "wd" flag to 0x0aac (udma mode
2, dma mode 2, pio mode 4) and rebooted. The numerous error messages were
no longer manifesting at all. (though they would still appear during
install, since I haven't modified the install kernel. Can I just copy my
modded kernel to the installer? Or does the installer kernel do some
special and different stuff?)
Also I plan on looking into a means of quieting the console error messages
during install.
On Fri, Jan 24, 2025 at 1:05=E2=80=AFPM Chris Tucker <capa150%gmail.com@localhost> wr=
ote:
>
>
> On Thu, Jan 23, 2025 at 3:25=E2=80=AFAM Martin Husemann via gnats <
> gnats-admin%netbsd.org@localhost> wrote:
>
>> The following reply was made to PR port-macppc/59014; it has been noted
>> by GNATS.
>>
>> From: Martin Husemann <martin%duskware.de@localhost>
>> To: gnats-bugs%netbsd.org@localhost
>> Cc:
>> Subject: Re: port-macppc/59014: Shutdown -r now often freezes on macppc
>> b&w G3
>> Date: Thu, 23 Jan 2025 12:22:25 +0100
>>
>> > netbsd# rndctl -S seed2 (works)
>> > netbsd# rndctl -S seed2 (works)
>> > netbsd# rndctl -S seed2 (works)
>> > netbsd# rndctl -S seed2 (freezes, and I press ctrl-t)
>> > [ 139.8510292] load: 0.42 cmd: rndctl 633 [biowait] 0.01u 0.00s 0%
>> 1424k
>>
>> Just for completenes: could you mount a tmpfs on /tmp (if you haven't
>> that already as part of your standard install) and then try again with =
a
>> sequence of
>>
>> # rndctl -S /tmp/seed
>>
>> One other thing to check if the drive knows it is failing:
>>
>> # atactl wd0 smart status
>>
>> This could be the disk not giving up on the sector (and remapping it
>> yet),
>> but running into issues whenever trying to write it. I would expect
>> dmesg spam from that though.
>>
>> If you have anything but the fresh install on the disk, I would do a
>> backup
>> ASAP.
>>
>> Martin
>>
>> A terrific idea!
>
> I did a
> mount -t tmpfs tmpfs /tmp
> followed by
> # rndctl -S /tmp/seed
> I repeated the rndctl -S command above 32 times for good measure with no
> errors. I also did a rndctl -L off the tmpfs another 32 times without err=
or
> (seems to have eliminated the problem).
>
> Smart on my IBM DJSA-220 test-install drive running NetBSD 10.1:
> netbsd# atactl wd0 smart status
> SMART supported, SMART enabled
> id value thresh crit collect reliability description raw
> 1 100 62 yes online positive Raw read error rate 0
> 2 100 40 yes offline positive Throughput performance 0
> 3 102 33 yes online positive Spin-up time
> 107374182402
> 4 100 0 no online positive Start/stop count 1506
> 5 100 5 yes online positive Reallocated sector count 0
> 7 100 67 yes online positive Seek error rate 0
> 8 100 40 yes offline positive Seek time performance 0
> 9 57 0 no online positive Power-on hours count 1906=
7
> 10 100 60 yes online positive Spin retry count 0
> 12 100 0 no online positive Device power cycle count 1391
> 191 100 0 no online positive G-sense error rate 0
> 192 100 0 no online positive Power-off retract count 86
> 193 1 50 no online negative Load cycle count
> 1059282
> 196 100 0 no online positive Reallocated event count 7
> 197 100 0 no online positive Current pending sector 2
> 198 100 0 no offline positive Offline uncorrectable 0
> 199 200 0 no online positive Ultra DMA CRC error count 127
> netbsd#
>
> Smart on my Maxtor DiamondMax Plus 8 (new old stock) NetBSD 9.1 system:
> kawaii# atactl wd0 smart status
> SMART supported, SMART enabled
> id value thresh crit collect reliability description raw
> 3 221 63 yes online positive Spin-up time 1138=
5
> 4 253 0 no online positive Start/stop count 185
> 5 253 63 yes online positive Reallocated sector count 0
> 6 253 100 yes offline positive Read channel margin 0
> 7 253 0 no online positive Seek error rate 0
> 8 252 187 yes online positive Seek time performance 5288=
6
> 9 253 0 no online positive Power-on hours count 6774
> 10 253 157 yes online positive Spin retry count 0
> 11 253 223 yes online positive Calibration retry count 0
> 12 253 0 no online positive Device power cycle count 177
> 99 253 0 no offline positive Unknown 0
> 100 253 0 no offline positive Erase/Program Cycles 0
> 101 253 0 no offline positive Unknown 0
> 192 253 0 no online positive Power-off retract count 120
> 193 253 0 no online positive Load cycle count 191
> 194 253 0 no online positive Temperature 42
> 195 253 0 no online positive Hardware ECC Recovered 2226
> 196 253 0 no offline positive Reallocated event count 0
> 197 253 0 no offline positive Current pending sector 0
> 198 253 0 no offline positive Offline uncorrectable 0
> 199 199 0 no offline positive Ultra DMA CRC error count 1
> 200 253 0 no online positive Write error rate 0
> 201 253 0 no online positive Soft read error rate 3
> 202 253 0 no online positive Data address mark errors 0
> 203 253 180 yes online positive Run out cancel 0
> 204 253 0 no online positive Soft ECC correction 0
> 205 253 0 no online positive Thermal asperity check 0
> 207 253 0 no online positive Spin high current 0
> 208 253 0 no online positive Spin buzz 0
> 209 185 0 no offline positive Offline seek performance 0
> kawaii#
>
> Both drives exhibited the rndctl crash problem.
>
> I suspect the Mac's onboard IDE controller is flakey, as it is known to b=
e
> wacky. See the following link:
> https://en.wikipedia.org/wiki/Power_Macintosh_G3#Blue_and_White_2
>
> I have the "good" revision 2 motherboard, which some people think is also
> quirky.
>
> My next plan is to modify the kernel to turn off UDMA mode on the hard
> disk using the wd flags, see if that resolves the problem.
>
> Thanks to all for helping to narrow down the cause of the problem.
>
--000000000000a7016b062d7295fe
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Modifying the kernel to turn off UDMA and even DMA did not=
resolve the problem when running=C2=A0the drive off the motherboard UDMA p=
ort.<div><br></div><div><div>(Also, as an aside, I got no rndctl crashes wh=
en I ran the drive off the=C2=A0"IDE" port on the Mac's mothe=
rboard, which is normally used for the CDROM and different from the UDMA po=
rt)</div></div><div><br></div><div>I purchased a Sonnet ATA Tempo 133 IDE c=
ontroller and connected the drive to it.</div><div><br></div><div>This elim=
inated the rndctl problem entirely when using the unaltered GENERIC kernel.=
I ran a script to test=C2=A0rndctl 250 times for both load and save. The M=
ac never crashed.</div><div><br></div><div>However, there was a new problem=
: I got well over 100 repeated warnings/errors:</div><div>wd0: error readin=
g fsbn ... xfer f70, retry 0</div><div>wd0: (aborted command, interface CRC=
error)</div><div>wd0: soft error (corrected) xfer f70</div><div><br></div>=
<div>These errors occur during the installer process, making it difficult t=
o read. It does successfully install, however.</div><div>The errors also oc=
cur during boot and normal operation.</div><div><br></div><div>I am using a=
short UDMA cable.</div><div><br></div><div>According to=C2=A0<a href=3D"ht=
tps://mail-index.netbsd.org/tech-kern/2005/08/24/0000.html">https://mail-in=
dex.netbsd.org/tech-kern/2005/08/24/0000.html</a> CRC errors are harmless a=
s long as they do not occur often:</div><div><br></div><div>[quote]</div><d=
iv>"This is harmless as long as it doesn't occur often. This means=
that</div>the data got corrupted during transfers on the IDE bus, and this=
was<br>detected by the Ultra-DMA CRC function (in this case the driver jus=
t redo the<br>transfers). It's expected to see occasionnal CRC errors o=
n Ultra-DMA IDE<br>busses, this bus just can't do reliable data transmi=
ssion at this speed<br>(PATA Ultra-DMA could be called a hardware hack :)&q=
uot;<div><div><br></div><div>I also noted that during boot there was a mess=
age along the lines of=C2=A0"transfer error downgrading to udma mode 3=
"</div><div>=C2=A0</div><div>This blue and white G3 officially=C2=A0on=
ly does UDMA mode 2. So the system was trying initially to use udma mode 4,=
then dropped down to mode 3, causing errors along the way.</div><div><br><=
/div><div>Taking that as a clue, I modified the kernel "wd" flag =
to 0x0aac (udma mode 2, dma mode 2, pio mode 4) and rebooted. The numerous =
error messages were no longer manifesting at all. (though they would still =
appear during install, since I haven't modified the install kernel. Can=
I just copy my modded kernel to the installer? Or does the installer kerne=
l do some special and different stuff?)</div><div><br></div><div>Also I pla=
n on looking into a means of quieting the console error messages during ins=
tall.</div><div><br></div></div></div><br><div class=3D"gmail_quote gmail_q=
uote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jan 24, 2025 =
at 1:05=E2=80=AFPM Chris Tucker <<a href=3D"mailto:capa150%gmail.com@localhost";>ca=
pa150%gmail.com@localhost</a>> wrote:<br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:so=
lid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><=
div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c=
lass=3D"gmail_attr">On Thu, Jan 23, 2025 at 3:25=E2=80=AFAM Martin Husemann=
via gnats <<a href=3D"mailto:gnats-admin%netbsd.org@localhost"; target=3D"_blank">=
gnats-admin%netbsd.org@localhost</a>> wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-s=
tyle:solid;border-left-color:rgb(204,204,204);padding-left:1ex">The followi=
ng reply was made to PR port-macppc/59014; it has been noted by GNATS.<br>
<br>
From: Martin Husemann <<a href=3D"mailto:martin%duskware.de@localhost"; target=3D"_=
blank">martin%duskware.de@localhost</a>><br>
To: <a href=3D"mailto:gnats-bugs%netbsd.org@localhost"; target=3D"_blank">gnats-bugs@n=
etbsd.org</a><br>
Cc: <br>
Subject: Re: port-macppc/59014: Shutdown -r now often freezes on macppc b&a=
mp;w G3<br>
Date: Thu, 23 Jan 2025 12:22:25 +0100<br>
<br>
=C2=A0>=C2=A0 netbsd# rndctl -S seed2=C2=A0 =C2=A0(works)<br>
=C2=A0>=C2=A0 netbsd# rndctl -S seed2=C2=A0 =C2=A0(works)<br>
=C2=A0>=C2=A0 netbsd# rndctl -S seed2=C2=A0 =C2=A0(works)<br>
=C2=A0>=C2=A0 netbsd# rndctl -S seed2=C2=A0 =C2=A0(freezes, and I press =
ctrl-t)<br>
=C2=A0>=C2=A0 [ 139.8510292] load: 0.42=C2=A0 cmd: rndctl 633 [biowait] =
0.01u 0.00s 0% 1424k<br>
<br>
=C2=A0Just for completenes: could you mount a tmpfs on /tmp (if you haven&#=
39;t<br>
=C2=A0that already as part of your standard install) and then try again wit=
h a<br>
=C2=A0sequence of<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # rndctl -S /tmp/seed<br>
<br>
=C2=A0One other thing to check if the drive knows it is failing:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 # atactl wd0 smart status<br>
<br>
=C2=A0This could be the disk not giving up on the sector (and remapping it =
yet),<br>
=C2=A0but running into issues whenever trying to write it. I would expect<b=
r>
=C2=A0dmesg spam from that though.<br>
<br>
=C2=A0If you have anything but the fresh install on the disk, I would do a =
backup<br>
=C2=A0ASAP.<br>
<br>
=C2=A0Martin<br>
<br></blockquote><div>A terrific idea!</div><div><br></div><div>I did a</di=
v><div>mount -t tmpfs tmpfs /tmp=C2=A0</div><div>followed by=C2=A0</div><di=
v># rndctl -S /tmp/seed</div><div>I repeated the rndctl -S command above 32=
times for good measure with no errors. I also did a rndctl -L off the tmpf=
s another 32 times without error (seems to have eliminated the problem).=C2=
=A0</div><div><br></div><div>Smart on my IBM=C2=A0<span>=C2=A0</span>DJSA-2=
20 =C2=A0test-install drive running NetBSD 10.1:</div><div>netbsd# atactl w=
d0 smart status<br>SMART supported, SMART enabled<br>id value thresh crit c=
ollect reliability description =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 raw<br>=C2=A0 1 100 =C2=A0 62 =C2=A0 =C2=A0 yes online =C2=A0=
positive =C2=A0 =C2=A0Raw read error rate =C2=A0 =C2=A0 =C2=A0 =C2=A0 0<br>=
=C2=A0 2 100 =C2=A0 40 =C2=A0 =C2=A0 yes offline positive =C2=A0 =C2=A0Thro=
ughput performance =C2=A0 =C2=A0 =C2=A00<br>=C2=A0 3 102 =C2=A0 33 =C2=A0 =
=C2=A0 yes online =C2=A0positive =C2=A0 =C2=A0Spin-up time =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0107374182402<br>=C2=A0 4 100 =C2=
=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=A0positive =C2=A0 =C2=A0Start=
/stop count =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01506<br>=C2=A0 5 100 =
=C2=A0 =C2=A05 =C2=A0 =C2=A0 yes online =C2=A0positive =C2=A0 =C2=A0Realloc=
ated sector count =C2=A0 =C2=A00<br>=C2=A0 7 100 =C2=A0 67 =C2=A0 =C2=A0 ye=
s online =C2=A0positive =C2=A0 =C2=A0Seek error rate =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 0<br>=C2=A0 8 100 =C2=A0 40 =C2=A0 =C2=A0 yes offline =
positive =C2=A0 =C2=A0Seek time performance =C2=A0 =C2=A0 =C2=A0 0<br>=C2=
=A0 9 =C2=A057 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=A0positive =
=C2=A0 =C2=A0Power-on hours count =C2=A0 =C2=A0 =C2=A0 =C2=A019067<br>=C2=
=A010 100 =C2=A0 60 =C2=A0 =C2=A0 yes online =C2=A0positive =C2=A0 =C2=A0Sp=
in retry count =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00<br>=C2=A012 100 =
=C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=A0positive =C2=A0 =C2=A0De=
vice power cycle count =C2=A0 =C2=A01391<br>191 100 =C2=A0 =C2=A00 =C2=A0 =
=C2=A0 no =C2=A0online =C2=A0positive =C2=A0 =C2=A0G-sense error rate =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00<br>192 100 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no=
=C2=A0online =C2=A0positive =C2=A0 =C2=A0Power-off retract count =C2=A0 =
=C2=A0 86<br>193 =C2=A0 1 =C2=A0 50 =C2=A0 =C2=A0 no =C2=A0online =C2=A0neg=
ative =C2=A0 =C2=A0Load cycle count =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A01059282<br>196 100 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=A0po=
sitive =C2=A0 =C2=A0Reallocated event count =C2=A0 =C2=A0 7<br>197 100 =C2=
=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=A0positive =C2=A0 =C2=A0Curre=
nt pending sector =C2=A0 =C2=A0 =C2=A02<br>198 100 =C2=A0 =C2=A00 =C2=A0 =
=C2=A0 no =C2=A0offline positive =C2=A0 =C2=A0Offline uncorrectable =C2=A0 =
=C2=A0 =C2=A0 0<br>199 200 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=
=A0positive =C2=A0 =C2=A0Ultra DMA CRC error count =C2=A0 127<br>netbsd#=C2=
=A0<br></div><div><br></div><div>Smart on my Maxtor DiamondMax=C2=A0Plus 8 =
(new old stock) NetBSD 9.1 system:</div><div>kawaii# atactl wd0 smart statu=
s<br>SMART supported, SMART enabled<br>id value thresh crit collect reliabi=
lity description =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ra=
w<br>=C2=A0 3 221 =C2=A0 63 =C2=A0 =C2=A0 yes online =C2=A0positive =C2=A0 =
=C2=A0Spin-up time =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A01=
1385<br>=C2=A0 4 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=A0pos=
itive =C2=A0 =C2=A0Start/stop count =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0185<br>=C2=A0 5 253 =C2=A0 63 =C2=A0 =C2=A0 yes online =C2=A0positive =
=C2=A0 =C2=A0Reallocated sector count =C2=A0 =C2=A00<br>=C2=A0 6 253 =C2=A0=
100 =C2=A0 =C2=A0 yes offline positive =C2=A0 =C2=A0Read channel margin =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 0<br>=C2=A0 7 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =
=C2=A0online =C2=A0positive =C2=A0 =C2=A0Seek error rate =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 0<br>=C2=A0 8 252 =C2=A0187 =C2=A0 =C2=A0 yes onli=
ne =C2=A0positive =C2=A0 =C2=A0Seek time performance =C2=A0 =C2=A0 =C2=A0 5=
2886<br>=C2=A0 9 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=A0pos=
itive =C2=A0 =C2=A0Power-on hours count =C2=A0 =C2=A0 =C2=A0 =C2=A06774<br>=
=C2=A010 253 =C2=A0157 =C2=A0 =C2=A0 yes online =C2=A0positive =C2=A0 =C2=
=A0Spin retry count =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00<br>=C2=A011 =
253 =C2=A0223 =C2=A0 =C2=A0 yes online =C2=A0positive =C2=A0 =C2=A0Calibrat=
ion retry count =C2=A0 =C2=A0 0<br>=C2=A012 253 =C2=A0 =C2=A00 =C2=A0 =C2=
=A0 no =C2=A0online =C2=A0positive =C2=A0 =C2=A0Device power cycle count =
=C2=A0 =C2=A0177<br>=C2=A099 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0offl=
ine positive =C2=A0 =C2=A0Unknown =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 0<br>100 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =
=C2=A0offline positive =C2=A0 =C2=A0Erase/Program Cycles =C2=A0 =C2=A0 =C2=
=A0 =C2=A00<br>101 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0offline positi=
ve =C2=A0 =C2=A0Unknown =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 0<br>192 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0onl=
ine =C2=A0positive =C2=A0 =C2=A0Power-off retract count =C2=A0 =C2=A0 120<b=
r>193 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=A0positive =C2=
=A0 =C2=A0Load cycle count =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0191<br>=
194 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=A0positive =C2=A0 =
=C2=A0Temperature =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 4=
2<br>195 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=A0positive =
=C2=A0 =C2=A0Hardware ECC Recovered =C2=A0 =C2=A0 =C2=A02226<br>196 253 =C2=
=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0offline positive =C2=A0 =C2=A0Reallocate=
d event count =C2=A0 =C2=A0 0<br>197 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =
=C2=A0offline positive =C2=A0 =C2=A0Current pending sector =C2=A0 =C2=A0 =
=C2=A00<br>198 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0offline positive =
=C2=A0 =C2=A0Offline uncorrectable =C2=A0 =C2=A0 =C2=A0 0<br>199 199 =C2=A0=
=C2=A00 =C2=A0 =C2=A0 no =C2=A0offline positive =C2=A0 =C2=A0Ultra DMA CRC=
error count =C2=A0 1<br>200 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0onli=
ne =C2=A0positive =C2=A0 =C2=A0Write error rate =C2=A0 =C2=A0 =C2=A0 =C2=A0=
=C2=A0 =C2=A00<br>201 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=
=A0positive =C2=A0 =C2=A0Soft read error rate =C2=A0 =C2=A0 =C2=A0 =C2=A03<=
br>202 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=A0positive =C2=
=A0 =C2=A0Data address mark errors =C2=A0 =C2=A00<br>203 253 =C2=A0180 =C2=
=A0 =C2=A0 yes online =C2=A0positive =C2=A0 =C2=A0Run out cancel =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00<br>204 253 =C2=A0 =C2=A00 =C2=A0 =
=C2=A0 no =C2=A0online =C2=A0positive =C2=A0 =C2=A0Soft ECC correction =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 0<br>205 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=
=A0online =C2=A0positive =C2=A0 =C2=A0Thermal asperity check =C2=A0 =C2=A0 =
=C2=A00<br>207 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=A0posit=
ive =C2=A0 =C2=A0Spin high current =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0<br>=
208 253 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0online =C2=A0positive =C2=A0 =
=C2=A0Spin buzz =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 0<br>209 185 =C2=A0 =C2=A00 =C2=A0 =C2=A0 no =C2=A0offline positive =C2=
=A0 =C2=A0Offline seek performance =C2=A0 =C2=A00<br>kawaii#=C2=A0<br></div=
><div><br></div><div>Both drives exhibited the rndctl crash problem.</div><=
div><br></div><div>I suspect the Mac's onboard IDE controller is flakey=
, as it is known to be wacky. See the following link:</div><div><a href=3D"=
https://en.wikipedia.org/wiki/Power_Macintosh_G3#Blue_and_White_2"; target=
=3D"_blank">https://en.wikipedia.org/wiki/Power_Macintosh_G3#Blue_and_White=
_2</a><br></div><div><br></div><div>I have the "good" revision 2 =
motherboard, which some people think is also quirky.</div><div><br></div><d=
iv>My next plan is to modify the kernel to turn off UDMA mode on the hard d=
isk using the wd flags, see if that resolves the problem.</div><div><br></d=
iv><div>Thanks to all for helping to narrow down the cause of the problem.<=
/div></div></div>
</blockquote></div>
--000000000000a7016b062d7295fe--
Home |
Main Index |
Thread Index |
Old Index