The file just loaded doesn't appear to be executable
I'm trying to get my Blade1000 (UltraSPARC-III/2x750MHz) to boot
from the external disk cabinet (MultiPack 12).
There's a Debian GNU/Linux installation on sda (the internal FC
disk), but that's to be used solely as a development platform
in a chroot (don't have to machines, and I don't want to 'clutter'
the system with development stuff).
I managed to RAID6 a bunch of the disks and that's to be used
as the root FS (including /usr, /tmp and what have you).
BUT, since I need to boot from a non-raid'ed disk (since the
openprom don't understand /dev/md/X :), I created a /boot as
the first partition on the first (external) disk - sdb. This
partition starts at block 1 (so that mke2fs won't overwrite
the partition table), and partition 2 is part of the MD (type:fd).
Then there's the 'Whole disk' which starts at block 0...
When I run silo under strace, I see that silo DO write the
'boot record' (?) on sdb3...
The problem is that when I try to boot it, I get the message
"The file just loaded doesn't appear to be executable."...
I've tried "boot raid" and "boot raid:c" but neither work
(see attachment)...
Am I really booting from the correct device!?
Booting from the internal FC disk ("boot disk") work like
a charm. I've had to add an entry in that disks silo.conf
so that I can get the RAID up and running. But this will
"break" sooner than later (I'll just forget and update
the wrong kernel location etc :). The "correct" way in
my eyes is to make it boot from sdb, not sda with a
"pointer" to sdb...
Reply to: