View Single Post
  #11  
Old January 5th 18, 02:33 AM posted to alt.comp.os.windows-10
Tim[_10_]
external usenet poster
 
Posts: 249
Default Failed Redundancy

Paul wrote in news
After a RAID experiment, I connect the SATA drive
to an older computer, and use diskpart to "clean all".
For hardware RAID, clean all won't clean all of the
disk. You have to arrange things, in the case of
hardware RAID, so the RAID metadata areas are exposed,
so you can erase them. Even erasing from Linux is
not foolproof, as sometimes Linux tries to read
the metadata and make it work as it did in Windows.
When I work with a drive, the drive must be
completely clean, as I have had cases where a
later experiment is ruined, because the test
case can "sniff" the metadata from a previous
experiment.

Paul

First off, I never said I wasn't backing up my data. That is not the
issue, as you can see in some of my responses. My sole concern with this
post is the best way to clear up the failed redundancy error. Right now
that sounds like take my new drive and add it to the mirror. Then remove
one of the current mirror drives, test the hell out of it to make sure
there is no hardware problem, then add it back to the mirror. At that
point I should have to good fully redundant drives in the mirror. I can
then remove the other drive that is showing failed redundancy, test the
hell out of it, then use it to replace the other failed drive that is not
part of the scope of this thread.

And totally OT, I understand what you are talking about with data that
hangs around on a disk. Back in the late 90s were were running Microsoft
Lan Manager on a UNIX server (a valid configuration) We had some load
problems and added a second UNIX server for a little while, while we
migrated to Windows NT for the main server. Once that was accomplished, I
got one of the UNIX boxes to use as my desktop, as I had 80286 based PC
at the time. I completely wiped and formatted the drive, and loaded
whatever version of Windows we were using at the time. Every time I
booted the maching, the antivirus software would have a cow about a
bootloader virus. We finally figured out that the UNIX boot block was
larger than the later Windows boot loader, and the antivirus was seeing
the remnants of that block still there behind the valid Windows boot
block. As the song says, "Strange Things Happen In This World".
Ads