Summary: | emerge fails with python traceback when emerging python-2.3.5-r2 | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Kamaji <kkcoupons> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | ||
Priority: | High | ||
Version: | 2.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Complete failed emerge output for dev-lang/python-2.3.5-r2 |
Description
Kamaji
2005-09-09 15:11:27 UTC
Created attachment 68066 [details]
Complete failed emerge output for dev-lang/python-2.3.5-r2
Input/output error: '/usr/portage/distfiles/Python-2.3.5.tar.bz2' Looks like filesystem corruption or your disk is dying. Check dmesg to confirm nothing suspicious there. If not, try unpacking it with tar. Confirmed. It does appear to be a disk and/or filesystem corruption problem. Dmesg: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=78698032, sector=78698 027 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 78698027 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=78698032, sector=78698 019 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 78698019 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=78698032, sector=78698 027 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 78698027 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=78698032, sector=78698 027 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 78698027 hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=78698032, sector=78698 027 ide: failed opcode was: unknown end_request: I/O error, dev hda, sector 78698027 |