|
Hello Phillip (and other people in this list),
Here are some outputs of dmraid that may help you understand the situation. $ dmraid -ay -vvv -d WARN: locking /var/lock/dmraid/.lock NOTICE: /dev/sdd: asr discovering NOTICE: /dev/sdd: ddf1 discovering NOTICE: /dev/sdd: hpt37x discovering NOTICE: /dev/sdd: hpt45x discovering NOTICE: /dev/sdd: isw discovering DEBUG: not isw at 500107860992 DEBUG: isw trying hard coded -2115 offset. DEBUG: not isw at 500106779136 NOTICE: /dev/sdd: jmicron discovering NOTICE: /dev/sdd: lsi discovering NOTICE: /dev/sdd: nvidia discovering NOTICE: /dev/sdd: pdc discovering ERROR: pdc: zero sectors on /dev/sdd ERROR: pdc: setting up RAID device /dev/sdd NOTICE: /dev/sdd: sil discovering NOTICE: /dev/sdd: via discovering NOTICE: /dev/sdc: asr discovering NOTICE: /dev/sdc: ddf1 discovering NOTICE: /dev/sdc: hpt37x discovering NOTICE: /dev/sdc: hpt45x discovering NOTICE: /dev/sdc: isw discovering DEBUG: not isw at 500107860992 DEBUG: isw trying hard coded -2115 offset. DEBUG: not isw at 500106779136 NOTICE: /dev/sdc: jmicron discovering NOTICE: /dev/sdc: lsi discovering NOTICE: /dev/sdc: nvidia discovering NOTICE: /dev/sdc: pdc discovering ERROR: pdc: zero sectors on /dev/sdc ERROR: pdc: setting up RAID device /dev/sdc NOTICE: /dev/sdc: sil discovering NOTICE: /dev/sdc: via discovering NOTICE: /dev/sdb: asr discovering NOTICE: /dev/sdb: ddf1 discovering NOTICE: /dev/sdb: hpt37x discovering NOTICE: /dev/sdb: hpt45x discovering NOTICE: /dev/sdb: isw discovering DEBUG: not isw at 500107860992 DEBUG: isw trying hard coded -2115 offset. DEBUG: not isw at 500106779136 NOTICE: /dev/sdb: jmicron discovering NOTICE: /dev/sdb: lsi discovering NOTICE: /dev/sdb: nvidia discovering NOTICE: /dev/sdb: pdc discovering ERROR: pdc: zero sectors on /dev/sdb ERROR: pdc: setting up RAID device /dev/sdb NOTICE: /dev/sdb: sil discovering NOTICE: /dev/sdb: via discovering NOTICE: /dev/sda: asr discovering NOTICE: /dev/sda: ddf1 discovering NOTICE: /dev/sda: hpt37x discovering NOTICE: /dev/sda: hpt45x discovering NOTICE: /dev/sda: isw discovering DEBUG: not isw at 64023256064 DEBUG: isw trying hard coded -2115 offset. DEBUG: not isw at 64022174208 NOTICE: /dev/sda: jmicron discovering NOTICE: /dev/sda: lsi discovering NOTICE: /dev/sda: nvidia discovering NOTICE: /dev/sda: pdc discovering NOTICE: /dev/sda: sil discovering NOTICE: /dev/sda: via discovering no raid disks WARN: unlocking /var/lock/dmraid/.lock I have also attached the output of "dmraid -rD" Hopefully you can point me to the correct offset for the metadata. Kind regards, Mark-Willem > Date: Fri, 23 Mar 2012 13:23:46 -0400 > From: psusi@xxxxxxxxxx > To: markwillem@xxxxxxxxxxx > CC: ataraid-list@xxxxxxxxxx; iuculano@xxxxxxxxxx; themuso@xxxxxxxxxx > Subject: Re: Howto: implement AMD SB9xx RAID5 support in dmraid > > On 3/23/2012 12:52 PM, Mark-Willem Jansen wrote: > > > > Dear dmraid developer(s)/maintainer(s), > > > > Since a few weeks I am trying to get my new rig up and running under > > linux. I run a dual-boot system with Windows 7 and Debian/wheezy. I > > have installed the OS files on a small SSD and have setup a RAID-5 > > for the rest of the files. It is a FakeRAID/SATA-RAID which is > > controlled by the AMD SB950 chip. Unfortunately dmraid does not seem > > to support this chip in combination with a RAID-5 setup. I would like > > to implement this, but to do that I need some help and information. > > The plan is as follows > > I would advise using mdadm instead since it is much better supported and > more reliable and feature complete. > > > - Get dmraid working with the dm-raid module. Dmraid needs a > > dm-target that support RAID-5. In the past there was a patch for the > > prior 3.x linux-kernel which added the dm-raid45 module. Now a days > > there is a module called dm-raid which will provide the same > > aliases(dm-raid4, dm-raid5) as the dm-raid45 module. How does on > > check if dmraid can be made compatible with this new module? My first > > idea was to look at the symbols dm-raid and dm-raid45 export to the > > user space and which of these symbols are used by dmriad. > > I believe it should just work unless they changed the format of the > dmsetup table. > > > - Find the metadata offset for the SB950 chipset. For this I need not > > know with which characters the header of the metadata starts? The > > SB950 seems to contain a Promise controller. > > dmraid -n doesn't already recognize it? You can find the existing known > offsets in pdc.h. > > > - Interpret the metadata provided on the disks. From the setup screen > > provided by the UEFI driver I can find the stripe size, but in which > > sequence(ls,rs,la,ra) these stripes are order I do not know, yet. > > What is the best way to find this sequence? The RAID-5 disk hold a > > GPT table, maybe one can look at how the header of this table is > > distributed over the disk to find the stripe sequence. > > dmraid already understands pdc metadata. > > > - [optionally] Implement GPT support. > > Ubtunu 12.04 has switched to letting kpartx activate the partitions > instead of dmraid, which supports GPT. > |
Attachment:
SB950-raid5_dmraid.tar.bz2
Description: application/bzip
_______________________________________________ Ataraid-list mailing list Ataraid-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/ataraid-list
