<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 04/15/2014 07:18 AM, Joshua Kramer
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAMPA5gdm7Njjw-TNLXXK4LYvYHFB2mfeTLvNOyXZNe0Rk3RbXQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>
                <div>
                  <div>
                    <div>
                      <div>
                        <div>Hello All,<br>
                          <br>
                        </div>
                        Has anyone ever encountered hardware that is bad
                        because it'll let you run Linux just fine
                        (memtest86 passes) but the Linux installer
                        freezes up at various points and won't run?<br>
                        <br>
                      </div>
                      I have a Gigabyte motherboard, 1155, with an i3.&nbsp;
                      A while ago, when I first put this system together
                      with all new parts (8g ram, one 1T disk), the
                      installer ran fine, and the box has been running a
                      few VM's since then.<br>
                      <br>
                    </div>
                    I decided that I wanted to put another disk in the
                    system to have a RAID1 setup, and replace the RAM
                    with 16G.&nbsp; So I put the new drive and RAM in, and
                    backed up my data.&nbsp; Popped in my CentOS 6.5 install
                    DVD, and... I can't install.&nbsp; The installer freezes
                    up at various points, usually when it is first
                    detecting the storage.<br>
                    <br>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Best to change 1 variable at a time<br>
    <br>
    <blockquote
cite="mid:CAMPA5gdm7Njjw-TNLXXK4LYvYHFB2mfeTLvNOyXZNe0Rk3RbXQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>
                <div>I got a new power supply (600w), thinking that the
                  cheapo 400w unit wasn't delivering enough power.&nbsp; Same
                  problem.&nbsp; Put the old RAM back in.&nbsp; Same problem.&nbsp;
                  Disconnected the new disk.&nbsp; Same problem.&nbsp;
                  Disconnected the original disk, connected the new
                  one.&nbsp; Same problem.&nbsp; Most recently, I got another
                  motherboard - an exact duplicate of the first - and,
                  same problem.&nbsp; (Actually, the first time I installed
                  on the new motherboard, I got past the "detecting
                  volumes" screen, but realized the partitioning and
                  RAID wasn't set up how I wanted it, so I cancelled
                  that install.&nbsp; Subsequent install attempts result in
                  the same problem as the original motherboard.)<br>
                  <br>
                </div>
                <div>But the OS that is currently on there runs just
                  fine... no kernel panics, no weird messages in dmesg,
                  etc.<br>
                </div>
                <div><br>
                  I'm not sure what has failed now that was working the
                  first time I installed the system.<br>
                  <br>
                </div>
                I also attempted to create a RAID array on the
                properly-running system by using sfdisk to clone the
                partition table to the new drive, then creating a RAID
                device and extending the Volume Group to that device,
                then doing a pvmove to move the logical volume to the
                new RAID device.&nbsp; I used this guide:<br>
                <br>
                <a moz-do-not-send="true"
href="http://community.spiceworks.com/how_to/show/340-lvm-single-drive-to-lvm-raid-1-mirror-migration">http://community.spiceworks.com/how_to/show/340-lvm-single-drive-to-lvm-raid-1-mirror-migration</a><br>
                <br>
              </div>
              Unfortunately, sfdisk does not accurately clone the
              partition table if the partitions don't end on cylinder
              boundaries, which is the case here.&nbsp; So the pvmove failed
              (and probably ate some data).<br>
              <br>
            </div>
            I think my next step is going to be to put the two hard
            drives in external enclosures, plug them into my laptop, and
            then install the system using that.&nbsp; It will probably boot
            and run just fine after that.&nbsp; Does anyone have suggestions
            as to what else I might do?<br>
            <br>
          </div>
          Thanks!<br>
        </div>
        -JK<br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
colug-432 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:colug-432@colug.net">colug-432@colug.net</a>
<a class="moz-txt-link-freetext" href="http://lists.colug.net/mailman/listinfo/colug-432">http://lists.colug.net/mailman/listinfo/colug-432</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>