Description of problem: Mageia does not start if there is in / etc. / fstab a partition(score) which does not exist. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Thanks for reporting. Can you give us more details, for example attaching your /etc/fstab to this bug report and also tell at which stage of boot (what gets printed last on the screen you can get when pressing ESC) it gets stuck?
Whiteboard: (none) => NEEDINFO
Created attachment 7061 [details] /etc/fstab
CC: (none) => nmrk.n
What if you add the nofail option to the fstab line for sdc? Does it allow to boot even if the disk is missing? Note: "score" is the English for French's "partition" in a musical context. Otherwise, use "partition".
Created attachment 7062 [details] Screen Ãcran 1 et écran 2 après de longues attentes. Screen 1 and screen 2 after long expectations(waits).
Je n'ai pas trouvé comment supprimer un fichier attaché pour le remplacer. /etc/fstab attaché est celui qui me permet de démarrer. /etc/fstab qui ne fonctionne pas est : I did not how find to delete(eliminate) a file attached to replace him(it). /etc/fstab Attaché is the one who allows me to start. /etc/fstab Which(who) does not work is: # Entry for /dev/sda7 : UUID=5910e910-aa80-4669-a716-4a6e5cee7599 / ext4 noatime,acl 1 1 # Entry for /dev/sdb2 : UUID=d69bb625-8b66-415e-9562-13829551f251 /HITACHI_640 ext4 defaults 1 2 # Entry for /dev/sdc1 : # Lorsque le disque sdc n'est pas connecté (ou défectueux) il faut commenter la ligne ci-dessous sinon Mageia ne démarre pas. UUID=3e1f5a24-6163-4221-bcf4-d7d364b6f720 /HSAV ext4 defaults 1 2 # Entry for /dev/sdb1 : UUID=68e45323-ecf1-4553-ab6e-cdeac733fc85 /home ext4 noatime,acl 1 2 none /proc proc defaults 0 0 # Entry for /dev/sda9 : UUID=ae9b5667-4ca8-4d25-a522-b9e109b0c7df swap swap defaults 0 0
Have you seen comment #2?
(In reply to Samuel VERSCHELDE from comment #6) > Have you seen comment #2? I mean comment #3
Ãa fonctionne avec nofail comme ci-dessous: That works with nofail as below: # Entry for /dev/sda7 : UUID=5910e910-aa80-4669-a716-4a6e5cee7599 / ext4 noatime,acl 1 1 # Entry for /dev/sdb2 : UUID=d69bb625-8b66-415e-9562-13829551f251 /HITACHI_640 ext4 defaults 1 2 # Entry for /dev/sdc1 : # Lorsque le disque sdc n'est pas connecté (ou défectueux) il faut commenter la ligne ci-dessous sinon Mageia ne démarre pas. UUID=3e1f5a24-6163-4221-bcf4-d7d364b6f720 /HSAV ext4 nofail, defaults 1 2 # Entry for /dev/sdb1 : UUID=68e45323-ecf1-4553-ab6e-cdeac733fc85 /home ext4 noatime,acl 1 2 none /proc proc defaults 0 0 # Entry for /dev/sda9 : UUID=ae9b5667-4ca8-4d25-a522-b9e109b0c7df swap swap defaults 0 0
Summary: Mageia does not start => Mageia falls into recovery mode after long time if an external disk from fstab is not connectedWhiteboard: NEEDINFO => (none)
So, I think it behaves like it should (but maybe there is a bug elsewhere). Hard disk entries can have parameters such as nofail, but also the last digit on on the line if you want to avoid fsck to check the disk when it is mounted: set it to 0 and it will not be checked at boot. How was the line added to fstab? Was it automatically during installation or did you use diskdrake to add it afterwards?
Source RPM: Unknow => (none)
Pour ce disque la ligne a été ajoutée avec diskdrake après l'installation. For this disk the line was added with diskdrake after the installation.
Assigning to diskdrake maintainer. I think (if it's doable) that diskdrake could detect the disk is external and automatically propose to add the nofail option in order to avoid that. I'll turn this bug report into an enhancement report.
Assignee: bugsquad => thierry.vignaudSource RPM: (none) => drakxtoolsSeverity: normal => enhancement
Summary: Mageia falls into recovery mode after long time if an external disk from fstab is not connected => diskdrake could automatically propose the nofail option for external hard drives?
Je ne sais pas si j'ai bien compris, toutefois je précise : Il ne s'agit pas d'un disque externe (usb) Il s'agit d'un disque interne SATA. I do not know if I understood well, however I specify: It is not about an external disk (usb). It is about an internal disk SATA.
Thanks for the precision. Then it's not a bug, closing as INVALID since everything works as expected (except maybe that the delay seems too long?). Remember this nofail option, this is what you are looking for in your case.
Status: NEW => RESOLVEDResolution: (none) => INVALID
"... since everything works as expected ..." On peut le voir comme ça. On peut aussi se demander pourquoi on se retrouve en ligne de commande et pas en interface graphique car : / -> Ok /home -> Ok swap -> Ok We can see him(it) like that. We can also wonder why we find ourselves on-line of command(order) and not in graphical interface because: / -> Ok /home -> Ok swap -> Ok