webOS Nation Forums >  Homebrew >  WebOS Internals > WebOS Doctor - 12% Issue - Fixed!!!
WebOS Doctor - 12% Issue - Fixed!!!
  Reply
Like Tree21Likes

 
Thread Tools Display Modes
Old 08/31/2011, 01:39 AM   #1 (permalink)
Member
 
Posts: 19
It seems that this particular issue is revolving around an issue with "resizefat /dev/mapper/store-media" and the fact that the fat size is different than the backup.

I did a bit of research and came up with the following solution:

Run WebOS Doctor via CMD line "java -jar webosdoctorp302hstnhwifi.jar"

When the Dr. hangs up at 12% open novaterm and connect to your device

Then type the following command:

dosfsck -r /dev/mapper/store-media

And follow the prompts to correct the fat size to the backup (I believe I chose option 2 and then restore to backup and then 'Y')

Now put your tablet back into recovery mode and re-run WebOS Doctor. The error where it is hanging up should be gone and the system will flash completely.


(Comments on attempts appreciated)

OK - I had an issue after running webos doc 3.0.2 so I ran 3.0.0 - after it finished I had to plug the tablet into a power outlet and let it charge for a bit before it let me set up the system. It was hung up at the stupid HP splash screen for maybe 5-10 minutes but once it charged I got the prompt to select a language.

-I'd appreciate someone else trying this work around to verify. I'd hate for it to only work on mine

Last edited by onebadtaz; 08/31/2011 at 02:09 AM. Reason: More info... Again...
onebadtaz is offline   Reply With Quote
Liked by Rnp, nyrath, slayerpsp and 8 others like this.
Old 08/31/2011, 01:55 AM   #2 (permalink)
Moderator

 
sledge007's Avatar
 
Posts: 6,335
Nice work! I suggest getting in touch with webOS Internals so they can check it out and add it to their wiki. RWhitby here or @webosinternals on Twitter.

Hopefully, for many involved, that is THE be all-end all cure. Frustrating, for many of us sitting on the sidelines, who've used the Doctor many, MANY times without hassle (aside from using it of course), and not being of much help.
sledge007 is offline   Reply With Quote
Old 08/31/2011, 04:02 AM   #3 (permalink)
Member
 
Posts: 46
Darn you posted this right after I went to the UPS store to send my touchpad back to be replaced.. haha oh well hopefully this works so if my new one does the same thing I'll have a fix!
Jace985 is offline   Reply With Quote
Old 08/31/2011, 04:19 AM   #4 (permalink)
Member
 
Posts: 4
Hey! This is great news. I'm living abroad and did not want to have to ship the touchpad back.

I have a quick questions because I am not so computer literate. Then I don't understand when you say "When the device hangs up, open Noveterm and connect your device." First, it hangs up but goes into a never ending loop of messages scrolling in the comand window. How do I stop this? How do I open novaterm, and wouldn't my device already be connected?

Thank you so much for your help!

BEst regards from Norway

Gergey

Last edited by gergey; 08/31/2011 at 04:36 AM.
gergey is offline   Reply With Quote
Old 08/31/2011, 05:27 AM   #5 (permalink)
Member
 
Posts: 19
novaterm is a separate program that lets you modify the webOS once webOS doctor reaches 12%. When you load novaterm it has a button where you connect your device. Then you enter the sequence into novaterm. Granted this only works if your webOS doctor is hanging up at 12% and the log is actually stopping at fatresize /dev/mapper/store-media. That is the problem I solved because it was the one I had to work with :-)

Last edited by onebadtaz; 08/31/2011 at 09:19 AM. Reason: Not resident.. fatresize - Stupid auto correct!
onebadtaz is offline   Reply With Quote
Old 08/31/2011, 05:41 AM   #6 (permalink)
Member
 
mbudden's Avatar
 
Posts: 50
Quote:
Originally Posted by gergey View Post
Hey! This is great news. I'm living abroad and did not want to have to ship the touchpad back.

I have a quick questions because I am not so computer literate. Then I don't understand when you say "When the device hangs up, open Noveterm and connect your device." First, it hangs up but goes into a never ending loop of messages scrolling in the comand window. How do I stop this? How do I open novaterm, and wouldn't my device already be connected?

Thank you so much for your help!

BEst regards from Norway

