[Bug 223011] Re: Partition not mounted after Gutsy to Hardy upgrade

dino99 223011 at bugs.launchpad.net
Tue Jan 17 13:56:04 UTC 2012


** Changed in: update-manager (Ubuntu)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/223011

Title:
  Partition not mounted after Gutsy to Hardy upgrade

Status in “update-manager” package in Ubuntu:
  Invalid

Bug description:
  STEPS TO REPRODUCE:
  1. Initial configuration: Intel 32-bit machine with up-to-date Gutsy.
  2. Upgrade to Hardy release (no alphas, betas or release candidates installed).
  3, Check mounted volumes.

  EXPECTED OUTCOME:
  Two volumes mounted, as in Gutsy.

  ACTUAL OUTCOME:
  a. NTFS partition mounted.
  b. VFAT  partition not mounted.

  ADDITIONAL INFORMATION:
  After the upgrade /etc/fstab was as follows:

      # /etc/fstab: static file system information.
      #
      # <file system> <mount point>   <type>  <options>       <dump>  <pass>
      proc            /proc           proc    defaults        0       0
      # /dev/hda3 -- converted during upgrade to edgy
      UUID=e891ea48-fa1b-456c-b5a2-1a0a1f00aaa3 / ext3 defaults,errors=remount-ro 0 1
      # /dev/hda1 -- converted during upgrade to edgy
      UUID=B0042B18042AE158 /media/hda1 ntfs defaults,nls=utf8,umask=007,gid=46 0 2
      # /dev/hda2 -- converted during upgrade to edgy
      UUID=95d7c42e-de7c-4832-a220-87cafdeeacae none swap sw 0 0
      /dev/hda4       /media/hda4     vfat    defaults,umask=007,gid=46       0       2
      /dev/cdrom        /media/cdrom0   udf,iso9660 user,noauto     0       0

  The machine on which I am experiencing this problem has gone through a
  number of upgrades (from Dapper all the way to Hardy without
  installing). As you can see, most /dev/hd* entries got converted to
  UUID-style entries when upgrading to Edgy.  All, expect hda4.

  KNOWN WORKAROUND:
  Manually editing /etc/fstab and changing /dev/hda4 into /dev/sda4 solves the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/223011/+subscriptions




More information about the foundations-bugs mailing list