Openmandriva LX4 and EFI

ben79 · May 18, 2019, 8:17pm

You’re losing me here. This is from OpenMandriva Lx 4.0 installed from RC ISO:

$ sudo parted -l
[sudo] password for ben79: 
Model: ATA WDC WD1002FAEX-0 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size   File system  Name  Flags
 1      1049kB  500GB   500GB  ext4
 2      500GB   1000GB  500GB  ext4


Model: ATA Crucial_CT500MX2 (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name  Flags
 1      17.4kB  538MB   538MB   fat32                 boot, esp
 2      538MB   5907MB  5369MB  linux-swap(v1)        swap
 3      5907MB  27.4GB  21.5GB  ext4
 4      27.4GB  38.1GB  10.7GB  ext4
 5      38.1GB  59.6GB  21.5GB  ext4
 6      59.6GB  70.3GB  10.7GB  ext4
 7      70.3GB  91.8GB  21.5GB  ext4
 8      91.8GB  103GB   10.7GB  ext4
 9      103GB   124GB   21.5GB  ext4
10      124GB   135GB   10.7GB  ext4
11      135GB   156GB   21.5GB  ext4
12      156GB   167GB   10.7GB  ext4
13      167GB   188GB   21.5GB  ext4
14      188GB   199GB   10.7GB  ext4
15      199GB   333GB   134GB   ext4

I did not install parted which means it is a system package. So it is part of a default install. So run that on your OpenMandriva installation and post the entire output including the command you used here.

ben79 · May 18, 2019, 8:29pm

If you really want to solve this problem let’s start over. Mount the ‘Live’ ISO and simply run:

$ sudo parted -l

and post the output here. That will tell us if the ISO system is recognizing all drives or not. You might also run:

$ sudo os-prober

to see what other operating systems the ISO system “sees”. And post that here also.

Post-edit: In retrospect we or I should have started with “Is OpenMandriva Lx 4 seeing all drives?” and then “If it is not, why not?”. But the first thing to establish from a problem solving perspective is simply are all drives recognized or not.

Post-edit-2: This above information applies to any user with a problem with a drive not being recognized or another operating system not being recognized. Any user is well advised to post screen-shots. Screen-shots eliminate a lot of confusion and misinformation.

ben79 · May 18, 2019, 9:06pm

Then the next step is to run the Calamares installer from Konsole so we can see logs. Then copy and paste the entire Konsole output including the command you used to a .txt file and attach that file here. To run Calamares in Konsole you do this ( the -d is for debug):

$ pkexec calamares -d

Then in the logs you would look for this:

That will tell for sure whether Calamares is or is not recognizing all drives it should. And post sceen-shots.

The above I am doing from ‘Live’ ISO myself.

Post-edit: Any user having any problems with Calamares installer is advised to run Calamares as shown above and put the entire Konsole output including the command you used in a .txt file and attach that to your forum post. Any user is well advised to post screen-shots. Screen-shots eliminate a lot of confusion and misinformation.

stephane · June 2, 2019, 10:46am

you should check more often

rugyada · June 2, 2019, 11:21am

Sorry check more often what, exactly?

ben79 · June 2, 2019, 3:05pm

I don’t see any point in keeping a thread open if the Original Poster can’t provide requested information exactly as requested. If you expect people to take time out of their busy day to help you this is not to much to ask.

rugyada · June 2, 2019, 3:38pm

So to end with a bang this false-statements-festival thread, worth to mention that one of our most active devs is one of calamares devs too.
Cannot guess anyone/anything more up2date than OM on this regard

ben79 · June 12, 2019, 4:36am

This is reopened because I just confirmed this is a very real bug with the new ISO # 2535. It will happen in one has existing partitions and uses “Manual Partitioning” and attempts to use an existing /boot/efi partition.

OK a logical question is why did I not see this in my previous testing. Because I was using ISO’s that did not have this bug. The most recent used by me before this was ISO # 2485. Worth noting is that OP did not tell us what ISO he was using. This points out the huge importance of accurate information for such problems. If the ISO’s I was using previously had this problem I would have seen it right away because this is how I do each and every hardware install on my boxes.

Also reported here.

ben79 · June 12, 2019, 4:54am

I think there is no functional problem, nothing technically wrong. This looks like an error message that does not belong.

This based on a hardware install of ISO 2535 where other than the error message everything appears to be normal. It did install grub2 menu ect.

ben79 · June 13, 2019, 3:27pm

From your /dev/sdb:

That, ‘msftdata’, is not an EFI partition. As long as it says ‘msftdata’ it will give that error.

This one probably is legitimate EFI partition if “démarrage” means boot. It is from you /dev/sda.

Also if you run ‘sudo fdisk -l’ it should say:

/dev/sdx1 34 1048609 1048576 512M EFI System

If it does not say EFI System then it isn’t. And it must have boot and esp flags as listed by parted. So I see 2 options for you to avoid that error:

If both conditions are not met then you will need to delete the /dev/sdb1 and create a new /boot/efi.
Or just use the existing /boot/efi on /dev/sda1 with ‘Keep’ selected (don’t format). It will hold entries from many different operating systems. You can switch which it uses in your BIOS or with “efibootmgr” (example):

$ sudo efibootmgr
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0001,0002,0003,0004,0005
Boot0000* openmandriva
Boot0001* opensuse
Boot0002* grub
Boot0003* UEFI:CD/DVD Drive
Boot0004* Hard Drive 
Boot0005* CD/DVD Drive

That would be booting from 0000 or OpenMandriva. To change the boot order you would use -o like:

$ sudo efibootmgr -o 0005,0001,0002,0003,0004,0000
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0005,0001,0002,0003,0004,0000
Boot0000* openmandriva
Boot0001* opensuse
Boot0002* grub
Boot0003* UEFI:CD/DVD Drive
Boot0004* Hard Drive 
Boot0005* CD/DVD Drive

Now it will look first to boot from 0005 CD/DVD Drive. So obviously it will boot from the first entry in the list unless you go in to your BIOS and select another.

Post-edit: By now is obvious I’m learning about this myself. The above is based on what I know at this moment. If I get something wrong a dev will correct me. Count on that.

stephane · June 13, 2019, 6:09pm

in fact some calamares version 3.27 introduce regression & issue on that ,
manjaro use calamares since 2016 , bur be careful on that
each distribution report for “same” calamares , so you mays have regression

on version 3.27 the team was tested new version libparted with one flag , instaed of 2 ( boot,esp )
version 3.29 is ok

https://forum.manjaro.org/t/manjaro-does-not-boot-after-installation/89729

abucodonosor · June 13, 2019, 6:29pm

In fact that is not true.

Manual partitioning problem has nothing to do what so ever with parted but
new kpmcore4.

Manjaro switched back to kpmcore3 so it has nothing to do with the calamares version.

That means if your /boot/efi was create wrong already , eg: not flagged ‘EFI System’
in Manual partitioning if you want to keep that partition won’t work right now with
either calamares version and kpmcore4.

And is easy to fix if you know you have this problem.

Before you install just do that:

sudo fdisk /dev/sdX
type p ( and notice which is the efi partition )
type t
( select the partition nr of the efi partition )
type 1
type w
type quit

Start installation and Manual partitioning will work just fine

stephane · June 13, 2019, 6:41pm

how many users will do this ?

abucodonosor · June 13, 2019, 6:43pm

You know that or don’t you ?

A user can’t know but that is not what I’ve suggested to you ?

stephane · June 13, 2019, 7:52pm

i have tried with gparted under manjaro to solve the flag on sdb
but it needs boot and esp , not good if twice boot is selected

as i couldn’t flag boot&esp for mountpoint under calamares , i cant select /boot/efi on the other disk sdb for install , kpmcore is a part of calamares

next iso will be better

abucodonosor · June 13, 2019, 9:05pm

kpmcore is a part of calamares

No is not part of calamares.

as i couldn’t flag boot&esp for mountpoint under calamares

Because there is no ESP is merged into bootflag in kpmcore4

i have tried with gparted under manjaro to solve the flag on sdb

I have told you already how to solve that, didn’t I ?

ben79 · June 17, 2019, 2:19am

This is noted in our Errata for OM Lx 4.0 final release.

And bug report:

https://issues.openmandriva.org/show_bug.cgi?id=2489