Bug 11869 - non-permanent media added to /etc/fstab on first boot after install
Summary: non-permanent media added to /etc/fstab on first boot after install
Status: RESOLVED DUPLICATE of bug 12631
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-04 04:01 CET by Pierre Fortin
Modified: 2014-05-31 10:08 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Pierre Fortin 2013-12-04 04:01:57 CET
Description of problem: (selected x86_64; but probably should be all)

See bug 11820 comment 8 for more background. 
Installed mga4 using unetbootin created UDB stick as sdc1 and local repo on external HD sdd2.

On reboot, in order to access boot.iso on USB stick requires BIOS F12 and manual selection of USB to boot; repo files on external non-bootable HD. 

Unlike when using a CD/DVD to boot into installation, neither of these media get invoked on reboot after installation, so they were not removed.  However, /etc/fstab gets entries auto-created for these external devices. That shouldn't be a problem; but the system will not boot up if those drives are removed.

Shouldn't partitions other than /, /usr, /home [1] be marked noauto to prevent boot failures? 

[1] and any other partition (such as /var, /bin,...)normally used by the basic system if on separate partitions.


Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:
1. boot up with non-permanent media connected
2. remove that media
3. reboot fails and goes into emergency mode


Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2014-05-31 10:08:25 CEST
use one

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

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


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