[Bug 858531] New: Boot hangs if secondary drive (not system drive) is not found
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c0 Summary: Boot hangs if secondary drive (not system drive) is not found Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: ibantxo28@gmail.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36 My system was not starting properly because I unplugged a secondary drive (not system drive). The system enters in a LOOP telling that "you are in emergency mode" (or something like that), but you cannot type anything to modify /etc/fstab. Reproducible: Always Steps to Reproduce: 1.Install Opensuse 13.1 in a "first drive". 2.Power off. 3.Plug-in a secondary drive. 4.Power on. 5.Mount secondary drive's partition. 6.Power off. 7.Unplug that secondary drive. 8.Power on. Actual Results: Solution for this issue: 1. In main starting menu of Opensuse, type 'e' 2. At the end of "linux" line, insert a parameter. 3. Edit /etc/fstab --> commenting the unused partition mount. 4. Reboot Expected Results: If you unplug an "secondary" drive, the system should boot OK. May be, warning that a drive is missing -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c1 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Component|Bootloader |Basesystem InfoProvider| |ibantxo28@gmail.com AssignedTo|jsrain@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com QAContact|jsrain@suse.com |qa-bugs@suse.de --- Comment #1 from Jiri Srain <jsrain@suse.com> 2014-01-16 09:09:21 UTC --- Is this a bug about just the drive not being present, or about not being able to mount a partition, which is located on the secondary drive? In any case, according to the description, the problem is far after kernel is successfully booted... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c2 Iban Txo <ibantxo28@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ibantxo28@gmail.com | --- Comment #2 from Iban Txo <ibantxo28@gmail.com> 2014-01-16 14:27:34 UTC --- First one: The drive is not present because I unplugged it before switching on. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c3 Ulf Michel <u.michel@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |u.michel@t-online.de --- Comment #3 from Ulf Michel <u.michel@t-online.de> 2014-01-19 05:17:37 UTC --- I had the same problem when I had an external disk drive not plugged in on boot. Solution is to add the option "nofail" to the related line in the /etc/fstab file, e.g. /dev/disk/by-id/usb-TOSHIBA_STOR.E_ALU_2S_201301113627-0:0-part1 /Data-disk ntfs-3g users,uid=michel,gid=users,fmask=133,dmask=022,locale=de_DE.UTF-8,nofail 0 0 I agree that the beaviour of the system should be more benign in case of a missing disk that contains no system data. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c4 --- Comment #4 from Ulf Michel <u.michel@t-online.de> 2014-01-23 17:31:56 UTC --- The same happens on a dual boot system with Windows if the Windows NTFS partition was not cleanly unmounted under Windows, e.g. due to hibernation. If Linux is selected in the next boot, the windows drive cannot be mounted under /windows/C and the boot fails as described above. The workaround in this situation is again to add the option "nofail" in the /etc/fstab file. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c5 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com --- Comment #5 from Bernhard Wiedemann <bwiedemann@suse.com> 2014-02-13 11:28:54 CET --- So what created those fstab entries? YaST? Because it should likely put "nofail" into those lines. Some elaboration on 5. in the initial report would thus be nice. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c6 --- Comment #6 from Ulf Michel <u.michel@t-online.de> 2014-02-13 10:47:49 UTC --- The /windows/C entry was very likely created by YaST without the nofail option. If an external disk is attached during work, the interim mount point should be changed to a permanent one in fstab to keep the mount point unchanged whenever the disk is attached. This entry (with disk-id) must be made manually and here one must not forget to add the option nofail. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c zhang jiajun <jzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |ro@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c7 Ruediger Oertel <ro@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |YaST2 AssignedTo|ro@suse.com |yast2-maintainers@suse.de QAContact|qa-bugs@suse.de |jsrain@suse.com --- Comment #7 from Ruediger Oertel <ro@suse.com> 2014-02-21 12:43:00 UTC --- okay, so this is about failing to add "nofail" to the created fstab entry ... let's try to re-assign this back -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c8 Ruediger Oertel <ro@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |illumilore@gmail.com --- Comment #8 from Ruediger Oertel <ro@suse.com> 2014-02-21 12:43:45 UTC --- *** Bug 865000 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=865000 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c10 Arvin Schnell <aschnell@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com Component|YaST2 |Basesystem AssignedTo|aschnell@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com QAContact|jsrain@suse.com |qa-bugs@suse.de --- Comment #10 from Arvin Schnell <aschnell@suse.com> 2014-02-21 13:40:08 UTC --- YaST does not add mount points for Windows in openSUSE 13.1 (see bug #763630). I need YaST logs of an installation where this is supposed to happen to analyse the problem further. Otherwise I think the boot process (systemd) should offer a more user-friendly interface to handle the situation of missing devices. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c11 --- Comment #11 from ill lume <illumilore@gmail.com> 2014-02-21 22:50:08 UTC --- Why is it default behaviour to fail to boot even without the nofail flag? Wouldn't it make more sense to give an error message by default instead of rendering the system unbootable if its not an important drive/mount? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c12 --- Comment #12 from Iban Txo <ibantxo28@gmail.com> 2014-02-22 00:07:41 UTC --- I agree 100% with this last comment#11. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c13 --- Comment #13 from Ulf Michel <u.michel@t-online.de> 2014-02-22 03:56:59 UTC --- I also agree with comment#11. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c14 --- Comment #14 from Bernhard Wiedemann <bwiedemann@suse.com> 2014-02-22 15:40:22 CET --- (In reply to comment #11)
if its not an important drive/mount?
importance might be not as easy to decide for the boot code. E.g. missing /home means autologin will not work missing /var will mean, various programs will not work also, I just added an ext4 partition from an extra disk under /mnt/data with yast2 disk and it added the nofail option by itself, so that looks good. Maybe it depends on the filesystem? On the other hand, I would also like a nicer failure behaviour than the current one which remains in minimalistic initrd environment. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c15 --- Comment #15 from Iban Txo <ibantxo28@gmail.com> 2014-02-22 19:51:37 UTC --- Some aditional info: the issue I told was not about an "important" partition. It was a "/mnt/data" type partition. I only know that it was quite hard to recover de system. I did not have the possibility to use any easy console. If I had had one possibility then I would have solved the issue very simply, commenting the line in /etc/fstab in 10 seconds. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c zhang jiajun <jzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |sbrabec@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c16 Stanislav Brabec <sbrabec@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ibantxo28@gmail.com --- Comment #16 from Stanislav Brabec <sbrabec@suse.com> 2014-02-26 20:00:15 CET --- Without "nofail" option the failure is expected and required behavior. The boot loop does not. Does the boot process look the same as bug 849863 comment 0? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c17 ill lume <illumilore@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ibantxo28@gmail.com | --- Comment #17 from ill lume <illumilore@gmail.com> 2014-02-26 19:52:16 UTC --- "Without "nofail" option the failure is expected and required behavior." Why is it expected? Why is it required? Last time I lost a non important drive on windows even, it did not intentionally cripple itself. If you run a headless server, this will cause problems. Avoidable problems. At least make the installer put in the nofail option by default if you can't fix the boot self crippling behaviour. "The boot loop does not" Does not what? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=858531 https://bugzilla.novell.com/show_bug.cgi?id=858531#c18 --- Comment #18 from Felix Miata <mrmazda@earthlink.net> 2014-07-14 02:18:20 EDT --- This looks to me like yet another bug 832220 duplicate. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=858531 Tomáš Chvátal <tchvatal@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #19 from Tomáš Chvátal <tchvatal@suse.com> --- This is systemd behaviour. Duping againts systemd bug. Shortly put, sysvinit ignored specs and let you do naughty stuff in fstab. Systemd expects you to properly put things there. *** This bug has been marked as a duplicate of bug 832220 *** -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com