[Bug 204759] New: unable to unmount all devices after installation, forces fsck at first boot
https://bugzilla.novell.com/show_bug.cgi?id=204759 Summary: unable to unmount all devices after installation, forces fsck at first boot Product: openSUSE 10.2 Version: Alpha 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: jsrain@novell.com udevd remains running and /mnt and /mnt/dev are therefore unmountable, forcing a fsck of / at first install. This can be very time consuming and expensive, although not with most filesystems. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204759 ------- Comment #1 from olh@novell.com 2006-09-12 14:27 MST ------- can you find out what is keeping it busy? boot the installation with the 'start_shell' kernel cmdline option, leave the fist shell with 'exit' and poke around in the second shell once yast has finished. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204759 ------- Comment #2 from jnelson-suse@jamponi.net 2006-09-12 15:06 MST ------- udevd for /mnt/dev remains running I used 'lsof | grep /mnt' but all I saw were some libraries and udevd. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204759 ------- Comment #3 from jnelson-suse@jamponi.net 2006-09-12 15:07 MST ------- Is this related to the 'large quantities of udevd output on boot' that 10.2 Alpha 4 (not Alpha3, though) exhibits? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204759 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Comment #4 from aj@novell.com 2006-09-20 11:25 MST ------- Ad #3: That's something different. Unfortunately we then cannot do anything to fix it. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204759 jnelson-suse@jamponi.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Comment #5 from jnelson-suse@jamponi.net 2006-09-20 11:34 MST ------- I don't understand - you can't find a way to kill off udevd before restarting? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204759 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kay.sievers@vrfy.org AssignedTo|bnc-team- |yast2-maintainers@suse.de |screening@forge.provo.novell| |.com | Status|REOPENED |NEW ------- Comment #6 from aj@novell.com 2006-09-20 11:42 MST ------- Sorry, misunderstood comment #2. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204759 fehr@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |locilka@novell.com ------- Comment #7 from fehr@novell.com 2006-09-21 01:45 MST ------- Reassigne to maintainer of yast2-installation -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204759 olh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|locilka@novell.com |kay.sievers@vrfy.org Severity|Normal |Critical Component|Installation |Basesystem ------- Comment #8 from olh@novell.com 2006-09-21 14:02 MST ------- this is an udev bug. it restarts itself with the binary inside the chroot. this is has to be fixed. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204759 kasievers@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |snwint@novell.com ------- Comment #9 from kasievers@novell.com 2006-09-21 14:44 MST ------- Why can udevd in chroot can be started, there should be a udevd running from the real root, which prevents the starting, right? There is also a check in the rpm script for -z "$YAST_IS_RUNNING" which should prevent this. Doesn't that work? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204759 ------- Comment #10 from olh@novell.com 2006-09-21 15:06 MST ------- maybe the inst-sys one is a different bug. rpm --root /dir -Uvh udev.rpm has to work. glibc and sysvinit have code to check wether they are inside a chroot or not. YAST_IS_RUNNING is most likely the wrong approach. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204759 kasievers@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC|kay.sievers@vrfy.org | AssignedTo|kay.sievers@vrfy.org |kasievers@novell.com Status|NEEDINFO |ASSIGNED Info Provider|snwint@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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=204759 kasievers@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #11 from kasievers@novell.com 2006-10-02 14:41 MST ------- Changed the scripts to chroot detection now, let's see how that works... -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com