New issue
Advanced search Search tips

Issue 924153 link

Starred by 1 user
Status: Unconfirmed
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

External storage ejects without user interaction

Reported by stevendh...@gmail.com, Today (13 hours ago) 
UserAgent: Mozilla/5.0 (X11; CrOS x86_64 11316.82.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.59 Safari/537.36
Platform: 11316.82.0 (Official Build) beta-channel nami

Steps to reproduce the problem:
1. Since the latest beta when I put in an external storage (micro SD) I will get eject warnings and then the drive will be remounted.  
2. I also have some new folders being created related to android ... see attachments
3. This is on an Acer Spin 13.  When this happens my fans will engage to cool down the processor or motherboard.

What is the expected behavior?
No storage ejections.  No high speed fan engagement when sitting idle.

What went wrong?
Storage is ejecting without user interactions.  Once this happens the system will spin up the fans to cool down the system.  This happens when I am actively using the system and when it is sitting idle.

Did this work before? Yes The stock version of Chrome that came with the Acer Spin 13

Chrome version: 72.0.3626.59  Channel: beta
OS Version: 11316.82.0
Flash Version: 32.0.0.114 

If there are other logs that I should upload then let me know.
Screenshot 2019-01-22 at 08.52.55.png
38.1 KB View Download
Screenshot 2019-01-22 at 08.52.55.png
38.1 KB View Download

Comment 1 by dtapu...@chromium.org, Today (13 hours ago)

Components: Platform>Apps>FileManager

Comment 2 by slangley@google.com, Today (9 hours ago)

Labels: CrOSFilesFeature-ExternalMedia
Please also press shift-alt-i and file feedback - probably mention this bug number in the feedback.

Filing feedback will attach the relevant system logs to help us diagnose.

Thanks.

Comment 3 by stevendh...@gmail.com, Today (7 hours ago) 

I just submitted the shift-alt-i file and referenced the bug number.

Comment 4 by amistry@chromium.org, Today (6 hours ago) 

https://listnr.corp.google.com/report/85925808455

It looks like the USB connection is corrupted and so the kernel is resetting the device after seeing too many errors. It could be one of many things. If you have another card, can you try that in the device? Or try to use the same SD card in a different device.

Partial syslog:
2019-01-22T09:59:45.520827-08:00 NOTICE kernel: [ 7746.697639] scsi 3:0:0:0: Direct-Access     Generic  STORAGE DEVICE   0819 PQ: 0 ANSI: 6
2019-01-22T09:59:46.000827-08:00 NOTICE kernel: [ 7747.177591] sd 3:0:0:0: [sda] 125042688 512-byte logical blocks: (64.0 GB/59.6 GiB)
2019-01-22T09:59:46.001825-08:00 NOTICE kernel: [ 7747.178030] sd 3:0:0:0: [sda] Write Protect is off
2019-01-22T09:59:46.001835-08:00 DEBUG kernel: [ 7747.178034] sd 3:0:0:0: [sda] Mode Sense: 87 00 00 00
2019-01-22T09:59:46.001836-08:00 NOTICE kernel: [ 7747.178497] sd 3:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
2019-01-22T09:59:46.004824-08:00 INFO kernel: [ 7747.180817]  sda: sda1
2019-01-22T09:59:46.005819-08:00 NOTICE kernel: [ 7747.182549] sd 3:0:0:0: [sda] Attached SCSI removable disk
2019-01-22T09:59:46.319406-08:00 WARNING mount.exfat-fuse[15549]: libminijail[15549]: ioctl(SIOCSIFFLAGS) failed: Operation not permitted
2019-01-22T09:59:46.331700-08:00 WARNING mount.exfat-fuse[15549]: volume was not unmounted cleanly
2019-01-22T10:04:46.641836-08:00 WARNING kernel: [ 8047.822488] usb 2-4: Disable of device-initiated U1 failed.
2019-01-22T10:04:46.645831-08:00 WARNING kernel: [ 8047.826357] usb 2-4: Disable of device-initiated U2 failed.
2019-01-22T10:04:46.648833-08:00 ERR kernel: [ 8047.829768] usb 2-4: usb_reset_and_verify_device Failed to disable LTM
2019-01-22T10:04:46.648862-08:00 ERR kernel: [ 8047.829768] .
2019-01-22T10:04:46.679910-08:00 INFO kernel: [ 8047.860058] sd 3:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
2019-01-22T10:04:46.679941-08:00 INFO kernel: [ 8047.860075] sd 3:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 8d 35 20 00 00 f0 00
2019-01-22T10:04:46.679945-08:00 ERR kernel: [ 8047.860082] blk_update_request: I/O error, dev sda, sector 9254176
2019-01-22T10:04:46.709923-08:00 INFO kernel: [ 8047.890128] sd 3:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
2019-01-22T10:04:46.709952-08:00 INFO kernel: [ 8047.890145] sd 3:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 8d 36 10 00 00 10 00
2019-01-22T10:04:46.709964-08:00 ERR kernel: [ 8047.890153] blk_update_request: I/O error, dev sda, sector 9254416
2019-01-22T10:04:46.740865-08:00 INFO kernel: [ 8047.921076] sd 3:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
2019-01-22T10:04:46.740897-08:00 INFO kernel: [ 8047.921093] sd 3:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 8d 36 20 00 00 f0 00
2019-01-22T10:04:46.740901-08:00 ERR kernel: [ 8047.921101] blk_update_request: I/O error, dev sda, sector 9254432
2019-01-22T10:04:46.771864-08:00 INFO kernel: [ 8047.952067] sd 3:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
2019-01-22T10:04:46.771895-08:00 INFO kernel: [ 8047.952085] sd 3:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 8d 37 10 00 00 10 00
2019-01-22T10:04:46.771898-08:00 ERR kernel: [ 8047.952092] blk_update_request: I/O error, dev sda, sector 9254672
2019-01-22T10:04:46.801878-08:00 INFO kernel: [ 8047.982077] sd 3:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
2019-01-22T10:04:46.801909-08:00 INFO kernel: [ 8047.982095] sd 3:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 8d 35 20 00 00 08 00
2019-01-22T10:04:46.801912-08:00 ERR kernel: [ 8047.982103] blk_update_request: I/O error, dev sda, sector 9254176
2019-01-22T10:04:46.801914-08:00 ERR kernel: [ 8047.982111] Buffer I/O error on dev sda1, logical block 1152676, async page read
2019-01-22T10:04:46.831176-08:00 ERR mount.exfat-fuse[15552]: failed to read cluster 0x8c38
2019-01-22T10:04:46.831871-08:00 INFO kernel: [ 8048.012064] sd 3:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
2019-01-22T10:04:46.831895-08:00 INFO kernel: [ 8048.012081] sd 3:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 8d 36 00 00 00 08 00
2019-01-22T10:04:46.831899-08:00 ERR kernel: [ 8048.012089] blk_update_request: I/O error, dev sda, sector 9254400
2019-01-22T10:04:46.831900-08:00 ERR kernel: [ 8048.012097] Buffer I/O error on dev sda1, logical block 1152704, async page read
2019-01-22T10:04:46.864866-08:00 INFO kernel: [ 8048.045068] sd 3:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
2019-01-22T10:04:46.864882-08:00 INFO kernel: [ 8048.045078] sd 3:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 ed 5f 58 00 00 20 00
2019-01-22T10:04:46.864884-08:00 ERR kernel: [ 8048.045082] blk_update_request: I/O error, dev sda, sector 15556440
2019-01-22T10:04:46.895915-08:00 INFO kernel: [ 8048.076137] sd 3:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
2019-01-22T10:04:46.895934-08:00 INFO kernel: [ 8048.076148] sd 3:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 ed 5f 58 00 00 08 00
2019-01-22T10:04:46.895936-08:00 ERR kernel: [ 8048.076153] blk_update_request: I/O error, dev sda, sector 15556440
2019-01-22T10:04:46.895937-08:00 ERR kernel: [ 8048.076159] Buffer I/O error on dev sda1, logical block 1940459, async page read
2019-01-22T10:04:46.950173-08:00 INFO kernel: [ 8048.131056] sd 3:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
2019-01-22T10:04:46.950201-08:00 INFO kernel: [ 8048.131073] sd 3:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 02 29 ef 00 00 00 08 00
2019-01-22T10:04:46.950204-08:00 ERR kernel: [ 8048.131080] blk_update_request: I/O error, dev sda, sector 36302592
2019-01-22T10:04:46.950206-08:00 ERR kernel: [ 8048.131089] Buffer I/O error on dev sda1, logical block 4533728, async page read
2019-01-22T10:04:46.950292-08:00 ERR mount.exfat-fuse[15552]: failed to read cluster 0x228f1
2019-01-22T10:04:46.981912-08:00 INFO kernel: [ 8048.162171] sd 3:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
2019-01-22T10:04:46.981932-08:00 INFO kernel: [ 8048.162189] sd 3:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 02 29 ef 00 00 00 08 00
2019-01-22T10:04:46.981935-08:00 ERR kernel: [ 8048.162196] blk_update_request: I/O error, dev sda, sector 36302592
2019-01-22T10:04:46.981938-08:00 ERR kernel: [ 8048.162205] Buffer I/O error on dev sda1, logical block 4533728, async page read
2019-01-22T10:04:47.002938-08:00 INFO kernel: [ 8048.183036] usb 2-4: USB disconnect, device number 6
2019-01-22T10:04:47.002974-08:00 ERR kernel: [ 8048.184048] Buffer I/O error on dev sda1, logical block 4533728, async page read

Comment 5 by stevendh...@gmail.com, Today (6 hours ago) 

Could it be caused by a "bad" external card reader?  I just realized that is mostly happening at work where I have a different USB 4-port and a different external USB card reader.

Comment 6 by amistry@chromium.org, Today (5 hours ago) 

Yes, it could. Any part of the hardware chain from the Chromebook to the SD card could be causing the problem. It could also be a software bug. At this point, I can't tell.

Comment 7 by stevendh...@gmail.com, Today (2 hours ago) 

I have eliminated the USB 4-port and external USB card reader.  I don't get any errors with those with my two test MicroSD cards.  I think it is more than likely the internal reader but I'll try some more testing soon (which would be a real bummer if it is the internal MicroSD card port).
►

Sign in to add a comment