Bug 4902

Summary: NVRAID array not detectable on boot or after updates
Product: Mageia Reporter: Greg McGee <gjmcgee>
Component: InstallerAssignee: Thierry Vignaud <thierry.vignaud>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Normal CC: mageia, mageia, marja11, pterjan, tmb
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: /root/drakx installer log dir
report.bug.gz for raid seen as corrupt drives on NVRAID system

Description Greg McGee 2012-03-12 14:52:29 CET
Description of problem:
Prexisting NVRAID RAID 1 array not detectable by installer or after install/reboot and update. dmraid found not installed on system.
Works with Windows and Mageia1 fine. (multiboot system)

Version-Release number of selected component (if applicable):
X86-64 install from DVD, Mageia2 beta1

How reproducible:
Reinstall, same results.


Steps to Reproduce:
1.Boot/install from DVD
2.Installer cannot parse the array, asks if you want to reformat the drive (ugh)
3.install dmraid later after reboot and mount partition?

The rescue system has dmraid, but the installed image appears to be missing the RPM.(?) 

I did not attempt a third reinstall to see if I could go to runlevel1, load DMRAID/array before running the installer, that's unacceptable for most folks anyway.
Comment 1 Greg McGee 2012-03-12 14:53:59 CET
Similar but not same as Intel RAID not detected issue with missing mdadm bug.
Manuel Hiebel 2012-03-12 18:16:23 CET

CC: (none) => mageia, mageia, pterjan, tmb
Assignee: bugsquad => thierry.vignaud

Comment 2 Pascal Terjan 2012-03-12 18:20:42 CET
If the installer does not detect it, it is normal that the package does not get installed.
Do you still have the installer logs (in /root/drakx/)?
Comment 3 Greg McGee 2012-03-12 22:42:31 CET
Created attachment 1743 [details]
/root/drakx installer log dir

drakx installer logs
Comment 4 Greg McGee 2012-03-12 22:43:58 CET
"If the installer does not detect it, it is normal that the package does not get
installed.
Do you still have the installer logs (in /root/drakx/)?"

Certainly, tar.bz2 of the /root/draks dir attached.
Comment 5 Pascal Terjan 2012-03-12 23:00:15 CET
* running: /sbin/insmod /tmp/dm_mod.ko
* running: /sbin/insmod /tmp/dm_log.ko
* running: /sbin/insmod /tmp/dm_region_hash.ko
* running: /sbin/insmod /tmp/dm_mirror.ko
* running: /sbin/insmod /tmp/dm_zero.ko
* running: dmraid -ay
* running: dmraid -s -c -c
* _raid_devices_raw
* running: dmraid -d -s -c -c
* running: dmraid -r -c -c
* dmraid: 
* using dmraid on 

So, it seems that dmraid run from the installer did not detect anything :(
Between each of the command, we should get the output of it, so it means the dmraid commands did not display anything.
Comment 6 Thierry Vignaud 2012-03-13 08:40:31 CET
Maybe are we missing a dmraid patch from RH?
Does Fedora works on that machine? What's used with FC? dmraid?

Keywords: (none) => NEEDINFO

Comment 7 Greg McGee 2012-03-13 13:27:03 CET
dmraid from the installed/updated distro worked fine (once installed), will try the version in the rescue image now.
Currently about to reboot anyway due to a urpmi update fail that just occurred, says it cant open the database after the updates a moment ago, but I digress...
Comment 8 Greg McGee 2012-03-13 14:13:51 CET
Reran the installer this time it could SEE the array, but could not activate it, complained about corrupt partition table.
(same for the rescue image, the array is listed but dmraid -ay rails to activate it)

same version of dmraid as installed/working, perhaps not dmraid itself, the device mapper and some other things have to cooperate IIRC.

OT again, Trying to track down db4_recover setup, it looks like the libs are not even installed for db4, probably part of an update borked.
Comment 9 Greg McGee 2012-03-13 14:14:24 CET
dmraid 1.0.0.0 rc16, btw.
Comment 10 Marja Van Waes 2012-04-02 10:44:15 CEST
(In reply to comment #8)
> Reran the installer this time it could SEE the array, but could not activate
> it, complained about corrupt partition table.
> (same for the rescue image, the array is listed but dmraid -ay rails to
> activate it)
> 
> same version of dmraid as installed/working, perhaps not dmraid itself, the
> device mapper and some other things have to cooperate IIRC.
> 
> OT again, Trying to track down db4_recover setup, it looks like the libs are
> not even installed for db4, probably part of an update borked.

(In reply to comment #9)
> dmraid 1.0.0.0 rc16, btw.

Can you please attach /root/drakx/report.bug.gz from this install (where the array was seen, but DrakX thought the partition table was corrupt), too?

CC: (none) => marja11

Comment 11 Greg McGee 2012-04-02 15:17:44 CEST
Created attachment 1903 [details]
report.bug.gz for raid seen as corrupt drives on NVRAID system

report.bug.gz by itself by request. Later brought up RAID manually.
Marja Van Waes 2012-04-21 19:44:46 CEST

Keywords: NEEDINFO => (none)

Comment 12 Thierry Vignaud 2012-04-21 22:52:56 CEST
Can you try latest boot.iso (eg from http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/install/images/boot.iso) and perform a net install?
(so that it uses the latest stage2, eg from http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/install/stage2/)

I think this is the same issue I fixed for soft RAID a couple days ago, now that we have udev in the installer, it tries to setup RAID early but proper modules were not loaded and thus RAID array is inactive.
I've fixed this but too late for beta3
Thierry Vignaud 2012-04-21 22:53:02 CEST

Keywords: (none) => NEEDINFO

Comment 13 Greg McGee 2012-04-22 01:38:05 CEST
I'll give it a shot this evening.
Comment 14 Marja Van Waes 2012-05-09 15:11:37 CEST
@ Greg

You can also test with rc instead of with boot.iso now

http://blog.mageia.org/en/2012/05/09/almost-there-download-mageia-2-rc-new-date-for-final-release/

Please tell us whether the problem got solved
Comment 15 Greg McGee 2012-05-10 04:41:22 CEST
Tried with the x64 RC in both livecd and install modes.
Picked up the RAID just fine either way, so consider this fixed.

clocksource=jiffies still needs to be the default (as it does not hurt anything) but that is another issue.
Comment 16 Thierry Vignaud 2012-05-10 08:48:23 CEST
CLosing then

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 17 Greg McGee 2012-05-10 10:52:46 CEST
Thank you!