You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WTMF - ChromeOS will no longer mount ext4 on an external device:
(not exactly a crouton issue, but this will break all "proper" chroots running on USB sticks, and presumably SD cards as well)
Version 38.0.2104.0 dev (64-bit)
Platform 6092.0.0 (Official Build) dev-channel peppy
Firmware Google_Peppy.4389.86.0
tail -f /var/log/messages
2014-08-01T11:35:07.804796-07:00 localhost disks[3905]: File system type 'ext4' on device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1' is not supported
2014-08-01T11:35:07.804817-07:00 localhost disks[3905]: Failed to mount '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1'
The text was updated successfully, but these errors were encountered:
It's not the best turn of events, but they won't be removing the ability to mount via command line. Don't forget that verified mode is the primary driver of Chromium OS, and I suspect the number of people in verified mode who mount and manage ext partitions is slim to nil.
As for dev mode, crouton will provide a workaround as ever...
WTMF - ChromeOS will no longer mount ext4 on an external device:
(not exactly a crouton issue, but this will break all "proper" chroots running on USB sticks, and presumably SD cards as well)
Version 38.0.2104.0 dev (64-bit)
Platform 6092.0.0 (Official Build) dev-channel peppy
Firmware Google_Peppy.4389.86.0
tail -f /var/log/messages
2014-08-01T11:35:07.804796-07:00 localhost disks[3905]: File system type 'ext4' on device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1' is not supported
2014-08-01T11:35:07.804817-07:00 localhost disks[3905]: Failed to mount '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/host4/target4:0:0/4:0:0:0/block/sdb/sdb1'
The text was updated successfully, but these errors were encountered: