Can't expand file system after installing Max2play (2.34) for Ubuntu Mate 16.04

Max2Play Home 2016 (en) Forums Max2Play Add-ons Can't expand file system after installing Max2play (2.34) for Ubuntu Mate 16.04

This topic contains 3 replies, has 3 voices, and was last updated by  Heiner premium 1 month, 1 week ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • 17. September 2016 at 17:40 #23078

    I tried installing the latest image for Odroid XU4: m2p-2.34-xu4-ubuntu-mate-16.img

    On first boot I clicked expand file system but get an unsuccessful message:

    mmcblk0p2
    Resize not successful

    I’ve tried a number of times: re-burning image and even re-downloading from Max2play, but can’t get it to work. Am I doing something wrong? I had the 2.22 image previously and used update button to get to latest version, but I thought I’d try the latest Ubuntu to see if it solved some issues I’ve been having with USB drives. Alternatively, is there a way to update to latest Ubuntu 16.04 from the previous one? It seemed even though I was on latest Max2play it was still Ubuntu version 15.04.

    Debug info says:

    #### FILESYSTEM ####
    Filesystem 1K-blocks Used Available Use% Mounted on
    udev 759012 0 759012 0% /dev
    tmpfs 203864 8320 195544 5% /run
    /dev/mmcblk0p2 7383016 4188772 2910968 59% /

    12. October 2016 at 12:12 #23390

    Hello Teetertank,

    We worked on this issue. Thanks for your advice. The problem should be solved. Please try the newer version from our download site.

    Best Regards.

    15. October 2016 at 2:30 #23422

    Hi Christoph,

    Thanks for looking into it.

    I tried downloading a fresh image and installing on the XU4 but still get same message that resize is not successful.
    The image reference I downloaded is still m2p-2.34, same as one I downloaded previously – has anything updated or is it the same?

    I read on another forum that Ubuntu 16.04 resizes the file system automatically though. Could this be the case?

    My eMMC module is 8gb and these are the details in the debug info (so maybe ok?):

    #### FILESYSTEM ####
    Filesystem 1K-blocks Used Available Use% Mounted on
    udev 759012 0 759012 0% /dev
    tmpfs 203864 10852 193012 6% /run
    /dev/mmcblk0p2 7383016 4116592 2983148 58% /

    I still can’t get any USB drive or pen drive to mount on this system. They are sometimes recognised (not always) and when they are I get a message

    <name of drive> in not mounted (Device /dev/sda2 with UUID 18A03768A0374C0E)
    Set fixed Mountpoint to prevent directory switching on reboot:

    Have you any ideas, I tried so many times and nothing will mount.

    • This reply was modified 1 month, 3 weeks ago by  Teetertank.
    24. October 2016 at 16:41 #23557

    Hi Teetertank,
    You are correct in your assumption. 8 gb emmc’s are already expanded. The process is only necessary for emmc’s of bigger sizes.

    Regarding the mounting issue, this was in fact a bug caused by an Ubuntu update. We managed to fix it with a beta update. So you just need to click on the Beta-Update button under the Settings/Reboot menu in our web interface and your USB drives should be able to mount again.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

Register here