Description of problem: I have 2 disks: one SSD on /dev/sdb, and one HDD on /dev/sda / and /home are one /dev/sdb When I try to go to the MCC to configure and use /dev/sda, it adds this line in the /etc/fstab: /dev/sda1 /home/ofaurax/big1 ext4 acl,noatime 1 2 At reboot, this doesn't work, and the system doesn't want to boot (see attached image). Version-Release number of selected component (if applicable): I don't know which component is the culprit.... How reproducible: I have this laptop : http://www.ldlc.com/fiche/PB00140494.html I don't know if this is because I have 2 internals hd, or if this is due to the fact I have it installed on /dev/sdb rather than /dev/sda Steps to Reproduce: 1. Go to the MCC, add a new partition to /dev/sda, format it, and add a mount point (no need for expert mode) 2. Reinstall GRUB (to be sure.... I have to report another bug....) 3. Reboot Reproducible: Steps to Reproduce:
Created attachment 5470 [details] Screen when the boot hang The problem comes from /dev/sda1
Is this sda disk always present in the system? You can add noauto,nofail options to the fstab entry to keep this mount failure from breaking the boot process, but if the disk is available, why is it failing to mount it? Something to look into.
Yes, it is always present. Thanks for the options, I will add them to see if I'm able to mount it after boot. If I remember well, the /dev/sda1 seems to have been gone after reboot. Perhaps diskdrake failed to create properly the partition.
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD