Results 1 to 7 of 7
Like Tree1Likes
  • 1 Post By creepingmee
  1.    #1  
    I am trying to resurrect my old pre2 and am having some trouble. I decided to doctor it because I think some patches went awry and even though I uninstalled them, they not all of the original files seemed to be reverted correctly...

    In any case, I grabbed the meta-doctor script and build a custom version of the webOS 2.2.4 doctor and tried to run it. At 8% the doctor said that the device had reset. Looking at the log, it appears there was some issue with the partitioning:

    got lvm static, running vgscan
    +++++runCommand /usr/sbin/lvm.static
    flushing and closing
    -----runCommand
    vgscan ran, running vgchange
    no LVVM
    Feb 18, 2015 4:37:12 PM com.palm.nova.installer.core.MountUtils readCurrentLvmValues
    WARNING: no LVVM
    This was followed by a bunch of java stack traces.


    So, I found this which said to format the usb partition, so I did. No luck.

    Then I tried to wipe and rebuild the LVM with a modified version of these instructions from xda dev that talk about rebuilding corrupted lvm on the touchpad (basically I changed /dev/mmcblk0p14 to /dev/mmcblk0p3).

    webOS doctor still gives the same errors. So I thought it might be because I was using a modified doctor, so I used the stock doctor for 2.2.4, 2.2.0, and 2.0.0, all gave the same problem.

    So now I have a phone that wont boot (loads first hp logo, not the pulsing one) or take a doctoring.

    It should be noted that I CAN memboot using the nova-installer...uImage from the various doctors and I can run gvscan and gvchange without error.


    So I'm stumped. Anyone have a bright idea?
  2.    #2  
    I think I want to try to manually partition the disk and configure the lvm layout.

    Would someone be willing to connect to their working pre2 and get a dump of the partition/volume info?

    Using novaterm you can get the partition table using:
    fdisk -l /dev/mmcblk0

    and the lvm layout with these three commands:
    lvm.static pvdisplay -m
    lvm.static vgdisplay
    lvm.static lvdisplay

    I think the output from those four commands would let me figure out how to rebuild...
    Last edited by zane9000; 02/20/2015 at 02:01 AM.
  3. #3  
    As far as I can tell, fdisk isn't available in novaterm. Not sure how to proceed there.
  4.    #4  
    Oh, really? Well, the output of the lvm.static commands would still be helpful.
  5. #5  
    ok here ya go:

    lvm.static pvdisplay -m

    File descriptor 13 (socket:[6190]) leaked on lvm.static invocation. Parent PID 2985: /bin/sh
    --- Physical volume ---
    PV Name /dev/mmcblk0p3
    VG Name store
    PV Size 14.80 GB / not usable 7.50 MB
    Allocatable yes
    PE Size (KByte) 8192
    Total PE 1893
    Free PE 3
    Allocated PE 1890
    PV UUID BZM6bt-GqQz-H1UH-YloU-7sc7-M1sv-VRlXxh

    --- Physical Segments ---
    Physical extent 0 to 56:
    Logical volume /dev/store/root
    Logical extents 0 to 56
    Physical extent 57 to 64:
    Logical volume /dev/store/var
    Logical extents 0 to 7
    Physical extent 65 to 66:
    Logical volume /dev/store/update
    Logical extents 0 to 1
    Physical extent 67 to 69:
    Logical volume /dev/store/log
    Logical extents 0 to 2
    Physical extent 70 to 87:
    Logical volume /dev/store/mojodb
    Logical extents 0 to 17
    Physical extent 88 to 104:
    Logical volume /dev/store/filecache
    Logical extents 0 to 16
    Physical extent 105 to 1876:
    Logical volume /dev/store/media
    Logical extents 0 to 1771
    Physical extent 1877 to 1889:
    Logical volume /dev/store/swap
    Logical extents 0 to 12
    Physical extent 1890 to 1892:
    FREE

    lvm.static vgdisplay

    File descriptor 13 (socket:[6190]) leaked on lvm.static invocation. Parent PID 2985: /bin/sh
    --- Volume group ---
    VG Name store
    System ID
    Format lvm2
    Metadata Areas 2
    Metadata Sequence No 9
    VG Access read/write
    VG Status resizable
    MAX LV 0
    Cur LV 8
    Open LV 7
    Max PV 0
    Cur PV 1
    Act PV 1
    VG Size 14.79 GB
    PE Size 8.00 MB
    Total PE 1893
    Alloc PE / Size 1890 / 14.77 GB
    Free PE / Size 3 / 24.00 MB
    VG UUID zczxNn-6biD-1SWu-pflF-6S91-Sn4K-2ewv1t

    lvm.static lvdisplay

    File descriptor 13 (socket:[6190]) leaked on lvm.static invocation. Parent PID 2985: /bin/sh
    --- Logical volume ---
    LV Name /dev/store/root
    VG Name store
    LV UUID dJklY2-cMvW-ldTX-k4re-2wnY-0CAz-w0ZQLE
    LV Write Access read/write
    LV Status available
    # open 1
    LV Size 456.00 MB
    Current LE 57
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Persistent major 254
    Persistent minor 0
    Block device 254:0

    --- Logical volume ---
    LV Name /dev/store/var
    VG Name store
    LV UUID enELbH-jR9G-ifFJ-mNVs-99Rh-jTGP-NcOZ9W
    LV Write Access read/write
    LV Status available
    # open 1
    LV Size 64.00 MB
    Current LE 8
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Persistent major 254
    Persistent minor 1
    Block device 254:1

    --- Logical volume ---
    LV Name /dev/store/update
    VG Name store
    LV UUID Jukoq2-U3cE-QlZl-r6vD-plV3-qy52-6QqBgF
    LV Write Access read/write
    LV Status available
    # open 0
    LV Size 16.00 MB
    Current LE 2
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Persistent major 254
    Persistent minor 2
    Block device 254:2

    --- Logical volume ---
    LV Name /dev/store/log
    VG Name store
    LV UUID SOy2TT-pLQn-Mubq-IpJh-enzX-KWl0-98tTes
    LV Write Access read/write
    LV Status available
    # open 1
    LV Size 24.00 MB
    Current LE 3
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Persistent major 254
    Persistent minor 3
    Block device 254:3

    --- Logical volume ---
    LV Name /dev/store/mojodb
    VG Name store
    LV UUID H9xceY-7W78-YwRT-Sxlq-6joi-qVYY-Lcj1xf
    LV Write Access read/write
    LV Status available
    # open 1
    LV Size 144.00 MB
    Current LE 18
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Persistent major 254
    Persistent minor 4
    Block device 254:4

    --- Logical volume ---
    LV Name /dev/store/filecache
    VG Name store
    LV UUID 7dEkgb-DYT4-Z7UF-m1VE-4f6g-BGAO-5ITtsk
    LV Write Access read/write
    LV Status available
    # open 1
    LV Size 136.00 MB
    Current LE 17
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Persistent major 254
    Persistent minor 5
    Block device 254:5

    --- Logical volume ---
    LV Name /dev/store/media
    VG Name store
    LV UUID z076am-6hBd-Vv07-VtK8-z2Vw-yJGy-R5Xe27
    LV Write Access read/write
    LV Status available
    # open 1
    LV Size 13.84 GB
    Current LE 1772
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Persistent major 254
    Persistent minor 6
    Block device 254:6

    --- Logical volume ---
    LV Name /dev/store/swap
    VG Name store
    LV UUID m3n33l-QdYC-36Sw-uAIq-qDmH-3Jlz-InPBeD
    LV Write Access read/write
    LV Status available
    # open 1
    LV Size 104.00 MB
    Current LE 13
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Persistent major 254
    Persistent minor 7
    Block device 254:7

    Hope this helps!!
    Preemptive likes this.
  6.    #6  
    Awesome, thanks a lot! Hopefully I can get this thing rebuilt over the weekend.
  7.    #7  
    So I am pretty sure it was a hardware problem causing the phone to disconnect during vgscan for some reason. I was able to manually rebuild the filesystem, send the rootfs image over using novacom, unpack the image onto the newly built filesystem, and get webOS running again.

    I am convinced that my phone has a hardware issue because even after I installed webOS on a cleanly partitioned disk, the doctor STILL would not run.

    So if someone has issues with their phone disconnecting at 8% while using the doctor, there IS a solution, just a messy one. If anyone needs help doing it, I would be happy to lend a hand.

Similar Threads

  1. Where can i find webOS doctor 1.3 or 1.2?
    By rfrloureiro in forum Palm Pre and Pre Plus
    Replies: 5
    Last Post: 06/08/2012, 02:32 PM
  2. Can Someone Help Me Find WebOS Doctor 1.3.5?
    By cyberstven in forum Palm Pre and Pre Plus
    Replies: 4
    Last Post: 03/26/2010, 12:15 PM
  3. Doctor won't find pre
    By djmcgee in forum Palm Pre and Pre Plus
    Replies: 17
    Last Post: 03/04/2010, 10:56 AM
  4. cant find webos doctor in repair utility
    By Lost Prototype in forum Palm Pre and Pre Plus
    Replies: 5
    Last Post: 10/12/2009, 09:55 AM

Posting Permissions