Gergey
That never ending loop is due to the fact that the computer and device can't communicate to each other. :\ You might be SOL dude. It seems this fix is for only when it happens at that moment in time, not after you pulled the cord etc etc.
mbudden is offline   Reply With Quote
Old 08/31/2011, 08:29 AM   #7 (permalink)
Member
 
Posts: 4
So I managed to run novaterm and get to to steps described. I then get this message:

***********************************

root@webos-device:/# dosfsck -r /dev/mapper/store-media
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offsetriginal/backup)
71:48/20, 72:50/20, 74:54/20, 75:4f/20, 76:55/20, 77:43/20, 78:48/20
, 79:50/20, 80:41/20, 81:44/20
1) Copy original to backup
2) Copy backup to original
3) No action
? 2
/wallpapers and
/downloads/07 The Wig Party.m4v
share clusters.
1) Truncate first to 25165824 bytes
2) Truncate second to 0 bytes
?
*********************************************

So it seems that the problem lies somewhere with /wallpapers and /downloads[...] sharing clusters. Is there anyway I can just delete this movie file form the terminal?

Actually, why is that I can access the device through the terminal, but it won't mount. Can I force it to mount?

Thanks,

Gergey
gergey is offline   Reply With Quote
Old 08/31/2011, 08:55 AM   #8 (permalink)
Member
 
Posts: 19
Yes you should be able to force it to mount and then re-run the Dr. Let's see here... Try " rm -rf /downloads/07 the wig party.m4v " That should forcibly remove the file from your touchpad. The second option might be to Truncate second to 0 bytes or option 2 since what you want to do is delete the file after all. Then the original & backup are the same size

When you access it via Terminal you are basically sneaking in a back door that WebOS Dr. has opened for you by reaching 12% and giving you access. I've yet to figure out how to write the image this way. Seems the system is allowing you to "fix" issues and retry

Last edited by onebadtaz; 08/31/2011 at 08:58 AM. Reason: Oh yeah...
onebadtaz is offline   Reply With Quote
Old 08/31/2011, 09:04 AM   #9 (permalink)
Member
 
Posts: 4
Thanks onebadtaz. I get the following message:

************************************
root@webos-device:/# rm -rf /downloads/07 the wig party.m4v
rm: can't remove '/downloads/07': No such file or directory
rm: can't remove 'the': No such file or directory
rm: can't remove 'wig': No such file or directory
rm: can't remove 'party.m4v': No such file or directory
root@webos-device:/#
************************************

It's strange, as if it doesn't exist! Frustrating, shipping it back from Norway will cost more than I paid for the machine! ;-)
gergey is offline   Reply With Quote
Old 08/31/2011, 09:15 AM   #10 (permalink)
Member
 
Posts: 19
Ok try typing the file as a single word (rm -rf /downloads/07thewigparty.m4v) Maybe that'll delete the file. Or choose the second option and re-run the (dosfsck -r /dev/mapper/store-media) and then when it asks if you want to Truncate via option 1 or 2, choose 2 so it Truncates the download directory to 0 bytes.
onebadtaz is offline   Reply With Quote
Old 08/31/2011, 01:10 PM   #11 (permalink)
Member
 
Posts: 4
Hey onebadtaz. Thank you for your help. I tried all those options but it didn't work.

It didn't recognize the file to be removed, and truncating it didn't work either. My IT knowledge is too limited, so I gave up and called in a repair.... now I'll have to wait a few months. In case it can help for future problems, here is the message I got. I actually tried many many combinations, starting with copying backup to original, but they all ended in the same way.

*******************************************

