LMDE4 install crashes at partitioning! (ASUS VivoBook)

[ObiSandwich]

I've used the same LMDE4 (Rufus/Fat32) USB stick to install on a 3 different computers in the last couple of weeks, but struggling on a new ASUS VivoBook E12 (E203MAS) laptop (Intel(R) Celeron(R) N4000 CPU @ 1.10GHz / 4GB Ram / eMMC);

I have set the laptop bios settings as...

• 'Secure Boot Control' to: Disabled

• 'Fast Boot' to: Disabled

• (there is no 'CSM Support' option to enable)

• According to Asus support page, this latptop has the latest Latest Firmware (319).

Windows 10 was installed, but after first failed LMDE4 install, removed Win10 partitions via Live LMDE4 GParted.


AUTOMATED INSTALLATION

No matter what I do at the start of the installation (eg. changing the LVM/Encrypt options has no affect) the installation will fail as follows...

Continuing with Automated Installation and choosing to install on: mmcblk0, a pop-up asks;

No partition table was found on the hard drive: mmcblkboot0 (4MB) Do you want the installer to create a set of partitions for you?

(duplicate pop-up message for: mmcblkboot1)

Choosing Yes crashes/closes installer. Choosing No goes to this section;

Install the GRUB Boot menu on /dev/mmcblk0

Once I confirm this the installer shows the "Creating partitions on /dev/mmcblk0" message. After approx. 5 seconds, this message box pops up:

The partition /dev/mmcblk01 could not be created. The installation will stop. Restart the computer and try again.

MANUAL PARTITIONING

So, I tried manual partitioning as an alternative option but get stuck with a different problem...

(receive the same "No partition table was found on the hard drive: mmcblkboot0..." pop-up as above)

I can choose Edit "Free space" partition and create a Primary partition (ext4). But can't create a Swap partition because the Logical Partition option is greyed-out.

Not sure if this is a clue, but whenever I remove all partitions in Live GParted, they reappear again like this;




Does any one know what are 'mmcblkboot0' and 'mmcblkboot1' and how/should I get rid of them?

I would really love somebody's help to solve this one and point me in the right direction to a happy installation please?


UPDATE
To help, here's the install code;

Code: Select all

mint@mint:~$ sudo live-installer
Excluding /dev/sda (detected as the live device)
Can't find model in blkid output: ['disk', 'mmcblk0', '0', '58.2G']
Can't find model in blkid output: ['disk', 'mmcblk0boot0', '0', '4M']
Can't find model in blkid output: ['disk', 'mmcblk0boot1', '0', '4M']
Can't find model in blkid output: ['loop', 'loop0', '0', '1.7G']
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Starting PartitionSetup()
Excluding /dev/sda (detected as the live device)
Can't find model in blkid output: ['disk', 'mmcblk0', '0', '58.2G']
Can't find model in blkid output: ['disk', 'mmcblk0boot0', '0', '4M']
Can't find model in blkid output: ['disk', 'mmcblk0boot1', '0', '4M']
Can't find model in blkid output: ['loop', 'loop0', '0', '1.7G']
Disks:  [('/dev/mmcblk0', 'mmcblk0 (62 GB)'), ('/dev/mmcblk0boot0', 'mmcblk0boot0 (4 MB)'), ('/dev/mmcblk0boot1', 'mmcblk0boot1 (4 MB)')]
    Analyzing path='/dev/mmcblk0' description='mmcblk0 (62 GB)'
      - Found the device...
      - Found the disk...
      - Looking at partitions...
           -> 2 free space partitions
           -> 1 primary partitions
           -> 0 logical partitions
           -> 0 raid partitions
           -> 0 LVM partitions
           -> set of 3 partitions
              -> Building partition object for /dev/mmcblk0p1
                  . length 585728
                  . size_percent 1
                  . size 299.9 MB
                  . name /dev/mmcblk0p1
                  . type Unknown
                  . About to mount it...
mount: /tmp/live-installer/tmpmount: wrong fs type, bad option, bad superblock on /dev/mmcblk0p1, missing codepage or helper program, or other error.
                  . value error!
