[SOLVED]Mageia3 RC Impossible installation

[Lebarhon]

Hi,
I installed M3 alpha and several beta without any problem but I tried twice to install RC and it fails.
Installation seems OK and ask for reboot. After a while, the boot stops with these message:
"Timed out waiting for device dev-disk-by\x2duuu......device
"Dependency failed for /mnt/hd
"Dependency failed for Local File Systems.
"Dependency failed for relabel all filesystems, if necessary
"Dependency failed for setup links in /boot for running kernel.
" Dependency failed for Mark the need to relabel after reboot
Enter root password or Ctrl D

I entered root password and tried to update, but there was no ethernet connection.
I could have a GUI with startx, according the system tray and MCC, ethernet was connected and working, but firefox couldn't open a web site. I disconnected/reconnected (BTW, no Guest account) but no better. A last, create a new connection worked. I installed the Cauldron sources make an update (fine, no error messages) and reboot. Same behaviour and the ethernet connection was gone. I did all the stuff again, then urpmi --auto-update. Everything is update.
Reboot
OK Mounted /media/windows
OK Mounted /home
TIME Timed out waiting for device dev-disk-by\x2duuu......device
DEPEND Dependency failed for /mnt/hd
DEPEND Dependency failed for Local File Systems.
DEPEND Dependency failed for relabel all filesystems, if necessary
DEPEND Dependency failed for setup links in /boot for running kernel.
DEPEND Dependency failed for Mark the need to relabel after reboot
Welcome to emergency mode! After logging in, type "journalctl -b" to view system logs, ....

What broke Mageia 3 RC ? If I install M 3 Beta4 and make an update, I have M3RC working!
Thanks

[waferhead]

Please specify what hardware, exactly.

I just tried it on 5 wildly different machines,(AMD desktops of 2 different generations, and 3 laptops) worked like a charm, so YMMV.

Just guessing, It sounds like the HD controller driver for that drive isn't makin it into the initrd, or perhaps an unsupported FS type?

I prefer to set things up with human-readable labeled partitions vs. uuid, but it requires more setup.

[ghmitch]

For one things, I suspect the dependency failures you are seeing appear to be systemd dependencies, NOT package dependencies. It is as if systemd *thinks* it has successfully executed a particular task, such as mounting a specific partition, and it hasn't, therefore following tasks fail for lack of that dependency. I agree with the previous poster. I would make sure that all partitions are LABELED and that those labels are utilized in fstab. If /dev/sd?? are used, that is a serious problem because a simple move from beta 4 to RC can alter the way the kernel enumerates the partitions and break your system. In my experience, even UUIDs can have problems. LABELS, are the other hand, never change and are portable through various OS modifications and switching to LABELS may well fix your problem.

But, and correct me if I am wrong, it sounds like this is a fresh install of RC? If that is the case, something appears to be going wrong with the way the installer is assigning UUIDs and recording them in fstab. Hopefully someone else can independently verify this problem. But it may be unique to your situation. I would suggest that you get this system up as best you can and include a full copy of the output of `blkid` and `cat /etc/fstab` in your next post. That may reveal something interesting. - George

[Lebarhon]

Thanks for your help,
The hardware is a Dell Latitude D630.
There is only one HD with 7 partitions : Windows, Cauldron sda5, Home (for Cauldron) sda6, swap, data (ext4), Mageia2, Home (for Mageia2).
I made a fresh install with a CD boot ISO and Mageia RC DVD 64 bits ISO on a USB stick on sda5 I formatted. Before this fresh install, Cauldron was with two NFS partitions mounted on /mnt/Documents and /mnt/Multimedia.
I think you are right with a label problem, because before I read your posts, I re-install NFS and re-mounted the two partitions like before, and now it seems all is working again. For example, the boot is normal with a graphic connection and ethernet is working.
Is it because the USB stick took the sda name ?

[Lebarhon]

Code: Select all

[root@localhost ~]# blkid
/dev/sda1: UUID="F8A8DABFA8DA7B96" TYPE="ntfs"
/dev/sda5: LABEL="Cauldron" UUID="78374130-56ca-45cc-b8ca-c484d85934ec" TYPE="ext4"
/dev/sda6: UUID="98a2549b-0757-4eb6-8a14-aa1a4b01e481" TYPE="ext4"
/dev/sda7: UUID="ff20a8d1-33c0-41d7-bd3e-ca8ff72c8773" TYPE="swap"
/dev/sda8: LABEL="ISO" UUID="9e820774-9686-469a-ae22-9b6bd840f030" TYPE="ext4"
/dev/sda9: LABEL="Mga2" UUID="0805ed8f-2a5d-47b7-b42e-2d25de1f8e50" TYPE="ext4"
/dev/sda10: UUID="157049eb-c1d0-4506-9446-c90c3e205053" TYPE="swap"
/dev/sda11: UUID="932ad13d-6909-4f12-970e-a0e2064531fb" TYPE="ext4"
[root@localhost ~]#

Code: Select all

[root@localhost ~]# cat /etc/fstab
# Entry for /dev/sda5 :
UUID=78374130-56ca-45cc-b8ca-c484d85934ec / ext4 acl,noatime 1 1
# Entry for /dev/sda6 :
UUID=98a2549b-0757-4eb6-8a14-aa1a4b01e481 /home ext4 acl,noatime 1 2
# Entry for /dev/sda1 :
UUID=F8A8DABFA8DA7B96 /media/windows ntfs-3g defaults,umask=000 0 0
192.168.0.5:/home/samageia/Documents /mnt/Documents nfs rsize=8192,wsize=8192,nosuid,soft 0 0
192.168.0.5:/home/samageia/multimedia /mnt/multimedia nfs rsize=8192,wsize=8192,nosuid,soft 0 0
none /proc proc defaults 0 0
# Entry for /dev/sda7 :
UUID=ff20a8d1-33c0-41d7-bd3e-ca8ff72c8773 swap swap defaults 0 0
# Entry for /dev/sda10 :
UUID=157049eb-c1d0-4506-9446-c90c3e205053 swap swap defaults 0 0
[root@localhost ~]#


[ghmitch]

The NFS volumes throw a curve into the whole issue. If for whatever reason the system was unable to mount those NFS volumes, that might cause some sort of stumble. UUIDs *should* avoid problems with USB sticks and such, but they become confusing. I have found labels to be absolutely the best answer to managing partitions. In any case, glad things are working again for you. If everything stays OK for a while, you might want to edit your original post and prefix the title with [SOLVED]. - George

[waferhead]

Thanks for your help,
The hardware is a Dell Latitude D630.
There is only one HD with 7 partitions : Windows, Cauldron sda5, Home (for Cauldron) sda6, swap, data (ext4), Mageia2, Home (for Mageia2).
I made a fresh install with a CD boot ISO and Mageia RC DVD 64 bits ISO on a USB stick on sda5 I formatted. Before this fresh install, Cauldron was with two NFS partitions mounted on /mnt/Documents and /mnt/Multimedia.
I think you are right with a label problem, because before I read your posts, I re-install NFS and re-mounted the two partitions like before, and now it seems all is working again. For example, the boot is normal with a graphic connection and ethernet is working.
Is it because the USB stick took the sda name ?

Cool, glad you got it sorted.

I have run into uuid issues occasionally when doing upgrades (esp playing with several distros) so I have developed the habit of using labels.

I always blamed it on using a USB stick, as I never had the issue from CD/DVD, but could never really pin down the exact issue, or cared enough to dig too hard, as it was easy to use labels.

Requires a little more manual intervention, but can save head scratching later, and if nothng else you are still sure what partition you wnat to use for root/home etc. (IIRC still an issue w/Ubuntu last I checked, couldn't see the labels in the installer, Brilliant !!! Design!!!)
Kinda old skool now, but has always worked for me.

I tend to do a straight installation and add /home and any nfs/cifs stuff after the install completes and I see how things look.
Sometimes doing complex things in the limited installer environment work great...
Sometimes they bork.

[Lebarhon]

I tend to do a straight installation and add /home and any nfs/cifs stuff after the install completes and I see how things look.
Sometimes doing complex things in the limited installer environment work great...
Sometimes they bork.

How to say the installer to not take care about the NFS network ? It was a fresh install and the installer shouldn't have known there was 2 NFS mounting.