Comment 5 for bug 1657659

First of all, I couldn't reproduce that bug on any systems I've got control over.

Log analysis tells us that the removable_storage_watcher script didn't see any insertion of a drive satifsying following requirements: {'block-fs', 'non-empty', 'mounted', 'partition'}.

SUT detected the whole drive (/dev/sdc) as a file system mounting it to a mount point. This made udisks2 not report that as a 'partition', thus ignoring the drive.

When USB stick got inserted SUT tried mounted the whole drive (sdc) to the mount point, which made the 'partition' predicate fail. On another try, it detected sdc1 as a NTFS partition, but did not mount it, making 'mounted' predicate fail.

When Pierre tested removable_storage_watcher with different USB-stick, the SUT properly detected it.

I tried reproducing the bug on very slow machines to see if there's a race condition problem, but no luck.

My conclusion is that the drive could have had its partition table completely messed up making this bug happen.

For pathology purposes, the USB that failed: SanDisk_Ultra_USB_3_2e0_4C530001070610102232 Label: "EE@SanDisk".

@gavin, @erin
Could you try running that test with a fresh drive (that's proven to work preferably) on 201701-25329?

The quickest way should be
$ checkbox-cli run 2013.com.canonical.certification::usb3/insert