Boot problem

holden093 · 2017-01-31 09:56:19

I installed this distro into my new laptop (Lenovo ideapad 100s) but It wont go over a strange boot menu

http://i.imgur.com/2RRPDlA.jpg

I booted through the live usb and re-installed the grub through chroot (I followed this guide http://wiki.ubuntu-it.org/Amministrazio … Ripristino, it's in Italian since it's my native language) but the same issue came back

Thanks in advance for your help

Kevin

Mod Note: oversized image replaced with link, please limit images to ~250x250px
-HoaS

Last edited by Head_on_a_Stick (2017-01-31 09:59:21)

Head_on_a_Stick · 2017-01-31 10:00:56

From the live USB, please post the full output of this command:

sudo parted --list

holden093 · 2017-01-31 10:02:26

Head_on_a_Stick wrote:

From the live USB, please post the full output of this command:
sudo parted --list

user@debian:~$ sudo parted --list
Model: Generic STORAGE DEVICE (scsi)
Disk /dev/sda: 7851MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size   Type     File system  Flags
 1      32.8kB  884MB  884MB  primary               boot, hidden


Error: /dev/mmcblk0boot0: unrecognised disk label
                                                                 Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/mmcblk0boot0: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags: 

Error: /dev/mmcblk0boot1: unrecognised disk label
                                                                 Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/mmcblk0boot1: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags: 

Model: MMC DB4032 (sd/mmc)
Disk /dev/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system     Flags
 1      1049kB  29.9GB  29.9GB  primary   ext4
 2      29.9GB  31.3GB  1318MB  extended
 5      29.9GB  31.3GB  1318MB  logical   linux-swap(v1)

Head_on_a_Stick · 2017-01-31 10:19:47

Does Windows still work?

It looks like the eMMC device partition table may be broken.

Have you ever managed to boot into the installed BunsenLabs system?

Were there any errors during the installation process?

holden093 · 2017-01-31 10:22:37

Windows' not here anymore

I never managed to boot into the installed BunsenLabs system

No errors during the installation process

Last edited by Head_on_a_Stick (2017-01-31 16:31:26)

holden093 · 2017-01-31 13:34:11

Thank you, but the "Secure Boot" option is missing from my bios :-( I've already switched to the Legacy mode, anyway..

Last edited by Head_on_a_Stick (2017-01-31 16:31:37)

Head_on_a_Stick · 2017-01-31 16:39:22

holden093 wrote:

I followed this guide http://wiki.ubuntu-it.org/Amministrazio … Ripristino

That guide should work for BunsenLabs (with a few changes), can you please confirm the *exact* commands that you used?

At any rate, I think that the partition table on your storage device is broken.

We can try to clear the table from the BunsenLabs "live" USB:

sudo apt install gdisk
sudo sgdisk --zap-all /dev/mmcblk0

Check if the table is cleared by using `parted --list` again, post the output here if you can't understand it.

It may be best to then use gparted (or similar) to make the partitions you want *before* starting the installer again.

Also, there is no need to "full quote" a question if you are just replying directly.

I have edited your earlier posts, I am sure you will agree that the thread is more readable now

Head_on_a_Stick · 2017-02-01 09:45:44

@GM: the OP can boot the BunsenLabs live ISO image and so must have enabled CSM ("Legacy" mode), I think the problem may have been that the eMMC storage device had a GUID partition table and this was not cleared correctly during the installation process, this is why the boot is failing.

My given commands should eradicate all traces of both GUID and traditional "MRB-style" (msdos) partition tables and leave the drive "clean" for re-formatting.

@OP: be sure to chose an "msdos" partition table, GPT might work but would require motherboard compatibility and a separate BIOS boot partition to hold the GRUB bootloader — this is not needed if a traditional MBR is used.

holden093 · 2017-02-01 09:51:52

Right now I'm at work, I will try in the Evening and let you guys know! Thank you

holden093 · 2017-02-02 12:45:16

Head_on_a_Stick wrote:

holden093 wrote:
I followed this guide http://wiki.ubuntu-it.org/Amministrazio … Ripristino
That guide should work for BunsenLabs (with a few changes), can you please confirm the *exact* commands that you used?

The exact commands that I used were

sudo mount /dev/mmcblk0p1 /mnt

To mount the partition with the operative system, and

sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys

sudo chroot /mnt

To access chroot and after that

grub-install /dev/mmcblk0
update-grub2

To install grub, I've done this a couple of times to restore the bootloader on my work computer (which runs Ubuntu linux) and since this distro is debian based I figured out that it might would work.

I tried the command that you suggested me, this is the output

user@debian:~$ sudo sgdisk --zap-all /dev/mmcblk0

***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. 
***************************************************************

Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
GPT data structures destroyed! You may now partition the disk using fdisk or
other utilities.
user@debian:~$ parted --list
user@debian:~$

Is this any good?

Kevin

Head_on_a_Stick · 2017-02-02 12:59:22

holden093 wrote:

Is this any good?

I think so, yes.

This would confirm it:

sudo parted --list

If the drive is clear then you can try running the BunsenLabs installer again — it should have no problems creating it's own partition table now.

holden093 · 2017-02-02 13:10:41

I've tried running the BunsenLabs installer and unfortunately the same boot screen appeared

Head_on_a_Stick · 2017-02-02 13:15:37

Can we see this output now that the installer has finished:

sudo parted --list

holden093 · 2017-02-02 13:24:43

Here you go

user@debian:~$ sudo parted --list
Model: Generic STORAGE DEVICE (scsi)
Disk /dev/sda: 7851MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size   Type     File system  Flags
 1      32.8kB  884MB  884MB  primary               boot, hidden


Error: /dev/mmcblk0boot0: unrecognised disk label
                                                                  Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/mmcblk0boot0: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags: 

Error: /dev/mmcblk0boot1: unrecognised disk label
                                                                  Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/mmcblk0boot1: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags: 

Model: MMC DB4032 (sd/mmc)
Disk /dev/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system     Flags
 1      1049kB  9000MB  8999MB  primary   ext4            boot
 2      9001MB  31.3GB  22.3GB  extended
 5      9001MB  12.0GB  2999MB  logical   ext4
 6      12.0GB  14.6GB  2556MB  logical   linux-swap(v1)
 7      14.6GB  15.0GB  398MB   logical   ext4
 8      15.0GB  31.3GB  16.3GB  logical   ext4


user@debian:~$

Head_on_a_Stick · 2017-02-02 14:04:03

Oh dear, the installer doesn't seem to like your eMMC storage device

I will suggest clearing the drive again:

sudo sgdisk --zap-all /dev/mmcblk0

Then check `sudo parted --list` and make sure that these messages are gone:

Error: /dev/mmcblk0boot0: unrecognised disk label

The system will not boot unless the above error message is *not* present in the `sudo parted --list` output.

You can try creating a partion table *before* starting the installer by using `gparted` from the live USB, that might work better.

Head_on_a_Stick · 2017-02-02 14:06:47

Hold the presses!

http://unix.stackexchange.com/questions … eapad-100s

Try disabling the "speed boot" option from your firmware ("BIOS") menus.

holden093 · 2017-02-02 14:17:05

I've found that solution but I don't have anything related to "speed boot" in my bios..

ohnonot · 2017-02-03 06:45:31

holden093 wrote:

Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
GPT data structures destroyed! You may now partition the disk using fdisk or
other utilities.

shouldn't one reboot after this?

holden093 · 2017-02-03 14:56:47

That's the first thing that I did no results. It looks like that Bunsenlabs doesn't like my laptop. I will try with the next release!

Head_on_a_Stick · 2017-02-04 10:39:50

holden093 wrote:

I will try with the next release!

We should have some Deuterium point-release ISO images out soon that may fix your issues, I will bump this thread when they are ready.

#1 2017-01-31 09:56:19

Boot problem

#2 2017-01-31 10:00:56

Re: Boot problem

#3 2017-01-31 10:02:26

Re: Boot problem

#4 2017-01-31 10:19:47

Re: Boot problem

#5 2017-01-31 10:22:37

Re: Boot problem

#6 2017-01-31 13:34:11

Re: Boot problem

#7 2017-01-31 16:39:22

Re: Boot problem

#8 2017-02-01 09:45:44

Re: Boot problem

#9 2017-02-01 09:51:52

Re: Boot problem

#10 2017-02-02 12:45:16

Re: Boot problem

#11 2017-02-02 12:59:22

Re: Boot problem

#12 2017-02-02 13:10:41

Re: Boot problem

#13 2017-02-02 13:15:37

Re: Boot problem

#14 2017-02-02 13:24:43

Re: Boot problem

#15 2017-02-02 14:04:03

Re: Boot problem

#16 2017-02-02 14:06:47

Re: Boot problem

#17 2017-02-02 14:17:05

Re: Boot problem

#18 2017-02-03 06:45:31

Re: Boot problem

#19 2017-02-03 14:56:47

Re: Boot problem

#20 2017-02-04 10:39:50

Re: Boot problem

Board footer