<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 03/03/12 22:54, Alexander Hartner wrote:
<blockquote
cite="mid:DBF2D737-C9C3-4F11-9F5F-14CAA0D355A9@j2anywhere.com"
type="cite"><font class="Apple-style-span" face="Arial">Hi Tim</font>
<div><font class="Apple-style-span" face="Arial"><br>
</font></div>
<div><font class="Apple-style-span" face="Arial">Thanks for your
post. I tried this several times now, but everytime I boot of
the Live CD I get md125 again. I have't been able to boot of
hard drive as I keep on getting a kernel panic on boot up. I
suspect the panic is caused by the kernel also not being able
to find the correct md devices. I tried running the commands </font></div>
<div>
<pre class="bz_comment_text" id="comment_text_1" style="white-space: pre-wrap; width: 50em; "><font class="Apple-style-span" face="Arial"><b> mdadm -S /dev/md125
mdadm -A /dev/md1 --update=super-minor</b></font></pre>
<div><font class="Apple-style-span" face="Arial">But they didn't
fix the issue. Still on every reboot from LiveCD I get back
to md125.</font></div>
</div>
</blockquote>
<br>
This is due to the LiveCD not "knowing" about the array so it mounts
it as md125 etc. (Its the auto assembling of the array that is the
problem). The update super-minor stuff will assign it the correct
"name", but it's still up to the initramfs to mount it correctly,
and it uses mdadm.conf to know which number it should be. So after
doing an update super-minor, you'll need to chroot into the new
install, and update the mdadm.conf file AND the same file in the
initramfs (see Brian's post for some info on that). There is a
command to auto create the mdadm.conf file, but you'll need to
google for that.<br>
<blockquote
cite="mid:DBF2D737-C9C3-4F11-9F5F-14CAA0D355A9@j2anywhere.com"
type="cite"><font size="3"><font face="Arial"><snip></font></font></blockquote>
<br>
<blockquote
cite="mid:DBF2D737-C9C3-4F11-9F5F-14CAA0D355A9@j2anywhere.com"
type="cite"><span style="letter-spacing: 0px; "><font
class="Apple-style-span" face="Arial" size="3">and a reboot,
fdisk now reports that the partition table for mdX is not
valid. </font></span>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom:
0px; margin-left: 0px; font: normal normal normal 9px/normal
Menlo; "><span style="letter-spacing: 0px; "><font
class="Apple-style-span" face="Arial" size="3"><br>
</font></span></div>
<div style="margin: 0px; font: 9px Menlo;">
<div style="margin-top: 0px; margin-right: 0px; margin-bottom:
0px; margin-left: 0px; font: normal normal normal 9px/normal
Menlo; "><font class="Apple-style-span" face="Arial" size="3"><b>Disk
/dev/md127: 995.6 GB, 995640344576 bytes</b></font></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom:
0px; margin-left: 0px; font: normal normal normal 9px/normal
Menlo; "><font class="Apple-style-span" face="Arial" size="3"><b>2
heads, 4 sectors/track, 243076256 cylinders, total
1944610048 sectors</b></font></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom:
0px; margin-left: 0px; font: normal normal normal 9px/normal
Menlo; "><font class="Apple-style-span" face="Arial" size="3"><b>Units
= sectors of 1 * 512 = 512 bytes</b></font></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom:
0px; margin-left: 0px; font: normal normal normal 9px/normal
Menlo; "><font class="Apple-style-span" face="Arial" size="3"><b>Sector
size (logical/physical): 512 bytes / 4096 bytes</b></font></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom:
0px; margin-left: 0px; font: normal normal normal 9px/normal
Menlo; "><font class="Apple-style-span" face="Arial" size="3"><b>I/O
size (minimum/optimal): 4096 bytes / 4096 bytes</b></font></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom:
0px; margin-left: 0px; font: normal normal normal 9px/normal
Menlo; "><font class="Apple-style-span" face="Arial" size="3"><b>Disk
identifier: 0x00000000</b></font></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom:
0px; margin-left: 0px; font: normal normal normal 9px/normal
Menlo; "><font class="Apple-style-span" face="Arial" size="3"><b><br>
</b></font></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom:
0px; margin-left: 0px; font: normal normal normal 9px/normal
Menlo; "><font class="Apple-style-span" face="Arial" size="3"><b>Disk
/dev/md127 doesn't contain a valid partition table</b></font></div>
</div>
</blockquote>
<br>
There shouldn't be partitions on the raid device (/dev/mdX). The
partitions should be on the physical disk (/dev/sdX or /dev/hdX) and
essentially /dev/mdX is a partition. You /can/ put partitions on top
of the raid device, same as any other block device, but it's not the
recommended way (AFAIK).<br>
<br>
<snip><br>
<blockquote
cite="mid:DBF2D737-C9C3-4F11-9F5F-14CAA0D355A9@j2anywhere.com"
type="cite">
<div><font class="Apple-style-span" face="Arial">I wonder why it
is not picking up the partition table I created. <br>
</font></div>
</blockquote>
Try fdisk /dev/sda<br>
<blockquote
cite="mid:DBF2D737-C9C3-4F11-9F5F-14CAA0D355A9@j2anywhere.com"
type="cite">
<div><font class="Apple-style-span" face="Arial"><br>
</font></div>
<div><font class="Apple-style-span" face="Arial">I am using Gentoo
for this as I really like it. It makes things a little bit
more complicated but generally they work, well at least until
now they did. <br>
</font></div>
</blockquote>
I've used Gentoo a long time ago, but never with raid, sorry.<br>
<br>
Hopefully this, with Brians post and some more googleing will help
you get running!<br>
<br>
Tim<br>
</body>
</html>