Results 1 to 8 of 8
  1.    #1  
    Hey all,
    My TouchPad came with a problem out of the box which keeps me from successfully repairing it using WebOS Doctor or installing CM7.
    My TouchPad goes to the language selection screen and all files keep coming back if I try deleting them. Update also fails.
    WebOS Doctor fails at 8% where it fails unmounting /dev/mapper/store-log
    Others have solved it by nuking the volume group store, and creating the logical volumes again.
    However, I know of only two ways to get terminal access, using nova boot image in the WebOS Doctor .jar or the developer mode in WebOS.
    When I try removing the volume group, it says it did it, yet I can do it again, and again, and check for it, and its still there.

    ln: /var/luna/preferences/localtime: File exists
    root@webos-device:/# lvm.static vgremove store
    Do you really want to remove volume group "store" containing 8 logical volumes? [y/n]: y
    Logical volume "root" successfully removed
    Logical volume "var" successfully removed
    Logical volume "update" successfully removed
    Logical volume "log" successfully removed
    Logical volume "mojodb" successfully removed
    Logical volume "filecache" successfully removed
    Logical volume "media" successfully removed
    Logical volume "swap" successfully removed
    Volume group "store" successfully removed
    root@webos-device:/# lvm.static vgremove store
    Do you really want to remove volume group "store" containing 8 logical volumes? [y/n]: y
    Logical volume "root" successfully removed
    Logical volume "var" successfully removed
    Logical volume "update" successfully removed
    Logical volume "log" successfully removed
    Logical volume "mojodb" successfully removed
    Logical volume "filecache" successfully removed
    Logical volume "media" successfully removed
    Logical volume "swap" successfully removed
    Volume group "store" successfully removed
    root@webos-device:/# lvm.static vgscan
    Reading all physical volumes. This may take a while...
    Found volume group "store" using metadata type lvm2
    root@webos-device:/#

    So basically the system is somehow write protected.
    I even tried a desperate move:

    root@webos-device:/# dd if=/dev/zero of=/dev/mmcblk0
    dd: writing '/dev/mmcblk0': Input/output error
    2363625+0 records in
    2363624+0 records out
    1210175488 bytes (1.1GB) copied, 255.889841 seconds, 4.5MB/s
    root@webos-device:/# cat /proc/partitions
    major minor #blocks name
    179 0 15550464 mmcblk0
    179 1 102400 mmcblk0p1
    179 2 500 mmcblk0p2
    179 3 1500 mmcblk0p3
    179 4 1 mmcblk0p4
    179 5 500 mmcblk0p5
    179 6 750 mmcblk0p6
    179 7 2500 mmcblk0p7
    179 8 10240 mmcblk0p8
    179 9 1500 mmcblk0p9
    179 10 3072 mmcblk0p10
    179 11 3072 mmcblk0p11
    179 12 4096 mmcblk0p12
    179 13 32768 mmcblk0p13
    179 14 14895104 mmcblk0p14
    root@webos-device:/#

    I get an I/O error trying to DD into the block device representing device's flash! However the size of the block device corresponds to capacity of my TouchPad (16GB).

    I tried also tried to nova boot ACMEInstaller, but it eventually segfaults, and does not appear to have a console I could connect to.

    Guys, help me wipe this thing and create new partition/volume structure. Help is much appreciated.
  2. #2  
    Did you try the steps listed on this page?
    How To Recover - WebOS Internals
  3.    #3  
    Quote Originally Posted by alex80386 View Post
    Did you try the steps listed on this page?
    How To Recover - WebOS Internals
    Yes, and unfortunately nothing gets written when I do

    mkdosfs -f 1 -s 64 /dev/store/media

    It still has files if I mount it. Its like the device is write protected, yet in most cases the system pretends to write instead of giving any obvious errors.
  4. #4  
    Quote Originally Posted by r00tb33r View Post
    Yes, and unfortunately nothing gets written when I do

    mkdosfs -f 1 -s 64 /dev/store/media

    It still has files if I mount it. Its like the device is write protected, yet in most cases the system pretends to write instead of giving any obvious errors.
    I have the same error and webos don't boot. help me!!!!
  5. alan sh's Avatar
    Posts
    766 Posts
    Global Posts
    913 Global Posts
    #5  
    You may have a blown memory controller which leaves the memory in read-only mode. It's been discussed many times before - solution is to return it to HP for repair.

    Alan
  6. #6  
    Quote Originally Posted by alan sh View Post
    You may have a blown memory controller which leaves the memory in read-only mode. It's been discussed many times before - solution is to return it to HP for repair.

    Alan

    now that does not create new partitions. no way to make these partitions can be created?



    Ahora entiendo
  7.    #7  
    I never found a solution. It was probably a hardware defect. I sent it in for repair and my unit came back refurbished with another board.

    That was like what, 4 years ago? I played around with CM that was in early state. I was disappointed by the devices weight, so I sold it a couple weeks later.
  8. #8  
    Quote Originally Posted by r00tb33r View Post
    I never found a solution. It was probably a hardware defect. I sent it in for repair and my unit came back refurbished with another board.

    That was like what, 4 years ago? I played around with CM that was in early state. I was disappointed by the devices weight, so I sold it a couple weeks later.
    Thank you. Here in Mexico there is where I think repaired. I give my team dead. Shame.

    Enviado desde mi GT-I9500 mediante Tapatalk

Posting Permissions