root@webos-device:/# dosfsck -r /dev/mapper/store-media
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offsetriginal/backup)
71:48/20, 72:50/20, 74:54/20, 75:4f/20, 76:55/20, 77:43/20, 78:48/20
, 79:50/20, 80:41/20, 81:44/20
1) Copy original to backup
2) Copy backup to original
3) No action
? 1
/wallpapers and
/downloads/07 The Wig Party.m4v
share clusters.
1) Truncate first to 25165824 bytes
2) Truncate second to 0 bytes
? 2
/downloads/07 The Wig Party.m4v
File size is 669357430 bytes, cluster chain length is 25165824 bytes.
Truncating file to 25165824 bytes.
Reserved field in VFAT long filename slot is not 0 (but 0x3e).
1: Fix.
2: Leave it.
? 2
Start cluster field in VFAT long filename slot is not 0 (but 0x156c).
1: Fix.
2: Leave it.
? 2
Unfinished long file name ":A-H:A-r:Bb-:2FX:7xL:0Fe:9Dp:AL7:COM:4-s:279:CEqaF".
(Start may have been overwritten by ??:?!f?\234.\225\232?)
1: Delete LFN
2: Leave it as it is.
3: Fix numbering (truncates long name and attaches it to short name ??:?!f?\234.\225\232?)
? 1
Long filename fragment "?:9Fn:97w:0zp:BXh:3lC:BqR:F6m:2gA:0CU:64B:4Sc:6Bz" found outside a LFN sequence.
(Maybe the start bit is missing on the last fragment)
1: Delete fragment
2: Leave it as it is.
3: Set start bit
? 1
Long filename fragment ":7wz:1Ou:EXw:E0D:Emd:54M:3EC:0oe:ArT:5Xhou:0lP:4J0" found outside a LFN sequence.
(Maybe the start bit is missing on the last fragment)
1: Delete fragment
2: Leave it as it is.
3: Set start bit
? 1
Long filename fragment ":2rY:6n-fL:C1G:6waRg:6Ej:FpA:0us:EYJ:5Fh:Fvg:Ej5" found outside a LFN sequence.
(Maybe the start bit is missing on the last fragment)
1: Delete fragment
2: Leave it as it is.
3: Set start bit
? 1
Reserved field in VFAT long filename slot is not 0 (but 0xa4).
1: Fix.
2: Leave it.
? 1
Start cluster field in VFAT long filename slot is not 0 (but 0xd6f1).
1: Fix.
2: Leave it.
? 1
Unfinished long file name ":8YQ:AFC:F--:BPQ4y:2Tr:97M:99+:FzV:EJq:8lF:5QF:A+P".
(Start may have been overwritten by ??֩%9??.b\007\223)
1: Delete LFN
2: Leave it as it is.
3: Fix numbering (truncates long name and attaches it to short name ??֩%9??.b\007\223)
? 1
Long filename fragment ":Ewc:2gZ:F9S:AujSa:1vj:1pO:59o:5hR:A9F:8zd:835:F86" found outside a LFN sequence.
(Maybe the start bit is missing on the last fragment)
1: Delete fragment
2: Leave it as it is.
3: Set start bit
? 1
Reserved field in VFAT long filename slot is not 0 (but 0xbb).
1: Fix.
2: Leave it.
? 1
Start cluster field in VFAT long filename slot is not 0 (but 0xbf37).
1: Fix.
2: Leave it.
? 1
Unfinished long file name ":1BJ:7Wh:76i:8dd:B0b:3F2:Bs7:Bby:7Ki:C+x:1eV:CxX:21T".
(Start may have been overwritten by ??!?@???.?\035\216)
1: Delete LFN
2: Leave it as it is.
3: Fix numbering (truncates long name and attaches it to short name ??!?@???.?\035\216)
? 1
Long filename fragment ":52t:0qwC4:AUJ:8X6:4K5:9zq:0gJ:4vc:Ce1:BHj:9xP:5Xc" found outside a LFN sequence.
(Maybe the start bit is missing on the last fragment)
1: Delete fragment
2: Leave it as it is.
3: Set start bit
? 1
Long filename fragment ":9MI:E4Una:EQJfs:CM0u2:02FO1:A4K:80K:13K:4SW" found outside a LFN sequence.
(Maybe the start bit is missing on the last fragment)
1: Delete fragment
2: Leave it as it is.
3: Set start bit
? 1
Reserved field in VFAT long filename slot is not 0 (but 0x2b).
1: Fix.
2: Leave it.
? 1
Start cluster field in VFAT long filename slot is not 0 (but 0x15b7).
1: Fix.
2: Leave it.
? 1
Unfinished long file name ":218:07q38:4D4:AE5:4U-:6BS:4fi:A6K:0G8:1ld:Fr+:1lI".
(Start may have been overwritten by L??\000\000?\000?.???)
1: Delete LFN
2: Leave it as it is.
3: Fix numbering (truncates long name and attaches it to short name L??\000\000?\000?.???)
? 1
Long filename fragment ":2BC:9ij:B2k:3KE:0mi:FIE:EEr:Ehi:ErR:FlV:CSn:1+3:ExV" found outside a LFN sequence.
(Maybe the start bit is missing on the last fragment)
1: Delete fragment
2: Leave it as it is.
3: Set start bit
? 1
Long filename fragment ":6c8:EJM:0x0:F2Q:7Ur:60t:4TH:FyX:F14:E3E:CDG:6fU:3ec" found outside a LFN sequence.
(Maybe the start bit is missing on the last fragment)
1: Delete fragment
2: Leave it as it is.
3: Set start bit
? 1
Reserved field in VFAT long filename slot is not 0 (but 0x22).
1: Fix.
2: Leave it.
? 1
Start cluster field in VFAT long filename slot is not 0 (but 0x503d).
1: Fix.
2: Leave it.
? 1
Long filename fragment ":1V9:3aQg2:63Q:9fu:AlG:7Or:06A:6nI:Cwr:0Nm:8dM:CpD" found outside a LFN sequence.
(Maybe the start bit is missing on the last fragment)
1: Delete fragment
2: Leave it as it is.
3: Set start bit
? 1
*** glibc detected *** dosfsck: munmap_chunk(): invalid pointer: 0x00064f98 ***
======= Backtrace: =========
/lib/libc.so.6[0x2ab567d8]
dosfsck[0xf49c]
dosfsck[0xffb4]
dosfsck[0xa2bc]
dosfsck[0xc0f0]
dosfsck[0xc190]
dosfsck[0xc290]
dosfsck[0xce6c]
/lib/libc.so.6(__libc_start_main+0x118)[0x2aafafe0]
======= Memory map: ========
00008000-00014000 r-xp 00000000 01:00 1111 /usr/sbin/dosfsck
0001b000-0001c000 rw-p 0000b000 01:00 1111 /usr/sbin/dosfsck
0001c000-00081000 rw-p 00000000 00:00 0 [heap]
2aaab000-2aaca000 r-xp 00000000 01:00 3015 /lib/ld-2.8.so
2aaca000-2aace000 rw-p 00000000 00:00 0
2aad1000-2aad2000 r--p 0001e000 01:00 3015 /lib/ld-2.8.so
2aad2000-2aad3000 rw-p 0001f000 01:00 3015 /lib/ld-2.8.so
2aad3000-2aade000 r-xp 00000000 01:00 3019 /lib/libgcc_s.so.1
2aade000-2aae5000 ---p 0000b000 01:00 3019 /lib/libgcc_s.so.1
2aae5000-2aae6000 rw-p 0000a000 01:00 3019 /lib/libgcc_s.so.1
2aae6000-2ac18000 r-xp 00000000 01:00 181 /lib/libc-2.8.so
2ac18000-2ac20000 ---p 00132000 01:00 181 /lib/libc-2.8.so
2ac20000-2ac22000 r--p 00132000 01:00 181 /lib/libc-2.8.so
2ac22000-2ac23000 rw-p 00134000 01:00 181 /lib/libc-2.8.so
2ac23000-2ac26000 rw-p 00000000 00:00 0
2af9b000-2bd6c000 rw-p 00000000 00:00 0
7efc2000-7efe3000 rw-p 00000000 00:00 0 [stack]
Aborted
****************************************************
gergey is offline   Reply With Quote
Thanked By: JaakLeen
Old 08/31/2011, 06:16 PM   #12 (permalink)
Member
 
