Re: [suse-sparc] RAID troubles

From: nod (nod@bouncing.org)
Date: Sat Mar 02 2002 - 16:48:06 PST

  • Next message: Brian Hazlehurst: "Re: [suse-sparc] RAID troubles"

    Message-Id: <200203030045.g230j4I31278@slimnblack.bouncing.org>
    From: nod <nod@bouncing.org>
    Date: Sun, 3 Mar 2002 00:48:06 +0000
    Subject: Re: [suse-sparc] RAID troubles
    

    to my unexpert eye the raidtab looks correct, but what I meant was have you
    set the partition type correctly in fdisk e.g.

    # fdisk -l /dev/sde

    outputs :

    Disk /dev/hde: 16 heads, 63 sectors, 59560 cylinders
    Units = cylinders of 1008 * 512 bytes

       Device Boot Start End Blocks Id System
    /dev/sde1 * 1 40635 20480008+ fd Linux raid autodetect
    /dev/sde2 40636 59560 9538200 fd Linux raid autodetect

    so that the systems identifies it correctly ?

    On Saturday 02 Mar 2002 10:58 pm, Brian Hazlehurst wrote:
    > > could you include your raidtab and I'll compare it with mine. Also you
    > > are setting the partition type correctly using fdisk ?
    >
    > I believe the partitions are being set right. The first partition (Linux
    > native) is being used on each disk. The only other partition is a third
    > partition (whole disk) which is required by Sun (as I understand it).
    >
    > If I don't create the RAID (with mkraid), then the disks each maintain
    > their partition tables on reboot. If I do make the RAID, then everything
    > appears fine, but on reboot the partitions are hosed.
    >
    > Here is the raidtab file:
    >
    > raiddev /dev/md0
    > raid-level 5
    > nr-raid-disks 7
    > nr-spare-disks 1
    > persistent-superblock 1
    > parity-algorithm left-symmetric
    > chunk-size 32
    > device /dev/sde1
    > raid-disk 0
    > device /dev/sdf1
    > raid-disk 1
    > device /dev/sdg1
    > raid-disk 2
    > device /dev/sdh1
    > raid-disk 3
    > device /dev/sdi1
    > raid-disk 4
    > device /dev/sdj1
    > raid-disk 5
    > device /dev/sdk1
    > raid-disk 6
    > device /dev/sdl1
    > spare-disk 0
    >
    > On Sat, 2 Mar 2002, nod wrote:
    > > could you include your raidtab and I'll compare it with mine. Also you
    > > are setting the partition type correctly using fdisk ?
    > >
    > > On Saturday 02 Mar 2002 2:07 am, Brian Hazlehurst wrote:
    > > > Hi list,
    > > >
    > > > I make the raid device (mkraid, with a raidtab that specifies raid 5
    > > > for 8 distinct drives, including one "spare").
    > > >
    > > > I create a file system (I've tried ext2 and reiser file systems).
    > > >
    > > > I reboot (sometimes, I've mounted the block device and successfully
    > > > written to it first).
    > > >
    > > > Each time, on the reboot, the partition tables on most of the disks get
    > > > "lost" (usually, the first and last disk seem to retain their partition
    > > > tables), and the device is unusable.
    > > >
    > > > I'm not sure what's going on. Any suggestions? I'm running 7.3 and
    > > > the raid is an array on a single scsi controller.
    > > >
    > > > -Brian
    > > >
    > > > brian@dcog.net
    > >
    > > --
    > > To unsubscribe, e-mail: suse-sparc-unsubscribe@suse.com
    > > For additional commands, e-mail: suse-sparc-help@suse.com

    -- 
    To unsubscribe, e-mail: suse-sparc-unsubscribe@suse.com
    For additional commands, e-mail: suse-sparc-help@suse.com
    



    This archive was generated by hypermail 2.1.0 : Sat Mar 02 2002 - 16:44:21 PST