| View previous topic :: View next topic |
| Author |
Message |
Vitus
n00b
Joined: 12 Mar 2004
Posts: 6
Location: a Dane in Sao Paulo, Brasil
|
 Posted: Mon Mar 15, 2004 2:29 am Post subject: Getting "Bus error" on "silo -C /boot/silo.co |
 |
|
(NOTE! I posted this in "Installing..." but got a hint that maybe I ought to post it here as well...)
Hi all,
First-timer here... 
I'm installing gentoo on a Sun Ultra5 and so far it has not been too bad, however I'm now at step 9.f, Bootloader - Using Silo and I am getting this "Bus Error" (see in quote, italics):
| Quote: |
livecd / # pwd
/
livecd / # more /etc/silo.conf
partition = 1 # Boot partition
root = /dev/hda4 # Root partition
timeout = 10 # Wait 10 seconds before booting the default section
image = /boot/kernel-2.4.24-sparc-r2
label = linux
livecd / # ls -la /boot/silo.conf
-rw-r--r-- 1 root root 206 Mar 14 17:13 /boot/silo.conf
livecd / # more /boot/silo.conf
livecd / # /sbin/silo -C /boot/silo.conf
Bus error
livecd / #
|
Note that when I do a more on /boot/silo.conf - nothing comes up, even though it has size of 206 in the /boot directory?!
Additional info:
| Quote: |
livecd / # fdisk /dev/hda
Command (m for help): p
Disk /dev/hda (Sun disk label): 16 heads, 63 sectors, 17660 cylinders
Units = cylinders of 1008 * 512 bytes
Device Flag Start End Blocks Id System
/dev/hda1 0 62 31248 83 Linux native
/dev/hda2 u 63 1055 499968 83 Linux native
/dev/hda3 0 17660 8900640 5 Whole disk
/dev/hda4 1056 17660 8368416 83 Linux native
Command (m for help): q
livecd / #
|
| Quote: |
livecd / # more /etc/fstab
# /etc/fstab: static file system information.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.14 2003/10/13 20:03
:38 azarah Exp $
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail and tail freely.
# <fs> <mountpoint> <type> <opts>
<dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1 /boot ext2 noauto,noatime
1 1
/dev/hda4 / ext3 noatime
0 0
/dev/hda2 none swap sw
0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro
0 0
#/dev/fd0 /mnt/floppy auto noauto
0 0
# NOTE: The next line is critical for boot!
none /proc proc defaults
0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
# Adding the following line to /etc/fstab should take care of this:
none /dev/shm tmpfs defaults
0 0
none /proc/openprom openpromfs defaults 0 0
livecd / #
|
I've used a universal CD ("install-sparc64-universal-2004.0.iso"), and i chose the portage from the CD, followed by emerge to update.
Anyone out there who might have an idea?
_________________
Bst rgds
Vitus |
|
| Back to top |
|
 |
