Ubuntu
dmraid package

dmraid doesn't open the fakeraid

Bug #152409 reported by Fonso
4
Affects Status Importance Assigned to Milestone
dmraid (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi,

I updated Feisty amd64 to Gutsy Release Candidate. I used update-manager, it was without problem.

When I reboot the computer I can boot Vista using grub but I can't boot Ubuntu. I try to use Gutsy Release Candidate Desktop AMD64 CD to repair the boot Ubuntu partition.

I follow the steps in FakeRaid Howto, when I execute dmraid -r, it shows:

/dev/sda: isw, "isw_diagfejhc", GROUP, ok, 488397166 sectors, data@ 0
/dev/sdb: isw, "isw_diagfejhc", GROUP, ok, 488397166 sectors, data@ 0

After I execute dmraid -ay without messages, I try with dmraid -ay -v, it shows:

INFO: Activating GROUP RAID set "isw_diagfejhc"

But the partitions of the raid don't appear in /dev/mapper.

The motherboard is an Intel DWG965H and the raid is a raid 1 (mirror).

I execute the next command dmraid -tay -vvvv -dddd -f isw, it appears in other bug report the result is:

NOTICE: checking format identifier isw
WARN: locking /var/lock/dmraid/.lock
NOTICE: /dev/sda: isw discovering
NOTICE: /dev/sda: isw metadata discovered
NOTICE: /dev/sdb: isw discovering
NOTICE: /dev/sdb: isw metadata discovered
DEBUG: _find_set: searching isw_diagfejhc
DEBUG: _find_set: not found isw_diagfejhc
DEBUG: _find_set: searching isw_diagfejhc_Volume0
DEBUG: _find_set: searching isw_diagfejhc_Volume0
DEBUG: _find_set: not found isw_diagfejhc_Volume0
DEBUG: _find_set: not found isw_diagfejhc_Volume0
NOTICE: added /dev/sda to RAID set "isw_diagfejhc"
DEBUG: _find_set: searching isw_diagfejhc
DEBUG: _find_set: found isw_diagfejhc
DEBUG: _find_set: searching isw_diagfejhc_Volume0
DEBUG: _find_set: searching isw_diagfejhc_Volume0
DEBUG: _find_set: found isw_diagfejhc_Volume0
DEBUG: _find_set: found isw_diagfejhc_Volume0
NOTICE: added /dev/sdb to RAID set "isw_diagfejhc"
DEBUG: checking isw device "/dev/sda"
DEBUG: checking isw device "/dev/sdb"
DEBUG: set status of set "isw_diagfejhc_Volume0" to 16
DEBUG: set status of set "isw_diagfejhc" to 16
isw_diagfejhc_Volume0: 0 488390656 mirror core 2 131072 nosync 2 /dev/sda 0 /dev/sdb 0
INFO: Activating GROUP RAID set "isw_diagfejhc"
WARN: unlocking /var/lock/dmraid/.lock
DEBUG: freeing devices of RAID set "isw_diagfejhc_Volume0"
DEBUG: freeing device "isw_diagfejhc_Volume0", path "/dev/sda"
DEBUG: freeing device "isw_diagfejhc_Volume0", path "/dev/sdb"
DEBUG: freeing devices of RAID set "isw_diagfejhc"
DEBUG: freeing device "isw_diagfejhc", path "/dev/sda"
DEBUG: freeing device "isw_diagfejhc", path "/dev/sdb"

Also I executed dmraid -n, the result was:

/dev/sda (isw):
0x000 sig: " Intel Raid ISM Cfg Sig. 1.1.00"
0x020 check_sum: 2596695977
0x024 mpb_size: 480
0x028 family_num: 380654972
0x02c generation_num: 246092
0x030 reserved[0]: 4080
0x034 reserved[1]: 3221225472
0x038 num_disks: 2
0x039 num_raid_devs: 1
0x03a fill[0]: 2
0x03b fill[1]: 0
0x0d8 disk[0].serial: " 6RT039QQ"
0x0e8 disk[0].totalBlocks: 488397168
0x0ec disk[0].scsiId: 0x0
0x0f0 disk[0].status: 0x53a
0x108 disk[1].serial: " 6RT039T1"
0x118 disk[1].totalBlocks: 488397168
0x11c disk[1].scsiId: 0x10000
0x120 disk[1].status: 0x53a
0x138 isw_dev[0].volume: " Volume0"
0x14c isw_dev[0].SizeHigh: 0
0x148 isw_dev[0].SizeLow: 488390656
0x150 isw_dev[0].status: 0x8c
0x154 isw_dev[0].reserved_blocks: 0
0x158 isw_dev[0].filler[0]: 65536
0x188 isw_dev[0].vol.reserved[0]: 953888
0x190 isw_dev[0].vol.migr_state: 0
0x191 isw_dev[0].vol.migr_type: 2
0x192 isw_dev[0].vol.dirty: 0
0x193 isw_dev[0].vol.fill[0]: 255
0x194 isw_dev[0].vol.filler[0]: 22
0x1a8 isw_dev[0].vol.map.pba_of_lba0: 0
0x1ac isw_dev[0].vol.map.blocks_per_member: 488390656
0x1b0 isw_dev[0].vol.map.num_data_stripes: 1907776
0x1b4 isw_dev[0].vol.map.blocks_per_strip: 128
0x1b6 isw_dev[0].vol.map.map_state: 0
0x1b7 isw_dev[0].vol.map.raid_level: 1
0x1b8 isw_dev[0].vol.map.num_members: 2
0x1b9 isw_dev[0].vol.map.reserved[0]: 2
0x1ba isw_dev[0].vol.map.reserved[1]: 255
0x1bb isw_dev[0].vol.map.reserved[2]: 1
0x1d8 isw_dev[0].vol.map.disk_ord_tbl[0]: 0x0
0x1dc isw_dev[0].vol.map.disk_ord_tbl[1]: 0x1

/dev/sdb (isw):
0x000 sig: " Intel Raid ISM Cfg Sig. 1.1.00"
0x020 check_sum: 2596695977
0x024 mpb_size: 480
0x028 family_num: 380654972
0x02c generation_num: 246092
0x030 reserved[0]: 4080
0x034 reserved[1]: 3221225472
0x038 num_disks: 2
0x039 num_raid_devs: 1
0x03a fill[0]: 2
0x03b fill[1]: 0
0x0d8 disk[0].serial: " 6RT039QQ"
0x0e8 disk[0].totalBlocks: 488397168
0x0ec disk[0].scsiId: 0x0
0x0f0 disk[0].status: 0x53a
0x108 disk[1].serial: " 6RT039T1"
0x118 disk[1].totalBlocks: 488397168
0x11c disk[1].scsiId: 0x10000
0x120 disk[1].status: 0x53a
0x138 isw_dev[0].volume: " Volume0"
0x14c isw_dev[0].SizeHigh: 0
0x148 isw_dev[0].SizeLow: 488390656
0x150 isw_dev[0].status: 0x8c
0x154 isw_dev[0].reserved_blocks: 0
0x158 isw_dev[0].filler[0]: 65536
0x188 isw_dev[0].vol.reserved[0]: 953888
0x190 isw_dev[0].vol.migr_state: 0
0x191 isw_dev[0].vol.migr_type: 2
0x192 isw_dev[0].vol.dirty: 0
0x193 isw_dev[0].vol.fill[0]: 255
0x194 isw_dev[0].vol.filler[0]: 22
0x1a8 isw_dev[0].vol.map.pba_of_lba0: 0
0x1ac isw_dev[0].vol.map.blocks_per_member: 488390656
0x1b0 isw_dev[0].vol.map.num_data_stripes: 1907776
0x1b4 isw_dev[0].vol.map.blocks_per_strip: 128
0x1b6 isw_dev[0].vol.map.map_state: 0
0x1b7 isw_dev[0].vol.map.raid_level: 1
0x1b8 isw_dev[0].vol.map.num_members: 2
0x1b9 isw_dev[0].vol.map.reserved[0]: 2
0x1ba isw_dev[0].vol.map.reserved[1]: 255
0x1bb isw_dev[0].vol.map.reserved[2]: 1
0x1d8 isw_dev[0].vol.map.disk_ord_tbl[0]: 0x0
0x1dc isw_dev[0].vol.map.disk_ord_tbl[1]: 0x1

Revision history for this message
Phillip Susi (psusi) wrote :

Is it just the partitions that fail to appear, or is /dev/mapper/isw_diagfejhc_Volume0 missing as well?

Revision history for this message
Fonso (fonsocm) wrote :

/dev/mapper/isw_diagfejhc_Volume0 is missing. In /dev/mapper only there is a file "control".

Revision history for this message
Fonso (fonsocm) wrote :

I am the same problem with Final Gutsy amd64 Desktop in other computer with the same motherboard and RAID the before.

This time I didn't make an update from Feisty, I used the CD with Final Gutsy Desktop amd64 directly. And when I am in the live session after install dmraid, the problem is the same. Gutsy also detect a bluetooth keyboard and mouse.

Revision history for this message
Phillip Susi (psusi) wrote :

If this is still an issue, please update the report if anything has changed, or if you still get the same results, post the output of dmesg after running dmraid -ay.

Changed in dmraid:
status: New → Incomplete
Revision history for this message
Fonso (fonsocm) wrote :

In Ubuntu 8.04 x86_64, it looks to have the same problem, I execute the next command dmraid -tay -vvvv -dddd -f isw, the result is:

NOTICE: checking format identifier isw
WARN: locking /var/lock/dmraid/.lock
NOTICE: /dev/sdb: isw discovering
NOTICE: /dev/sdb: isw metadata discovered
NOTICE: /dev/sda: isw discovering
NOTICE: /dev/sda: isw metadata discovered
DEBUG: _find_set: searching isw_ebjhhbejgc
DEBUG: _find_set: not found isw_ebjhhbejgc
DEBUG: _find_set: searching isw_ebjhhbejgc_Volume0
DEBUG: _find_set: searching isw_ebjhhbejgc_Volume0
DEBUG: _find_set: not found isw_ebjhhbejgc_Volume0
DEBUG: _find_set: not found isw_ebjhhbejgc_Volume0
NOTICE: added /dev/sdb to RAID set "isw_ebjhhbejgc"
DEBUG: _find_set: searching isw_ebjhhbejgc
DEBUG: _find_set: found isw_ebjhhbejgc
DEBUG: _find_set: searching isw_ebjhhbejgc_Volume0
DEBUG: _find_set: searching isw_ebjhhbejgc_Volume0
DEBUG: _find_set: found isw_ebjhhbejgc_Volume0
DEBUG: _find_set: found isw_ebjhhbejgc_Volume0
NOTICE: added /dev/sda to RAID set "isw_ebjhhbejgc"
DEBUG: checking isw device "/dev/sda"
DEBUG: checking isw device "/dev/sdb"
DEBUG: set status of set "isw_ebjhhbejgc_Volume0" to 16
DEBUG: set status of set "isw_ebjhhbejgc" to 16
isw_ebjhhbejgc_Volume0: 0 488390656 mirror core 2 131072 nosync 2 /dev/sda 0 /dev/sdb 0
INFO: Activating GROUP RAID set "isw_ebjhhbejgc"
WARN: unlocking /var/lock/dmraid/.lock
DEBUG: freeing devices of RAID set "isw_ebjhhbejgc_Volume0"
DEBUG: freeing device "isw_ebjhhbejgc_Volume0", path "/dev/sda"
DEBUG: freeing device "isw_ebjhhbejgc_Volume0", path "/dev/sdb"
DEBUG: freeing devices of RAID set "isw_ebjhhbejgc"
DEBUG: freeing device "isw_ebjhhbejgc", path "/dev/sda"
DEBUG: freeing device "isw_ebjhhbejgc", path "/dev/sdb"

In OpenSuSE 11 x86_64, dmraid works without problem.

Revision history for this message
Phillip Susi (psusi) wrote :

The -t tells dmraid not to activate the set, but to only pretend like it would. You need to omit the -t to actually activate the set.

Revision history for this message
Fonso (fonsocm) wrote :

I used -t to get the inform because it was recommended in other thread.

I used to open the raid: dmraid -ay

Revision history for this message
Phillip Susi (psusi) wrote :

Can you post the output of dmraid -ay -dddd -vvvv, and then after you do that, the output of dmesg | tail.

Revision history for this message
Fonso (fonsocm) wrote :

The output of dmraid -ay -dddd -vvvv is:

NOTICE: creating directory /var/lock/dmraid
WARN: locking /var/lock/dmraid/.lock
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
NOTICE: /dev/sdb: isw metadata discovered
NOTICE: /dev/sdb: jmicron discovering
NOTICE: /dev/sdb: lsi discovering
NOTICE: /dev/sdb: nvidia discovering
NOTICE: /dev/sdb: pdc discovering
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
NOTICE: /dev/sda: isw metadata discovered
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
DEBUG: _find_set: searching isw_ebjhhbejgc
DEBUG: _find_set: not found isw_ebjhhbejgc
DEBUG: _find_set: searching isw_ebjhhbejgc_Volume0
DEBUG: _find_set: searching isw_ebjhhbejgc_Volume0
DEBUG: _find_set: not found isw_ebjhhbejgc_Volume0
DEBUG: _find_set: not found isw_ebjhhbejgc_Volume0
NOTICE: added /dev/sdb to RAID set "isw_ebjhhbejgc"
DEBUG: _find_set: searching isw_ebjhhbejgc
DEBUG: _find_set: found isw_ebjhhbejgc
DEBUG: _find_set: searching isw_ebjhhbejgc_Volume0
DEBUG: _find_set: searching isw_ebjhhbejgc_Volume0
DEBUG: _find_set: found isw_ebjhhbejgc_Volume0
DEBUG: _find_set: found isw_ebjhhbejgc_Volume0
NOTICE: added /dev/sda to RAID set "isw_ebjhhbejgc"
DEBUG: checking isw device "/dev/sda"
DEBUG: checking isw device "/dev/sdb"
DEBUG: set status of set "isw_ebjhhbejgc_Volume0" to 16
DEBUG: set status of set "isw_ebjhhbejgc" to 16
INFO: Activating GROUP RAID set "isw_ebjhhbejgc"
WARN: unlocking /var/lock/dmraid/.lock
DEBUG: freeing devices of RAID set "isw_ebjhhbejgc_Volume0"
DEBUG: freeing device "isw_ebjhhbejgc_Volume0", path "/dev/sda"
DEBUG: freeing device "isw_ebjhhbejgc_Volume0", path "/dev/sdb"
DEBUG: freeing devices of RAID set "isw_ebjhhbejgc"
DEBUG: freeing device "isw_ebjhhbejgc", path "/dev/sda"
DEBUG: freeing device "isw_ebjhhbejgc", path "/dev/sdb"

The output of dmesg | tail is:

[ 327.632940] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Half Duplex, Flow Control: None
[ 327.632945] e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO
[ 327.636403] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 338.249339] eth0: no IPv6 routers present
[ 439.400363] device-mapper: uevent: version 1.0.3
[ 439.400393] device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: <email address hidden>
[ 439.921405] device-mapper: table: 254:0: mirror: Device lookup failure
[ 439.921410] device-mapper: ioctl: error adding target to table
[ 580.990088] device-mapper: table: 254:0: mirror: Device lookup failure
[ 580.990094] device-mapper: ioctl: error adding target to table

