Page 1 of 1

Installation problems

PostPosted: Jun 13th, '14, 17:30
by magi
hello,

I'm having a problem installing Mageia to my main computer.

I have two desktop pc's, one is the main pc which i'll call pc1 and the other then will be pc2.
pc1 i use mostly and is connected to the internet while pc2 is not connected and is mainly used for testing and grand kids playing games.
Both pc's have asus mobos; pc1 m5a97 and pc2 m5a97le. These mobos have dual firmware namely uefi and bios.
In other words, i could install a uefi compatible os in either mbr or efi mode.

I successfully installed Mageia on pc2 mbr mode dual booting with windows 7.
( i use Terabyte Unlimited's BIBM to manage partitions and booting in mbr mode)
But am unable to install Mageia on pc1.

I create partitions ( one 30gig linux native and one 2gig swap) and the boot item using BIBM and boot into the install using the Mageia dvd.
Everything goes ok 'till i get to the partitions. I click on the partition 30gig partition and mount "/".
Continuing, it asks me to format and i reply "yes" which is then followed by a error message that the partition could not be mounted.
Error message; a bunch of numbers plus "mnt/media/win_d2 failed.

I repeated the install on several different disks ( an SSD, harddrive and also a 32gig usb configured as a hard drive) with the same negative results.

i would like to perhaps install onto a GPT disk in uefi mode but am not sure how to handle the boot loader.
you see, i have two windows os's installed on this disk.
but that is another issue.

If anyone has any thoughts on these i would be grateful to hear from you.

Cheers
Bernard Boonstra

Re: Installation problems

PostPosted: Jun 14th, '14, 12:13
by doktor5000
magi wrote:Everything goes ok 'till i get to the partitions. I click on the partition 30gig partition and mount "/".
Continuing, it asks me to format and i reply "yes" which is then followed by a error message that the partition could not be mounted.
Error message; a bunch of numbers plus "mnt/media/win_d2 failed.


The error is about an NTFS partition in the system. Can you try custom partitioning, and change the windows partitions to not have a mountpoint?

Re: Installation problems

PostPosted: Jun 14th, '14, 16:48
by magi
Alright, thanks, i'll give that a go.

Bernard B

Re: Installation problems

PostPosted: Jun 20th, '14, 23:57
by magi
All right, I tried to install twice again, once in legacy (MBR) and the other in UEFI.
Both brought the same results with the installer telling me that a windows partition is mounted and I should unmount it.
I located the offending partition using gparted and according to the information this partition is unmounted as is the rest of the windows partitions.

If I cannot get it installed should I perhaps install an older version of Mageia and then update the kernel?
Would that be a viable alternative?

Thanks for any comments,

Bernard B

Re: Installation problems

PostPosted: Jun 21st, '14, 00:40
by doktor5000
magi wrote:All right, I tried to install twice again, once in legacy (MBR) and the other in UEFI.
Both brought the same results with the installer telling me that a windows partition is mounted and I should unmount it.

So in installer via custom partitioning you removed the mountpoints for all windows partitions and it still threw an error? What partition was that about?
You can switch to a terminal via Ctrl+Alt+F3 or Ctrl+Alt+F4, not sure which holds the error message.

magi wrote:I located the offending partition using gparted and according to the information this partition is unmounted as is the rest of the windows partitions.

Huh? If you boot gparted, how does that reflect the Mageia installer environment? Also per default in gparted no partition will be mounted, so that comparison is totally useless.

Re: Installation problems

PostPosted: Jun 21st, '14, 01:51
by magi
No, i didn't boot the gparted by itself. I was referring to the gparted in the installation.
Sorry, i was not clear about that.

Bernard

Re: Installation problems

PostPosted: Jun 21st, '14, 03:12
by doktor5000
That's not gparted, it's called diskdrake: Check http://doc.mageia.org/installer/4/en/co ... drake.html

You still didn't answer the question from previous posts. You shouldn't make sure the partitions are not mounted, but remove the mountpoint definitions for those.
Did you do that?

Re: Installation problems

PostPosted: Jun 21st, '14, 05:33
by magi
Diskdrake it is. I thought wrongly it was gparted.

How does one remove mountpoint definitions on partitions ?

Thanks for your time.

Bernard

Re: Installation problems

PostPosted: Jun 21st, '14, 11:16
by doktor5000
Click on the windows partition, click on mountpoint, and empty that field.

Re: Installation problems

PostPosted: Jun 22nd, '14, 18:33
by magi
Thanks, that worked.

One more hurdle to get over.
I installed Mageia up to the boot loader configuration.
Have 3 drives and installed Mageia on a SSD in its own partition.
This drive also 2 window OS's. The partitioning and booting is managed by BIBM from Terabyte Unlimited.
With other linux installs i usually place the boot loader on the root "/" partition and and it works.
However when i did this with the Mageia install i got an error message;
"Cannot install boot loader on a btrfs partition.....propagated.

Any tips?
Thanks again.
Bernard B

Re: Installation problems

PostPosted: Jun 22nd, '14, 19:56
by doktor5000
So why did you choose a btrfs partition? grub legacy does not support btrfs, FWIW.

Re: Installation problems

PostPosted: Jun 22nd, '14, 20:39
by magi
Actually, I have no idea what a btrfs partition is or where it came from on my system.
I googled about it but could not come up with anything that would be helpful.

Like I said earlier, I places the boot loader to the root partition.
I'm probably missing something here ?

Thanks.
Bernard B

Re: Installation problems

PostPosted: Jun 27th, '14, 15:51
by magi
So, how could i possibly get a btrfs partition on system?
Using file information, i have no such partitions.

Re: Installation problems

PostPosted: Jun 27th, '14, 18:14
by doktor5000
Could you at least post the output of fdisk -l or lsblk -fl as root so that others could take a look at your current partitioning? Otherwise this is only guesswork.