yashsingh1/xdaforums huggingface dataset:
[TouchPad General] stace:
My problem can be summed up here: http://xdaforums.com/showthread.php?t=1932168

Shorter story is that I don't seem to have any volumes, so things fail. Any tips?

root@webos-device:/# lvm.static vgscan --ignorelockingfailure

Reading all physical volumes. This may take a while...

root@webos-device:/# lvm.static vgchange -ay --ignorelockingfailure

root@webos-device:/# lvm.static vgremove store

Volume group "store" not found

root@webos-device:/# lvm.static vgscan --ignorelockingfailure

Reading all physical volumes. This may take a while...

root@webos-device:/# lvm.static vgchange -ay --ignorelockingfailure

root@webos-device:/# lvm.static vgcreate -s 8M store /dev/mmcblk0p14

No physical volume label read from /dev/mmcblk0p14

/dev/mmcblk0p14 not identified as an existing physical volume

Unable to add physical volume '/dev/mmcblk0p14' to volume group 'store'.
[TouchPad General] Jondoeiowa:
already running custom rom

The run commands are what aren't working. When I enter in my computer command mode I can't get it to accept any of the commands typed out at the beginning
[TouchPad General] stace:
The lvm.static commands? Sounds like you're not in the right mode. What's on the screen of your touchpad while you're typing those commands?
[TouchPad General] Jondoeiowa:
Commands

II. What to do

1) Install Novacom and extract Novaterm. (Both done no problem)

2) Open a command prompt and navigate to your Palm, Inc folder (usually \Program Files\Palm, Inc) (did this just through explorer)

3) Move the recovery uImage to the Palm, Inc folder. (did through explorer)

4) Boot your Touchpad into recovery (Power + Volume Up from power off) (boots up fine to just the USB symbol showing it in safe mode)

5) In that command prompt, run ( novacom boot mem:// < nova-installer-image-topaz.uImage ) (without the parenthesis) (this is where I get stuck, the command won't work for me, don't know if i'm entering it wrong)

6) Once run, all you'll see on the Touchpad is the HP logo. This is good. Now open Novaterm and hit Connect

7) If you see a prompt that says something like "root@webOS device" this is good, now run these commands IN ORDER and these commands are CASE SENSITIVE
[TouchPad General] stace:
What is the exact error?
[TouchPad General] vsp2979:
I am having exact same issue, "Volume group "store" not found:" Cannot restore with Novacom or webos(multiple versions).

Any guidance is appreciated.
[TouchPad General] vsp2979:
Any suggestions?
[TouchPad General] rr5678:
It's not booting to that recovery image? Does it display an error or do you just see nothing. Sometimes, it may take a while. I'd say leave it plugged in for around 10 minutes, just to see what happens.

can you create a volume group? Or is the volume group there but then it says it isn't?
[TouchPad General] brandonmarkb:
I'm also having this same error. Attempting to mount -a yields:

"mount: mounting /dev/mapper/store-var on /var failed: No such file or directory

mount: mounting /dev/mapper/store-log on /var/log failed: No such file or directory

mount: mounting /dev/mapper/store-media on /media/internal failed: No such file or directory"

also pvscan and lvscan:

"root@webos-device:/# pvscan

/bin/sh: pvscan: not found

root@webos-device:/# lvscan

/bin/sh: lvscan: not found"

