Location: http://autobuilder.yoctoproject.org/pub/nightly/20130226-2 branch: danny poky: 98292d1ef1cb44cf96f0a28fbca6439eda55ce1b This issue is same with bug 3935, but for 1.3.1 branch. So I file a new bug. The usb stick works fine. Can mount, write, read and remount without problem. Beagleboard: ########### usb 1-2.4.4: new high-speed USB device number 7 using ehci-omap scsi0 : usb-storage 1-2.4.4:1.0 scsi 0:0:0:0: Direct-Access Netac OnlyDisk 1.00 PQ: 0 ANSI: 2 sd 0:0:0:0: [sda] 2009600 512-byte logical blocks: (1.02 GB/981 MiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 sd 0:0:0:0: [sda] No Caching mode page present sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] No Caching mode page present sd 0:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sd 0:0:0:0: [sda] No Caching mode page present sd 0:0:0:0: [sda] Assuming drive cache: write through sd 0:0:0:0: [sda] Attached SCSI removable disk EXT4-fs (sda): VFS: Can't find ext4 filesystem EXT3-fs (sda): error: can't find ext3 filesystem on dev sda. EXT2-fs (sda): error: can't find an ext2 filesystem on dev sda. FAT-fs (sda): invalid media value (0xb9) FAT-fs (sda): Can't find a valid FAT filesystem VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sda. kjournald starting. Commit interval 5 seconds EXT3-fs (sda1): using internal journal EXT3-fs (sda1): recovery complete EXT3-fs (sda1): mounted filesystem with ordered data mode ########### Routerstation: ###########EXT4-fs (sda): VFS: Can't find ext4 filesystem EXT3-fs (sda): error: can't find ext3 filesystem on dev sda. EXT2-fs (sda): error: can't find an ext2 filesystem on dev sda. FAT-fs (sda): invalid media value (0xb9) FAT-fs (sda): Can't find a valid FAT filesystem VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sda. SQUASHFS error: Can't find a SQUASHFS superblock on sda FAT-fs (sda): invalid media value (0xb9) FAT-fs (sda): Can't find a valid FAT filesystem EXT3-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended kjournald starting. Commit interval 5 seconds EXT3-fs (sda1): using internal journal EXT3-fs (sda1): recovery complete EXT3-fs (sda1): mounted filesystem with ordered data mode ################ Mpc8315e ################ EXT4-fs (sda): VFS: Can't find ext4 filesystem EXT3-fs (sda): error: can't find ext3 filesystem on dev sda. EXT2-fs (sda): error: can't find an ext2 filesystem on dev sda. FAT-fs (sda): invalid media value (0x00) FAT-fs (sda): Can't find a valid FAT filesystem EXT4-fs (sdb): VFS: Can't find ext4 filesystem EXT3-fs (sdb): error: can't find ext3 filesystem on dev sdb. EXT2-fs (sdb): error: can't find an ext2 filesystem on dev sdb. FAT-fs (sdb): bogus number of reserved sectors FAT-fs (sdb): Can't find a valid FAT filesystem VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sda. FAT-fs (sda): invalid media value (0x00) FAT-fs (sda): Can't find a valid FAT filesystem VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sdb. FAT-fs (sdb): bogus number of reserved sectors FAT-fs (sdb): Can't find a valid FAT filesystem eth0: no IPv6 routers present EXT4-fs (sda4): unable to read superblock EXT3-fs (sda4): error: unable to read superblock EXT2-fs (sda4): error: unable to read superblock FAT-fs (sda4): bogus number of reserved sectors FAT-fs (sda4): Can't find a valid FAT filesystem MINIX-fs: unable to read superblock FAT-fs (sda4): bogus number of reserved sectors FAT-fs (sda4): Can't find a valid FAT filesystem kjournald starting. Commit interval 5 seconds EXT3-fs (sdb1): using internal journal EXT3-fs (sdb1): recovery complete EXT3-fs (sdb1): mounted filesystem with ordered data mode ################
We need to identify a resource to fix this. Ack'ing it as a placeholder.
This has been fixed in master so hopefully can be easily backported.
Backported be218292ee3f05afe47545aa8e1625452e0cd614 to my danny-next.
looks like that fix have been merged into danny branch , but issue still exists. from git log: commit 881f4b9bdd44bd4849155f54915eb5aed005869d Author: Saul Wold <sgw@linux.intel.com> Date: Sat Apr 13 09:55:55 2013 -0700 udev-extraconf: Add -o silent to auto mount for mount.util-linux This will silence some of the noisy output from mount.util-linux and the kernel when trying to automount filesystems or devices. Busybox does not accept the silent option, it uses a loud option instead. [YOCTO #3935] (From OE-Core rev: 796e1390487d602c55467d7654f52e43a4617548) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The uprev to 3.10 has solved this problem in local testing. Closing the bug.