Results 1 to 16 of 16
Like Tree10Likes
  • 1 Post By George Mari
  • 1 Post By Mutoidi
  • 1 Post By George Mari
  • 1 Post By George Mari
  • 1 Post By George Mari
  • 1 Post By George Mari
  • 1 Post By George Mari
  • 2 Post By George Mari
  • 1 Post By MAMISHO
  1.    #1  
    Hi.
    I'm lunetube's developer and I would like to test the app in a real device like pre 3 but I have a problem with my pre3. By mistake I disconnected the USB cable while I was running webosDoctor and my device was frozen in the time. When I use it for half an hour the phone is frozen and I have to force the reboot. I tried to make a hardreset, but it always stays at 12% and when I restore the partition it starts webOs on the same date with all the files it had the last time. It is as if the storage is blocked and does not allow to write anything. What can I do?.
    Last edited by MAMISHO; 06/14/2017 at 07:40 AM.
  2. #2  
    Hi Mamisho.

    I don't have any experience with the Pre3, but it sounds like you have some minor corruption on your flash filesystem that may have left it in a read-only state.

    If you boot the device as normal, you'll be trying to repair the filesystem while it's in use, and that's not really possible. Just like PCs have rescue CDs, webOS has something similar called memboot - How To Recover - WebOS Internals
    The link explains it best, but basically, you connect your phone to a PC via the USB cable, then run a command from the PC to boot the phone from a kernel you extract from a webOS doctor .jar file. This way, you can then use novaterm to connect to the command line environment in your phone, and use standard Linux tools like fsck to try to repair the file system on the flash storage.

    If you're not familiar with doing that sort of thing, just keep posting here - myself and others can talk you through it.
    MAMISHO likes this.
  3.    #3  
    Thank you so much George Mari, I gonna try to repair in this way, but I have a question about the section "Complete filesystem creation". It say "the following is for a 32GB TouchPad" and my device is pre 3 8GB. Could be any problem with the follow commands?.

    lvm.static vgscan --ignorelockingfailure
    lvm.static vgchange -ay --ignorelockingfailure
    lvm.static vgremove store
    lvm.static vgscan --ignorelockingfailure
    lvm.static vgchange -ay --ignorelockingfailure
    lvm.static vgcreate -s 8M store /dev/mmcblk0p14
    lvm.static vgscan --ignorelockingfailure
    lvm.static vgchange -ay --ignorelockingfailure
    lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
    lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
    lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
    lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
    lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
    lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
    lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store
    lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
    lvm.static vgscan --ignorelockingfailure
    lvm.static vgchange -ay --ignorelockingfailure
    mkdosfs -f 1 -s 64 /dev/store/media
  4. #4  
    If you need to, you can download any Pre3 WebOS 'Doctor' here:

    https://docs.google.com/spreadsheets...it?pli=1#gid=0

    I have 2.2.4 installed.

    Last edited by Mutoidi; 06/03/2017 at 10:43 AM.

    TP 32Gb 4G. 3.0.5 / CM10. ~ Pre3 16Gb GSM. 2.2.4. ~ TS2 BT Audio-Dock ~ HP iPaq. hx-2790b.
    TP 32Gb Wifi. 3.0.5 / CM10. ~ Veer (Wht.) 8Gb GSM. 2.2.4. ~ HP Omen-15-5206tx. 256Gb SSD. i7-O/C@3.39Ghz. Win10.
    MAMISHO likes this.
  5. #5  
    Quote Originally Posted by MAMISHO View Post
    Thank you so much George Mari, I gonna try to repair in this way, but I have a question about the section "Complete filesystem creation". It say "the following is for a 32GB TouchPad" and my device is pre 3 8GB. Could be any problem with the follow commands?.

    lvm.static vgscan --ignorelockingfailure
    lvm.static vgchange -ay --ignorelockingfailure
    lvm.static vgremove store
    lvm.static vgscan --ignorelockingfailure
    lvm.static vgchange -ay --ignorelockingfailure
    lvm.static vgcreate -s 8M store /dev/mmcblk0p14
    lvm.static vgscan --ignorelockingfailure
    lvm.static vgchange -ay --ignorelockingfailure
    lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
    lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
    lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
    lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
    lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
    lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
    lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store
    lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
    lvm.static vgscan --ignorelockingfailure
    lvm.static vgchange -ay --ignorelockingfailure
    mkdosfs -f 1 -s 64 /dev/store/media
    Yeah, DON'T do that. :-) It's hard to say what you will need to do after you memboot. In general, you want to examine the existing file system on the flash storage and see if there is any corruption, using fsck. Let me try it on my Veer and post again later today.
    MAMISHO likes this.
  6. #6  
    Ok, here is what I would do to try to fix any filesystem corruption on my webOS device. I will be showing what it looks like on my Veer, but your Pre3 should be practically the same.

    So follow the instructions on the link I posted previously about how to memboot your device. This is equivalent to booting your PC from a CD or USB flash drive in order to fix a corrupted hard drive. The main thing with membooting, your not mounting the filesystem on your phone's flash storage, but it's still accessible. This way, you can run filesystem check (fsck) on the unmounted filesystems on the flash storage.

    So after you memboot, and use novaterm to connect to your phone, you get a prompt:

    Code:
    root@palm-webos:/#
    All of the flash storage partitions/volumes will be visible in the /dev/store/ directory, so lets get a listing. I enter the following command: (everything after the prompt)

    Code:
    root@palm-webos:/# ls -alh /dev/store/
    ...and I get a bunch of output:

    Code:
    drwx------    2 root     root         200 Aug 26 12:31 .
    drwxr-xr-x   14 root     root        4.1K Aug 26 12:31 ..
    lrwxrwxrwx    1 root     root          27 Aug 26 12:31 filecache -> /dev/mapper/store-filecache
    lrwxrwxrwx    1 root     root          21 Aug 26 12:31 log -> /dev/mapper/store-log
    lrwxrwxrwx    1 root     root          23 Aug 26 12:31 media -> /dev/mapper/store-media
    lrwxrwxrwx    1 root     root          24 Aug 26 12:31 mojodb -> /dev/mapper/store-mojodb
    lrwxrwxrwx    1 root     root          22 Aug 26 12:31 root -> /dev/mapper/store-root
    lrwxrwxrwx    1 root     root          22 Aug 26 12:31 swap -> /dev/mapper/store-swap
    lrwxrwxrwx    1 root     root          24 Aug 26 12:31 update -> /dev/mapper/store-update
    lrwxrwxrwx    1 root     root          21 Aug 26 12:31 var -> /dev/mapper/store-var
    Each line corresponds to webOS "disk" volume that holds a filesystem: filecache, log, media, etc. (Well, most of them, anyway) The linux command-line environment we are in has the standard filesystem check command "fsck" that we can use to try to repair any filesystem corruption. Now even though my Veer doesn't have any filesystem corruption, I can still run fsck on these volumes - it won't hurt. I'll do each, one-by-one:

    Code:
    root@palm-webos:/# fsck /dev/store/filecache
    ...which results in:
    Code:
    fsck 1.41.4 (27-Jan-2009)
    WARNING: couldn't open /etc/fstab: No such file or directory
    e2fsck 1.41.4 (27-Jan-2009)
    fsck.ext2: Superblock invalid, trying backup blocks...
    fsck.ext2: Bad magic number in super-block while trying to open /dev/store/filecache
    
    The superblock could not be read or does not describe a correct ext2
    filesystem.  If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>
    
    root@palm-webos:/#
    The warning about not being able to open /etc/fstab can be ignored for our purposes. So here, it's telling me something is wrong, and giving me an option of another command I can try if I want to fix it, but I'm not going to do that because I don't want to make any changes to this filesystem at this time.

    Let's move on to the next one:

    Code:
    root@palm-webos:/# fsck /dev/store/log
    ...which results in:

    Code:
    fsck 1.41.4 (27-Jan-2009)
    WARNING: couldn't open /etc/fstab: No such file or directory
    e2fsck 1.41.4 (27-Jan-2009)
    /var/log: clean, 61/6144 files, 2262/6144 blocks
    root@palm-webos:/#
    The line that starts with "e2fsck" is telling me fsck found a Linux ext2 or ext3 filesystem. The fsck program tries to automatically detect the filesystem. The last line about /var/log being clean, and showing the number of files and blocks tells me there is no filesystem corruption on this volume. Let's move on to the next one:

    Code:
    root@palm-webos:/# fsck /dev/store/media
    This is the phone's media partition, where you can put all of your own files when you plug in your USB cable to your PC.

    Code:
    fsck 1.41.4 (27-Jan-2009)
    WARNING: couldn't open /etc/fstab: No such file or directory
    dosfsck 2.11, 12 Mar 2005, FAT32, LFN
    There are differences between boot sector and its backup.
    Differences: (offset:original/backup)
      71:48/20, 72:50/20, 74:56/20, 75:45/20, 76:45/20, 77:52/20
    1) Copy original to backup
    2) Copy backup to original
    3) No action
    ? 3
    /dev/store/media: 2485 files, 3759/188136 clusters
    root@palm-webos:/#
    This time, about the 3rd line down, fsck is running the dosfsck module, as it found a FAT32 filesystem, which makes sense because it's the media partition. This time, it found a problem in the boot sector. Hmmm...that sounds strange to me, because I know webOS doesn't really boot from the media partition, so when it prompted me for what I wanted to do, I entered option 3, to do nothing. The last line tells me the number files and clusters it found.

    So if I was having a problem with this filesystem, like I couldn't access the data or whatever, I would have chosen to have fsck fix it when it prompted me.

    Let's try the next one:

    Code:
    root@palm-webos:/# fsck /dev/store/mojodb
    ..which results in:

    Code:
    fsck 1.41.4 (27-Jan-2009)
    WARNING: couldn't open /etc/fstab: No such file or directory
    e2fsck 1.41.4 (27-Jan-2009)
    fsck.ext2: Superblock invalid, trying backup blocks...
    fsck.ext2: Bad magic number in super-block while trying to open /dev/store/mojodb
    
    The superblock could not be read or does not describe a correct ext2
    filesystem.  If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>
    
    root@palm-webos:/#
    Again, just like with the filecache filesystem, I'm not really having trouble with this mojodb filesystem, so I'm not going enter the suggested command. Let's go to the next one.

    Code:
    root@palm-webos:/# fsck /dev/store/root
    ...with results in:

    Code:
    fsck 1.41.4 (27-Jan-2009)
    WARNING: couldn't open /etc/fstab: No such file or directory
    e2fsck 1.41.4 (27-Jan-2009)
    /: clean, 23439/116736 files, 109044/116736 blocks
    The root filesystem is clean. This is where all the guts of webOS reside, so that's a good sign.

    Now swap is the next filesystem in our list, but I know that it's not really a filesystem, so it doesn't make sense to run fsck on it. If you do, you won't hurt anything:

    Code:
    root@palm-webos:/# fsck /dev/store/swap
    Code:
    fsck 1.41.4 (27-Jan-2009)
    WARNING: couldn't open /etc/fstab: No such file or directory
    fsck: fsck.swap: not found
    fsck: Error 2 while executing fsck.swap for /dev/store/swap
    Next is update:

    Code:
    root@palm-webos:/# fsck /dev/store/update
    Code:
    fsck 1.41.4 (27-Jan-2009)
    WARNING: couldn't open /etc/fstab: No such file or directory
    e2fsck 1.41.4 (27-Jan-2009)
    /var/lib/update: clean, 11/4096 files, 1163/4096 blocks
    root@palm-webos:/#
    And finally var:

    Code:
    root@palm-webos:/# fsck /dev/store/var
    Code:
    fsck 1.41.4 (27-Jan-2009)
    WARNING: couldn't open /etc/fstab: No such file or directory
    e2fsck 1.41.4 (27-Jan-2009)
    /var: clean, 632/16384 files, 1991/16384 blocks
    root@palm-webos:/#
    Mamisho, when you do this on your Pre3, you may get some messages back from fsck telling you it found some corruption and asking if you want to fix it. (Which you should agree to.)

    So after this is all done, type "exit" to leave your novaterm session, and then manually hard reset your phone. I'm not sure how to do this on a Pre3, but on my Veer, I hold down the power button and switch the mute button back and forth 3 times.

    If after you reboot your phone, you still have the same problem, we can try to re-create all of your storage volumes, but NOT using the commands you posted - we would have to find the equivalent ones for your 8GB Pre 3.
  7. #7  
    Mamisho, I posted some instructions, but it was really long, so it's waiting for a moderator to approve it. I'm not sure when it will appear.
    MAMISHO likes this.
  8.    #8  
    Thank you! I'm waiting
  9.    #9  
    I have tried everything, and when it reboots, it is as if nothing changed. Check this out:

    Code:
    root@webos-device:/# lvm.static vgscan --ignorelockingfailure
      Reading all physical volumes.  This may take a while...
      Found volume group "store" using metadata type lvm2
    
    root@webos-device:/# lvm.static vgchange -ay --ignorelockingfailure
      8 logical volume(s) in volume group "store" now active
    
    root@webos-device:/# lvm.static vgremove store
    Do you really want to remove volume group "store" containing 8 logical volumes? [y/n]: y
    
    Do you really want to remove active logical volume "root"? [y/n]: y
      Logical volume "root" successfully removed
    
    Do you really want to remove active logical volume "var"? [y/n]: y
      Logical volume "var" successfully removed
    
    Do you really want to remove active logical volume "update"? [y/n]: y
      Logical volume "update" successfully removed
    
    Do you really want to remove active logical volume "log"? [y/n]: y
      Logical volume "log" successfully removed
    
    Do you really want to remove active logical volume "mojodb"? [y/n]: y
      Logical volume "mojodb" successfully removed
    
    Do you really want to remove active logical volume "filecache"? [y/n]: y
      Logical volume "filecache" successfully removed
    
    Do you really want to remove active logical volume "media"? [y/n]: y
      Logical volume "media" successfully removed
    
    Do you really want to remove active logical volume "swap"? [y/n]: y
      Logical volume "swap" successfully removed
      Volume group "store" successfully removed
    root@webos-device:/#
    It says it's removed but I inmediately launch this command
    Code:
    root@webos-device:/# lvm.static vgscan --ignorelockingfailure
      Reading all physical volumes.  This may take a while...
      Found volume group "store" using metadata type lvm2
    
    
    root@webos-device:/# lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
      Redundant stripes argument: default is 1
      Logical volume "root" already exists in volume group "store"
    STILL THERE!! LOL this is crazy... is it a hardware problem?
    I read something about touchpad in read-only mode. Can be that my pre 3 its in read-only mode too?
  10.    #10  
    Thank you.

    This was my result:

    Code:
    iMac:carpeta sin título Developer$ novacom boot mem:// < nova-installer-image-mantaray.uImage 
    iMac:carpeta sin título Developer$ novaterm
    section_start 0x1347d60
    section_start 0x1d91144
    ramdisk at 0x1347da0, len 10785697
    using command line 'root=/dev/ram0 rw fbcon=disable console=ttyS2,115200n8 nduid=6d50e9f1b143a27308c9d530094f5b866d1cefbe klog=0x4ff00000 klog_len=0x100000  boardtype=mantaray-pvt lcd_enable_vsync lastboot=reboot'
    copying kernel image from 0x100008c to 0x208000, len 3439828
    
    Tue Jun  6 00:14:15 2017
     novacomd socket was closed prematurely
    novacom: unexpected EOF from server
    iMac:carpeta sin título Developer$ novaterm
    root@webos-device:/# ls -alh /dev/store/
    drwx------    2 root     root         200 Jan  6 12:31 .
    drwxr-xr-x   14 root     root        4.6K Jan  6 12:31 ..
    lrwxrwxrwx    1 root     root          27 Jan  6 12:31 filecache -> /dev/mapper/store-filecache
    lrwxrwxrwx    1 root     root          21 Jan  6 12:31 log -> /dev/mapper/store-log
    lrwxrwxrwx    1 root     root          23 Jan  6 12:31 media -> /dev/mapper/store-media
    lrwxrwxrwx    1 root     root          24 Jan  6 12:31 mojodb -> /dev/mapper/store-mojodb
    lrwxrwxrwx    1 root     root          22 Jan  6 12:31 root -> /dev/mapper/store-root
    lrwxrwxrwx    1 root     root          22 Jan  6 12:31 swap -> /dev/mapper/store-swap
    lrwxrwxrwx    1 root     root          24 Jan  6 12:31 update -> /dev/mapper/store-update
    lrwxrwxrwx    1 root     root          21 Jan  6 12:31 var -> /dev/mapper/store-var
    root@webos-device:/# fsck /dev/store/filecache
    fsck 1.41.4 (27-Jan-2009)
    e2fsck 1.41.4 (27-Jan-2009)
    fsck.ext2: Superblock invalid, trying backup blocks...
    fsck.ext2: Bad magic number in super-block while trying to open /dev/store/filecache
    
    The superblock could not be read or does not describe a correct ext2
    filesystem.  If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>
    
    root@webos-device:/# fsck /dev/store/log
    fsck 1.41.4 (27-Jan-2009)
    e2fsck 1.41.4 (27-Jan-2009)
    /var/log: recovering journal
    fsck.ext3: unable to set superblock flags on /var/log
    
    root@webos-device:/# fsck /dev/store/media
    fsck 1.41.4 (27-Jan-2009)
    dosfsck 2.11, 12 Mar 2005, FAT32, LFN
    /dev/store/media: 13352 files, 26732/177129 clusters
    root@webos-device:/# fsck /dev/store/mojodb
    fsck 1.41.4 (27-Jan-2009)
    e2fsck 1.41.4 (27-Jan-2009)
    fsck.ext2: Superblock invalid, trying backup blocks...
    fsck.ext2: Bad magic number in super-block while trying to open /dev/store/mojodb
    
    The superblock could not be read or does not describe a correct ext2
    filesystem.  If the device is valid and it really contains an ext2
    filesystem (and not swap or ufs or something else), then the superblock
    is corrupt, and you might try running e2fsck with an alternate superblock:
        e2fsck -b 8193 <device>
    
    root@webos-device:/# fsck /dev/store/root
    fsck 1.41.4 (27-Jan-2009)
    e2fsck 1.41.4 (27-Jan-2009)
    /: recovering journal
    fsck.ext3: unable to set superblock flags on /
    
    root@webos-device:/# fsck /dev/store/swap
    fsck 1.41.4 (27-Jan-2009)
    fsck: fsck.swap: not found
    fsck: Error 2 while executing fsck.swap for /dev/store/swap
    root@webos-device:/# fsck /dev/store/update
    fsck 1.41.4 (27-Jan-2009)
    e2fsck 1.41.4 (27-Jan-2009)
    /var/lib/update: clean, 13/4096 files, 1166/4096 blocks
    root@webos-device:/# fsck /dev/store/var
    fsck 1.41.4 (27-Jan-2009)
    e2fsck 1.41.4 (27-Jan-2009)
    /var: recovering journal
    fsck.ext3: unable to set superblock flags on /var
    
    root@webos-device:/#
    Some results they were "fsck.ext3: unable to set superblock flags on /var" and are different of you results.

    After all of them them I typed these:

    Code:
    root@webos-device:/# lvm.static vgscan --ignorelockingfailure
      Reading all physical volumes.  This may take a while...
      Found volume group "store" using metadata type lvm2
    root@webos-device:/# lvm.static vgchange -ay --ignorelockingfailure
      8 logical volume(s) in volume group "store" now active
    root@webos-device:/# lvm.static vgremove store
    Do you really want to remove volume group "store" containing 8 logical volumes? [y/n]: y
    Do you really want to remove active logical volume "root"? [y/n]: y
      Logical volume "root" successfully removed
    Do you really want to remove active logical volume "var"? [y/n]: y
      Logical volume "var" successfully removed
    Do you really want to remove active logical volume "update"? [y/n]: y
    y  Logical volume "update" successfully removed
    Do you really want to remove active logical volume "log"? [y/n]: 
      Logical volume "log" successfully removed
    Do you really want to remove active logical volume "mojodb"? [y/n]: y
      Logical volume "mojodb" successfully removed
    Do you really want to remove active logical volume "filecache"? [y/n]: y
      Logical volume "filecache" successfully removed
    Do you really want to remove active logical volume "media"? [y/n]: y
      Logical volume "media" successfully removed
    Do you really want to remove active logical volume "swap"? [y/n]: y
      Logical volume "swap" successfully removed
      Volume group "store" successfully removed
    root@webos-device:/# lvm.static vgscan --ignorelockingfailure
      Reading all physical volumes.  This may take a while...
      Found volume group "store" using metadata type lvm2
    root@webos-device:/# lvm.static vgchange -ay --ignorelockingfailure
      8 logical volume(s) in volume group "store" now active
    root@webos-device:/# lvm.static vgcreate -s 8M store /dev/mmcblk0p15
      /dev/store: already exists in filesystem
      New volume group name "store" is invalid
      Run `vgcreate --help' for more information.
    root@webos-device:/# lvm.static vgscan --ignorelockingfailure
      Reading all physical volumes.  This may take a while...
      Found volume group "store" using metadata type lvm2
    root@webos-device:/# lvm.static vgchange -ay --ignorelockingfailure
      8 logical volume(s) in volume group "store" now active
    root@webos-device:/# lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
      Redundant stripes argument: default is 1
      Logical volume "root" already exists in volume group "store"
    root@webos-device:/# lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
      Redundant stripes argument: default is 1
      Logical volume "var" already exists in volume group "store"
    root@webos-device:/# lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
      Redundant stripes argument: default is 1
      Logical volume "update" already exists in volume group "store"
    root@webos-device:/# lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
      Redundant stripes argument: default is 1
      Logical volume "log" already exists in volume group "store"
    root@webos-device:/# lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
      Redundant stripes argument: default is 1
      Logical volume "mojodb" already exists in volume group "store"
    root@webos-device:/# lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
      Redundant stripes argument: default is 1
      Logical volume "filecache" already exists in volume group "store"
    root@webos-device:/# lvm.static lvcreate -l 573 -i 1 -M y --major 254 --minor 6 -n media store
      Redundant stripes argument: default is 1
      Logical volume "media" already exists in volume group "store"
    root@webos-device:/# lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
      Redundant stripes argument: default is 1
      Logical volume "swap" already exists in volume group "store"
    root@webos-device:/# lvm.static vgscan --ignorelockingfailure
      Reading all physical volumes.  This may take a while...
      Found volume group "store" using metadata type lvm2
    root@webos-device:/# lvm.static vgchange -ay --ignorelockingfailure
      8 logical volume(s) in volume group "store" now active
    root@webos-device:/# mkdosfs -f 1 -s 64 /dev/store/media
    mkdosfs 2.11 (12 Mar 2005)
    root@webos-device:/#
    Then reboot and everything was same (Apps, Pictures, sounds..)

    What can I do?.

    Thanks.
  11. #11  
    Huh. It does seem like your flash is "frozen", although I've never heard of it happening on a Pre3. On a TouchPad, yes, but not a Pre3.

    Next time you boot the phone normally (without memboot) and novaterm into the shell, let's see if you can write to the filesystem. First,

    Code:
    root@webos-device:/# cd ~
    ...then...
    Code:
    root@webos-device:/var/home/root# touch test.txt
    Code:
    root@webos-device:/var/home/root# ls -alh test.txt
    -rw-r--r--    1 root     root           0 Jun  6 21:38 test.txt
    root@webos-device:/var/home/root#
    MAMISHO likes this.
  12. #12  
    Also, another thing you can try that is non-destructive -

    Code:
    lvm.static pvck -v /dev/mmcblk0p15
    This runs a consistency check, kind of like fsck, on the physical volume that forms the basis of the volume groups. Here it is running on my TouchPad:

    Code:
    root@webos-device:/var/home/root# lvm.static pvck -v /dev/mmcblk0p14
        Creating directory "/var/lock/lvm"
        Scanning /dev/mmcblk0p14
      Found label on /dev/mmcblk0p14, sector 1, type=LVM2 001
      Found text metadata area: offset=4096, size=8450048
      Found text metadata area: offset=15244197888, size=8388608
        Found LVM2 metadata record at offset=15244300800, size=4096, offset2=0 size2=0
        Found LVM2 metadata record at offset=15244296704, size=4096, offset2=0 size2=0
    ...
    root@webos-device:/var/home/root#
    MAMISHO likes this.
  13. #13  
    Finally, if none of that works, you can try removing and re-creating the physical volume (pv). Here is part of what I did to revive a dead 64GB TouchPad from that other post I mentioned earlier:

    Code:
    lvm.static pvremove  /dev/mmcblk0p14
      Labels on physical volume "/dev/mmcblk0p14" successfully wiped
    Code:
    lvm.static pvcreate --verbose --zero y /dev/mmcblk0p14
    Code:
    lvm.static pvdisplay
      "/dev/mmcblk0p14" is a new physical volume of "29.09 GB"
      --- NEW Physical volume ---
      PV Name               /dev/mmcblk0p14
      VG Name               
      PV Size               29.09 GB
      Allocatable           NO
      PE Size (KByte)       0
      Total PE              0
      Free PE               0
      Allocated PE          0
      PV UUID               J2H1WK-N3KV-eEjK-mmH3-kqTT-cOcz-C0kbq5
    Last edited by George Mari; 06/07/2017 at 07:15 AM. Reason: typo
    MAMISHO likes this.
  14.    #14  
    Thank you so much for support. These are my results.

    Code:
    Last login: Mon Jun  5 23:23:48 on ttys001
    iMac:~ Developer$ novaterm
    
    root@EdwinHPPre3:/# cd ~
    root@EdwinHPPre3:/var/home/root# touch test.txt
    root@EdwinHPPre3:/var/home/root# ls -alh test.txt
    -rw-r--r--    1 root     root           0 Feb 14 14:21 test.txt
    root@EdwinHPPre3:/var/home/root# echo "hello HP pre 3" > test.txt
    root@EdwinHPPre3:/var/home/root# cat test.txt 
    hello HP pre 3
    
    root@EdwinHPPre3:/var/home/root# lvm.static pvck -v /dev/mmcblk0p15
        Creating directory "/var/lock/lvm"
        Scanning /dev/mmcblk0p15
      Found label on /dev/mmcblk0p15, sector 1, type=LVM2 001
      Found text metadata area: offset=4096, size=8450048
        Found LVM2 metadata record at offset=16896, size=3072, offset2=0 size2=0
        Found LVM2 metadata record at offset=14336, size=2560, offset2=0 size2=0
        Found LVM2 metadata record at offset=11776, size=2560, offset2=0 size2=0
        Found LVM2 metadata record at offset=9728, size=2048, offset2=0 size2=0
        Found LVM2 metadata record at offset=8192, size=1536, offset2=0 size2=0
        Found LVM2 metadata record at offset=6656, size=1536, offset2=0 size2=0
        Found LVM2 metadata record at offset=5632, size=1024, offset2=0 size2=0
      Found text metadata area: offset=7355367424, size=8421376
        Found LVM2 metadata record at offset=7355380224, size=3072, offset2=0 size2=0
        Found LVM2 metadata record at offset=7355377664, size=2560, offset2=0 size2=0
        Found LVM2 metadata record at offset=7355375104, size=2560, offset2=0 size2=0
        Found LVM2 metadata record at offset=7355373056, size=2048, offset2=0 size2=0
        Found LVM2 metadata record at offset=7355371520, size=1536, offset2=0 size2=0
        Found LVM2 metadata record at offset=7355369984, size=1536, offset2=0 size2=0
        Found LVM2 metadata record at offset=7355368960, size=1024, offset2=0 size2=0
    
    root@EdwinHPPre3:/var/home/root# lvm.static pvremove  /dev/mmcblk0p15
      Can't pvremove physical volume "/dev/mmcblk0p15" of volume group "store" without -ff
    
    root@EdwinHPPre3:/var/home/root# lvm.static pvremove  /dev/mmcblk0p15 -ff
    Really WIPE LABELS from physical volume "/dev/mmcblk0p15" of volume group "store" [y/n]? y
      WARNING: Wiping physical volume label from /dev/mmcblk0p15 of volume group "store"
      Can't open /dev/mmcblk0p15 exclusively - not removing. Mounted filesystem?
    
    root@EdwinHPPre3:/var/home/root# lvm.static pvcreate --verbose --zero y /dev/mmcblk0p15
      Can't initialize physical volume "/dev/mmcblk0p15" of volume group "store" without -ff
    
    root@EdwinHPPre3:/var/home/root# lvm.static pvcreate --verbose --zero y /dev/mmcblk0p15 -ff
    Really INITIALIZE physical volume "/dev/mmcblk0p15" of volume group "store" [y/n]? y
      Can't open /dev/mmcblk0p15 exclusively.  Mounted filesystem?
    
    root@EdwinHPPre3:/var/home/root# lvm.static pvdisplay
      --- Physical volume ---
      PV Name               /dev/mmcblk0p15
      VG Name               store
      PV Size               6.86 GB / not usable 22.66 MB
      Allocatable           yes 
      PE Size (KByte)       8192
      Total PE              875
      Free PE               1
      Allocated PE          874
      PV UUID               YhBXUt-gZS3-ETI4-i56F-aqhH-ho9k-3XMRxt
  15. #15  
    Ok, so NOW, if you haven't already, you can proceed with re-creating your volume group (lvm.static vgcreate) and logical volumes (lvm.static lvcreate)...
    MAMISHO and Mutoidi like this.
  16.    #16  
    ok, thanks I gonna try this weekend because and let you know my results. thanks again.
    Mutoidi likes this.

Similar Threads

  1. WTT: Palm Pre 2 for any unlocked Nexus device of recent vintage.
    By Davide-NYC in forum Marketplace
    Replies: 1
    Last Post: 03/23/2017, 08:48 PM
  2. WTB: Pre 3 back cover
    By Xeron in forum Marketplace
    Replies: 3
    Last Post: 03/02/2017, 11:43 PM
  3. Need help with fixing Original Palm Pre
    By ecksreturns in forum Palm Pre and Pre Plus
    Replies: 2
    Last Post: 01/23/2017, 07:27 PM
  4. Replies: 5
    Last Post: 01/03/2017, 06:18 PM
  5. Pre 2 change ESN/MEID
    By ipixi in forum Palm Pre 2
    Replies: 1
    Last Post: 11/16/2016, 12:53 PM

Posting Permissions