WARNING: Partition /dev/mmcblk0p1 or type 0 failed to mount!
                  . self.os_fs_info : Unknown, self.description , self.free_space , self.used_percent 0
                  . umounting it
                  . done
(u'/dev/mmcblk0p1', '299.9 MB', 299892736.0)
              -> Building partition object for /dev/mmcblk0p-1
                  . length 4062
                  . size_percent 1
                  . size 2.1 MB
                  . name 
                  . type Free space
                  . About to mount it...
mount: /tmp/live-installer/tmpmount: special device /dev/mmcblk0p-1 does not exist.
df: /dev/mmcblk0p-1: No such file or directory
                  . value error!
WARNING: Partition /dev/mmcblk0p-1 or type 4 failed to mount!
                  . self.os_fs_info : Free space, self.description , self.free_space , self.used_percent 0
                  . umounting it
                  . done
(u'/dev/mmcblk0p-1', '2.1 MB', 2079744.0)
('skipping ', u'/dev/mmcblk0p-1', 2079744.0)
              -> Building partition object for /dev/mmcblk0p-1
                  . length 121552863
                  . size_percent 79
                  . size 62.2 GB
                  . name 
                  . type Free space
                  . About to mount it...
mount: /tmp/live-installer/tmpmount: special device /dev/mmcblk0p-1 does not exist.
df: /dev/mmcblk0p-1: No such file or directory
                  . value error!
WARNING: Partition /dev/mmcblk0p-1 or type 4 failed to mount!
                  . self.os_fs_info : Free space, self.description , self.free_space , self.used_percent 0
                  . umounting it
                  . done
(u'/dev/mmcblk0p-1', '62.2 GB', 62235065856.0)
      - Found partitions...
      - Iterating partitions...
        . Appending partition /dev/mmcblk0p1...
        . Appending partition ...
      - Loading HTML view...
    Analyzing path='/dev/mmcblk0boot0' description='mmcblk0boot0 (4 MB)'
      - Found the device...
      - Found an issue while looking for the disk: /dev/mmcblk0boot0: unrecognised disk label
    Analyzing path='/dev/mmcblk0boot1' description='mmcblk0boot1 (4 MB)'
      - Found the device...
      - Found an issue while looking for the disk: /dev/mmcblk0boot1: unrecognised disk label
Finished PartitionSetup()
Loading HTML string
Showing the partition screen
 ## INSTALLATION 
 --> Installation started
umount: /target/dev/shm: no mount point specified.
umount: /target/dev/pts: no mount point specified.
umount: /target/dev/: no mount point specified.
umount: /target/sys/: no mount point specified.
umount: /target/proc/: no mount point specified.
umount: /target/run/: no mount point specified.
 --> Mounting partitions
 ------ Mounting /run/live/medium/live/filesystem.squashfs on /source/
EXECUTING: 'mount -o loop -t squashfs /run/live/medium/live/filesystem.squashfs /source/'
 --> Creating partitions on /dev/mmcblk0
mkpart primary 2MB 302MB
Could not find /dev/mmcblk01, waiting 1s...
Could not find /dev/mmcblk01, waiting 1s...
Could not find /dev/mmcblk01, waiting 1s...
Could not find /dev/mmcblk01, waiting 1s...
Could not find /dev/mmcblk01, waiting 1s...
mint@mint:~$ 

Also, discovered somebody that looks like they had the same problem on the blog here: https://blog.linuxmint.com/?p=3867

Juan
March 27, 2020 at 12:02 am

Install hangs at ‘Partitioning’…
Analyzing path=’/dev/mmcblk0boot0′ description=’mmcblk0boot0 (4 MB)’
– Found the device…
– Found an issue while looking for the disk: /dev/mmcblk0boot0: unrecognised disk label
Performing a full disk format
Error: Operation not permitted during write on /dev/mmcblk0boot0

Tried soloution from https://github.com/linuxmint/lmde-3-cin ... /issues/13 but replacement live-installer is lower version than provided in LMDE 4 iso. and fails to install.
Any help greatly appreciated.

jean-claude
March 27, 2020 at 8:55 pm

Hi Juan,
Before install, create with GParted a new partition table in GPT, this will erase all your mmcblk0,
but this should solve your partitioning issue in my opinion.

Juan
March 28, 2020 at 10:36 pm

Thanks, I used gparted and got down to a partition free mmcblk0. I then tried running the ‘live-installed which failed reporting not being able to find /dev/mmcblk0boot1??? I rebooted the tablet into the LMDE live session to find that /dev/mmcblk0boot0 had been (re) created by booting into the LMDE live session from the USB. Your help is much appreciated, thank

Not sure if this helps in any way, but I don't fully understand the steps this person did to find the solution - I just opened GParted and deleted all partitions again, created one new Primary partition and ran the installer, but the same problem happened again. Did I miss something here?? What does "create with GParted a new partition table in GPT" mean?


UPDATE
OK, figured out how to create a new partition table in GPT: GParted \ Device \ Create Partition Table \ Select type 'gpt'

Followed the same steps that Juan did above - attempted install straight after GPT partition table and experienced the same problem also tried after restarting laptop. What the hell's going on here!?


UPDATE
As a test I tried to install LMDE3, but the laptops touchpad didn't work during installation so went with Mint 19.3 instead... and it successfully installed
(but I did have to change the Rufus settings to get this to work - Partition scheme: GPT \ Target system: UEFI)

So repeated the Rufus settings above for LMDE4 and attempted to install over Mint 19.3, but the installation failed again like before

What has LMDE4 got against Asus VivoBook's?? And why is LMDE4 so obsessed with 'mmcblk0boot0' and 'mmcblk0boot1'??

HELP ME PLEASE!?!? Any one?


Thanks,

[ObiSandwich]

After investigating this further and exploring other possible Debian/UEFI solutions, my tiny brain is frazzled and beat.

I had hoped somebody out there was experiencing the same issue, but I guess I've discovered an isolated LMDE4/VivoBook issue... Or, VivoBook people stick to Windows 10!

I'll just have to go with a standard Mint 19.3 install for now and just hope the clever LMDE developers fix this in future releases.

[Adonnen]

I hope you are still following this. I am having the exact same issue on my 32 gb Dell inspiron 3162. I guess I'll bite the bullet and try non-debian, but first, I am going to try to get LMDE 3 and upgrade from there. I have some mice if the touchpad doesn't work.

[Joesmith]

This is happening to me too. I was trying to install Debbie on an SD card on Mint Box mini 2. Regular Debian installs fine on an SD card. As soon as Debbie starts to install the first partition, I get: "The partition /dev/mmcblk01 could not be created. The installation will stop. Restart the computer and try again."

I figured I would let you guys know.

Joe

[Karibou1312]

Hi !
I have the same problem !
I try to install LMDE4 on Asus E200HA with 32GB EMMC and 4GB RAM.
But impossible ! He cannot create partition.
I have this message of error when he create partition on emmblk0 :
"'ascii codec can't decode byte 0xc3 in position 14 : ordinal not in range (128)"

Have you found a solution to this problem ?

After that, I installed Manjaro AND I had no problem ! Very easy installation !

Why Linux Mint Ubuntu works and Linux Mint Debian Edition doesn't work ?

If you have a solution, please let me know.

If I install LMDE3 and after I upgrade to LMDE4 it will work normally ? Is that the solution ?

Will Linux Mint correct thus issue ?

Best regards

Karibou1312

[Karibou1312]

Hello,
Please, have you some solution about this issue ?
How can I install LMDE 4 on my Asus E200HA ? He has a eMMC.
The installation of LMDE 4 crashes when he try the partitioning of the eMMC named mmcblk0.
Many thanks.
Karibou1312

[Karibou1312]

Hello,
I succeed with the installation of LMDE 4 !!!
It was difficult...

See here how I did :
viewtopic.php?f=63&t=341260&p=1981017#p1981017

Best regards,

karibou1312

[revelle]

