Error mounting partition for Mageia 4

[doktor5000]

When I ran CODE: SELECT ALL it returned > which I assume means root.

Nope, that means you probably run "CODE: SELECT ALL" which is not part of the command, that's just from the forum software.
Click on the blue SELECT ALL to only mark the command inside, that's what you want to run.

I ran journalctl -xb > log again. When I typed dir it returned drakx log tmp When i went back into Mint and opened the second last partition before the NTFS folder named Movies6 (This should be the Mageia partition.) and tried to open the root folder it said I did not have sufficient permsissions to view the contents.

So you saved it to /root/log
You need to have root permissions to view or copy that file. Try

Code: Select all

sudo cat /path/where/Mageia/partition/is/mounted/root/log

where /path/where/Mageia/partition/is/mounted is a placeholder to the path where that Mageia partition is mounted under Mint.
Could be /run/media/username/partitionname or so.

[archp2008]

arch@arch-System-Product-Name ~ $ sudo cat /media/arch/957157e2-82de-446f-bb71-0970c79b26d8/root/log
[sudo] password for arch:
cat: /media/arch/957157e2-82de-446f-bb71-0970c79b26d8/root/log: No such file or directory

???

arch@arch-System-Product-Name ~ $ sudo cat /run/media/arch/957157e2-82de-446f-bb71-0970c79b26d8/root/log
[sudo] password for arch:
cat: /run/media/arch/957157e2-82de-446f-bb71-0970c79b26d8/root/log: No such file or directory
arch@arch-System-Product-Name ~ $

[doktor5000]

Sorry, if you don't know where that file is on your box, can't help much further.

I'd suggest going with what I've already proposed to get the Mageia system booting.

Otherwise, you can simply edit /etc/fstab when in Mageia emergency shell and comment out all noncritical/windows filesystems by prepending a # on the line, or by adding nofail to their options. Also see https://wiki.mageia.org/en/Mageia_4_Err ... rrect_UUID

[archp2008]

I'm sorry for my ignorance, but I am going to struggle to figure out how to edit /etc/fstab when in the emergency shell. I can get into the etc directory and view fstab along with many other files but have no idea what commands are usable to edit fstab in the shell. The reason I can't identify the Mageia partition from inside Mint is that when I click on Computer it does not show the partitions in the same order as they are on the disk. Also the sizes of the partitions are not the same as shown in a parition editor like Gparted. When I use GParted I can tell exactly which one is the Mageia partition because it says sdc11 and the UUID ends in e49d and it's the second last partition before the Movies (NTFS) partition. Is there a Linux explorer that enables opening folders and editing of files from an interface that gives the drive number and UUID numbers of the partitions. I notice that in the emergency shell I can see fstab but in the Mint "Computer" view I can only see fstab.d which is empty. I liked Mageia from my experience with Mageia 3 in a virtual setup. I noticed one reviewer rated Mageia as the second best Linux distro ahead of Ubuntu. It's too bad to be unable to use it from my hard drive.

[alex123]

I had this a couple of this,Through this highlight of yours things can be made better.I personally feel that there is a chance necessary for keeping things in order when its about development so yeah keeping it that way is what works.

[doktor5000]

Ok, the command would be vi /etc/fstab in emergency shell - I've described this here already: viewtopic.php?p=46326#p46326
Look, the point is: We need some information why you're being dropped to emergency shell. Either you can find out on your own, or post the relevant information here.
Otherwise we can't help much further than to provide some generic hints.

Although it seems you didn't pay attention to the other hints - if you removed mountpoint definitions for all windows partitions during installation like suggested,
it would not fail to boot trying to mount a windows partition.

For your explorer issue - usually file manager show the size of the partition, or the label if present. If you have that much partitions, my suggestion would be add labels to them so you can easier distinguish them from one another. You can also run sudo lsblk -fl where it will show the UUIDs and where they are mounted.

If you want to test Mageia, you can still take one of the LiveDVD version, write it to an usb drive and boot directly from it.

[archp2008]

Thank you for this. I apologize for my impatience in going ahead with the install without waiting for your replies regarding Windows mount info, etc. I didn't know that Mageia would be so different from Ubuntu distros in this respect. If I had known about these differences I probabably would hot have attempted the installation in the first place. Is it normal for Mageia 4 not to list existing Ubuntu distros in its boot menu at the end of the installation? I will try the commands you listed here and get back to you.

[archp2008]

This is what I got for vi /etc/fstab
https://onedrive.live.com/?cid=FCE7BAB5 ... 53!771&v=3
I did not know how to do a screen capture so I took a photo of the screen.
It looks as though some of it may have scrolled up the screen out of sight. Is there a linux switch similar to the /p in Windows?

[doktor5000]

This is what I got for sudo lsblk -fl from Mint 16 (This is the one that I use to write to MBR).

arch@arch-System-Product-Name ~ $ sudo lsblk -fl
[sudo] password for arch:
NAME FSTYPE LABEL MOUNTPOINT
sda
sda1 ntfs XP
sda2 ntfs Vista x86 SP2
sda3 ntfs Vista x64 SP1
sda4
sda5 ntfs Movies3
sdb
sdb1 ntfs Win7 (x64)
sdb2 ntfs Win8 x64
sdb3 ntfs Win8.1 x64
sdb4
sdb5 ntfs Data2
sdb6 ntfs Movies2
sdc
sdc1 ext3 /
sdc2
sdc5 swap [SWAP]
sdc6 ext3
sdc7 ext4
sdc8 ext4
sdc9 ext4
sdc10 ext4
sdc11 ext4
sdc12 ntfs Movies6
sdc13 ext4
sde
sde1 vfat EOS_DIGITAL /media/arch/EOS_DIGITAL
sr0
arch@arch-System-Product-Name ~ $

This shows everything - even the memory card in the slot. Why does it label the ntfs folder Movies 6 as sdc12, the same as what fstab listed for Mageia. From this I can't tell which of the partitions is Mageia because there is no UUID shown. I am guessing the Mageia partition is sdc11, but there is actually no partition after the Movies 6 partition, so sdc 13 is a mystery to me. Possibly sdc10 could be Mageia. Who knows?

[doktor5000]

For the fstab, that looks good. Simply comment out all the lines referencing ntfs-3g partitions. See the previous post for a link how to use vi.
You can also use any other editor that's available in emergency shell, but I'm not sure which that includes. Maybe nano, emacs, or mcedit ... ?

Seems Mint's lsblk doesn't display UUID by default, maybe an older version? This is what it looks like here:

Code: Select all

[doktor5000@Mageia4 ~]$ sudo lsblk -fl
NAME FSTYPE LABEL   UUID                                 MOUNTPOINT
sda                                                     
sda1 ntfs           5283596B0C6EE41F                     /media/win_c
sda2                                                     
sda5 ext4   MGAroot a8229474-2eb9-48fe-bd56-be606de0fd2f /
sda6 swap   swap    3d760264-99f4-4363-a4dd-860f705bf7a5 [SWAP]
sda7 ext4   MGAhome 2d072f85-753f-492c-b1bb-b87a047bc492 /home
sdb                                                     
sdb1 ntfs   EXTERN3 4000C55B00C55894                     /run/media/doktor5000/EXTERN3
sdb2 ntfs   EXTERN4 2222D88522D85EFB                     /run/media/doktor5000/EXTERN4
sr0

The long form of that would be

Code: Select all

sudo lsblk -o NAME,FSTYPE,LABEL,UUID,MOUNTPOINT -l

[doktor5000]

Thanks for this. This confirms that the Mageia partition is sdc11. So now how do I find that partition outside of the terminal to find that log file?
Only Gparted shows it as sdc11.

Code: Select all

arch@arch-System-Product-Name ~ $ sudo lsblk -o NAME,FSTYPE,LABEL,UUID,MOUNTPOINT -l
[sudo] password for arch:
NAME  FSTYPE LABEL         UUID                                 MOUNTPOINT
sda                                                             
sda1  ntfs   XP            785CD0D55CD08F6E                     
sda2  ntfs   Vista x86 SP2 E4843BCF843BA2CA                     
sda3  ntfs   Vista x64 SP1 449EDDDE9EDDC896                     
sda4                                                           
sda5  ntfs   Movies3       E666AD6166AD336B                     
sdb                                                             
sdb1  ntfs   Win7 (x64)    01CF04BEB8434F30                     
sdb2  ntfs   Win8 x64      01CF04BECFD7FDD0                     
sdb3  ntfs   Win8.1 x64    34AACC96AACC55D0                     
sdb4                                                           
sdb5  ntfs   Data2         E888111B8810EA38                     
sdb6  ntfs   Movies2       01CF02688A26B2C0                     
sdc                                                             
sdc1  ext3                 c2e3561e-43ab-4f30-8539-3af7debd3b86 /
sdc2                                                           
sdc5  swap                 bd4bcbc1-1222-477c-ac94-e476dfa67387 [SWAP]
sdc6  ext3                 f9a6f367-560c-4129-9e15-6d0db3decc82
sdc7  ext4                 ce7ca6d2-5fc5-44fe-9be1-0d47c5085462
sdc8  ext4                 84f77526-b1f4-4f7b-90dc-01724cc58643
sdc9  ext4                 2be260ac-82c6-4c7b-bb87-10d20c981e66
sdc10 ext4                 957157e2-82de-446f-bb71-0970c79b26d8
sdc11 ext4                 243676c1-0972-478c-b31f-80831931e49d
sdc12 ntfs   Movies6       01CEE7D7530CB650                     
sdc13 ext4                 4f22a842-7efd-493a-91f2-885cf7461ba8
sde                                                             
sde1  vfat   EOS_DIGITAL   2276-1630                            /media/arch/EOS_
sr0                                                             
arch@arch-System-Product-Name ~ $

[archp2008]

For your explorer issue - usually file manager show the size of the partition, or the label if present. If you have that much partitions, my suggestion would be add labels to them so you can easier distinguish them from one another. You can also run sudo lsblk -fl where it will show the UUIDs and where they are mounted.

I could not find any application inside Mint called File Manager, only File Manager Preferences. In Mint's "Places" /media/arch/243676c1-0972-478c-b31f-80831931e49d/ is definitely looking inside the Mageia partition but again the Root folder is X'd out saying I don't have permission to view. There is a file manager called Caja which appears to be fancy name for "Places" which is always open in the left margin but Root inside the partition cannot be accessed.

[archp2008]

sudo mcedit /etc/fstab and commenting out the windows partitions worked. In fact I am posting now from inside Mageia. Love you, Doktor! If we were in person I'd give you a hug! Thank you so much! Is there anything else I need to do?

[archp2008]

I needed to insert the live CD to install solitaire - something called Core .... (can't remember the other word)

[doktor5000]

Love you, Doktor! If we were in person I'd give you a hug!

Baah. Only if you're a good-looking joung lady
Seriously, either send beer, or cookies (or both) or, even better, contribute in some way to Mageia: https://www.mageia.org/en/contribute/

Is there anything else I need to do?

As mentioned, for all noncritical filesystems add nofail as option in /etc/fstab, and remove the # sign you added previously. This is what it should look like then:

[doktor5000@Mageia4 ~]$ cat /etc/fstab
# Entry for /dev/sda5 :
UUID=a8229474-2eb9-48fe-bd56-be606de0fd2f / ext4 acl,discard,noatime 1 1
# Entry for /dev/sda7 :
UUID=2d072f85-753f-492c-b1bb-b87a047bc492 /home ext4 acl,discard,noatime 1 2
# Entry for /dev/sda1 :
UUID=5283596B0C6EE41F /media/win_c ntfs-3g defaults,nofail,umask=000 0 0
none /proc proc defaults 0 0
none /tmp tmpfs defaults 0 0
# Entry for /dev/sda6 :
UUID=3d760264-99f4-4363-a4dd-860f705bf7a5 swap swap defaults 0 0

On next boot you can run mount -a as root to see which partition fails why.

Then add your other linux installations to Mageia's bootloader. For traditional bootloaders like Windows or legacy grub, I'd simply add those as chainloader entries.
Check https://doc.mageia.org/mcc/4/en/content ... -boot.html
If you click the Add button, do NOT select linux, but choose "Other OS (Windows)" then simply choose the partition
where the other bootloader is located, and specify the name which you want to see in Mageia bootloader.

For grub2 which IIRC is used by Mint and most other current distros that is quite different. Check https://wiki.mageia.org/en/Mageia_4_Errata#Grub2 and also https://wiki.mageia.org/en/Mageia_4_Err ... stribution and https://wiki.mageia.org/en/Mageia_4_Err ... UB2_system

[archp2008]

Thanks for the additional instructions. Being that I like to use Daniel Richter's Grub Customizer and all Linux installations are listed and booting now, Would you please tell me the reason whey the nofaila are needed and why I need to add to the Mageia bootloader. Thanks again. I will definitely try to help with the forum questions if you can accept help from someone who is as illiterate in Linux as you know I am. Personal funds are really badly negative and likely will remain that way forever pending a mircacle - will need to ask the wife about adding more to the plastic to offer Mageia a deserving donation.

[doktor5000]

Would you please tell me the reason whey the nofaila are needed and why I need to add to the Mageia bootloader.

Those are two separate things. nofail is needed for all nocritical filesystems as an option in /etc/fstab.
See the previously posted link for more details: https://wiki.mageia.org/en/Mageia_4_Err ... rrect_UUID
Basically Mageia tries to mount all filesystems, and when one of them fails to mount for whatever reason, it drops to an emergency shell.

And why add the other OSes to the Mageia bootloader? That's what you wanted because they were not automatically found, no?