TrAvELAr
n00b
Joined: 02 Mar 2004
Posts: 25
Location: Baltimore, MD
|
| Posted: Mon Mar 15, 2004 2:59 am Post subject: |
|
|
Out of curiosity what happens when you run /sbin/silo without -C /boot/silo.conf. It should check the silo.conf that is in /etc.
Also, I'm sure you have tried this, have you recopied the /etc/silo.conf to /boot? Check your mountpoints too. It's almost like it's trying to read the /boot off of the livecd.
I installed Gentoo on two U5s this weekend and did not experience this problem. |
|
| Back to top |
|
|
Vitus
n00b
Joined: 12 Mar 2004
Posts: 6
Location: a Dane in Sao Paulo, Brasil
|
| Posted: Mon Mar 15, 2004 2:33 pm Post subject: |
|
|
Ok - running /sbin/silo looks troubled as well...
| Code: | livecd / # pwd
/
livecd / # /sbin/silo
/etc/silo.conf appears to be valid
Fatal error: Couldn't read new silo bootblock from /boot/ultra.b
livecd / # |
But that error on the /boot/ultra.b got me started on a little test, have a look at the file copy/more session below - note the behaviour of the file(s) in "boot" - is this normal behaviour??
| Code: |
livecd / # cd etc
livecd etc # ls -la silo.*
-rw-r--r-- 1 root root 207 Mar 15 13:52 silo.conf
-rw-r--r-- 1 root root 2350 Mar 14 17:05 silo.conf.org
livecd etc # more silo.conf
partition = 1 # Boot partition
root = /dev/hda4 # Root partition
timeout = 10 # Wait 10 seconds before booting the default section
image = /boot/kernel-2.4.24-sparc-r2
label = linux
livecd etc # cp silo.conf /boot/silo.conf
livecd etc # cd /boot
livecd boot # ls -la silo.*
-rw-r--r-- 1 root root 207 Mar 15 14:29 silo.conf
livecd boot # more silo.conf
livecd boot # cp silo.conf /testing/silo.conf
cp: reading `silo.conf': Input/output error
livecd boot # cd /testing
livecd testing # ls -la
total 8
drwxr-xr-x 2 root root 4096 Mar 15 14:30 .
drwxr-xr-x 18 root root 4096 Mar 15 14:27 ..
-rw-r--r-- 1 root root 0 Mar 15 14:30 silo.conf
livecd testing # more silo.conf
livecd testing #
|
Just in case - I've included the output from "mount"
| Code: |
livecd / # mount
/dev/ROOT on / type xfs (rw,noatime)
none on /proc/openprom type openpromfs (rw)
livecd / #
livecd / #
livecd / # mount -a
mount: mount point /dev/shm does not exist
livecd / #
|
and I tried to exit from the jail and check the fstab - and since it seemed to miss a "new line" after the last entry I added that and chroot'ed back in jail - so here's the updated fstab (only added the "new line"):
| Code: |
livecd / # more /etc/fstab
# /etc/fstab: static file system information.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.14 2003/10/13 20:03:38 azarah Exp $
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail and tail freely.
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1 /boot ext2 noauto,noatime 1 1
/dev/hda4 / ext3 noatime 0 0
/dev/hda2 none swap sw 0 0
/dev/cdroms/cdrom0 /mnt/cdrom iso9660 noauto,ro 0 0
#/dev/fd0 /mnt/floppy auto noauto 0 0
# NOTE: The next line is critical for boot!
none /proc proc defaults 0 0
# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
# use almost no memory if not populated with files)
# Adding the following line to /etc/fstab should take care of this:
none /dev/shm tmpfs defaults 0 0
none /proc/openprom openpromfs defaults 0 0
livecd / #
|
I hope there's someone out there with a hint... 'cause I'm stuck! 
_________________
Bst rgds
Vitus |
|
| Back to top |
|
|
Ferris
Retired Dev
Joined: 13 Jan 2003
Posts: 426
Location: N. Virginia (USA)
|
| Posted: Mon Mar 15, 2004 9:06 pm Post subject: |
|
|
I am having some trouble following how you have your disks partitioned,
but have you 'emerge silo' with /boot the place you are booting from? It
looks like all you have in /boot is silo.conf, and that isn't enough.
If /boot does not contain at least silo.conf, your kernel, ultra.b, and
second.b, you will have problems.
The 'emerge silo' should give you these files in your actual /boot partition:
| Code: |
1 /boot/cd.b 1 /boot/generic.b 8 /boot/old.b 1 /boot/ultra.b
1 /boot/fd.b 1 /boot/ieee32.b 62 /boot/second.b
1 /boot/first.b 7 /boot/isofs.b 60 /boot/silotftp.b
|
Then, it's up to you to put silo.conf & the kernel there (or copy in the ones
from the install disk.)
Once that is set up, the 'silo -C/boot/silo.conf' will set up the little boot
loader (ultra.b) so that it will load your kernel loader (second.b), and
it will load your kernel.
In your case, you want to make sure that /dev/hda1 is mounted
on /boot when you emerge silo, otherwise you will not have a bootable
/boot partition.
Sorry to be confusing. Make sure /boot is mounted, emerge silo,
and do everything else like you have been, and that should work (or be
pretty close.) |
|
| Back to top |
|
|
Vitus
n00b
Joined: 12 Mar 2004
Posts: 6
Location: a Dane in Sao Paulo, Brasil
|
| Posted: Mon Mar 15, 2004 9:41 pm Post subject: |
|
|
Hello - first of all, thanks for your attention it is much appreciated!
Now - I did not do an "emerge silo" but while I was trying to figure out the problem myself I ran into another issue that in turn lead me to a "fsck /dev/hda1" and boy did I get a lot of errors on that! [like group, inode, free-space and so on].
So, now I'll take it all down and restart from scratch (NOTE! Is there something other than a new fdisk to "set my disk straight" that I could/should do??) and then when I get to the silo, I'll first start with an "emerge silo" - and then check for the files you mention.
Now that you say you have trouble following my partitions - is there anything you think I should do different since I am starting from scratch anyway??
I did the partitions according to the install handbook last time (http://www.gentoo.org/doc/en/handbook/handbook.xml?part=1&chap=4#doc_chap5 - and am going to do it like that again unless you yell "stop - don't do it! - here's a better way!" 
again - thx for your time on this!
_________________
Bst rgds
Vitus |
|
| Back to top |
|
|
Ferris
Retired Dev
Joined: 13 Jan 2003
Posts: 426
Location: N. Virginia (USA)
|
| Posted: Tue Mar 16, 2004 1:11 pm Post subject: |
|
|
My confusion arose from what seemed to be in your /boot (=/dev/hda1)
partition. It will really be easier if you make it s separate partition (as you
did) and put everything you need for booting there.
Maybe the documentation could be worded differently, but what it is
trying to say is this:
- mount /dev/hda1 /boot
- emerge -k silo
- cp /etc/silo.conf /boot
- nano /boot/silo.conf
- silo -C /boot/silo.conf (or, "silo -C /silo.conf -f" if you are as paranoid as I am sometimes)
You now have to put whatever kernel you are booting into /boot at whatever
point /boot/silo.conf says it is.
Since you have /boot on s separate partition, it will be easier for you if
you change any "/boot/xxx" references to plain "/xxx" or make sure
there is a soft link in /boot which looks something like this:
| Code: |
cd /boot
ln -s . /boot
|
As to your partitions, they look fine to me. I was having trouble reconciling your partition
for /boot with what seemed to be in it.
The key here is that you do have to 'emerge silo' with /dev/hda1 mounted
on /boot for any of the rest of this to get you what you want.
Regards, |
|
| Back to top |
|
|
Vitus
n00b
Joined: 12 Mar 2004
Posts: 6
Location: a Dane in Sao Paulo, Brasil
|
| Posted: Tue Mar 16, 2004 3:09 pm Post subject: |
|
|
Hi Ferris,
ok - good to hear and definitely the "emerge -k silo" clarification helps!
Anyway - I'm in a meeting right now but will start my install over from scratch when I get home tonight.
I'll hopefully provide a feedback of success by tomorrow night - which in my time is ~36-42h from now
Until then... no worries...
_________________
Bst rgds
Vitus |
|
| Back to top |
|
|
Vitus
n00b
Joined: 12 Mar 2004
Posts: 6
Location: a Dane in Sao Paulo, Brasil
|
| Posted: Wed Mar 17, 2004 7:05 pm Post subject: |
|
|
Hi again,
ooooooooookaay - so, not entirely(!) what one would call "successful"... 
I got the same ("Bus error") error on the "/sbin/silo -C /boot/silo.conf" - after remembering to do the "emerge -k silo" - now I think my problem is much more fundamental - i.e. in the mounting - or when/how to do it, more specifically.
I mean - when do I write: "mount /dev/hda1 /boot"?
Before or after "chroot"?
NOTE! in the following fdisk the labels and fs' to the right are my comments to the output - I created the partitions according to the install handbook - section 4.e.
http://www.gentoo.org/doc/en/handbook/handbook.xml?part=1&chap=4#doc_chap5
| Code: |
livecd / # fdisk /dev/hda
Command (m for help): p
Disk /dev/hda (Sun disk label): 16 heads, 63 sectors, 17660 cylinders
Units = cylinders of 1008 * 512 bytes
Device Flag Start End Blocks Id System
/dev/hda1 0 62 31248 83 Linux native - BOOT - ext3
/dev/hda2 u 62 1054 499968 82 Linux swap - SWAP - ext3
/dev/hda3 0 17660 8900640 5 Whole disk - Solaris - ext3
/dev/hda4 1054 17660 8369424 83 Linux native - ROOT - ext3
Command (m for help): q
livecd / #
|
(PS! Is there a problem in the start/end values - 62/62 - 1054/1054?)
After the swapon for hda2 (swap), I then mounted the partitions (according to step 4.j.) that I had created - i.e. mount hda3, mkdir /mnt/gentoo/boot, mount hda1 (boot) and hda3 (entire disk - solaris label) and the proc thing as well.
However when I after the "chroot" step did a "mount" I only got:
| Code: | | /dev/ROOT on / type xfs (rw,noatime) |
Trying to mount /dev/hda1 /boot from within the jail tells me that "boot is busy"
Also since I made all my fs = ext3 (ALL of them, incl. swap and entire disk) I find it strange to see "xfs" in the root - but if I exit jail and do "mount" I see:
| Code: |
exit
livecd / # mount
tmpfs on / type tmpfs (rw)
tmpfs on / type tmpfs (rw)
devfs on /dev type devfs (rw)
/newroot/dev/cdroms/cdrom0 on /mnt/cdrom type iso9660 (ro)
none on /proc type proc (rw)
/dev/hda3 on /mnt/gentoo type ext3 (rw)
none on /mnt/gentoo/proc type proc (rw)
|
Since this list misses "hda4" I then tried to mount it but got this:
| Code: |
livecd / # mount -t ext3 /dev/hda4 /
mount: wrong fs type, bad option, bad superblock on /dev/hda4,
or too many mounted file systems
|
However I can (out of jail) mount hda1 to "boot" - but that doesn't change the fact that after a new "chroot" I can't create files in "/boot" - i.e. same as before - e.g. "echo hello > /boot/testing.txt" results in a file that is reported to have a size ("ls -la") but a "more /boot/testing.txt" shows "blank" - This part concerns me as it seems to point to a fdisk/fs/mount problem that I have no clue to solve.
I am (sorry to admit it) befuddled to a higher level!
None needs to take too much time to help me - I just think I need to be directed to a "Total beginners guide in mounting and chrooting during installation" to get over this...?! OR maybe fill in the blanks that I feel are missing in the fdisk/mke2fs -j/mount/mkdir part of the install handbook... (or is this my ego trying to put the blame on someone else than myself?!  )
Thx in advance to anyone who'll push me over (the _correct_) edge!
_________________
Bst rgds
Vitus |
|
| Back to top |
|
|
Ferris
Retired Dev
Joined: 13 Jan 2003
Posts: 426
Location: N. Virginia (USA)
|
| Posted: Wed Mar 17, 2004 11:19 pm Post subject: |
|
|
In no particular order:
- the 62-62, etc is normal and expected. What fdisk calls 'End' is actually
start+size, so, for example, if size=1, it would say 1,2, but the next one
would start at 2.
- I don't recall if ext3 is OK for /boot or not. Certainly ext2 is.
- And, most important. Mount /boot after the chroot. The emerge of silo
is going to write into the /boot directory, and if you do the mount before you
chroot, then where /dev/hda1 is mounted is hidden. You want something like
| Code: |
chroot....
mount /dev/hda1 /boot
emerge -k silo
cp /etc/silo.conf /boot
nano .....
silo -C /boot/silo.conf
<put your kernel into /boot>
|
Because silo writes to the current /boot directory, and that changes when you
do the chroot.
Hope this helps, |
|
| Back to top |
|
|
Ferris
Retired Dev
Joined: 13 Jan 2003
Posts: 426
Location: N. Virginia (USA)
|
| Posted: Thu Mar 18, 2004 12:00 am Post subject: |
|
|
Ok, a couple other things.
You don't want a file system on the swap partition. In your case, you want
mkswap /dev/hda2
instead.
You certainly don't want an ext3 file system on /dev/hda3. It's a special partition
used as part of the sun disk label. It's something fdisk creates, and you never
touch.
And again, just make sure that the "mount /dev/hda1" and the "emerge -k silo"
are on the same side of the chroot.
Regards, |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gentoo on Sparc
