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).
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;
(duplicate pop-up message for: mmcblkboot1)No partition table was found on the hard drive: mmcblkboot0 (4MB) Do you want the installer to create a set of partitions for you?
Choosing Yes crashes/closes installer. Choosing No goes to this section;
Once I confirm this the installer shows the "Creating partitions on /dev/mmcblk0" message. After approx. 5 seconds, this message box pops up:Install the GRUB Boot menu on /dev/mmcblk0
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:~$
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.
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?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
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,