Reply to thread

Message

<blockquote data-quote="Rolo" data-source="post: 413691" data-attributes="member: 37118">OS not booting is a symptom, not the problem.Bad RAM will make a disk appear corrupt since it is reading good data from the disk and turning it into bad data in memory.&nbsp; CHKDSK, et. al. will act on this bad bad data and try to repair it, in which case the good repair data will also get corrupted into bad data when it gets written. Think of playing a vinyl LP with a bad needle: it destroys the LP (assuming anyone here even knows what that is, heh).We don&#039;t go swapping parts guessing; we use diagnostic tools with sound methods and procedures and deductive logic.&nbsp; The OP started a disk diagnostic and it reports bad clusters.&nbsp; Don&#039;t assume that is the problem since a diagnostic reporting bad clusters can be caused by bad physical media (very likely), bad logic on the disk controller (unlikely), bad bus (very unlikely) or bad RAM (likely).&nbsp; You want to eliminate bad RAM first because if you don&#039;t, you&#039;ll destroy all that good data.&nbsp; If the RAM is good, you risked nothing.&nbsp; Bad RAM will even fool your RAID controller into thinking the RAID configuration needs repair.&nbsp; Don&#039;t tell it to repair until you&#039;ve tested RAM first!&nbsp; (personal experience...destroyed the RAID and all the contents on it and I was out of town at the time...tactical rebuild!)</blockquote>

[QUOTE="Rolo, post: 413691, member: 37118"] OS not booting is a [I]symptom[/I], not the [I]problem[/I]. Bad RAM will make a disk appear corrupt since it is reading good data from the disk and turning it into bad data in memory. CHKDSK, et. al. will act on this bad bad data and try to repair it, in which case the good repair data will also get corrupted into bad data when it gets written. Think of playing a vinyl LP with a bad needle: it destroys the LP (assuming anyone here even knows what that is, heh). We don't go swapping parts guessing; we use diagnostic tools with sound methods and procedures and deductive logic. The OP started a disk diagnostic and it [I]reports [/I]bad clusters. Don't assume that is the problem since a diagnostic reporting bad clusters can be caused by bad physical media (very likely), bad logic on the disk controller (unlikely), bad bus (very unlikely) or bad RAM (likely). You want to eliminate bad RAM first because if you don't, you'll destroy all that good data. If the RAM is good, you risked nothing. Bad RAM will even fool your RAID controller into thinking the RAID configuration needs repair. Don't tell it to repair until you've tested RAM first! (personal experience...destroyed the RAID and all the contents on it and I was out of town at the time...tactical rebuild!) [/QUOTE]

Verification