Repro video: https://storage.cloud.google.com/chromiumos-test-logs/bugfiles/cr/883139/reprovid.webm?_ga=2.221590928.-967102564.1532641052

amistry@ - Could you take a look at this one? Thanks!

I can't repro this locally.

sdantuluri@: Can you reliably repro this? If so, please file a feedback report immediately after reproducing so I can see if there's anything in the system logs.

amistry@: On testing the scenario again, I observed that usb drive is detected, but after a noticeable delay of more than 30sec and error notifications.

Repro steps:
1. Open File manager app
2. Insert a USB drive
3. Right-click on the drive entry. Rename the usb drive and click enter.
4. Observe that the usb drive entry is removed from files app
5. After >30s, error notifications "Removable device detected. Sorry, at least one partition on your external storage device could not be mounted" and "Whoa, there. Be careful" are displayed. USB drive appears in Files app.

I am able to repro this consistently. Observed issue on scarlet device as well.

New repro video: https://storage.cloud.google.com/chromiumos-test-logs/bugfiles/cr/883147/IMG_0864.MOV?_ga=2.173694379.-967102564.1532641052

Feddback report: https://listnr.corp.google.com/report/85656838208

The post-rename mount attempt is failing:
[1673:1673:0912/110521.272929:ERROR:object_proxy.cc(615)] Failed to call method: org.chromium.CrosDisks.Mount: object_path= /org/chromium/CrosDisks: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

cros-disks:
2018-09-12T11:04:45.942701-07:00 NOTICE kernel: [   60.532540] scsi 0:0:0:0: Direct-Access              Patriot Memory   PMAP PQ: 0 ANSI: 6
2018-09-12T11:04:46.386654-07:00 NOTICE kernel: [   60.976479] sd 0:0:0:0: [sda] 15466496 512-byte logical blocks: (7.92 GB/7.38 GiB)
2018-09-12T11:04:46.387606-07:00 NOTICE kernel: [   60.977872] sd 0:0:0:0: [sda] Write Protect is off
2018-09-12T11:04:46.387628-07:00 DEBUG kernel: [   60.977896] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
2018-09-12T11:04:46.389610-07:00 ERR kernel: [   60.979255] sd 0:0:0:0: [sda] No Caching mode page found
2018-09-12T11:04:46.389663-07:00 ERR kernel: [   60.979272] sd 0:0:0:0: [sda] Assuming drive cache: write through
2018-09-12T11:04:46.403686-07:00 INFO kernel: [   60.993704]  sda: sda1
2018-09-12T11:04:46.408628-07:00 NOTICE kernel: [   60.998438] sd 0:0:0:0: [sda] Attached SCSI removable disk
2018-09-12T11:04:55.687511-07:00 WARNING dosfslabel[3639]: libminijail[3639]: ioctl(SIOCSIFFLAGS) failed: Operation not permitted
2018-09-12T11:05:27.288796-07:00 INFO kernel: [  101.878688] usb 5-1: reset high-speed USB device number 2 using xhci-hcd
2018-09-12T11:05:27.407751-07:00 INFO kernel: [  101.997420] sda: detected capacity change from 7918845952 to 0
2018-09-12T11:05:27.411617-07:00 NOTICE kernel: [  102.001141] sd 0:0:0:0: [sda] 15466496 512-byte logical blocks: (7.92 GB/7.38 GiB)
2018-09-12T11:05:27.412626-07:00 ERR kernel: [  102.002529] udevd[3641]: inotify_add_watch(9, /dev/sda1, 10) failed: No such file or directory
2018-09-12T11:05:27.419593-07:00 INFO kernel: [  102.009823] sda: detected capacity change from 0 to 7918845952
2018-09-12T11:05:27.433654-07:00 INFO kernel: [  102.023404]  sda: sda1
2018-09-12T11:05:27.609674-07:00 ERR disks[2139]: Failed to determine the file system type of device '/sys/devices/platform/usb@fe900000/fe900000.dwc3/xhci-hcd.2.auto/usb5/5-1/5-1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1'
2018-09-12T11:05:27.609719-07:00 ERR disks[2139]: Failed to mount '/sys/devices/platform/usb@fe900000/fe900000.dwc3/xhci-hcd.2.auto/usb5/5-1/5-1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1'

What's interesting is that at 11:05:27, the USB device is reset. Assuming time stamps are reasonably consistent, it's happening as an effect of being unable to access/mount the device. Histograms list 2 success, and one "unknown filesystem" mount signals.

sdantuluri@ Can you try a different USB drive on the same device? Did you use the same USB drive on both the kevin and scarlet?

amistry@ Yes. I used the same USB drive on both kevin and scarlet.

I tried with another USB drive now and not able to reproduce the issue.

-RBS because I suspect this is a flaky USB drive, not a systemic problem. That said, leaving this open so I can investigate some more.

Having seen some of the same symptoms myself with a bad SD card, I'm very inclined to believe this is a bad USB stick. Unless there's evidence otherwise, I'm closing this.