This is crazy. I did a wipe in TWRP before installing AOKP, thinking that my WebOS partition would be safe (as everything I've read said it should be). But it has completely wiped everything. I can load TWRP, and in the file manager I only have access to the boot partition, as well as for mounting. It seems that everything else has just vanished.

Any help would be greatly appreciated!
[TouchPad General] rr5678:
When exactly are you trying to mount this? And did you try the 3.0.0 doctor?
[TouchPad General] brandonmarkb:
I've tried the 3.0 doctor, yes. All of them get me the same result, which is the 8% reboot and fail.

In trying to mount it I've done a few things, I've tried to mount usb using twrp in the beginning to see what that would get me, if perhaps I could just flash a Rom and fix it. The only mountable partition is the boot one. In fact, when I try various options in twrp (copy log file to sdcard, backup, etc) to see what's there, everything is reported as missing.

The mount commands I posted above were during a novaterm session after membooting. I've found other posts in various sites from people with a similar situation whose mount -a results were much better. As far as I can tell, none of the expected partitions-log, etc-are there.
[TouchPad General] stace:
I can't create a volume group. It's like it's just not able to see the "disk".

root@webos-device:/# lvm.static vgscan --ignorelockingfailure
Reading all physical volumes. This may take a while...
root@webos-device:/# lvm.static vgchange -ay --ignorelockingfailure
root@webos-device:/# lvm.static vgremove store
Volume group "store" not found
root@webos-device:/# lvm.static vgscan --ignorelockingfailure
Reading all physical volumes. This may take a while...
root@webos-device:/# lvm.static vgchange -ay --ignorelockingfailure
root@webos-device:/# lvm.static vgcreate -s 8M store /dev/mmcblk0p14
No physical volume label read from /dev/mmcblk0p14
/dev/mmcblk0p14 not identified as an existing physical volume
Unable to add physical volume '/dev/mmcblk0p14' to volume group 'store'.
[TouchPad General] Domvillan:
This worked like a charm!
[TouchPad General] chicle_11:
Please sticky this

Moderator, please sticky this, it's got some great information.
[TouchPad General] sstar:
Which post worked like a charm for you .
[TouchPad General] chicle_11:
I was having the same problem and this worked for me.
[TouchPad General] SCWells72:
Same problem here. Did you guys ever find a solution?

UPDATE: I found a solution! Check out my posting here. I think this should be added to the first posting for those who have run into this complete corruption of the LVM that has previously been perceived as requiring a hardware repair. I hope this helps others!
[TouchPad General] null0pointer:
I've been racking my brain for the past few days trying to get this 16GB TouchPad working. I've been running WebOS Doctor 3.0 and it fails at 12%. I've attemped numerous times to delete the partitions, but it never "takes". As soon as I re-scan, it finds the partitions once more. I've tried to repair each and everyone and that also does not work. I've searched and searched, but never seemed to find a solution to the partitions not actually deleting.

Any ideas would be greatly appreciated.

Log:

root@webos-device:/dev/mapper# lvm.static vgscan --ignorelockingfailure

Reading all physical volumes. This may take a while...

Found volume group "store" using metadata type lvm2

root@webos-device:/dev/mapper# lvm.static vgchange -ay --ignorelockingfailure

8 logical volume(s) in volume group "store" now active

root@webos-device:/dev/mapper# 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:/dev/mapper# lvm.static vgscan --ignorelockingfailure

Reading all physical volumes. This may take a while...

Found volume group "store" using metadata type lvm2

root@webos-device:/dev/mapper# lvm.static vgchange -ay --ignorelockingfailure

8 logical volume(s) in volume group "store" now active

root@webos-device:/dev/mapper# lvm.static vgcreate -s 8M store /dev/mmcblk0p14

/dev/store: already exists in filesystem

New volume group name "store" is invalid

Run `vgcreate --help' for more information.
[TouchPad General] null0pointer:
Anyone have any suggestions at all? I know I'm out of warranty now, is it a brick now?
[TouchPad General] SCWells72:
I don't know if it'll help at all, but did you see the link I added above that basically wipes out the LVM volume info and rebuilds it enough to allow things to work decently again (at least in my case)? Have you tried those steps? If not, I'd suggest giving them a shot before throwing in the towel!
[TouchPad General] null0pointer:
So when using the "guide" (Factory condition restoration), when exactly should I add the two new commands? Before or after attempting to delete the volume? Also, you are basically recreating this new partition, what command did you use to actually delete it?
[TouchPad General] SCWells72:
Sorry, yeah...I could've been more clear about that. The two commands I added should happen before all of the listed commands. That basically gets the physical volume back into a good state by overwriting it with blanks so that it doesn't appear to exist and then recreating it. Then the rest of the listed commands should work...again, assuming that you have a similar problem to the one I faced.
[TouchPad General] null0pointer:
First command actually executed, second command errored as follows:

root@webos-device:/# dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000

1000+0 records in

1000+0 records out

1024000 bytes (1000.0KB) copied, 0.013370 seconds, 73.0MB/s

root@webos-device:/# lvm.static pvcreate /dev/mmcblk0p14

Can't initialize physical volume "/dev/mmcblk0p14" of volume group "store" without -ff

I then tried adding "-ff" and it errors as follows:

root@webos-device:/# lvm.static pvcreate /dev/mmcblk0p14 -ff

Really INITIALIZE physical volume "/dev/mmcblk0p14" of volume group "store" [y/n]? y

Can't open /dev/mmcblk0p14 exclusively. Mounted filesystem?

So, then I tried:

root@webos-device:/# dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000

1000+0 records in

1000+0 records out

1024000 bytes (1000.0KB) copied, 0.013370 seconds, 73.0MB/s

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 pvcreate /dev/mmcblk0p14 -ff

Really INITIALIZE physical volume "/dev/mmcblk0p14" of volume group "store" [y/n

]? y

WARNING: Forcing physical volume creation on /dev/mmcblk0p14 of volume group "

store"

Physical volume "/dev/mmcblk0p14" successfully created

...and when I went to the first step of the "Factory restore", it scanned and yet again found the "store" volume.
[TouchPad General] SCWells72:
Can you try:

lvm.static vgremove store
dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static pvcreate /dev/mmcblk0p14
[TouchPad General] brandonmarkb:
I can't thank you enough for those 2 extra commands. I was able to get through and run the original batch of commands without a problem. I'm now waiting for my TP to charge enough to run the 3.0 doctor. I'm still not out of the woods yet, but I feel like I'm definitely getting there. I'll update once I get enough charge.

But regardless, thank you, thank you. I had given this thing up for a brick, but now there's some hope. :)

EDIT/UPDATE: This totally worked! Thanks so much for linking to the post. You saved my TouchPad. Looking at WebOS, and planning on installing Android again. My cautionary tale, never wipe in TWRP, or try and install AOKP over CM9 in TWRP. Doing this again I would find a different way.
[TouchPad General] SCWells72:
Sorry, I had a typo in my recommendation. I meant to recommend you try this (augmenting vgremove with some additional debugging flags for better diagnostics):

lvm.static vgremove -d -v store
dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static vgcreate -d -v -s 8M store /dev/mmcblk0p14

The -d option is to provide debug into and the -v option is to give verbose output. Between the two we should at least be able to see what it thinks it's doing!
[TouchPad General] null0pointer:
And here's the latest:

root@webos-device:/# lvm.static vgremove -d -v store
Using volume group(s) on command line
Finding volume group "store"
Do you really want to remove volume group "store" containing 8 logical volumes?
[y/n]: y
Archiving volume group "store" metadata (seqno 11).
Found volume group "store"
Found volume group "store"
Releasing logical volume "root"
Creating volume group backup "/var/lib/lvm/backup/store" (seqno 12).
Logical volume "root" successfully removed
Archiving volume group "store" metadata (seqno 12).
Found volume group "store"
Found volume group "store"
Releasing logical volume "var"
Creating volume group backup "/var/lib/lvm/backup/store" (seqno 13).
Logical volume "var" successfully removed
Archiving volume group "store" metadata (seqno 13).
Found volume group "store"
Found volume group "store"
Releasing logical volume "update"
Creating volume group backup "/var/lib/lvm/backup/store" (seqno 14).
Logical volume "update" successfully removed
Archiving volume group "store" metadata (seqno 14).
Found volume group "store"
Found volume group "store"
Releasing logical volume "log"
Creating volume group backup "/var/lib/lvm/backup/store" (seqno 15).
Logical volume "log" successfully removed
Archiving volume group "store" metadata (seqno 15).
Found volume group "store"
Found volume group "store"
Releasing logical volume "mojodb"
Creating volume group backup "/var/lib/lvm/backup/store" (seqno 16).
Logical volume "mojodb" successfully removed
Archiving volume group "store" metadata (seqno 16).
Found volume group "store"
Found volume group "store"
Releasing logical volume "filecache"
Creating volume group backup "/var/lib/lvm/backup/store" (seqno 17).
Logical volume "filecache" successfully removed
Archiving volume group "store" metadata (seqno 17).
Found volume group "store"
Found volume group "store"
Releasing logical volume "media"
Creating volume group backup "/var/lib/lvm/backup/store" (seqno 18).
Logical volume "media" successfully removed
Archiving volume group "store" metadata (seqno 18).
Found volume group "store"
Found volume group "store"
Releasing logical volume "swap"
Creating volume group backup "/var/lib/lvm/backup/store" (seqno 19).
Logical volume "swap" successfully removed
Archiving volume group "store" metadata (seqno 19).
Removing physical volume "/dev/mmcblk0p14" from volume group "store"
Volume group "store" successfully removed

root@webos-device:/# dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
1000+0 records in
1000+0 records out
1024000 bytes (1000.0KB) copied, 0.313169 seconds, 3.1MB/s

root@webos-device:/# lvm.static vgcreate -d -v -s 8M store /dev/mmcblk0p14
A volume group called 'store' already exists.

Perhaps it's the backup that it's creating that's causing the issue of it never really being deleted?
[TouchPad General] cschepers:
Mine is doing the same thing, and has been for eight months or so, every time I've tried to remove that volume group. Thanks for the mentioning the debug/verbose flags on the lvm commands.. I don't know why I'd never thought to look for those before. :mad: More pieces of the puzzle!
[TouchPad General] SCWells72:
Yeah, this is definitely pushing the boundaries of my knowledge on these volume management utilities. However, I did Google a bit more and found some references to entries in /etc/lvmtab possibly causing this type of issue. After vgcreate successfully completes, can you look at the contents of that file and see if for some reason it didn't remove the entry for 'store'? If it didn't, you might try removing it yourself (back the file up first!) and trying these steps again.

Also, vgremove does support a '-y' flag that will keep you from having to confirm each removal.

Let us know!
[TouchPad General] geomonroe:
bricked?
[TouchPad General] geomonroe:
root@webos-device:/# lvm.static vgcreate -s 8M store /dev/mmcblk0p14

root@webos-device:/# lvm.static vgcreate -s 8M store /dev/mmcblk0p14

No physical volume label read from /dev/mmcblk0p14

root@webos-device:/# lvm.static vgcreate -s 8M store /dev/mmcblk0p14

No physical volume label read from /dev/mmcblk0p14

/dev/mmcblk0p14 not identified as an existing physical volume

root@webos-device:/# lvm.static vgcreate -s 8M store /dev/mmcblk0p14

No physical volume label read from /dev/mmcblk0p14

/dev/mmcblk0p14 not identified as an existing physical volume

Unable to add physical volume '/dev/mmcblk0p14' to volume group 'store'.

do i have to create store first and if so is that mkdir command.

dont know android commands, please advise
[TouchPad General] rr5678:
It seems as if there's a solution to that "store" problem now

http://xdaforums.com/showpost.php?p=33658969&postcount=4
[TouchPad General] stace:
You are my hero. Thank you so much, my Touchpad is useful again!
[TouchPad General] geomonroe:
path ?

can you give the path to where you add code
[TouchPad General] rr5678:
I did not even see this post. I will add it to the first post as soon as possible. And don't worry, I'll give credit where it's due.
[TouchPad General] jerry0000:
I have a 16GB, and was told insufficient extend at this step:

lvm.static lvcreate -l 1618 -i 1 -M y --major 254 --minor 6 -n media store

Any ideas?

To add:

"Insufficient free extents (1565) in volume group store: 1618 required"

So seems my touchpad have slightly smaller storage???

In order to run the last logical volume creation, seems I have to change 1618 to 1501? as 64 was required for the last logical volume swap.

To add 2:

I changed the 1618 to 1501, and it worked. So seems I got a bad deal -- my touchpad has less storage????
[TouchPad General] geomonroe:
bricked?

[{SOLVED}]

Ran

1. http://xdaforums.com/showthread.php?t=1426244

2. http://xdaforums.com/showthread.php?t=1483066&page=3 (did not go to #27 post)

3. http://xdaforums.com/showthread.php?p=33976038#post33976038 (followed #157 post)

PS. YOU GUYS AND GALS ARE THE BBBBBBOOOOOOOOOOMMMMMMMMMMMBBBBBBBBBBBBBB!!!!!!!!!!!!!!!!!!
[TouchPad General] AniWarlock:
I have the same..

dd can't help, cause we all have read-only memory and this is the problem.
[TouchPad General] rr5678:
I've been looking into that whole read-only issue, but until it happens to my device (which I'm hoping it won't), I can't do much else I'm afraid.
[TouchPad General] emblem01:
camera problems

Hi there, im having camera problems with my touchpad it works for a few seconds then shuts off and i was thinking of sending it in for repair but i have android cm9 nightly installed. Will this method erase everything to factory condition where hp won't detect android and void my warranty? I kind of lost hope but then i found this threat i thought that maybe i can send it to hp even though i installed android...
[TouchPad General] rr5678:
After you follow these instructions, your TouchPad won't even LOOK like it ever had Android on it.
[TouchPad General] emblem01:
Thanks soo much
[TouchPad General] beetmonger:
This worked great for me, thanks. I had to make two adjustments:

1. in step 1, i had to point the novacom installer to use the WebOS Doctor jar file, otherwise it would hang on "initializing."

2. I kept getting "unhandled exception" errors with novaterm, but tried the solution mentioned in post #104 and it worked just fine.
[TouchPad General] Dalper5:
I'm having the same issue with the device being set in read only mode, has anyone been able to make progress on a fix?

Quick summary:

More info:
[TouchPad General] buddiec:
bricked touch pad i think

Hello guys hope you can help me in my novice but love to experiment phase. I have the same issue that Geomonroe had in his rootzwiki thread, I tried his fix and I can get in and input the code into novaterm, the issue is I don't have the store drive or folder it is not found so the other commands after that code does nothing how can I get the store folder in so I can re partition run the doc and then get cm9 back on my touch pad just ordered a nexus 10 but still love the touch pad any help is greatly apprieciated

went from cm9 nightly to AOPK.

bootloader is there can only access TWRP.

TWRP, error /sd card will not mount.

os doctor failed restore.

nothing but TWRP accessible from bootloader.

file manager shows all files empty. no backups accessible.

is this recoverable?
[TouchPad General] parkway233:
Also having the same issue, Store will no delete

I am also stuck with this inability to delete the "store. I have tried numerous solutions and I find I have the exactly same problem as Dalper5 and null0pointer. My results are exactly the same. If anyone comes up with a solution, please post. Try as I might, I can not get rid of the "store" and thus am unable to create it. I get the dreaded message " A volume group called 'store' already exists". Nothing seems to work. Anyone out there with some expert Linux and Touchpad experience that can help us solve this problem?? Please help. :confused:
[TouchPad General] SCWells72:
Have you guys tried the extra steps I documented here?

http://xdaforums.com/showpost.php?p=33658969&postcount=4

That resolved the "store" issue for me.
[TouchPad General] parkway233:
No such luck, but thanks

Thanks for the prompt reply SCWells72. I was all jazzed when I saw your posting and tried that, but no luck. I had the same issue as Dalper5 notes in post #170. Requires -ff on one line and it still doesn't allow me to delete the store. My results are the exact same as posted in #170.:(
[TouchPad General] rr5678:
Try warranty exchanging.......unless you've installed Android. Sounds like that read only issue and it seems there's no solution for that. I would try, but mine works. (hopefully I didn't just ruin my luck)
[TouchPad General] parkway233:
Read only why my touchpad???

I agree that it does seem to be a read only issue, but what I don't understand is why this particular touchpad is read only and others, like yours, are not. I would hope that there must be some way to take it out of read-only status....or why did it get in read-only status in the first place?? Again seems odd that what would work for yours doesn't work for mine, but I was unlucky enough to somehow have it stuck in read only. Does seem to be the case, but maybe there is someone out there with some extensive Linux? or Touchpad? programming experience that can help me? Jscullins? Jason Robitaille? Either that or if I could find some site to just install Android with out bothering with the re-boot loop in WebOS. The problem is I can't access the touchpad through my computer via the USB cable, so I am stuck there also. Frustrating that WebOS Doctor gets stuck at 12% and there seems to be nothing I can do about getting it up and running again.:(
[TouchPad General] rr5678:
You aren't the only one with that problem. Others have it too, and the cause is unknown.
[TouchPad General] poisonousjuice:
You can put me on that list of users with 'read only' problem. I am experiencing exactly what null0pointer documented but I'm too noobish in this area to come up with a solution.
[TouchPad General] ScottBroker:
I cannot get the terminal to work. How do You load novaterm
[TouchPad General] ScottBroker:
How do I "Run webos Doctor?"

It is a zip file. What do I do to start it????
[Android Q&A, Help & Troubleshooting] Scumbag Inc.:
I just bought a Transformer Prime and am going to be putting it into a portfolio with the dock on the right. Unfortunately this means apps that are native portrait will open upside down.