On 8/6/2015 4:21 PM, Chris Murphy wrote:> On Thu, Aug 6, 2015 at 2:08 PM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: > >> Doing a new install on the two 1TB drives is my current plan. If that >> works, I can connect the old drive, copy over all the data, and then try to >> figure out what I need to do to get all the programs running again. > Sounds like a pain. I would just adapt the CentOS 6 program.log > commands for your case. That's a 2 minute test. And it ought to work.I'm not familiar with that. How would I go about adapting the CentOS 6 program.log commands?> Clearly the computer finds the drive, reads the MBR and executes stage > 1. The missing part is it's not loading or not executing stage 2 for > some reason. I'm just not convinced the bootloader is installed > correctly is the source of the problem with the 2nd drive. It's not > like the BIOS or HBA card firmware is going to faceplace right in > between stage 1 and stage 2 bootloaders executing. If there were a > problem there, the drive simply doesn't show up and no part of the > bootloader gets loaded.Definitely a strange problem. I'm hoping that doing a new install onto these drives rather than trying to inherit the install used on the smaller drives will work better. -- Bowie
On Thu, Aug 6, 2015 at 2:29 PM, Bowie Bailey <Bowie_Bailey at buc.com> wrote:> On 8/6/2015 4:21 PM, Chris Murphy wrote: >> >> On Thu, Aug 6, 2015 at 2:08 PM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >> >>> Doing a new install on the two 1TB drives is my current plan. If that >>> works, I can connect the old drive, copy over all the data, and then try >>> to >>> figure out what I need to do to get all the programs running again. >> >> Sounds like a pain. I would just adapt the CentOS 6 program.log >> commands for your case. That's a 2 minute test. And it ought to work. > > > I'm not familiar with that. How would I go about adapting the CentOS 6 > program.log commands?I mentioned it in the last two posts yesterday on this subject. -- Chris Murphy
On Thu, Aug 6, 2015 at 2:29 PM, Bowie Bailey <Bowie_Bailey at buc.com> wrote:> Definitely a strange problem. I'm hoping that doing a new install onto > these drives rather than trying to inherit the install used on the smaller > drives will work better.The CentOS installer, and parted, predate AF drives, so the partitioning will not be correct with a new installation. There's no way to get the installer to do proper alignment. You can partition correctly in advance, and then have the installer reuse those partitions though. -- Chris Murphy
On 8/6/2015 4:39 PM, Chris Murphy wrote:> On Thu, Aug 6, 2015 at 2:29 PM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >> On 8/6/2015 4:21 PM, Chris Murphy wrote: >>> On Thu, Aug 6, 2015 at 2:08 PM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >>> >>>> Doing a new install on the two 1TB drives is my current plan. If that >>>> works, I can connect the old drive, copy over all the data, and then try >>>> to >>>> figure out what I need to do to get all the programs running again. >>> Sounds like a pain. I would just adapt the CentOS 6 program.log >>> commands for your case. That's a 2 minute test. And it ought to work. >> >> I'm not familiar with that. How would I go about adapting the CentOS 6 >> program.log commands? > I mentioned it in the last two posts yesterday on this subject.Ok. I'll give that a try tomorrow. Just a couple of questions. install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0,1) /grub/stage2 p (hd0,1)/grub/grub.conf It looks like this mixes paths relative to root and relative to /boot. Did your test system have a separate /boot partition? The --stage2 argument is "os stage2 file" according to my man page. Should this be relative to root even with a separate /boot partition? Also, why are the exact same root and install commands run twice in the log you show? Is that just a duplicate, or does it need to be run twice for some reason? grub> root (hd0,1) grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0,1) /grub/stage2 p (hd0,1)/grub/grub.conf grub> root (hd0,1) grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0,1) /grub/stage2 p (hd0,1)/grub/grub.conf -- Bowie