New issue
Advanced search Search tips

Issue 914576 link

Starred by 4 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Chrome OS does not detect external drives properly

Reported by scamdyn@gmail.com, Dec 12

Issue description

Chrome Version       : 73.0.3637.0
OS Version: 11389.0.0
URLs (if applicable) : N/A
Other browsers tested: N/A
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari: N/A
    Firefox: N/A
    IE/Edge: N/A

What steps will reproduce the problem?
1. Plug in an external drive (such as USB Flash Drive, external hard drive, etc.)
2. Have Files app open, and wait for notification. 
3. Chrome OS says "Sorry, your external storage device could not be recognized." Chrome OS Files app shows no sign of newly connected drives. 

What is the expected result?
Chrome OS recognizes the drive, and drive shows up in Files app. 

What happens instead of that?
Chrome OS cannot recognize the drive. 

Please provide any additional information below. Attach a screenshot if
possible.

I have tested this on Stable and Beta Channels, as well as my other Chromebook on Stable. The drive I am using (Western Digital 1 TB external hard drive, formatted to ext4 to support Crouton) is detected on both Chromebooks running Stable (or Beta), and switching back to Canary, the drive is unrecognized. 

First time encountering the bug, it has led me to believe the hard drive was corrupted and needed reformatting. I used my Chromebook on Stable to reformat it, however plugging it back into the Chromebook on Canary, the hard drive was still unrecognized. 

