[Bug 450221] New: DMRAID refuses to activate SATA RAID sets
https://bugzilla.novell.com/show_bug.cgi?id=450221 Summary: DMRAID refuses to activate SATA RAID sets Product: openSUSE 11.1 Version: RC 1 Platform: i686 OS/Version: Windows XP Status: NEW Severity: Blocker Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: lasse.penttinen@gmail.com QAContact: qa@suse.de Found By: Community User DMRAID has been tested to work on this PC using: Ubuntu 8.10 (and many older versions), PCLinuxOS 2008 Mini. I have a NTFS fake RAID setup I want to mount in openSUSE. I have done this with a number of Linux distros with success, but fails in openSUSE 11.1. Note: DMRAID detects two sets of metadata as I have changed the controller at some point. This has never been a problem. linux-jm7t:/home/ljpp # dmraid -r /dev/sdg: "pdc" and "isw" formats discovered (using isw)! /dev/sdf: "pdc" and "isw" formats discovered (using isw)! /dev/sdg: isw, "isw_beicabedcj", GROUP, ok, 240121726 sectors, data@ 0 /dev/sdf: isw, "isw_beicabedcj", GROUP, ok, 240121726 sectors, data@ 0 linux-jm7t:/home/ljpp # dmraid -ay -f pdc RAID set "pdc_begabfcgj" was not activated linux-jm7t:/home/ljpp # dmraid -an /dev/sdg: "pdc" and "isw" formats discovered (using isw)! /dev/sdf: "pdc" and "isw" formats discovered (using isw)! RAID set "isw_beicabedcj_RAID" is not active linux-jm7t:/home/ljpp # dmraid -ay -f pdc RAID set "pdc_begabfcgj" was not activated linux-jm7t:/home/ljpp # ls /dev/mapper control linux-jm7t:/home/ljpp # modprobe dm-mirror linux-jm7t:/home/ljpp # dmraid -ay -f pdc RAID set "pdc_begabfcgj" was not activated If this is a widespread problem, then I would presume it might be a blocker? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450221 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |mkoenig@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450221 User mkoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450221#c1 Matthias Koenig <mkoenig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |lasse.penttinen@gmail.com --- Comment #1 from Matthias Koenig <mkoenig@novell.com> 2008-12-01 09:02:39 MST --- What's the version of dmraid that worked, for example in Ubuntu 8.10? (dmraid -V) Can you please provide the output of the dmraid activation call with maximum verbosity and debug output? dmraid -ay -vvv -d -f pdc -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450221 User lasse.penttinen@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450221#c2 --- Comment #2 from Lasse Penttinen <lasse.penttinen@gmail.com> 2008-12-01 09:15:07 MST --- 8.10 is the last Ubuntu I have used DMRAID with success. Also several older versions. openSUSE 11.1 is the first distro to have problems with this. linux-jm7t:/home/ljpp # dmraid -ay -vvv -d -f pdc NOTICE: checking format identifier pdc WARN: locking /var/lock/dmraid/.lock NOTICE: skipping removable device /dev/sdb NOTICE: skipping removable device /dev/sdc NOTICE: skipping removable device /dev/sdd NOTICE: skipping removable device /dev/sde NOTICE: /dev/sdg: pdc discovering NOTICE: /dev/sdg: pdc metadata discovered NOTICE: /dev/sdf: pdc discovering NOTICE: /dev/sdf: pdc metadata discovered NOTICE: /dev/sda: pdc discovering DEBUG: _find_set: searching pdc_begabfcgj DEBUG: _find_set: not found pdc_begabfcgj DEBUG: _find_set: searching pdc_begabfcgj DEBUG: _find_set: not found pdc_begabfcgj NOTICE: added /dev/sdg to RAID set "pdc_begabfcgj" DEBUG: _find_set: searching pdc_begabfcgj DEBUG: _find_set: found pdc_begabfcgj DEBUG: _find_set: searching pdc_begabfcgj DEBUG: _find_set: found pdc_begabfcgj NOTICE: added /dev/sdf to RAID set "pdc_begabfcgj" DEBUG: checking pdc device "/dev/sdf" DEBUG: checking pdc device "/dev/sdg" DEBUG: set status of set "pdc_begabfcgj" to 16 DEBUG: checking pdc device "/dev/sdf" DEBUG: checking pdc device "/dev/sdg" DEBUG: set status of set "pdc_begabfcgj" to 16 RAID set "pdc_begabfcgj" was not activated WARN: unlocking /var/lock/dmraid/.lock DEBUG: freeing devices of RAID set "pdc_begabfcgj" DEBUG: freeing device "pdc_begabfcgj", path "/dev/sdf" DEBUG: freeing device "pdc_begabfcgj", path "/dev/sdg" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450221 User mkoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450221#c3 --- Comment #3 from Matthias Koenig <mkoenig@novell.com> 2008-12-02 05:24:48 MST --- Could you please also attach the metadata as provided by dmraid -n -f pdc and the output of dmraid -s -ccc -f pdc -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450221 User lasse.penttinen@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450221#c4 Lasse Penttinen <lasse.penttinen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mkoenig@novell.com |bnc-team-screening@forge.provo.novell.com Status|NEEDINFO |NEW Info Provider|lasse.penttinen@gmail.com | --- Comment #4 from Lasse Penttinen <lasse.penttinen@gmail.com> 2008-12-03 06:58:28 MST --- linux-jm7t:/home/ljpp # dmraid -n -f pdc /dev/sdg (pdc): 0x000 promise_id: "Promise Technology, Inc." 0x018 unknown_0: 0x20000 131072 0x01c magic_0: 0x0 0x020 unknown_1: 0x0 0 0x024 magic_1: 0x8b40425 0x028 unknown_2: 0x0 0 0x200 raid.flags: 0x80 0x204 raid.unknown_0: 0x7 7 0x205 raid.disk_number: 1 0x206 raid.channel: 1 0x207 raid.device: 0 0x208 raid.magic_0: 0x0 0x20c raid.unknown_1: 0x0 0 0x210 raid.start: 0x0 0 0x214 raid.disk_secs: 240121665 0x218 raid.unknown_3: 0xffffffff 4294967295 0x21c raid.unknown_4: 0x4 4 0x21e raid.status: 0x8f 0x21f raid.type: 0x1 0x220 raid.total_disks: 2 0x221 raid.raid0_shift: 7 0x222 raid.raid0_disks: 1 0x223 raid.array_number: 0 0x224 raid.total_secs: 238281250 0x228 raid.cylinders: 14831 0x22a raid.heads: 254 0x22b raid.sectors: 63 0x22c raid.magic_1: 0x8b40425 0x230 raid.unknown_5: 0x0 0 0x234 raid.disk[0].unknown_0: 0x7 0x236 raid.disk[0].channel: 0 0x237 raid.disk[0].device: 0 0x238 raid.disk[0].magic_0: 0x0 0x23c raid.disk[0].disk_number: 0 0x240 raid.disk[1].unknown_0: 0x7 0x242 raid.disk[1].channel: 1 0x243 raid.disk[1].device: 0 0x244 raid.disk[1].magic_0: 0x0 0x248 raid.disk[1].disk_number: 0 0x7fc checksum: 0x5cfb123c Ok /dev/sdf (pdc): 0x000 promise_id: "Promise Technology, Inc." 0x018 unknown_0: 0x20000 131072 0x01c magic_0: 0x0 0x020 unknown_1: 0x0 0 0x024 magic_1: 0x8b40425 0x028 unknown_2: 0x0 0 0x200 raid.flags: 0x80 0x204 raid.unknown_0: 0x7 7 0x205 raid.disk_number: 0 0x206 raid.channel: 0 0x207 raid.device: 0 0x208 raid.magic_0: 0x0 0x20c raid.unknown_1: 0x0 0 0x210 raid.start: 0x0 0 0x214 raid.disk_secs: 240121665 0x218 raid.unknown_3: 0xffffffff 4294967295 0x21c raid.unknown_4: 0x4 4 0x21e raid.status: 0x8f 0x21f raid.type: 0x1 0x220 raid.total_disks: 2 0x221 raid.raid0_shift: 7 0x222 raid.raid0_disks: 1 0x223 raid.array_number: 0 0x224 raid.total_secs: 238281250 0x228 raid.cylinders: 14831 0x22a raid.heads: 254 0x22b raid.sectors: 63 0x22c raid.magic_1: 0x8b40425 0x230 raid.unknown_5: 0x0 0 0x234 raid.disk[0].unknown_0: 0x7 0x236 raid.disk[0].channel: 0 0x237 raid.disk[0].device: 0 0x238 raid.disk[0].magic_0: 0x0 0x23c raid.disk[0].disk_number: 0 0x240 raid.disk[1].unknown_0: 0x7 0x242 raid.disk[1].channel: 1 0x243 raid.disk[1].device: 0 0x244 raid.disk[1].magic_0: 0x0 0x248 raid.disk[1].disk_number: 0 0x7fc checksum: 0x5cfa113c Ok linux-jm7t:/home/ljpp # dmraid -s -ccc -f pdc pdc_begabfcgj:238281216:128:mirror:ok:0:2:0 /dev/sdf:pdc:pdc_begabfcgj:mirror:ok:238281250:0 /dev/sdg:pdc:pdc_begabfcgj:mirror:ok:238281250:0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450221 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450221#c5 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Critical Priority|P5 - None |P3 - Medium Flag| |SHIP_STOPPER- --- Comment #5 from Stephan Kulow <coolo@novell.com> 2008-12-03 07:07:29 MST --- no general problem according to Matthias -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450221 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |mkoenig@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450221 User mkoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450221#c6 Matthias Koenig <mkoenig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |lasse.penttinen@gmail.com --- Comment #6 from Matthias Koenig <mkoenig@novell.com> 2008-12-03 08:33:05 MST --- By the way, is there any reason you keep the old metadata on the disk? Although I am not really sure if this is related to your problem, I highly recommend first to remove the metadata which is not needed anymore. Since even if it is not related and has not made problems in the past, there does not exist a mechanism to hand the information which raid metadata to activate to the initrd (and you can see from your initial description that isw will be preferred). This is not really supported and if it works you might be just lucky. You can remove unwanted metadata with the -rE option. So assuming you want to activate and keep the pdc metadata, and erasing the isw metadata (please doublecheck if this is correct), the command is dmraid -rE -f isw The metadata to be removed will be backed up in the current directory (stored in a directory called dmraid.isw in this case), so in case you erased the wrong one you can restore it later, it is not completely lost. It would good to know if removing the unwanted metadata changes anything in this situation. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450221 User lasse.penttinen@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450221#c7 Lasse Penttinen <lasse.penttinen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mkoenig@novell.com |bnc-team-screening@forge.provo.novell.com Status|NEEDINFO |NEW Info Provider|lasse.penttinen@gmail.com | --- Comment #7 from Lasse Penttinen <lasse.penttinen@gmail.com> 2008-12-16 03:36:58 MST --- No spcial reason to keep the redundant ISW metadata. However, if it ain't broken then dont fix it logic works here -- the metadata has NEVER been as issue with any operating system. I wouldn't even know it was there unless DMRAID would not notify about it. And as said, this has always worked with Linux distros, the most recent and older ones, so metadata is not the root cause here. I cannot tamper with the metadata (remove it etc.) as this RAID contais a lot of important data, some of it not backed up to secondary media. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450221 User lasse.penttinen@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450221#c8 --- Comment #8 from Lasse Penttinen <lasse.penttinen@gmail.com> 2008-12-28 01:51:49 MST --- Went back to Ubuntu Intrepid Ibex as this was a real show stopper for me. As said, DMRAID works and here is the version info. Seems to be older than in openSUSE. dmraid version: 1.0.0.rc14 (2006.11.08) shared dmraid library version: 1.0.0.rc14 (2006.11.08) device-mapper version: unknown -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450221 User mkoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450221#c9 Matthias Koenig <mkoenig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkoenig@novell.com Status|NEW |NEEDINFO Info Provider| |lasse.penttinen@gmail.com --- Comment #9 from Matthias Koenig <mkoenig@novell.com> 2009-01-07 10:10:33 MST --- Uh, please don't change the assignee, otherwise the bug gets lost from my list ;-) So as 1.0.0.rc14 works, it is a regression in 1.0.0.rc15. Currently it is not clear to me why the activation fails and you might be right that it is not related to the coexisting metadata. Hard to debug on a production system with important data. Anyway, a dump of the metadata might be helpful. Sooner or later other dists will also switch to rc15 and we want to make sure the problem gets fixed somehow, or at least report it to the upstream maintainer. You can dump the metadata with dmraid -rD The data will be written to a new subdirectory dmraid.format_name. Please tar them up and attach them here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450221 Matthias Koenig <mkoenig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |mkoenig@novell.com Status|NEEDINFO |ASSIGNED Info Provider|lasse.penttinen@gmail.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450221 Matthias Koenig <mkoenig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |lasse.penttinen@gmail.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=450221 Hendrik Vogelsang <hvogel@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|lasse.penttinen@gmail.com | Resolution| |NORESPONSE -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com