Results 1 to 2 of 2
  1. RickNY's Avatar
    Posts
    254 Posts
    Global Posts
    319 Global Posts
       #1  
    (Was originally posted in OK ROM comes thread -- created a new topic at several users request)

    Today I tried to plug in my rooted Pre to the USB cable and put the Pre in USB Mode.. I get the big disk icon on the screen for a few seconds, and then the wallpaper comes back. The bluetooth shuts off.. The status bar at the top momentarily changes from 'Sprint' to 'Phone Offline', and I cant turn the bluetooth back on again unless I turn airplane mode on and then off again.. And the drive doesn't mount on my PC.

    Running cat /var/log/messages | grep storaged from the point I plug the USB cable and select USB Mode returns the following:

    Code:
    2009-06-18T22:23:20.191496Z [724] castle user.debug storaged: get_load_media_path: called
    2009-06-18T22:23:20.191649Z [724] castle user.debug storaged: make_disk_mountable called; state of disk: connected
    2009-06-18T22:23:20.203734Z [724] castle user.err storaged: unmount_partition_here: stderr: umount: cannot umount /media/internal: Device or resource busy
    2009-06-18T22:23:20.204192Z [724] castle user.debug storaged: unmount_partition_here: unmount failed
    2009-06-18T22:23:20.747282Z [725] castle user.debug storaged: make_disk_mountable: force attempt 1.
    2009-06-18T22:23:20.782134Z [725] castle user.err storaged: unmount_partition_here: stderr: umount: cannot forcibly umount /media/internal: Device or resource busy
    2009-06-18T22:23:20.791655Z [725] castle user.debug storaged: unmount_partition_here: unmount failed
    2009-06-18T22:23:21.052367Z [725] castle user.debug storaged: make_disk_mountable: force attempt 2.
    2009-06-18T22:23:21.064879Z [725] castle user.err storaged: unmount_partition_here: stderr: umount: cannot forcibly umount /media/internal: Device or resource busy
    2009-06-18T22:23:21.065337Z [725] castle user.debug storaged: unmount_partition_here: unmount failed
    2009-06-18T22:23:21.244749Z [725] castle user.debug storaged: make_disk_mountable: force attempt 3.
    2009-06-18T22:23:21.256834Z [725] castle user.err storaged: unmount_partition_here: stderr: umount: cannot forcibly umount /media/internal: Device or resource busy
    2009-06-18T22:23:21.257292Z [725] castle user.debug storaged: unmount_partition_here: unmount failed
    2009-06-18T22:23:21.396544Z [726] castle user.debug storaged: make_disk_mountable: force attempt 4.
    2009-06-18T22:23:21.408690Z [726] castle user.err storaged: unmount_partition_here: stderr: umount: cannot forcibly umount /media/internal: Device or resource busy
    2009-06-18T22:23:21.409148Z [726] castle user.debug storaged: unmount_partition_here: unmount failed
    2009-06-18T22:23:21.486235Z [726] castle user.debug storaged: make_disk_mountable: force attempt 5.
    2009-06-18T22:23:21.498320Z [726] castle user.err storaged: unmount_partition_here: stderr: umount: cannot forcibly umount /media/internal: Device or resource busy
    2009-06-18T22:23:21.498778Z [726] castle user.debug storaged: unmount_partition_here: unmount failed
    2009-06-18T22:23:21.575926Z [726] castle user.warning storaged: make_disk_mountable: wasn't able to force unmount after 5 attemps
    2009-06-18T22:23:21.576445Z [726] castle user.debug storaged: SignalMSMProgress: sending {"stage":"failed", "enterIMasq": false} to luna://com.palm.storage/storaged/MSMProgress
    Obviously its not happy.. Does anyone know what might be going on here?

    Thanks,
    Rick
  2. RickNY's Avatar
    Posts
    254 Posts
    Global Posts
    319 Global Posts
       #2  
    Nevermind.. I think I found the cause of my problem -- unfortunately after I reset the device.. Saw the optware wiki was updated

    Notes on the old loopback method

    We used to use a loopback file on /media/internal to store the contents of /opt. This didn't work well, since as long as the loopback filesystem is mounted, this breaks the Pre's USB/MediaSync modes. When the user tries to enable either mode, webOS will try to umount /media/internal, and as long as the optware.ext3 file is being used, it can't. If you need to migrate from this mode to the new instructions, you need to kill any processes running from that filesystem and umount it, like so:
    Oh well... Time to set it up again.

Posting Permissions