I had a very similar issue installing to an HP Stream 11 notebook just now. Everything I looked at said I needed to use the 32bit version but i just managed to get past the partition error and install from a live UEFI boot 64bit USB. Kind of simple in the end but I'm new to Linux. I had to use the manual partitioning option where you designate which partition is for what. Did it a bit backwards by starting the installer (from console to see what was happening), choosing manual over automatic and then learning what partitions to set up where by following the error messages tutorials online were wrong for partitioning.

Can i suggest for trial and error people like me... that the need for a /boot/efi partition at the start of the disk - is not the last partition that it checks for and tells you about? And a hint about where to put the Grub bootloader (question that comes up on auto as well) would be helpful. I chose the same partition as / which was about the 3rd one on the disk. That worked, don't know if it's technically correct or not.

I'm posting this here because of the similarities. There were/are 2 hidden read only partitions on the internal eMMC the same as mentioned above, ending in boot0 and boot1, that I think could be something to do with the problem. 4mb each, it asks you if you want to put a partition table on them even if trying to install to something else like a USB stick. Select no or the installer will crash. They seem to not be easily touched and I don't know where they are on the disk, getting in the way and not letting the installer wipe the drive. Even if you've obliterated the Vendor recovery, Microsoft and Windows partitions they are still there hiding.

That's my noob input, I probably should have installed a non cinnamon version on this garbage excuse for a notebook but at least I can say LDME 4 64bit works (including networking and all the weird hardware) on this particular HP Stream 11 G Pro or whatever its full name is.

[antikythera]

That's my noob input, I probably should have installed a non cinnamon version on this garbage excuse for a notebook but at least I can say LDME 4 64bit works (including networking and all the weird hardware) on this particular HP Stream 11 G Pro or whatever its full name is.

Nicely done, sadly there is no official alternative ISO other than Cinnamon for LMDE4. The German Linux Mint community has a couple of guys making some though. If you can work your way around the german language interface initially you can select another language to use and install.

[revelle]

Ah I can read a bit of German, but I'll see how this one goes for now. I need to add to my post as there was an extra step and i see OP already tried manually partitioning.

I ran the auto install option first on the drive while unpartitioned/unallocated...as totally blank as possible. It failed as usual with the error message at creating the first partition. When i looked though it had actually created a 4GB swap partition as the first (visible) one on the drive. I recreated all the partitions including the swap partition but smaller, and not first. So my drive in the end looked like this before install succeeded:

/dev/mmcblk0p1 - 130mb FAT32 EFI partition mounted at /boot/efi - also flagged accordingly
/dev/mmcblk0p2 - 2GB Linux Swap - no idea if it's using it yet but it's there, it says it's active after booting into Mint
/dev/mmcblk0p3 - 25GB Ext4 mounted at Filesystem Root (the / dropdown option when installing manually). Also where the grub bootloader went.
/dev/mmcblk0p4 - 4GB Ext4 (all that was left) mounted at /home

/dev/mmcblk0boot0 (read only) is still there. It's showing up as a separate 4mb disk. It seems that it's possibly a container for mmcblk0boot1. Mystery block. Maybe the live USB puts GRUB there for UEFI and Legacy (both those were boot options but only UEFI actually loaded).

Another thought is that maybe there isnt enough RAM to install anything since the live USB takes it all up. So it makes a swap partition, then tries to make the EFI system partition on top of it. Both at mmcblk0p1.

Why these notebooks have a 32gb eMMC larping as harddrives is a question for another day. It's worked in the end so maybe this will help somebody. The model name of my drive is BGND3R incase that helps with anyone searching the forums.

[antikythera]

Why this notebook has a 32gb eMMC larping as a hard drive is a question for another day.

Because your HP Stream is a Chromebook, not a notebook. eMMC are very cheap, tiny and can be soldered onto the system board. You've essentially got an Android tablet with a decent keyboard there rather than a traditional notebook.

Your swap is active so it will be used as needed, 4GB was probably assigned to allow for hibernation. If you don't intend to use that feature then shrinking it to 2GB is not an issue.