Bug 4449 - at end of install all LVM partitions fail -> Grub fail, no mga boot alternative
Summary: at end of install all LVM partitions fail -> Grub fail, no mga boot alternative
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-02-08 23:39 CET by Morgan Leijström
Modified: 2012-08-04 14:14 CEST (History)
2 users (show)

See Also:
Source RPM: drakx-installer-stage2
CVE:
Status comment:


Attachments
report.bug.gz as per request (124.60 KB, application/x-gzip)
2012-02-11 14:49 CET, Morgan Leijström
Details
Screenshot for comment 1 (125.30 KB, image/jpeg)
2012-02-14 23:22 CET, Morgan Leijström
Details
Screenshot for comment #2 sda9 set by gparted worked (77.41 KB, image/jpeg)
2012-02-14 23:24 CET, Morgan Leijström
Details
Screenshot at text terminal at end of install before reboot (195.66 KB, image/jpeg)
2012-02-14 23:36 CET, Morgan Leijström
Details

Description Morgan Leijström 2012-02-08 23:39:48 CET
Description of problem:

During install later phases configuring video etc, i Ctrl-AltFx switch between terminals and see it failed mounting all LVM logical volumes, thus also grub failed.
(after next boot only grub alternative was Windows which luckily works)

For details of partitioning used, see https://bugs.mageia.org/show_bug.cgi?id=4442

__Comments

Is this problem with drakx, kernel or disk driver module?

I guess the bug 4442 is related.

This is an old Thinkpad T40 laptop, IDE PATA drive.

This install was made by boot.iso network based cauldron

mga 1 installer works perfectly - tried it this morning only to verify installable and boot to LXDE desktop.

mga 2 alpha 3 iso DVD do not even get through partitioning.



Version-Release number of selected component (if applicable):
All from network install now, my mirror syncs one or two times a day.

How reproducible:
Have only tried on this machine.
Comment 1 Morgan Leijström 2012-02-09 01:10:31 CET
Booted that machine on sysresccd.org live USB system, and issued
  vgscan
  vgchange -a y -v
and all my LVM partitions popped up in /dev/vg-mga/
vghange also said for each partition "activation/volume_list configuration not defined" but i have no idea if it is normal or what it means.

I could also mount them and see that the root partition have been populated.

I could also mount the ext4 /boot partition (which is outside LVM) and see it is populated with vmlinuz* grub folder etc.

So it installed things allright, but what happened then during final configuration??
Comment 2 Morgan Leijström 2012-02-09 02:43:21 CET
Used gparted on that same live USB system to remove the small weird lvm partition i mentionned in bug 4442.  The one i had to schrink as installer could not change its type.  Gparted removed it, but responded that it could not inform kernel about changes.
As mentionned in another bug this recent sysresccd also had various hickups on this avdenture so i dug up an old version, rebooted on that, and fixed that partition after the windows partition that mysteriously got set to swap after i formatted it to ntfs, now i set it to ext4.

Ran the boot.iso again, now in the installer i "reconnected" my partitions, and let it install again, without formatting anything.  Pretty soon it was finished and this time it managed to get grub working - i can boot cauldron!

Well things are broken, like grub is textmode and i need to select safe mode to get graphical login, and KDE miss lots of things.  But i blame that on that both this time and the last many packages were missing during install, maybe because timeout on my lousy connection, maybe changes in repo.

Now it is running update again, and I will see what i can fix.  I will come back here later.

I took photos of the screen showing partitions using gparted if you want.
Comment 3 Manuel Hiebel 2012-02-09 15:27:25 CET
Thanks for the bug report.
Could you provide the file /root/drakx/report.bug.gz as an attachment ?

Keywords: (none) => NEEDINFO

Comment 4 Morgan Leijström 2012-02-11 14:49:58 CET
Created attachment 1528 [details]
report.bug.gz as per request

Note this is after the sucessful second attempt as i described above, and a few crashes and reboots
Comment 5 Manuel Hiebel 2012-02-11 15:46:28 CET
OK thanks

Thierry, any ideas ?

Assignee: bugsquad => thierry.vignaud
Source RPM: (none) => drakx-installer-stage2

Manuel Hiebel 2012-02-11 15:52:12 CET

Keywords: NEEDINFO => (none)

Comment 6 Morgan Leijström 2012-02-12 09:53:50 CET
I used network install, and have a lousy connection.
Thought: During network install, is the *.sqfs checksummed?

It seems I did have problems during fetching it:
https://bugs.mageia.org/show_bug.cgi?id=4440#c8
Comment 7 Thierry Vignaud 2012-02-13 10:58:54 CET
No but if it was corrupted, the kernel should have issue unpacking it.
Comment 8 Morgan Leijström 2012-02-14 23:22:51 CET
Created attachment 1557 [details]
Screenshot for comment 1
Comment 9 Morgan Leijström 2012-02-14 23:24:27 CET
Created attachment 1558 [details]
Screenshot for comment #2 sda9 set by gparted worked
Comment 10 Morgan Leijström 2012-02-14 23:36:39 CET
Created attachment 1559 [details]
Screenshot at text terminal at end of install before reboot

It took me until now when i emptied my camera, that i saw the error message at top of this screen:

Entering step `Configure X'
error: Too many levels of recursion in macro expansion.

Should we file another bug for that? On what?


Near bottom we see it complains on LVM partitions that all partition tables are borked.
But reboot worked, and i could update it, and uninstall/reinstall grub graphic used mcc boot tool and now the install is completely working (minus shutdown and sound bugs)
Dan Joita 2012-03-07 11:21:59 CET

CC: (none) => djmarian4u
Summary: At end of install all LVM partitions fail -> Grub fail, no mga boot alternative => at end of install all LVM partitions fail -> Grub fail, no mga boot alternative

Comment 11 Marja Van Waes 2012-05-26 13:02:43 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 12 Marja Van Waes 2012-07-06 15:03:59 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 13 Marja Van Waes 2012-08-04 13:53:06 CEST
2x no reply, closing as old.

Feel free to reopen when needed and tell when this bug was still valid for Mageia 2 final

In that case, please put (MGA2) on the whiteboard and attach a new
/root/drakx/report.bug.gz

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD

Comment 14 Morgan Leijström 2012-08-04 14:14:37 CEST
Probably something very special with how that disk was configured before, or some odd hardware bug interfering rarely.  Let it rest.
Also see https://bugs.mageia.org/show_bug.cgi?id=4442#c14

Note You need to log in before you can comment on or make changes to this bug.