PD: In Fedora 9 x86_64, the raid (it is a fake RAID 1) is also detected without problems.

Revision history for this message
Phillip Susi (psusi) wrote :

Try running modprobe dm-mirror before dmraid.

Revision history for this message
Fonso (fonsocm) wrote :
Download full text (3.8 KiB)

> Try running modprobe dm-mirror before dmraid.

It doesn't work and it is loaded in memory, if I make lsmod after that command, it shows:

Module Size Used by
dm_mirror 26368 0
dm_mod 71160 1 dm_mirror
ipv6 311848 14
af_packet 27272 0
rfcomm 47392 2
l2cap 28800 13 rfcomm
bluetooth 67748 4 rfcomm,l2cap
ppdev 11400 0
lp 14916 0
acpi_cpufreq 10832 0
cpufreq_userspace 6180 0
cpufreq_stats 8416 0
cpufreq_powersave 3200 0
cpufreq_ondemand 11152 2
freq_table 6464 3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand
cpufreq_conservative 10632 0
video 23444 0
output 5632 1 video
sbs 17808 0
sbshc 8960 1 sbs
container 6656 0
dock 12960 0
ac 8328 0
iptable_filter 4608 0
ip_tables 24104 1 iptable_filter
x_tables 23560 1 ip_tables
snd_hda_intel 440408 3
snd_pcm_oss 47648 0
snd_mixer_oss 20224 1 snd_pcm_oss
snd_pcm 92168 2 snd_hda_intel,snd_pcm_oss
snd_page_alloc 13200 2 snd_hda_intel,snd_pcm
snd_hwdep 12552 1 snd_hda_intel
snd_seq_dummy 5764 0
snd_seq_oss 38912 0
snd_seq_midi 10688 0
snd_rawmidi 29856 1 snd_seq_midi
snd_seq_midi_event 10112 2 snd_seq_oss,snd_seq_midi
snd_seq 63232 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 27912 2 snd_pcm,snd_seq
i2c_core 28544 0
snd_seq_device 10644 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
parport_pc 41128 1
snd 70856 17 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
iTCO_wdt 15312 0
intel_agp 30624 0
shpchp 38172 0
evdev 14976 3
button 10912 0
iTCO_vendor_support 5764 1 iTCO_wdt
parport 44300 3 ppdev,lp,parport_pc
pci_hotplug 34608 1 shpchp
soundcore 10400 1 snd
pcspkr 4992 0
heci 65944 0
battery 16776 0
squashfs 46352 1
loop 21508 2
unionfs 87264 1
nls_cp437 8320 1
isofs 39464 1
ext3 149264 0
jbd 57000 1 ext3
mbcache 11392 1 ext3
sr_mod 20132 1
cdrom 41512 1 sr_mod
usbhid 35296 0
hid 44992 1 usbhid
pata_marvell 9472 1
sg 41880 0
sd_mod 33280 4
pata_acpi 9856 0
ohci1394 36532 0
ieee1394 106968 1 ohci1394
floppy 69096 0
ahci 33028 2
ata_generic ...

Read more...

Revision history for this message
RalphThesen (redimp-t3m4) wrote :

i had the same problem. i solved it with turning swap off. found here: http://ubuntuforums.org/showthread.php?p=5174091

Revision history for this message
Phillip Susi (psusi) wrote :

I think this is the same issue in bug #292302. Try the suggested solution there of using the older package and if that works, I'll mark this as a duplicate.

Revision history for this message
Kyle Jones (mutiny32) wrote :

Expired, several versions of dmraid have since been released, assumed resolved unless original bug reporter responds.

Changed in dmraid:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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