jason.b.williams at gmail
Jul 24, 2005, 9:21 PM
Post #3 of 3
Thank you for the reply. I am a little late receiving it because I had
forgotten check this email thread lately. However, I did get it
working, and interestingly enough one of your listed problems was the
same as I had. It turned out to be the software raid. Apparently
software raid inserts header information at block 0 and then stores
the array at the end of the partition, and of course as we should all
know, silo also wants to use block 0. The only part that was new to me
about this process was the fact that raid uses block 0, so of course
it's going to conflict with silo.
Anyways, I ended up separating off my boot directory to it's own
partition and for simplicity, made it the first partition on each
disk. Now I have all my partitions working as raid1 except sda1 and
sdb1. With these I now just use $(dd if=/dev/sda1 of=/dev/sdb1)
anytime I upgrade the kernel or silo. I know there's a way to have
silo boot from a different block other than 0, but that task will wait
for later play. Right now I'm just happy to have my server up and
running at full capacity.
On 7/18/05, Pilage <pilage [at] drizzt> wrote:
> I have had this issue also on a few occasions. do i have solutions?
> probably not but they may help you narrow something down.
> i will list just 2 cause the others were just config settings and me not
> knowing what the heck was going on.
> My first time was related to adding an additional scsi controller after
> the initial install and the new controller taking over the sda
> postion(well sda,b,c and d positions) which made for a pretty wierd
> silo.conf to get working. so i know this may sound basic but check to make
> sure the machine sees the same devices as what you see them as and are
> setting the variables too.
> second time related to trying to boot from a software raid. was never able
> to get it going that way. with that in mind, if you are trying to boot off
> a mirror, try boot off of one of those drives to see if that works.
> the others i was able to solve by trying different commands at the ok
> prompt to narrow down what the settings should be...hehe trial and error
> so to speak.
> again just things to try to help narrow it down.
> On Sat, 16 Jul 2005 17:45:18 -0500, Jason Williams
> <jason.b.williams [at] gmail> wrote:
> > Alright, I cannot boot my machine from the disk. Every time I try I
> > get 'The file just loaded does not appear to be executable' and a
> > return to the ok prompt; it's not even loading the S. I am not the
> > only one experiencing this. There several in the forum that are having
> > this problem. User zaanpenguin and I are having the exact same problem
> > down to the tee. He's tried various versions of silo, so it does not
> > appear to be a version problem. He and I did both recently upgrade our
> > OBP to the latest version of 3.31. However, the interesting part is I
> > had mine booting with this version until I ran into some disk issues
> > and decided to do a full format and surface analysis using the solaris
> > install CD. Ever since I put gentoo back on I have not been able to
> > boot off the disk.
> > For full and much better explanations this forum thread is where
> > zaanpenguin and I have been posting:
> > http://forums.gentoo.org/viewtopic-t-357797-postdays-0-postorder-asc-start-0.html?sid=54fbfa149d0c34e74349d4f2c8f6e6e4
> > We are both getting quite desperate; I appreciate anything anyone can
> > do to help.
> > Jason
> gentoo-sparc [at] gentoo mailing list
gentoo-sparc [at] gentoo mailing list