Bug 9675 - Installer gets stuck in infinite loop trying to mount drive if a module is missing
Summary: Installer gets stuck in infinite loop trying to mount drive if a module is mi...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: Mageia 3
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2013-04-09 11:06 CEST by Stuart Morgan
Modified: 2014-12-01 18:44 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
Screenshot showing error (126.38 KB, image/jpeg)
2013-04-09 11:15 CEST, Stuart Morgan
Details

Description Stuart Morgan 2013-04-09 11:06:40 CEST
Description of problem:

There seems to be two distinct issues here (#1, #2). When attempting an updated from Mageia 2 to Mageia 3 beta the installer tries to mount all drives listed in /etc/fstab. It fails to mount at least one, an XFS mount (#1 no XFS driver loaded by the installer?) and throws an error - "Unable to mount /path/to/mount". The only option on the dialog is OK, clicking OK causes it to start again mounting the drives and again failing, resulting in an unbreakable loop (#2).

The only way around the issue is to edit /etc/fstab to comment out the problematic mounts and then to re-enable them after the upgrade. This obviously wouldn't work if the root/home partitions were unmountable by the installer.


Reproducible: 

Steps to Reproduce:
Comment 1 Stuart Morgan 2013-04-09 11:15:22 CEST
Created attachment 3725 [details]
Screenshot showing error
Stuart Morgan 2013-04-16 22:34:25 CEST

Priority: Normal => release_blocker
CC: (none) => smorgan
Target Milestone: --- => Mageia 3

Comment 2 Manuel Hiebel 2013-04-16 22:39:35 CEST
should be fixed since beta3

*** This bug has been marked as a duplicate of bug 9317 ***

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

Comment 3 Manuel Hiebel 2013-04-16 22:50:45 CEST
wrong bug id sorry

*** This bug has been marked as a duplicate of bug 9428 ***
Comment 4 Stuart Morgan 2013-04-16 22:51:24 CEST
Sorry, but they aren't the same bug at all. This is about the installer itself trying to mount drives in an _existing_ fstab when doing an upgrade and has nothing to do with what the installer writes into /etc/fstab

This bug prevents the installer from proceeding to the installation step and occurs very early in the upgrade process, after selecting 'Upgrade from Mageia 2' in the installer menu.

Status: RESOLVED => REOPENED
Resolution: DUPLICATE => (none)

Comment 5 Manuel Hiebel 2013-04-16 22:55:16 CEST
well as you can see in my last comment, xfs module were missing in the beta3
Comment 6 Stuart Morgan 2013-04-16 22:59:22 CEST
My reply crossed with Manuel's correction of the duplicate ID. 9428 sounds like the first part of the bug, so yes it seem reasonable to close.

I'm not sure whether the other problem is really fixed, the bit where the installer keeps attempting to mount the same drive and never gives up? I may just re-file that as a separate bug. The correct behaviour would be to warn and offer the user the chance to abort or to skip the drive and move on.
Comment 7 Manuel Hiebel 2013-04-16 23:03:39 CEST
ok so let's keep that

Priority: release_blocker => Normal
Assignee: bugsquad => thierry.vignaud
Summary: Installer gets stuck in infinite loop trying to mount drive => Installer gets stuck in infinite loop trying to mount drive if a module is missing

Comment 8 Thierry Vignaud 2013-04-17 07:52:53 CEST
xfs module is included and has always been for years so the error must be something else.
Please attach your /root/drakx/report.bug.xz

Keywords: (none) => NEEDINFO

Comment 9 Dick Gevers 2014-12-01 18:44:52 CET
Unanswered too long.

Besides, pre-5 installers will not be fixed.

Kindly reopen if seen with 5beta1 (or higher), setting header fields accordingly (and remove NEEDINFO). Thanks.

Status: REOPENED => RESOLVED
Resolution: (none) => OLD


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