| Summary: | Anaconda installation hung after "creating new fs" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | tazu <tazu> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 12 | CC: | dougsland, gansalmon, itamar, kernel-maint, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-02-07 00:29:34 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
There's a huge number of errors coming from your hard drive:
<3>ata1.00: exception Emask 0x10 SAct 0xffff SErr 0x400100 action 0x6 frozen
<3>ata1.00: irq_stat 0x08000000, interface fatal error
<3>ata1: SError: { UnrecovData Handshk }
<3>ata1.00: cmd 61/a8:00:85:49:81/00:00:24:00:00/40 tag 0 ncq 86016 out
<3> res 40/00:34:dd:48:81/00:00:24:00:00/40 Emask 0x10 (ATA bus error)
...
<4>lost page write due to I/O error on sda3
<3>Buffer I/O error on device sda3, logical block 16810240
<4>lost page write due to I/O error on sda3
<6>sd 0:0:0:0: [sda] Unhandled error code
<6>sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
<3>end_request: I/O error, dev sda, sector 612451901
These indicate either hardware failure or a kernel problem. Either way, it explains why writes to your drive are taking so long. It's also nothing anaconda can do anything about.
So the problem might be related to hardware? It seems odd, because I just rebooted the box and installed using the same configuration options and it just went fine. I even used the same partition config, formated 2 partitions that had opensuse installed, used them as "/" and swap. Is there a way to push this into a kernel group for screening? Maybe the disk drivers are having a problem here? Thanks for fast response :) |
Created attachment 372574 [details] Anaconda debug info. Description of problem: Anaconda hung after the partition management screen while creating new fs'es (custom partition layout), other text consoles worked, but the installer stuck for a very long time (minutes), then produced error screen, after reboot installation worked flawlessly with the same steps... Version-Release number of selected component (if applicable): 12 x86_64 installation from DVD How reproducible: one time event, please see attached debugger info from anaconda Steps to Reproduce: 1. install using custom partition layout Actual results: installer hung for a long time in creating new fs screen, then produced error msg. Expected results: go as usual Additional info: debugger info saved [see attachements]