file doesn't appear to be bootable
2007-12-25 1:58:00
people on a remote campus who ran into a problem. When they installed
the system they took the default disk layout with only 200 meg in / and
it is now full. They had one slice on the disk that wasn't being used,
slice 3, so I created a larger root filesystem for them there and then
did a newfs on it.
I then walked them through booting off the cdrom into single user mode,
mounting the old root in /a, creating a b subdir in a, mounting the new
root there, and then doing an inline tar, excluding the b subdir, of the
contents of /a into /a/b. I then walked them through editing the vfstab
to point / to the new slice. Then I have them do the installboot to the
proper slice, no error message received. So, we shutdown and get back
to the ok prompt. I now have them nvalias the old root to backup in
case it's needed and setenv boot-device to the proper device location.
I've double and triple checked (from what they've read off the screen to
me) all the data and I don't see anything wrong. Permissions on
genunix, / , /kernel all appear to be fine.
The problem is that after pointing boot-device to the new root partition
we get the famous Boot load failed device does not appear to be
executable message. So, what am I missing here. It has to be something
simple that I've just totally forgotten about.
Please help,
Bob
Comments
Got something to say?
You must be logged in to post a comment.
