<div dir="ltr"><div>nice tool work, Phil! <br><br></div>+1 on process. Sounds like lightning strike killed the board on the drive. <br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 27, 2013 at 12:16 PM, Phil Turmel <span dir="ltr"><<a href="mailto:philip@turmel.org" target="_blank">philip@turmel.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Gene,<br>
<div class="im"><br>
On 11/27/2013 11:18 AM, Gene Poole wrote:<br>
> I'm running CentOS 5.9 x86_64 on a machine I built myself that has 6 SATA<br>
> II hard drives (4 - 1 TB drives; 2 - 1.5 TB drives) all in several RAID-1<br>
> arrays. These arrays were created when I did the original installation<br>
> with CentOS 5.1 and each created partition (both standard and LVM) were<br>
> built raid 1.<br>
><br>
> Due to some things happening around the house that required most of my<br>
> attention, I saw some alerts concerning drive /dev/sdb but I didn't have<br>
> time to address it and since I am running raid 1... One of the tings that<br>
> happened was my home took a lightening strike and we were down for 4 days.<br>
><br>
> When we got our electricity back and I brought the machine back up I<br>
> noticed that there were only 5 drives listed and I wasn't getting any<br>
> more alerts. What was /dev/sdb was no longer listed with any command<br>
> (fdisk; cat /proc/mdstat; mdadm --list).<br>
<br>
</div>Before you do anything else, document what you have. I suggest you<br>
start with "lsdrv" [1] for the bird's-eye view, then:<br>
<br>
"smartctl -x" for each drive,<br>
"fdisk -l" or "gdisk -l" for each drive,<br>
"mdadm -D" for each array,<br>
"mdadm -E" for each array member<br>
<div class="im"><br>
> I do have a spare drive and my questions are:<br>
><br>
> Anyone know how I can find the serial number of the bad drive?<br>
<br>
</div>After the above, turn off the system and look at the drive stickers.<br>
Find the one that doesn't match anything documented.<br>
<div class="im"><br>
> Once replaced, what is the best way to get the partitions recreated?<br>
<br>
</div>If your drives are still MBR, I'd just "dd" the pre-partion 1 area onto<br>
the new drive and issue "blockdev --rereadpt" (the new drive must be the<br>
same size as the original). If your drives have GPT partitions, use<br>
gdisk's backup and restore features.<br>
<br>
> Thanks,<br>
> Gene Poole<br>
<br>
HTH,<br>
<br>
Phil<br>
<br>
[1] <a href="http://github.com/pturmel/lsdrv" target="_blank">http://github.com/pturmel/lsdrv</a><br>
<br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr">-- <br>James P. Kinney III<br><i><i><i><i><br></i></i></i></i>Every time you stop a school, you will have to build a jail. What you
gain at one end you lose at the other. It's like feeding a dog on his
own tail. It won't fatten the dog.<br>
- Speech 11/23/1900 Mark Twain<br><i><i><i><i><br><a href="http://heretothereideas.blogspot.com/" target="_blank">http://heretothereideas.blogspot.com/</a><br></i></i></i></i></div>
</div>