Posts: 19
Now that is a mouthful - I'd go through and check every option for you but you said you're sending it in for repair so... lol
onebadtaz is offline   Reply With Quote
Old 09/02/2011, 09:42 AM   #13 (permalink)
Member
 
Posts: 1
I've got the same 12% problem for a couple days now.

I get the same results to the dosfsck command:
root@webos-device:/# dosfsck -r /dev/mapper/store-media
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offsetriginal/backup)
71:48/20, 72:50/20, 74:54/20, 75:4f/20, 76:55/20, 77:43/20, 78:48/20
, 79:50/20, 80:41/20, 81:44/20
1) Copy original to backup
2) Copy backup to original
3) No action
?

No matter what answer I give it (1,2,or 3), it keeps giving me results like:
Long filename fragment ":6tDrB:4Cq:8bX:4Wq:0vl:Cu4:6upKZ:7Xq:9LA:31P:6ZN" found outside a LFN sequence. (Maybe the start bit is missing on the last fragment)
1: Delete fragment
2: Leave it as it is.
3: Set start bit
? 1
Reserved field in VFAT long filename slot is not 0 (but 0x6d)
1: Fix.
2: Leave it.
?



Does this mean anything to anyone? It seems to go on forever.

Should I just give up and call HP to send it back for repair or service?

