https://bugzilla.novell.com/show_bug.cgi?id=225603 Summary: Yast boot loader module hangs on missing /dev entries Product: openSUSE 10.2 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: volker3204@paradise.net.nz QAContact: jsrain@novell.com After an installation where the boot loader installation fails (I find this commonly), it is necessary to boot into the rescue system. The easiest is to mount the root-fs into the rescue system, to chroot into it and to run yast. In this case, yast hangs on step 3 with 100% CPU use: [x] Check boot loader [x] Read partitioning [ ] Load boot loader settings Perhaps the hang is in some evms part: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND .. root 5002 0.0 0.0 14500 1780 tty1 S+ 05:00 0:00 /bin/bash /sbin/yast2 root 5022 50.9 2.2 205292 46088 tty1 R+ 05:00 0:53 /usr/lib/YaST2/bin/y2base menu ncurses --nothreads root 5050 0.0 0.1 77624 3964 tty1 Sl+ 05:00 0:00 /usr/lib/YaST2/bin/evms_access --log-path /var/log/YaST2 --log-file y2log --socket /var/lib/YaST2/socket_libstorage_evms --timeout 3000 strace repeats: select(5, [4], NULL, NULL, {1, 516000}) = 0 (Timeout) semop(0, 0x7fffaeb2b910, 1) = -1 EAGAIN (Resource temporarily unavailable) listen(4, 20) = 0 select(5, [4], NULL, NULL, {3, 0}) = 0 (Timeout) /proc and /sys are mounted inside the chroot. The hang can be prevented by creating the missing device entries /dev/hd* and /dev/sd* (for SATA disks). This bug report is for yast which shouldn't hang on missing device entries. I'll make another one for the missing entries. -- 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.