Bug 437669
Summary: | Unhandled exception (in vgcreate or thereabouts) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Pierre Lewis <lew001> | ||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 8 | ||||||
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: | 2008-07-03 00:55:35 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Pierre Lewis
2008-03-16 01:42:36 UTC
Created attachment 298171 [details]
anacdump.txt + anaconda.log
OUPS, forgot to put a DESCRIPTION: Trying to install to free space on HDD, anaconda gets an unhandled exception after 15+ minutes. Significant messages: /dev/sda5: read failed after 0 of 2048 at 0: Input/output error ... Unable to add physical volume '/dev/sda5' to volume group 'VolGroup00'. There are read errors from your drive here. Are you sure your hard drive isn't failing? Well, that HDD works fine with Vista, has never given trouble. Yes it does suggest drive problems, but not plain failure, rather some kind of incompatibility. I've browsed the web, but haven't found a conclusive answer. Linux does have drivers for SATA, but is the chipset I have supported? Maybe that's the root problem. The anaconda unhandled exception asked me to open a bug report, perhaps that will get me closer to an answer... Side question. I was surprised that 15+ minutes into the install, we were just beginning to do lvm vgcreate. What happened before? Have you encountered the same problem with Fedora 9? I have not tried with Fedora 9. I haven't read anything in the release notes that suggests this problem might have been fixed, and there hasn't been much action on this bug. Do you think it is worth a try? It probably is worth a try, at the very least so we know if it's still happening or if it got fixed (either deliberately or incidentally). Since there are read issues, it could also be a problem with your harddrive. Well, notwithstanding my doubts, it was a disk problem. Two months after the above attempts, the HDD died in Vista, and refused to let Vista be re-installed. I finally got a replacement drive, and installing Fedora 9 on it was a breeze. So I guess that closes this ticket. I suspect the disk problems were in the area where Linux tried to install, whereas Vista was at the bottom of the disk, far away from the trouble area. But eventually, the disease spread... |