boot partition is mounted read-only even though specify rw

Bug #629478 reported by Torez Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-linaro (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

while executing tool flash-kernel, it seems boot partition is originally mounted rw as desired. However, during the execution of the tool, and after we have written to the mounted file system, its not being reported as a read-only file system, causing subsequent writes not to sucessfully complete.

Running with build 20100902-0 and flashing kernel to 20100822-0

+ echo Using u-boot partition: /dev/mmcblk0p1
Using u-boot partition: /dev/mmcblk0p1
+ mktemp -d
+ TMPMOUNT=/tmp/tmp.aL5wD1VOmN
+ mount /dev/mmcblk0p1 /tmp/tmp.aL5wD1VOmN
+ printf Creating backups of uImage and uInitrd...
Creating backups of uImage and uInitrd... + [ -e /tmp/tmp.aL5wD1VOmN/uImage ]
+ cp /tmp/tmp.aL5wD1VOmN/uImage /tmp/tmp.aL5wD1VOmN/uImage.bak
+ [ -e /tmp/tmp.aL5wD1VOmN/uInitrd ]
+ cp /tmp/tmp.aL5wD1VOmN/uInitrd /tmp/tmp.aL5wD1VOmN/uInitrd.bak
[ 239.728942] FAT: Filesystem error (dev mmcblk0p1)
[ 239.734558] fat_free_clusters: deleting FAT entry beyond EOF
[ 239.741424] FAT: Filesystem has been set read-only
+ echo done.
done.
+ printf Generating kernel u-boot image...
Generating kernel u-boot image... + mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n Ubuntu Kernel -d /boot/vmlinuz-2.6.35-1004-linaro-omap /tmp/tmp.aL5wD1VOmN/uImage
mkimage: Can't open /tmp/tmp.aL5wD1VOmN/uImage: Read-only file system
+ cleanup
root@localhost:/boot# mount
/dev/mmcblk0p2 on / type ext3 (rw,errors=remount-ro)
none on /proc type proc (rw,noexec,nosuid,nodev)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
none on /dev type devtmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
/dev/mmcblk0p1 on /tmp/tmp.aL5wD1VOmN type vfat (rw)
root@localhost:/boot# ls /tmp/tmp.aL5wD1VOmN
MLO boot.ini boot.scr u-boot.bin uImage uImage.bak uInitrd uInitrd.bak

Revision history for this message
John Rigby (jcrigby) wrote :

I think this was related to the write protect gpio wrong in an older u-boot. I think it is fixed now.

Revision history for this message
Jamie Bennett (jamiebennett) wrote :

Torez, as the images have undergone huge changes since you reported this bug, can you confirm whether this issue still persists?

Changed in linux-linaro (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Torez Smith (lnxtorez) wrote :

this problem was fixed in subsequent revisions of the flash tool so no longer exists.

Changed in linux-linaro (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.