Thanks
tsihcaz is offline   Reply With Quote
Old 09/02/2011, 05:56 PM   #14 (permalink)
Member
 
Posts: 19
There are differences because there are bad clusters... Lemme figure this out and get back to you in a little bit

Setting up a media center at the moment lol
onebadtaz is offline   Reply With Quote
Old 09/07/2011, 10:04 AM   #15 (permalink)
Member
 
Posts: 1
I want to confirm that I followed onebadtaz' instructions and they do work for the 12% problem.

I did run the 3.0.0 installer and had to do it twice repeating the command

dosfsck -r /dev/mapper/store-media

I got tons of "long file name" errors and I either pressed Fix or delete directory (A lot of pressing #1 or Y for yes)

Thank you, I had the return box and everything ad was going to send it back.
jfjiba is offline   Reply With Quote
Old 09/10/2011, 01:32 AM   #16 (permalink)
Member
 
Posts: 4
Quote:
Originally Posted by tsihcaz View Post
I've got the same 12% problem for a couple days now.

I get the same results to the dosfsck command:
root@webos-device:/# dosfsck -r /dev/mapper/store-media
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offsetriginal/backup)
71:48/20, 72:50/20, 74:54/20, 75:4f/20, 76:55/20, 77:43/20, 78:48/20
, 79:50/20, 80:41/20, 81:44/20
1) Copy original to backup
2) Copy backup to original
3) No action
?

No matter what answer I give it (1,2,or 3), it keeps giving me results like:
Long filename fragment ":6tDrB:4Cq:8bX:4Wq:0vl:Cu4:6upKZ:7Xq:9LA:31P:6ZN" found outside a LFN sequence. (Maybe the start bit is missing on the last fragment)
1: Delete fragment
2: Leave it as it is.
3: Set start bit
? 1
Reserved field in VFAT long filename slot is not 0 (but 0x6d)
1: Fix.
2: Leave it.
?



Does this mean anything to anyone? It seems to go on forever.

Should I just give up and call HP to send it back for repair or service?

Thanks
I am having same problems. Tried removing offending file, renaming it, etc. Nothing is working. I have tried running WebOS Doc countless times. It runs & runs until the battery dies. Any help? Anyone?
qcshin is offline   Reply With Quote
Old 10/03/2011, 02:30 AM   #17 (permalink)
Member
 
Posts: 14
Hello there,

I had more or less the same issue on my Pr3.

However I had another issue: the novaterm software kept continually on crashing on every character I typed. As a result, it was impractical to use the interactive fix of dosfsck like recommended in this post.

Instead I tried using the automatic fix of dosfsck, however it took him so much time to work that I gave up before it finished. Also, some messages hinted that he wouldn't fix everything in non-interactive mode.

Finally, sure as hell that nothing was good on this filesystem, I tried to format it anew by using the following command in novaterm:

mkfs.msdos /dev/mapper/store-media

It was risky but then, as I hoped, I could use webOS Dotcor on my device with no more issue.

Hope this can help other people in the same situation!
NexusCrawler is offline   Reply With Quote
Liked by Atheist, demaho33, horn34 and 3 others like this.
Old 10/12/2011, 06:22 PM   #18 (permalink)
Member
 
Posts: 1
You're my hero, my problem is fixed!
Jeroen262 is offline   Reply With Quote
Old 10/13/2011, 06:26 AM   #19 (permalink)
Member
 
Posts: 1
mark! thany you!
Xevan is offline   Reply With Quote
Old 10/13/2011, 09:53 AM   #20 (permalink)
Member
 
Posts: 2
This worked a treat for me ..... SO HAPPY only had my Touchpad for about 2 weeks

Last edited by Hunterdiver; 10/13/2011 at 10:03 AM. Reason: aditional information
Hunterdiver is offline   Reply With Quote
Liked by leif likes this.
Reply

 

Thread Tools
Display Modes



 


Content Relevant URLs by vBSEO 3.6.0