[Bug 1622313] Re: gparted does not recognize the iso9660 file system in cloned Ubuntu USB boot drives

[Ian Bruntlett]

It affects me, too.

And here are some details from me...

I am running Ubuntu 16.04.1 LTS, 64-bit.

For some time I have been using Startup Disc Creator to create Lubuntu
32-bit install media (on USB flash drives).

However, today (8th September 2016), when I was attempting to create a
Lubuntu 16.04.1 LTS desktop 32-bit install USB flash drive using Startup
Disc Creator (0.3.2), it would write the iso to the flash drive OK.
Except for one thing. The flash drive is not being recognised. To quote
GPartEd, "Unable to detect file system!".

Bit more: Whilst the resulting install media can install Lubuntu OK, you
just can't look at it with a File Manager or GPartEd.

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

Title:
  gparted does not recognize the iso9660 file system in cloned Ubuntu
  USB boot drives

Status in GParted:
  Unknown
Status in gparted package in Ubuntu:
  Triaged

Bug description:
  I am testing in a live system and looking at the very drive, from
  which it is booted, the current daily iso file of Lubuntu Xenial i386
  (post 16.04.1 LTS). The problem is that the file system cannot be
  identified, and several end users may (and will) think that the USB
  boot drive is damaged. But it works, it is cloned, which is the
  straightforward method to create a boot drive from a hybrid iso file.

  this issue was worse in previous versions, where gparted would
  complain about an error; now it is at least seeing the partition. The
  next step is that it can see the file system too.

  lsblk can see it, as illustrated by the following command line (in a
  wide terminal window),

  sudo lsblk -fm

  The attached screenshot illustrates the problem, and shows that it
  affects the text mode program parted too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gparted 0.25.0-1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CasperVersion: 1.376
  CurrentDesktop: LXDE
  Date: Sun Sep 11 10:10:21 2016
  LiveMediaBuild: Lubuntu 16.04.1 LTS "Xenial Xerus" - Beta i386 (20160909)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gparted
  UpgradeStatus: No upgrade log present (probably fresh install)

  Edit:

  After some testing I found that the current i386 versions behave in a
  similar way as Xenial.

  But the current amd64 (64-bit) versions are more severely affected by
  this bug. It is much worse in Trusty, but also bad in Xenial as
  illustrated by screenshots in comments #6 and #7. This behaviour will
  really confuse new users of Ubuntu and the Ubuntu flavours.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gparted/+bug/1622313/+subscriptions