Comment 0 for bug 1622313

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)