Mounting RW rootfs for modprobe hid-multitouch at boot

589 views
Skip to first unread message

m...@kir.it

unread,
Dec 16, 2013, 5:49:37 AM12/16/13
to chromium-...@chromium.org
Hi, i'm trying to insert a script that load the module hid-multitouch at boot, but without success.

I can't write the rootfs even if i turn the rootfs verification off:


1. make_dev_ssd.sh --force --remove_root_fs 
2. mount -o remount,rw /

mount: cannot remount block device /dev/ROOT read-write, is write-protected

[  517.394412] EXT4-fs (sda3): couldn't mount RDWR because of unsupported optional features (ff000000)
[  529.552300] EXT4-fs (sda3): couldn't mount RDWR because of unsupported optional features (ff000000)
[  600.032221] EXT4-fs (sda3): couldn't mount RDWR because of unsupported optional features (ff000000)

e2fsck 1.42 (29-Nov-2011)
/dev/sda3 has unsupported feature(s): FEATURE_R24 FEATURE_R25 FEATURE_R26 FEATURE_R27 FEATURE_R28 FEATURE_R29 FEATURE_R30 FEATURE_R31
e2fsck: Get a newer version of e2fsck!

debugfs 1.42 (29-Nov-2011)
/dev/sda3: Filesystem has unsupported read-only feature(s) while opening filesystem
debugfs: feature -FEATURE_R24
feature: Filesystem not open
debugfs: quit

Chrome version: 29.0.1547.74  Channel: stable
OS Version: 3.4.0
Kernel /proc/cmdline
quiet console=tty2 init=/sbin/init boot=local rootwait noresume noswap loglevel=1 noinitrd root=/dev/sda3 
i915.modeset=1 cros_legacy cros_debug BOOT_IMAGE=vmlinuz.A 

Linux localhost 3.4.0 #1 SMP Thu Sep 12 16:21:50 PDT 2013 x86_64 Intel(R) Atom(TM) CPU D525 @ 1.80GHz GenuineIntel GNU/Linux


If I try to mount in rw at bootloader the system hangs, any suggestions? :)
Thanks in advance.
Cheers

m...@kir.it

unread,
Dec 16, 2013, 6:44:16 AM12/16/13
to chromium-...@chromium.org
I mistyped the command in the issue but it was correct at the terminal, my bad.

Some more infos:
This is the output with --remove_rootfs_verification

      !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
      ! INFO: ALL SANITY CHECKS WERE BYPASSED. YOU ARE ON YOUR OWN. !
      !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
      

Start in 5 second(s) (^C to abort)...  
Start in 4 second(s) (^C to abort)...  
Start in 3 second(s) (^C to abort)...  
Start in 2 second(s) (^C to abort)...  
Start in 1 second(s) (^C to abort)...  
Kernel A: Disabled rootfs verification.
Backup of Kernel A is stored in: /mnt/stateful_partition/backups/kernel_A_20131216_031643.bin
Kernel A: Re-signed with developer keys successfully.
Kernel B: Disabled rootfs verification.
Backup of Kernel B is stored in: /mnt/stateful_partition/backups/kernel_B_20131216_031645.bin
Kernel B: Re-signed with developer keys successfully.
Successfully re-signed 2 of 2 kernel(s)  on device /dev/sda.

At the reboot I still get the mount read-only error.

mount -o remount, rw /
mount: you must specify the filesystem type

mount -t ext2 -o remount, rw /
mount: cannot remount block device rw read-write, is write-protected

mount -t ext4 -o remount, rw /
mount: cannot remount block device rw read-write, is write-protected

[   24.066179] EXT4-fs (sda3): couldn't mount RDWR because of unsupported optional features (ff000000)
[   30.056144] EXT4-fs (sda3): couldn't mount RDWR because of unsupported optional features (ff000000)
[   46.912226] EXT4-fs (sda3): couldn't mount RDWR because of unsupported optional features (ff000000)
[  302.048034] EXT4-fs (sda3): error count: 13
[  302.048042] EXT4-fs (sda3): initial error at 1386694180: ext4_map_blocks:544: inode 32786: block 1577058816
[  302.048053] EXT4-fs (sda3): last error at 1386694194: ext4_map_blocks:544: inode 32786: block 486998326

Full dmesg in attachment.
Cheers
dmesgfullerrnew.txt

Mike Frysinger

unread,
Dec 16, 2013, 10:01:43 AM12/16/13
to m...@kir.it, Chromium OS discuss
when you run build_image, pass the --noenable_rootfs_verification flag to create a rootfs w/out verification enabled
-mike


--
--
Chromium OS discuss mailing list: chromium-...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en
 

DennisLfromGA

unread,
Dec 16, 2013, 5:25:16 PM12/16/13
to chromium-...@chromium.org
@m...@kir.it 

I use -

    sudo mount -i -o remount,rw / || bash ~/bin/rw-rootfs

in my .bashrc and it mounts without a problem unless chromeos was upgraded at which point it fails and runs my rw-rootfs script that does this -

    CURRENTROOT=`rootdev -s`
    if [ $CURRENTROOT = /dev/sda3 ]; then CURRENTKERNEL=2; else CURRENTKERNEL=4; fi
    sudo /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification --partitions $CURRENTKERNEL

This has worked well for me and I still get updates...

>At the reboot I still get the mount read-only error.
>mount -o remount, rw / 
>mount: you must specify the filesystem type 

>mount -t ext2 -o remount, rw / 
>mount: cannot remount block device rw read-write, is write-protected 

>mount -t ext4 -o remount, rw / 
>mount: cannot remount block device rw read-write, is write-protected

Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages