Re: [suse-axp] FW: New Thread - Getting "Block 0 not valid bootblock" error

From: Stefan Fent (sf@suse.de)
Date: Wed Jun 14 2000 - 12:12:12 PDT

  • Next message: William H. Magill: "Re: [suse-axp] Fdisk behavior is wrong in 6.3 ???" 

    Date: Wed, 14 Jun 2000 21:12:12 +0200 (CEST)
From: Stefan Fent <sf@suse.de>
Message-ID: <Pine.LNX.4.21.0006142101170.16362-100000@ampere.suse.de>
Subject: Re: [suse-axp] FW: New Thread - Getting "Block 0 not valid bootblock" error

    On Wed, 14 Jun 2000, Jim Hoepner wrote:

    > Date: Wed, 14 Jun 2000 11:16:16 -0500
    > From: Jim Hoepner <jhoepner@tvsw.org>
    > Cc: SuSE-axp@suse.com
    > Subject: [suse-axp] FW: New Thread - Getting "Block 0 not valid
    > bootblock" error
    >
    > Hi, I made a few changes and now I get to a "aboot>"
    > prompt.
    > In short, I re-did the BSD disk label to:
    > a: = /boot (started at cyl 3)
    > b: = swap (cyl 4-270)
    > c: = / (cyl 271-8347)

    You must not use partition 'c', if you create a BSD-label, you will remark
    that 'c' is created automatically, it contains the entire disk and must be
    of type 'unused'.
    you should create a partition 'd' of the size of your partition 'c' and
    mount it to '/'.

    to boot via aboot.conf, you will have to execute
    'abootconf /dev/sda 4' to make aboot look in partition 4 for
    /etc/aboot.conf.

    > and I did not create DOS partitions 1-4 because my swap is
    > recognized when I go in/out of YaST.
    >
    > Here's the install sequence:
    > ************************************************************
    > CONSOLE COMMAND DESCRIPTION
    > SRM >>>set boot_file ""
    > SRM >>>set bootdef_dev ""
    > SRM >>>set boot_osflags ""
    > SRM >>>boot dka200 -fl 0 (boot from CD)
    >
    > fdisk b enter BSD mode
    > fdisk n create partition tbl
    > a:Cyl 3-13, type ext2 (d) ( mount to /boot)
    > b:Cyl 14-270, type swap (8) ( swap )
    > c:Cyl 271-8347, type ext2 (8) ( mount to / )

    see above.

    > fdisk w write partition to disk
    > fdisk q quit fdisk
    > fdisk ALT-F1 go back to YaST
    > YaST ABORT go back to YaST's main
    > menu and go back in so
    > arguments which would be ok but I don't know what to enter?
    > Do I need to run "abootconf" to move on?

    It won't work in this case, but normally
    'aboot>1/boot/vmlinux.gz ro root=/dev/sda4' should boot.
    >

    regards,

            Stefan Fent 

    --
SuSE GmbH,             Tel:   +49-911-7405331 
Schanzaeckerstr. 10,   Fax:   +49-911-3206727
90443 Nuernberg,       Email: sf@suse.de
Germany                WWW:   http://www.suse.de

    The reason computer chips are so small is computers don't eat much.

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