UserAgentString: Mozilla/5.0 (X11; CrOS x86_64 11389.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3637.0 Safari/537.36



 
Screenshot 2018-12-12 at 1.59.49 PM.png
639 KB View Download
I also forgot to add, clicking "FORMAT THIS DEVICE" in the notification does nothing. 
Components: Platform>Apps>FileManager
Labels: CrOSFilesFeature-ExternalMedia Needs-Feedback
Can you grab /var/log/messages and attach it to this bug? Alternatively can you file feedback which will also grab a bunch of other logs as well. If you file feedback can you update the bug so I can go and track down the feedback?

Thanks
Here are the logs in /var/log/messages 
When capturing these logs, I have plugged in two external media devices, a Western Digital Passport External Hard Drive (1 TB) and a SanDisk Cruzer (4 GB) USB Flash Drive. 

I will also Send Feedback as soon as I can. 

Let me know if I can do anything more. This bug won't allow me to boot into my Crouton setup, or access any other regularly formatted USB Drive. 

ExternalMediaErrorLogs.txt
154 KB View Download
Project Member

Comment 5 by sheriffbot@chromium.org, Dec 13

Cc: slangley@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: amistry@chromium.org
Status: Untriaged (was: Unconfirmed)
What I pulled from the logs:

2018-12-13T16:32:15.656520-06:00 ERR drivefs[2258]: [140438190139776] drive_util.cc:1090:CloudStoreLog Transport error:  when getting https://www.googleapis.com/drive/v2internal/about?openDrive=false&reason=304&syncType=2&fields=rootFolderId%2CquotaBytesTotal%2CquotaBytesUsed%2CquotaBytesUsedAggregate%2CquotaType%2CexportFormats%2CimportFormats%2CmaxUploadSizes%2CadditionalRoleInfo%2Cuser
2018-12-13T16:32:16.637046-06:00 INFO kernel: [   22.641518] usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
2018-12-13T16:32:16.648866-06:00 INFO kernel: [   22.653182] usb 2-2: New USB device found, idVendor=1058, idProduct=25e1, bcdDevice=10.21
2018-12-13T16:32:16.648882-06:00 INFO kernel: [   22.653201] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2018-12-13T16:32:16.648885-06:00 INFO kernel: [   22.653214] usb 2-2: Product: My Passport 25E1
2018-12-13T16:32:16.648886-06:00 INFO kernel: [   22.653224] usb 2-2: Manufacturer: Western Digital
2018-12-13T16:32:16.648888-06:00 INFO kernel: [   22.653233] usb 2-2: SerialNumber: 575834314133384E3144385A
2018-12-13T16:32:16.651143-06:00 INFO kernel: [   22.656310] scsi2 : usb-storage 2-2:1.0
2018-12-13T16:32:16.754211-06:00 INFO permission_broker[1221]: ProcessPath(/dev/bus/usb/002/002)
2018-12-13T16:32:16.801261-06:00 INFO permission_broker[1221]:   AllowUsbDeviceRule: ALLOW
2018-12-13T16:32:16.801332-06:00 INFO permission_broker[1221]:   AllowTtyDeviceRule: IGNORE
2018-12-13T16:32:16.857968-06:00 INFO permission_broker[1221]:   DenyClaimedUsbDeviceRule: DENY
2018-12-13T16:32:16.857986-06:00 INFO permission_broker[1221]: Verdict for /dev/bus/usb/002/002: DENY
2018-12-13T16:32:16.858042-06:00 ERR permission_broker[1221]: OpenPath(...): Domain=permission_broker, Code=permission_denied, Message=Permission to open '/dev/bus/usb/002/002' denied
2018-12-13T16:32:17.653027-06:00 NOTICE kernel: [   23.657577] scsi 2:0:0:0: Direct-Access     WD       My Passport 25E1 1021 PQ: 0 ANSI: 6
2018-12-13T16:32:17.654030-06:00 NOTICE kernel: [   23.658686] scsi 2:0:0:1: Enclosure         WD       SES Device       1021 PQ: 0 ANSI: 6
2018-12-13T16:32:17.655030-06:00 NOTICE kernel: [   23.659714] sd 2:0:0:0: [sdb] Spinning up disk...
2018-12-13T16:32:21.664061-06:00 NOTICE kernel: [   24.660128] ....ready
2018-12-13T16:32:21.664085-06:00 NOTICE kernel: [   27.668175] sd 2:0:0:0: [sdb] 1953458176 512-byte logical blocks: (1.00 TB/931 GiB)
2018-12-13T16:32:21.664088-06:00 NOTICE kernel: [   27.668501] sd 2:0:0:0: [sdb] Write Protect is off
2018-12-13T16:32:21.664090-06:00 DEBUG kernel: [   27.668522] sd 2:0:0:0: [sdb] Mode Sense: 47 00 10 08
2018-12-13T16:32:21.665656-06:00 ERR kernel: [   27.668886] sd 2:0:0:0: [sdb] No Caching mode page present
2018-12-13T16:32:21.665673-06:00 ERR kernel: [   27.668906] sd 2:0:0:0: [sdb] Assuming drive cache: write through
2018-12-13T16:32:21.665675-06:00 ERR kernel: [   27.669893] sd 2:0:0:0: [sdb] No Caching mode page present
2018-12-13T16:32:21.665677-06:00 ERR kernel: [   27.669912] sd 2:0:0:0: [sdb] Assuming drive cache: write through
2018-12-13T16:32:21.763035-06:00 INFO kernel: [   27.767114]  sdb: unknown partition table
2018-12-13T16:32:21.764031-06:00 ERR kernel: [   27.768517] sd 2:0:0:0: [sdb] No Caching mode page present
2018-12-13T16:32:21.764043-06:00 ERR kernel: [   27.768531] sd 2:0:0:0: [sdb] Assuming drive cache: write through
2018-12-13T16:32:21.764045-06:00 NOTICE kernel: [   27.768543] sd 2:0:0:0: [sdb] Attached SCSI disk
2018-12-13T16:32:22.047792-06:00 ERR cros-disks[1276]: Failed to mount '/dev/sdb' '/media/removable/USB Drive' 'ext4' 142 'nosymfollow': Invalid argument
2018-12-13T16:32:22.047811-06:00 ERR cros-disks[1276]: Failed to mount '/dev/sdb' to '/media/removable/USB Drive' as filesystem 'ext4' with options 'nosymfollow,dirsync,rw,nodev,noexec,nosuid'
2018-12-13T16:32:22.048022-06:00 ERR kernel: [   28.052158] EXT4-fs (sdb): Unrecognized mount option "nosymfollow" or missing value
2018-12-13T16:32:22.048764-06:00 ERR cros-disks[1276]: Failed to mount '/dev/sdb' '/media/removable/USB Drive' 'ext4' 143 'nosymfollow': Invalid argument
2018-12-13T16:32:22.048777-06:00 ERR cros-disks[1276]: Failed to mount '/dev/sdb' to '/media/removable/USB Drive' as filesystem 'ext4' with options 'nosymfollow,dirsync,ro,nodev,noexec,nosuid'
2018-12-13T16:32:22.048790-06:00 ERR cros-disks[1276]: Failed to mount path '/sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/host2/target2:0:0/2:0:0:0/block/sdb'
2018-12-13T16:32:22.048814-06:00 ERR cros-disks[1276]: Failed to mount '/sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/host2/target2:0:0/2:0:0:0/block/sdb'
2018-12-13T16:32:22.049025-06:00 ERR kernel: [   28.053231] EXT4-fs (sdb): Unrecognized mount option "nosymfollow" or missing value

Anand - do you now if "nosymfollow" os something recently added to cros_disks?
Owner: amistry@chromium.org
Status: Started (was: Untriaged)
I think the following should temporarily work around this issue:
1. Open chrome://flags
2. Find "#enable-fs-nosymfollow" and set to disabled
3. Reboot


Cc: mortonm@chromium.org benchan@chromium.org
Thank you amistry@! That indeed is a temporary workaround for now. 
The user's device is running a 3.8 kernel, which I don't think has the necessary change backported.
Yep that's likely the issue. Let me see if we can disable < 3.14 through Chrome VariationsService or we should just make it default-disabled across the board.
Labels: -Pri-3 Hotlist-ConOps-CrOS Hotlist-ConOps-Source-Forum Pri-2
Status: Fixed (was: Started)
Symlink blocking on user-supplied file systems was disabled here: https://critique.corp.google.com/#review/225457024

We will re-enable for boards >= 3.14 soon. I think this is fixed

Sign in to add a comment