[Fwd: failure notice]

From: Harald Beugler-Bell (hbell@amazon.de)
Date: Tue Apr 04 2000 - 08:23:41 PDT

  • Next message: Waite, Michael: "installing on an ES40"

    Message-ID: <38EA08FD.91925A6B@amazon.de>
    Date: Tue, 04 Apr 2000 17:23:41 +0200
    From: Harald Beugler-Bell <hbell@amazon.de>
    Subject: [Fwd: failure notice]
    

    "Ward, Jonathan" wrote:
    > =

    > Actually the -f flag is needed for any and all partitions with overlap =
    the
    > REGION you are writing the boot sector to. If you use a standard UNIX =
    BSD
    > label with partition c =3D whole disk (0-xxx), then you need -f3. If y=
    ou
    > create a boot partition (most people do, but it is not needed) you wil=
    l
    > ALSO need -f1.
    > =

    > The result is
    > swriteboot -f1 -f3 /dev/sda /boot/bootlx
    > =

    > swriteboot should report an error if there are other overlapping partit=
    ions.
    > =

    > What command are you using to boot? Are you booting from SRM or AlphaB=
    IOS?
    > Was this an NT or UNIX machine before? SRM requires BSD style disklabe=
    ls,
    > AlphaBIOS requires DOS style.

    I'm booting from SRM. I had True64 on the machine before. I wrote a new
    disklabel with the Linux fdisk utility (bsd-type) and deleted c: as
    whole-disk-partition before I created the other partitions:
    a: /boot, b: /, c: swap, d: /usr, e: /var and f: /opt

    again the boot commands I used:
    >> boot dkb0 -fi 2/boot/vmlinuz -flags root=3D/dev/sda2
    and
    >> boot dkb0 0
    =2E..setting the following line in aboot.conf:
    0:2/boot/vmlinuz ro root=3D/dev/sda2

    > =

    > > -----Original Message-----
    > > From: Harald Beugler-Bell [mailto:hbell@amazon.de]
    > > Sent: Tuesday, April 04, 2000 9:14 AM
    > > To: Lennart B=F6rjeson
    > > Cc: suse-axp@suse.com
    > > Subject: Re: SV: [suse-axp] Boot problems
    > >
    > >
    > > Lennart B=F6rjeson wrote:
    > > >
    > > > You should do swriteboot to /dev/sda, not /dev/sda1 !
    > >
    > > Oh I=B4m sorry, this was a typo, I wrote to /dev/sda, also the line i=
    n
    > > aboot.conf is without " at the end:
    > > 0:2/boot/vmlinuz ro root=3D/dev/sda2
    > >
    > > >
    > > > (I don't remember all particulars concerning the -f switch,
    > > but I believe
    > > > -f3 is the recommended one.)
    > >
    > > as I understood the option -f is followed by the partition
    > > number (here
    > > 1 for a) where aboot will write to...
    > >
    > > >
    > > > -----Ursprungligt meddelande-----
    > > > Fran: Harald Beugler-Bell [mailto:hbell@amazon.de]
    > > > Skickat: den 4 april 2000 12:08
    > > > Till: suse-axp@suse.com
    > > > =C4mne: [suse-axp] Boot problems
    > > >
    > > > I installed axp-suse linux 6.3 on an Alpha 1200 server and ran into=

    > > > "some" problems.
    > > >
    > > > 1. The system does not boot from disk
    > > > 2. random system crashes
    > > >
    > > > Any help is welcome. See a more detailed description of
    > > problems below.
    > > >
    > > > Here some system data:
    > > > Server: Alpha 1200, 2 CPUs (EV56), 768 MB memory
    > > > Firmware: Version 5.6-4
    > > > Controller: NCR53C810 (CD-ROM)
    > > > QLogicISP10X0 (hard disks)
    > > > disk type (sda): DS-RZ10F-VW (9,1 GB)
    > > >
    > > > -------------------------------------------
    > > > + to 1. The system does not boot from disk
    > > > -------------------------------------------
    > > > I created 6 partitions and changed the blocksize in /boot
    > > and / to 1024.
    > > > a: /boot, b: /, c: swap, d: /usr, e: /var and f: /opt
    > > >
    > > > I installed Linux with the SMP-Kernel. Then I installed
    > > aboot with the
    > > > command:
    > > > # swriteboot -f1 /dev/sda1 /boot/bootlx
    > > >
    > > > I tried to boot:
    > > > >> boot dkb0 -fi 2/boot/vmlinuz -flags root=3D/dev/sda2
    > > > and
    > > > >> boot dkb0 0
    > > > ...setting the following line in aboot.conf:
    > > > 0:2/boot/vmlinuz ro root=3D/dev/sda2"
    > > >
    > > > however boot stops with the message "kernel stack not valid halt"
    > > > I reinstalled the kernel - same story. Did I miss something??
    > > >
    > > > ------------------------------
    > > > + to 2. random system crashes
    > > > ------------------------------
    > > > (after boot from the installation CD ROM) I experience random syste=
    m
    > > > crashes with log messages I cannot interperet (see below). Might be=

    > > > related to problem 1 ??
    > > >
    > > > The kernel is the SMP Kernel for multi-processor systems. The packe=
    t
    > > > kernmods.rpm is installed.
    > > >
    > > > from /var/log/messages:
    > > > ....
    > > >
    > > ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
    > > ^@^@^@^@^@^@^@
    > > >
    > > ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
    > > ^@^@^@^@^@^@^@
    > > > ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
    > > > Apr 4 10:41:27 de-linus-2 kernel: ^IEV5 BC_TAG_ADDR^I^I^I=3D
    > > > ffffff804c4f6fff
    > > > Apr 4 10:41:27 de-linus-2 kernel: ^IEV5 EI_ADDR: Phys addr
    > > of Xfer^I=3D
    > > > ffffff004c002f4f
    > > > Apr 4 10:41:27 de-linus-2 kernel: ^IFill Syndrome^I^I^I=3D
    > > > d200
    > > > Apr 4 10:41:27 de-linus-2 kernel: ^IEI_STAT reg^I^I^I=3D
    > > fffffff005ffffff
    > > > Apr 4 10:41:27 de-linus-2 kernel: ^ILD_LOCK^I^I^I^I=3D
    > > ffffff0000567d9f
    > > > Apr 4 10:46:27 de-linus-2 syslogd 1.3-3: restart.
    > > >
    > > > Hari
    > > > --
    > > > | Harald Beugler-Bell
    > > > | IT * UNIX Systems *
    > > > | ++49-(0)941-78878-181
    > > > | http://www.amazon.de



    This archive was generated by hypermail 2.1.0 : Mon Jun 04 2001 - 04:18:15 PDT