Request for new offset to Promise raid-metadata

Bug #465198 reported by Even Ambjørnrud
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dmraid (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: dmraid

I installed dmraid on my system running ubuntu 9.04, but dmraid -r did not find any raid disks on my fakeraid controller Promise FastTrak S150 TX2plus.

After using the description found here:
https://help.ubuntu.com/community/FakeRaidDebug
I found a new offset to the raid-metadata. The offset is 951

I have changed pdc.h and successfully compiled the 1.0.0.rc15-6ubuntu2 version myself, my raid1 is now up and running.
This offset was also mentioned by xprimnt way back in 2007: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/112402/comments/20

Can anyone of the developers commit this offset-value to the git-repository?

In pdc.h:
...
#define PDC_CONFIGOFFSETS ..., 951
...

Thanks!

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Thanks for your report. You might want to post this to https://www.redhat.com/mailman/listinfo/ataraid-list as well.

Changed in dmraid (Ubuntu):
status: New → Confirmed
Changed in dmraid (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package dmraid - 1.0.0.rc16-3ubuntu1

---------------
dmraid (1.0.0.rc16-3ubuntu1) lucid; urgency=low

  * Merge from debian testing. (LP: #503136) Remaining changes:
    - debian/dmraid-activate: Remove the special-casing of the root
      device which breaks in many situations and leaves the raw devices
      exposed. This was introduced in Debian to accommodate some broken
      configurations which wanted to access "partitions" on the raid
      raw devices. In Ubuntu, broken configurations has not been supported.
    - debian/dmraid.postinst: Comment out "udevadm trigger" call in postinst
      for now as it has severeconsequences when mountall is installed
      (clears /tmp). If dmraid is installed, then presumably the important
      system devices are up and one canbe bothered with a reboot to take
      the change into account. Let update-initramfs flag the system
      as needing a reboot.

dmraid (1.0.0.rc16-3) unstable; urgency=low

  * [3bea125] debian/patches/20_fix_isw_sectors_calculation.patch: Fix
    isw raid0 incorrect sectors calculation (Closes: #561866) - thanks
    to Valentin Pavlyuchenko
  * [239630a] Added ${misc:Depends} in Depends

dmraid (1.0.0.rc16-2) unstable; urgency=low

  * [0819a82] debian/patches/18_pdc_raid10_failure..patch: fix pdc
    metadata format handler to report the proper number of devices in a
    subset
  * [8418d6b] debian/patches/19_ddf1_lsi_persistent_name.patch: Because the
    LSI bios changes the timestamp in the metadata on every boot, neutralize
    it in order to allow for persistent names.

dmraid (1.0.0.rc16-1) experimental; urgency=low

  [ Tormod Volden ]
  * [aed3ea8] Add support for "nodmraid" boot option

  [ Giuseppe Iuculano ]
  * [6ae6d88] Imported Upstream version 1.0.0.rc16
  * [3bdcbf4] Remove old 1.0.0.rc15 directory
  * [f2b47d1] Refreshed patches and deleted patches merged in upstream
  * [27f877d] SONAME bump, libdmraid1.0.0.rc15 -> libdmraid1.0.0.rc16
  * [8ea0cf4] Updated symbols file
  * [e2bd834] debian/patches/02_disable_dmreg.patch: Disabled all dmreg
    stuff
  * [7339f26] Added 951 disk offset for Promise FastTrak S150 TX2plus
    (LP: #465198) - thanks to Even Ambjørnrud
  * [fbe64d4] Updated my email address and removed DM-Upload-Allowed
    control field
 -- Artur Rona <email address hidden> Thu, 04 Feb 2010 21:34:22 +0100

Changed in dmraid (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.