[Xoom Q&A, Help & Troubleshooting] ritter_xoom:
Did some aditional research.

I've installed Terminal Emulator from Android's Market. This little great piece of software

allows direct access to the kernel via old-good-linux-linecommands, so I issued 'cat /proc/partitions'

'df' and a dmesg just after booting. Besides I had the rare opportunty to repeat this in an stock tablet, so

I can compare the results. Here is what I've found:

df says:

in a brand new:

$df

Filesystem Size Used Free Blksize

/dev 359M 32K 359M 4096

/mnt/asec 359M 0K 359M 4096

/mnt/obb 359M 0K 359M 4096

/system 251M 215M 36M 4096

/data 28G 428M 27G 2048

/cache 163M 8M 155M 2048

/pds 1M 108K 1M 2048

/mnt/sdcard 28G 428M 27G 2048

In xoom:

$df

Filesystem Size Used Free Blksize

/dev 359M 32K 359M 4096

/mnt/asec 359M 0K 359M 4096

/mnt/obb 359M 0K 359M 4096

/system 251M 222M 29M 4096

/data 4G 218M 3G 4096

/cache 166M 4M 162M 4096

/pds 1M 108K 1M 2048

/mnt/sdcard 4G 218M 3G 4096

/mnt/sdcard-ext 14G 6G 8G 32768

Main differences are the size of the /data volume , some blocksizes and the existance of my sd-external.

When issuing cat /proc/partitions:

in the brand-new:

$ cat /proc/partitions

major minor #blocks name

179 0 31162368 mmcblk0

179 1 3072 mmcblk0p1

179 2 2048 mmcblk0p2

179 3 2048 mmcblk0p3

179 4 4096 mmcblk0p4

179 5 2048 mmcblk0p5

179 6 12288 mmcblk0p6

179 7 8192 mmcblk0p7

259 0 262144 mmcblk0p8

259 1 173056 mmcblk0p9

259 2 30663168 mmcblk0p10

in my tablet:

$ cat /proc/partitions

major minor #blocks name

179 0 15558144 mmcblk0

179 1 15554048 mmcblk0p1

179 8 31162368 mmcblk1

179 9 3072 mmcblk1p1

179 10 2048 mmcblk1p2

179 11 2048 mmcblk1p3

179 12 4096 mmcblk1p4

179 13 2048 mmcblk1p5

179 14 12288 mmcblk1p6

179 15 8192 mmcblk1p7

259 0 262144 mmcblk1p8

259 1 173056 mmcblk1p9

259 2 26214400 mmcblk1p10

259 3 4448768 mmcblk1p11

(mmcblk0 is my external SD)

So, interesting. The good new is that mmcblk1 (the internal memory) still has its 32 Gb!, but my tablet has one partition more.

Finally, from the booting log of boths machines I extract this part when mounting volumes:

brand new:

<4>[ 14.306181] Primary GPT is invalid, using alternate GPT.

<6>[ 14.306316] mmcblk0: p1 (ebb) p2 (pdsb) p3 (misc) p4 (logo.bin) p5 (kpanic) p6 (recovery) p7 (boot) p8 (system) p9 (cache) p10 (userdata)

<6>[ 14.326247] keychord: using input dev stingray-keypad for fevent

<6>[ 14.364011] whisper_notify: accy=none

<6>[ 14.416766] EXT4-fs (mmcblk0p8): mounted filesystem with ordered data mode. Opts: (null)

<6>[ 14.534220] EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts: (null)

<6>[ 14.547432] EXT4-fs (mmcblk0p9): mounted filesystem with ordered data mode. Opts: (null)

My tablet:

<4>[ 19.362795] Primary GPT is invalid, using alternate GPT.

<6>[ 19.362919] mmcblk1: p1 (ebb) p2 (pdsb) p3 (misc) p4 (logo.bin) p5 (kpanic) p6 (recovery) p7 (boot) p8 (system) p9 (cache) p10 (SDC) p11 (userdata)

<6>[ 19.389501] EXT4-fs (mmcblk1p8): mounted filesystem with ordered data mode. Opts: (null)

<6>[ 19.400500] EXT4-fs (mmcblk1p11): mounted filesystem with ordered data mode. Opts: (null)

<6>[ 19.428140] EXT4-fs (mmcblk1p9): mounted filesystem with ordered data mode. Opts: (null)

----------------------------------------

So, P11 (4 Gb) is assigned to userdata, and that explains why we have only 4 Gb. That makes also sense tho the problem when trying to flash userdata.img

where fastboot says it has no enough place. The weird thing is that 26 Gb p10 for SDC.

If the HK tablet is partitioned like that, maybe the HK systems makes further mounting when starting. I will look the way to manually mount this partition for

at list have the rest of the memory visible. Anyway my tablet is not rooted for the moment.

Any ideas how to follow? Some light from the experts?