Subject: RE: Problems booting Cobalt Qube 2 (fwd)
To: 'John Mackey' <s0lman@rootshell.be>
From: Bob Bostwick <bobb@digitechsystems.com>
List: port-cobalt
Date: 08/22/2002 14:02:13
Not sure if you are still working on this or not, I haven't had time to
work on mine lately. I think the problem you are having is the disk
needs to be partitioned with BSD, so it gets the correct magic number,
then the partition can be formatted by RH to get ext2fs. I could be
totally wrong here, but from what I have read in the man pages this is
what it looks like the problem is. Mine is kind of on a back burner for
right now, but once I get it up, I'll let you know if that worked or
not. Sorry I took so long to respond.
> -----Original Message-----
> From: port-cobalt-owner@netbsd.org
[mailto:port-cobalt-owner@netbsd.org]
> On Behalf Of John Mackey
> Sent: Friday, August 09, 2002 11:03 AM
> To: port-cobalt@netbsd.org
> Subject: RE: Problems booting Cobalt Qube 2 (fwd)
>
>
>
> ---------- Forwarded message ----------
> Date: Fri, 9 Aug 2002 18:01:53 +0200 (CEST)
> From: John Mackey <s0lman@phenix.rootshell.be>
> To: Bob Bostwick <bobb@digitechsystems.com>
> Subject: RE: Problems booting Cobalt Qube 2
>
> Ok, this is what Im doing to "format" the partition. First off, I am
using
> the original disk. I jsut happened to wipe everyhing before I started
> (silly me). Anyway, I format the partition by removing the HD and
putting
> in into a PC that runs RH 6.2. It uses the old ext2fs (1.18 I think).
I
> issue the the command "mke2fs -r 0 -O none /dev/hdb2" (hdb2 being the
> second drive in linux land). I mount it onthe RH 6.2 system with no
> problem and make a directory called boot.
>
> I remove the drive and place it back into the Qube 2. Netboot with no
> problems. I try to mount the rive and I get this error ...
>
> # mount /dev/wd0e /mnt
> mount_ext2fs: /dev/wd0e on /mnt: Input/output error
>
>
> I do fsck on it and I get this ...
>
> # fsck /dev/wd0e
> ** /dev/rwd0e
> BAD SUPER BLOCK: MAGIC NUMBER WRONG
> fsck: /dev/rwd0e: Trace/BPT trap
>
>
> Any ideas.
>
> Thanks in advance.
>
>
>
> Regards,
>
> ./john
>
>
>
>
> On Fri, 9 Aug 2002, Bob Bostwick wrote:
>
> > I see that your wd0e partition is only 15MB. This means that you
are
> > not using the original one that came with the Qube 2. I am trying
to do
> > the same thing, as I don't need a big partition for the kernel. I
am
> > wondering though, are you actually able to mount this partition? If
so,
> > how did you "format" it with ext2fs? I can't find any way to
actually
> > format the new small partition while netboot'd. Can you run fsck on
> > your wd0e partition? If it gives you errors, I think you and I may
be
> > having the same problem.?...
> >
> > B
> >
> > -----Original Message-----
> > From: port-cobalt-owner@netbsd.org
[mailto:port-cobalt-owner@netbsd.org]
> > On Behalf Of John Mackey
> > Sent: Friday, August 09, 2002 12:51 AM
> > To: port-cobalt@netbsd.org
> > Subject: Problems booting Cobalt Qube 2
> >
> >
> > Hi ppl,
> >
> > I have been struggling to install NetBSD on my cobalt Qube 2 .
> >
> > I have followed the steps on
> > http://www.netbsd.org/Ports/cobalt/faq.html.
> >
> > Some details on my configuration
> >
> > # fdisk
> > NetBSD disklabel disk geometry:
> > cylinders: 8912 heads: 15 sectors/track: 63 (945 sectors/cylinder)
> >
> > BIOS disk geometry:
> > cylinders: 8912 heads: 15 sectors/track: 63 (945 sectors/cylinder)
> >
> > Partition table:
> > 0: sysid 131 (Linux native)
> > start 63, size 31328 (15 MB), flag 0x0
> > beg: cylinder 0, head 1, sector 1
> > end: cylinder 33, head 3, sector 17
> > 1: sysid 169 (NetBSD)
> > start 42336, size 8379504 (4091 MB), flag 0x0
> > beg: cylinder 44, head 12, sector 1
> > end: cylinder 719, head 14, sector 63
> > 2: <UNUSED>
> > 3: <UNUSED>
> >
> >
> >
> > partition> E
> > # /dev/rwd0d:
> > type: ESDI
> > disk: QUANTUM FIREBALL
> > label: cylinders: 8912
> > flags:
> > bytes/sector: 512
> > sectors/track: 63
> > tracks/cylinder: 15
> > sectors/cylinder: 945
> > cylinders: 8912
> > total sectors: 8421840
> > rpm: 3600
> > interleave: 1
> > trackskew: 0
> > cylinderskew: 0
> > headswitch: 0 # microseconds
> > track-to-track seek: 0 # microseconds
> > drivedata: 0
> >
> > 8 partitions:
> > # size offset fstype [fsize bsize cpg/sgs]
> > c: 8379504 42336 4.2BSD 1024 8192 16 # (Cyl.
44*-
> > 8911)
> > d: 8421840 0 unused 0 0 # (Cyl.
0 -
> > 8911)
> > e: 31328 63 Linux Ext2 0 0 # (Cyl.
0*-
> > 33*)
> > f: 8379504 42336 unused 0 0 # (Cyl.
44*-
> > 8911)
> >
> >
> > # more fstab
> > # $NetBSD: fstab.wd,v 1.3 2000/06/19 18:32:08 soren Exp $
> >
> > /dev/wd0c / ffs rw 1 1
> > /dev/wd0e /stand ext2fs rw 1 2
> > #/dev/wd0f none swap sw 0 0
> >
> >
> >
> > OK, is this problem related to partitioning ?
> >
> > I have put this kernel
> >
> >
ftp.netbsd.org/pub/NetBSD/arch/cobalt/snapshot/1.5.3_RC2-20020428/binary
> > /kernel/
> > netbsd.GENERIC.gz
> >
> > into the /boot directory and renamed in to vmlinux_raq-2800.gz
> >
> >
> > When I reboot I get the error bellow.
> >
> > syncing disks... done
> > rebooting...
> >
> > Cobalt Microserver Diagnostics - 'We serve it, you surf it'
> > Built Tue May 25 15:58:41 PDT 1999
> >
> > 1.LCD Test................................PASS
> > 2.Controller Test.........................PASS
> > 5.Bank 0:.................................16M
> > 6.Bank 1:.................................0M
> > 7.Bank 2:.................................0M
> > 8.Bank 3:.................................0M
> > 9.Serial Test.............................PASS
> > 10.PCI Expansion Slot....................**EMPTY**
> > 12.IDE Test................................PASS
> > 13.Ethernet Test...........................PASS
> > 16.RTC Test................................PASS
> > BOOTLOADER ramcode: selected partition /dev/hda1
> > Decompressing done
> > Executing bootloader kernel...
> > Jump_to_Real_Kernel: disk error, trying BFD again
> > BOOTLOADER ramcode: selected partition /dev/hdc1
> > Decompressing - done
> > Executing bootloader kernel...
> > Jump_to_Real_Kernel: disk error, trying BFD again
> > get_root_dev: nr_boot_failures 0x00000002 exceeds maxtries
0x00000002
> > for
> > boot_i
> > ndex 0x00000000
> >
> >
> > *** halting ***
> >
> >
> >
> >
> > Any ideas on this. I knoiw it'll be something very simple.
> >
> > Thanks in advance.
> >
> >
> >
> > Regards,
> >
> > ./John
> >
> >