Ubuntu
ubiquity package

desktop install does not install fstab, causing boot failure

Bug #257580 reported by Martin Pitt
6
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
Critical
Colin Watson
Ubuntu intrepid-alpha-4
Intrepid
Fix Released
Critical
Colin Watson
Ubuntu intrepid-alpha-4

Bug Description

Binary package hint: ubiquity

With the current 20080813 desktop CDs, ubiquity does not create an fstab (/etc/fstab in the installed system just has "#UNCONFIGURED FSTAB FOR BASE SYSTEM"). This causes grub-installer to fail later on:

   grub-installer: Cannot determine root device. Assuming /dev/hda1
   grub-installer: This error is probably caused by an invalid /etc/fstab

and thus the booting fails.

Tags: iso-testing

Related branches

lp:ubuntu/lucid/ubiquity
Revision history for this message
Martin Pitt (pitti) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

The alternate CD works, it creates a proper fstab and grub-installer does its job.

Both installs (deskop and alternate) were done with standard options and "use entire disk".

Changed in ubiquity:
importance: Undecided → Critical
Revision history for this message
Ara Pulido (ara) wrote :

This is happening also in Kubuntu desktop CDs

Changed in ubiquity:
status: New → Confirmed
Revision history for this message
Martin Pitt (pitti) wrote :

Colin, can you please have a look or delegate to Evan as appropriate?

Changed in ubiquity:
assignee: nobody → kamion
milestone: none → intrepid-alpha-5
Revision history for this message
Martin Pitt (pitti) wrote :

I ran the install again in debugging mode (will attach logs in a minute), but there is not a single mention of partman-target in /var/log/partman. finish.d/ doesn't even seem to run. However, since I have no clue how the log is supposed to look like, this is all just speculation.

Revision history for this message
Martin Pitt (pitti) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Apparently this is caused by http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/revision/2753, so that the squashfs'es /etc/fstab overwrites the one which gets created in /target/.

According to Mario, this is the only file we create prior to copying, thus we special-case fstab for alpha-4.

Revision history for this message
Martin Pitt (pitti) wrote :

Confirmed this bug on real hardware, originally I believed it was only an issue in kvm (since we got two positive test results on real iron). A4 blocker.

Changed in ubiquity:
milestone: intrepid-alpha-5 → intrepid-alpha-4
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 1.9.9

---------------
ubiquity (1.9.9) intrepid; urgency=low

  * Explicitly remove etc/fstab from the list of files to be copied over.
    It is created from partman prior to file copy, so the recent commit
    to unlink files if they exist already is remvoing it. (LP: #257580)

 -- Mario Limonciello <email address hidden> Wed, 13 Aug 2008 14:30:41 -0500

Changed in ubiquity:
status: Confirmed → Fix Released
Revision history for this message
Ara Pulido (ara) wrote :

I have tested the fix successfully under kubuntu live cd 20080813.2

Ubuntu QA Website (ubuntuqa)
tags: added: iso-testing
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.