dmraid does not correctly identify disks under Promise Fasttrak TX4310

Bug #367665 reported by Paul R on 2009-04-27
2
Affects Status Importance Assigned to Milestone
dmraid (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: dmraid

I am running Ubuntu 8.10 (kernel 2.6.27-11-generic)
In trying to solve this I loaded the latest dmraid in testing: Version: 1.0.0.rc15-6

Using Promise Fasttrak TX4310 with 4 Seagate SATA 1.5TB drives ST31500341AS.
Booting from separate 40GB ATA disk (sda) without problem.
Unable to run dmraid as follows:

# dmraid -s
ERROR: pdc: identifying /dev/sde, magic_0: 0x2380414/0xab0409, magic_1: 0x2380414/0x0, total_disks: 0
ERROR: pdc: identifying /dev/sdd, magic_0: 0x2380414/0xaa0409, magic_1: 0x2380414/0x0, total_disks: 0
ERROR: pdc: identifying /dev/sdc, magic_0: 0x2370414/0xa90409, magic_1: 0x2370414/0x0, total_disks: 0
ERROR: pdc: identifying /dev/sdb, magic_0: 0x2370414/0xa80409, magic_1: 0x2370414/0x0, total_disks: 0
no raid disks

This occurs with any dmraid command that attempts to access the disks (-tay or -r)
Vol_id shows the following:
# vol_id /dev/sdb
ID_FS_USAGE=raid
ID_FS_TYPE=promise_fasttrack_raid_member
ID_FS_VERSION=
ID_FS_UUID=
ID_FS_UUID_ENC=
ID_FS_LABEL=
ID_FS_LABEL_ENC=
ID_FS_LABEL_SAFE=

I submitted this to debian as a bug, but they closed it saying it should be filed with Ubuntu first. From the debian bug report utility:
--- /proc/partitions:
major minor #blocks name

   8 0 39082680 sda
   8 1 37672393 sda1
   8 2 1 sda2
   8 5 1405656 sda5
   8 16 1465138584 sdb
   8 32 1465138584 sdc
   8 48 1465138584 sdd
   8 64 1465138584 sde

--- initrd.img-2.6.27-11-generic:
48124 blocks
lib/modules/2.6.27-11-generic/kernel/drivers/md/dm-mirror.ko
lib/modules/2.6.27-11-generic/kernel/drivers/md/dm-log.ko
lib/modules/2.6.27-11-generic/kernel/drivers/md/dm-mod.ko

--- /proc/modules:
dm_raid4_5 73996 0 - Live 0xde863000
dm_region_hash 19456 1 dm_raid4_5, Live 0xde81c000
dm_mem_cache 12800 1 dm_raid4_5, Live 0xde82d000
dm_message 11008 1 dm_raid4_5, Live 0xde829000
dm_mirror 27008 0 - Live 0xde844000
dm_log 17924 3 dm_raid4_5,dm_region_hash,dm_mirror, Live 0xde823000
dm_mod 63432 3 dm_raid4_5,dm_mirror,dm_log, Live 0xde833000

Versions of packages dmraid depends on:
ii dmsetup 2:1.02.30-3 The Linux Kernel Device Mapper use
ii libc6 2.8~20080505-0ubuntu9 GNU C Library: Shared libraries
ii libdmraid1.0.0.rc1 1.0.0.rc15-6 Device-Mapper Software RAID suppor
ii libselinux1 2.0.65-2 SELinux shared libraries
ii libsepol1 2.0.32-1 Security Enhanced Linux policy lib
ii udev 124-9ubuntu0.2 rule-based device node and kernel

Paul R (joe-palfreystreet) wrote :

This seems to have been around since 2006 (2.6.17). I found a near identical description in Bug #67468 - unfortunately, the reporter never responded to the request to test with Intrepid 8.10 so it was closed.

Phillip Susi (psusi) wrote :

Can you test with Karmic or Lucid? ;)

Also can you post the output of dmraid -n?

Changed in dmraid (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for dmraid (Ubuntu) because there has been no activity for 60 days.]

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

Other bug subscribers