|
Bugzilla – Full Text Bug Listing |
| Summary: | installation gets stuck when "preparing your hard disk" | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Olli Lehto <olli.lehto> |
| Component: | Installation | Assignee: | Hubert Mantel <mantel> |
| Status: | RESOLVED WONTFIX | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | /var/log/YaST2/ directory | ||
|
Description
Olli Lehto
2005-09-03 14:54:53 UTC
Please, provide YaST logs if possible http://www.opensuse.org/index.php/Bug_Reporting_FAQ#YaST Thanks Created attachment 48755 [details]
/var/log/YaST2/ directory
arvin, fehr, please have a look at it. I noticed that the logs I sent may not be relevant to the case: I had to kill the installation using power switch. Is it possible to get logs of installations that get locked this way? I've noticed this same problem with an earlier release version, too. After all, trying the installation again helped, the problem seems to be random by nature. Are the logs really from a hanging install? I can see no hang, but error messages that are caused by the fact that device nodes are created asynchronously by udev while YaST2 cannot know when they will be there. Ok, if the machine really hangs randomly I consider this either a kernel or a hardware problem. So far I did not get any error reports about hangs within yast2-storage related code. If the system really locks hard it is unfortunately not any more possible to get YaST2 related logs any more since these a stored in memory and copied to the disk at end of first stage installation. Reassigning this to kernel, they should know better what data they need to detect possible cause for the hang. Did you try "safe settings" as well? Did you try the various ACPI parameters such as "acpi=off"? Is "safe settings"=Failsafe (boot choice"? But the problem is that I've seen the problematic situation a couple of times. Every time the next try was a success. I just thought that the situation may be embarrassing when you get into it for the first time. I still don't see whether a failsafe boot works or not! No feedback in 1.5 months, closing |