Results 1 to 12 of 12
Like Tree1Likes
  • 1 Post By alex80386
  1.    #1  
    Hi guys having a major headache for a few days ... I normally do not post until I have exhausted my other options ...

    I have botched the Ubuntu install and have only 4gb of space usable for storage.

    Have tried to read through tutorials both for installing : UbuntuChroot - WebOS Internals
    and uninstalling:
    gadgetXplorer: #webOS: How to remove EXT3FS partition

    I am trying to figure out a way ... preferably automatic to go back to default partition tables. Is there anyways to achieve that. Let me know if I am missing any info.

    Code:
    C:\Users\NiKTaMeR\Desktop\Downloads\phones\WebOS\HP TouchPad>"C:/Program Files/P
    alm, Inc/novacom.exe" -d 0e771800c8a9ecddc90ab35baf84c4f6a293dde7 -t open tty://
    
    root@CheapTouchPad:/# lvdisplay
    lvdisplay
      --- Logical volume ---
      LV Name                /dev/store/root
      VG Name                store
      LV UUID                ddp1j9-42hc-o95u-sfyu-Xlxm-vR0y-yT7WOt
      LV Write Access        read/write
      LV Status              available
      # open                 1
      LV Size                568.00 MB
      Current LE             71
      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                VBjrKl-B61p-CMdS-L8AY-WK4Z-smRk-jj6X5K
      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                eolyN8-1fMc-W448-6EAE-EXc1-8zRe-EYUZZa
      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                vcSqGM-A66u-HWj9-nIc4-GMBX-siWx-auNdJ2
      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                8K1Tzh-JpqP-AW9w-BQL6-lWbN-MUTK-6Cyf6w
      LV Write Access        read/write
      LV Status              available
      # open                 1
      LV Size                256.00 MB
      Current LE             32
      Segments               2
      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                jk6Lhl-irdy-VuyY-cNd7-Bicy-b0Ke-sK3cqq
      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                GwzQv1-Oewn-niF3-y2i4-jM23-n8ke-DbWAzV
      LV Write Access        read/write
      LV Status              available
      # open                 1
      LV Size                4.00 GB
      Current LE             512
      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                yol9o0-t9Sy-WyUX-idJa-OX73-CtIO-lr3juk
      LV Write Access        read/write
      LV Status              available
      # open                 1
      LV Size                400.00 MB
      Current LE             50
      Segments               1
      Allocation             inherit
      Read ahead sectors     auto
      - currently set to     256
      Persistent major       254
      Persistent minor       7
      Block device           254:7
    Included is a resume of my partition table. P.S I have a 32 gb model.

    Thank you in advance
  2. #2  
    So that second link didn't work for you? That should do it, meta doctor, follow the manual instructions. I would assume web doctor would rewrite into one volume space, unless they didn't think users would partition the disk.
  3. #3  
    It looks like you went through that second link (above) and got rid of store-ext3fs as follows.

    # lvremove /dev/mapper/store-ext3fs

    Or perhaps you got rid of it another way?

    But it seems you can't expand your fat32 volume to original size?
    Here is mine (before resizing and adding ext3fs):

    # lvscan
    ACTIVE '/dev/store/root' [568.00 MB] inherit
    ACTIVE '/dev/store/var' [64.00 MB] inherit
    ACTIVE '/dev/store/update' [16.00 MB] inherit
    ACTIVE '/dev/store/log' [24.00 MB] inherit
    ACTIVE '/dev/store/mojodb' [256.00 MB] inherit
    ACTIVE '/dev/store/filecache' [136.00 MB] inherit
    ACTIVE '/dev/store/media' [27.63 GB] inherit
    ACTIVE '/dev/store/swap' [400.00 MB] inherit

    Did your procedure remove the line from /etc/fstab for mounting the new ext3fs volume?
    Otherwise you need to remove it later.

    The following is based on the procedure found here...
    UbuntuChroot - WebOS Internals

    In any case it looks like the first thing you might need to do is unmount /media/cryptofs and /media/internal (if these are mounted). The following should be done via novaterm:

    # pkill -SIGUSR1 cryptofs
    # umount /media/cryptofs
    # mount | grep cryptofs
    # umount /media/internal
    # mount | grep internal

    Neither /media/cryptofs or /media/internal should be mounted at this stage - please check with 'df' and 'mount' commands.

    Then when these have been unmounted, extend the size of your logical volume - the following should make it take all the remaining free space.

    # lvresize -l +100%FREE /dev/mapper/store-media

    Please check with 'lvscan' and/or 'lvdisplay' as above.
    Now we can resize the fat32 file system on that logical volume.

    # resizefat /dev/mapper/store-media 26G

    This will make it 26G and perhaps you can make it larger than that if you specify xxxxxM but don't try to make it larger than the size of the logical volume!

    Then when logical volume and fat filesystem are back to correct size, then you can try to mount...

    # mount -a

    Or you can just reboot - in fact just reboot and check with 'mount' and 'df' commands.
    Last edited by alex80386; 10/14/2011 at 06:42 AM. Reason: Updated the lvresize command to use +100%FREE
  4. #4  
    Perhaps I should add - please check before you make any changes.

    # cat /etc/fstab

    If there is a line like...

    /dev/mapper/store-ext3fs /media/ext3fs auto noatime 0 0

    Then we need to remove it before we go too far as it will attempt to mount on next reboot.
  5.    #5  
    Thanks A LOT for your help ! My fstab file does mention the ext3fs part:

    Code:
    root@CheapTouchPad:/# mount -a
    mount -a
    mount: mounting /dev/mapper/store-ext3fs on /media/ext3fs failed: No such file o
    r directory
    mount: mounting /dev/mapper/store-ext3fs on /media/ext3fs failed: No such file o
    r directory
    root@CheapTouchPad:/#
    root@CheapTouchPad:/# cat /etc/fstab
    cat /etc/fstab
    # fstab auto-generated by trenchcoat
    # <filesystem>  <mount point>   <type>  <options>       <dump>  <pass>
    rootfs  /       ext3    ro,suid,dev,exec,auto,nouser,async,noatime      1
    1
    /dev/mapper/store-var   /var    ext3    noatime,data=writeback  0       0
    /dev/mapper/store-cryptodb      /var/db ext3    noauto,noatime,data=ordered
    0       0
    /dev/mapper/store-cryptofilecache       /var/file-cache ext3    noauto,noatime,u
    ser_xattr       0       0
    /dev/mapper/store-log   /var/log        ext3    noatime 0       0
    /dev/mapper/store-update        /var/lib/update ext3    noauto,noatime  0
    0
    proc    /proc   proc    defaults        0       0
    devpts  /dev/pts        devpts  mode=0620,gid=5 0       0
    tmpfs   /tmp    tmpfs   size=40M,mode=1777      0       0
    tmpfs   /var/run        tmpfs   size=16M,mode=1777      0       0
    tmpfs   /var/tmp        tmpfs   size=32M,mode=1777      0       0
    tmpfs   /media/ram      tmpfs   defaults        0       0
    /dev/mapper/store-media /media/internal vfat    utf8,shortname=mixed,umask=0000
    0       0
    /dev/mapper/store-ext3fs /media/ext3fs auto noatime 0 0
    /dev/mapper/store-ext3fs /media/ext3fs ext3   noatime,data=writeback   0   0
  6.    #6  
    So the problem was in the last step you mentionned about the fstab ... Thanks a lot for the help !!! I have put a lot of code in here because I wanted to make sure that if someone else had this problem they could see everything.

    So basically for whatever reason when I got the the command lvresize -l 100%FREE /dev/mapper/store-media it only detected 2.64G ???
    Code:
    lvresize -l 100%FREE /dev/mapper/store-media
    File descriptor 11 (socket:[26154]) leaked on lvresize invocation. Parent PID 60
    00: /bin/sh
      WARNING: Reducing active and open logical volume to 2.64 GB
      THIS MAY DESTROY YOUR DATA (filesystem etc.)
    Do you really want to reduce media? [y/n]: y
    So when I tried to resize partition it couldn't work ...
    Code:
    root@CheapTouchPad:/# resizefat /dev/mapper/store-media 26G
    resizefat /dev/mapper/store-media 26G
    dosfsck 2.11, 12 Mar 2005, FAT32, LFN
    Free cluster summary wrong (941593 vs. really 585241)
      Auto-correcting.
    Performing changes.
    /dev/mapper/store-media: 11185 files, 104932/690173 clusters
    New size reduced to maximum available of 5537792 sectors
    So I got file /etc/fstab with WOQI and edited it in notepad from:
    Code:
    # fstab auto-generated by trenchcoat
    # <filesystem>	<mount point>	<type>	<options>	<dump>	<pass>
    rootfs	/	ext3	ro,suid,dev,exec,auto,nouser,async,noatime	1	1
    /dev/mapper/store-var	/var	ext3	noatime,data=writeback	0	0
    /dev/mapper/store-cryptodb	/var/db	ext3	noauto,noatime,data=ordered	0	0
    /dev/mapper/store-cryptofilecache	/var/file-cache	ext3	noauto,noatime,user_xattr	0	0
    /dev/mapper/store-log	/var/log	ext3	noatime	0	0
    /dev/mapper/store-update	/var/lib/update	ext3	noauto,noatime	0	0
    proc	/proc	proc	defaults	0	0
    devpts	/dev/pts	devpts	mode=0620,gid=5	0	0
    tmpfs	/tmp	tmpfs	size=40M,mode=1777	0	0
    tmpfs	/var/run	tmpfs	size=16M,mode=1777	0	0
    tmpfs	/var/tmp	tmpfs	size=32M,mode=1777	0	0
    tmpfs	/media/ram	tmpfs	defaults	0	0
    /dev/mapper/store-media	/media/internal	vfat	utf8,shortname=mixed,umask=0000	0	0
    /dev/mapper/store-ext3fs /media/ext3fs auto noatime 0 0
    /dev/mapper/store-ext3fs /media/ext3fs ext3   noatime,data=writeback   0   0
    to:
    Code:
    # fstab auto-generated by trenchcoat
    # <filesystem>	<mount point>	<type>	<options>	<dump>	<pass>
    rootfs	/	ext3	ro,suid,dev,exec,auto,nouser,async,noatime	1	1
    /dev/mapper/store-var	/var	ext3	noatime,data=writeback	0	0
    /dev/mapper/store-cryptodb	/var/db	ext3	noauto,noatime,data=ordered	0	0
    /dev/mapper/store-cryptofilecache	/var/file-cache	ext3	noauto,noatime,user_xattr	0	0
    /dev/mapper/store-log	/var/log	ext3	noatime	0	0
    /dev/mapper/store-update	/var/lib/update	ext3	noauto,noatime	0	0
    proc	/proc	proc	defaults	0	0
    devpts	/dev/pts	devpts	mode=0620,gid=5	0	0
    tmpfs	/tmp	tmpfs	size=40M,mode=1777	0	0
    tmpfs	/var/run	tmpfs	size=16M,mode=1777	0	0
    tmpfs	/var/tmp	tmpfs	size=32M,mode=1777	0	0
    tmpfs	/media/ram	tmpfs	defaults	0	0
    /dev/mapper/store-media	/media/internal	vfat	utf8,shortname=mixed,umask=0000	0	0
    And the when i resize the volume:
    Code:
    root@CheapTouchPad:/# lvresize -l 100%FREE /dev/mapper/store-media
    lvresize -l 100%FREE /dev/mapper/store-media
    File descriptor 11 (socket:[26154]) leaked on lvresize invocation. Parent PID 71
    38: /bin/sh
      Extending logical volume media to 25.00 GB
      Logical volume media successfully resized
    It allowed me to partition the whole thing:
    Code:
    root@CheapTouchPad:/# resizefat /dev/mapper/store-media 26G
    resizefat /dev/mapper/store-media 26G
    dosfsck 2.11, 12 Mar 2005, FAT32, LFN
    /dev/mapper/store-media: 11185 files, 104932/690868 clusters
    New size reduced to maximum available of 52428800 sectors
    Last edited by NiKTaMeR; 09/28/2011 at 05:33 PM.
  7. #7  
    Glad I was able to help. Somehow those mounts for the ext3fs volume must have been messing things up. Interesting to see that when you ran 'lvresize', the volume was extended to 25GB, but when you ran 'resizefat' you used 26GB:

    Code:
    # resizefat /dev/mapper/store-media 26G
    resizefat /dev/mapper/store-media 26G
    dosfsck 2.11, 12 Mar 2005, FAT32, LFN
    /dev/mapper/store-media: 11185 files, 104932/690868 clusters
    New size reduced to maximum available of 52428800 sectors
    So 'resizefat' seems to know the maximum available space in the volume and appears to have some correction mechanism to select the max size.
    LinuxKoss likes this.
  8. #8  
    I'm undoing an Ubuntu install (as well as cleaning up from a temporary CM7 install) and am seeing an odd problem.

    I've deleted the ext3fs and cm-* volumes, killed the cryptofs process, umounted cryptofs & internal, but am unable to regrow the internal volume:

    Code:
    root@DavesTouchPad:/# pvscan
      PV /dev/mmcblk0p14   VG store   lvm2 [29.07 GB / 10.01 GB free]
      Total: 1 [29.07 GB] / in use: 1 [29.07 GB] / in no VG: 0 [0   ]
    root@DavesTouchPad:/# lvscan
      ACTIVE            '/dev/store/root' [568.00 MB] inherit
      ACTIVE            '/dev/store/var' [64.00 MB] inherit
      ACTIVE            '/dev/store/update' [16.00 MB] inherit
      ACTIVE            '/dev/store/log' [24.00 MB] inherit
      ACTIVE            '/dev/store/mojodb' [256.00 MB] inherit
      ACTIVE            '/dev/store/filecache' [136.00 MB] inherit
      ACTIVE            '/dev/store/media' [17.52 GB] inherit
      ACTIVE            '/dev/store/swap' [512.00 MB] inherit
    root@DavesTouchPad:/# lvresize -l 100%FREE /dev/mapper/store-media
      WARNING: Reducing active logical volume to 10.01 GB
      THIS MAY DESTROY YOUR DATA (filesystem etc.)
    Do you really want to reduce media? [y/n]: n
      Logical volume media NOT reduced
      Command failed with status code 5.
    My fstab:

    Code:
    # fstab auto-generated by trenchcoat
    # <filesystem>	<mount point>	<type>	<options>	<dump>	<pass>
    rootfs	/	ext3	ro,suid,dev,exec,auto,nouser,async,noatime	1	1
    /dev/mapper/store-var	/var	ext3	noatime,data=writeback	0	0
    /dev/mapper/store-cryptodb	/var/db	ext3	noauto,noatime,data=ordered	0	0
    /dev/mapper/store-cryptofilecache	/var/file-cache	ext3	noauto,noatime,user_xattr	0	0
    /dev/mapper/store-log	/var/log	ext3	noatime	0	0
    /dev/mapper/store-update	/var/lib/update	ext3	noauto,noatime	0	0
    proc	/proc	proc	defaults	0	0
    devpts	/dev/pts	devpts	mode=0620,gid=5	0	0
    tmpfs	/tmp	tmpfs	size=40M,mode=1777	0	0
    tmpfs	/var/run	tmpfs	size=16M,mode=1777	0	0
    tmpfs	/var/tmp	tmpfs	size=32M,mode=1777	0	0
    tmpfs	/media/ram	tmpfs	defaults	0	0
    /dev/mapper/store-media	/media/internal	vfat	utf8,shortname=mixed,umask=0000	0	0
    Any advice?

    EDIT: For anyone else who may hit this... I'm not sure why the above quoted lvresize command was failing, but doing a manual "lvresize -L +nGB" (rather than the "100%FREE") worked.
    Last edited by elborak; 10/13/2011 at 04:47 PM.
  9. #9  
    Quote Originally Posted by elborak View Post

    EDIT: For anyone else who may hit this... I'm not sure why the above quoted lvresize command was failing, but doing a manual "lvresize -L +nGB" (rather than the "100%FREE") worked.
    You can also use "lvresize -l +100%FREE /dev/mapper/store-media" if you don't know how much free space you have.
    If you like my work on Kindle Import and the Calibre WebOS plugin and want to contribute toward improvements and future WebOS projects.

  10. #10  
    Quote Originally Posted by kjhenrie View Post
    You can also use "lvresize -l +100%FREE /dev/mapper/store-media" if you don't know how much free space you have.
    Ah! So the problem was using "100%FREE" rather than "+100%FREE" in my failed attempt?
  11. #11  
    Quote Originally Posted by elborak View Post
    Ah! So the problem was using "100%FREE" rather than "+100%FREE" in my failed attempt?
    Yes, without the + it will resize the partition to the size of the free space instead of increasing it by the size of the free space.
    If you like my work on Kindle Import and the Calibre WebOS plugin and want to contribute toward improvements and future WebOS projects.

  12. #12  
    Quote Originally Posted by kjhenrie View Post
    You can also use "lvresize -l +100%FREE /dev/mapper/store-media" if you don't know how much free space you have.
    Thanks for that... the missing + in my original post makes all the difference. I'm going to edit my post for the benefit of those people that find this thread and don't bother to scroll down.

Posting Permissions