Hi. I configured a remote machine to allow network installation when the machine is being loaded with PXE. I'm using an x86_64 desktop. The installation is almost fully automated with a kickstart file. I enabled PXE in the BIOS, started the installation and in the middle of the installation, i got a crash which reported an error. I opened a bug on this issue: http://bugs.centos.org/view.php?id=3394. Someone, called Tru, kindly gave me the following answer: from your logs: File "/usr/lib/anaconda/iw/progress_gui.py", line 243, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 1045, in handleRenderCallback self.currentWindow.renderCallback() IOError: [Errno 30] Read-only file system ... which was caused by: <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown <3>hda: no DRQ after issuing MULTWRITE_EXT <4>ide0: reset: success <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown <3>hda: no DRQ after issuing MULTWRITE_EXT <4>ide0: reset: success <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown ... <4>ide0: reset: success <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown <4>end_request: I/O error, dev hda, sector 344757 <3>hda: no DRQ after issuing MULTWRITE_EXT <4>hda: status error: status=0x58 { DriveReady SeekComplete DataRequest } <4>ide: failed opcode was: unknown <3>hda: drive not ready for command .... 4>hda: status error: status=0x58 { DriveReady SeekComplete DataRequest } <4>ide: failed opcode was: unknown <3>hda: drive not ready for command <4>ide0: reset: success <3>Aborting journal on device dm-0. <2>ext3_abort called. <2>EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal <2>Remounting filesystem read-only Issue History Date Modified Username Field Change ====================================================================== 2009-02-17 11:30dotan_bar New Issue 2009-02-17 11:30dotan_bar File Added: bug_report.txt 2009-02-17 11:34dotan_bar File Added: default.ks 2009-02-17 11:35dotan_bar Note Added: 0008711 2009-02-17 12:20tru Note Added: 0008713 ====================================================================== Reply Forward noreply at centos.org to me show details 2:21 PM (1 hour ago) Reply The following issue has been CLOSED ====================================================================== http://bugs.centos.org/view.php?id=3394 ====================================================================== Reported By: dotan_bar Assigned To: ====================================================================== Project: CentOS-5 Issue ID: 3394 Category: -OTHER Reproducibility: unable to reproduce Severity: crash Priority: normal Status: closed Resolution: open Fixed in Version: ====================================================================== Date Submitted: 2009-02-17 11:30 UTC Last Modified: 2009-02-17 12:21 UTC - Show quoted text - ====================================================================== Summary: There was a crash during the distribution installation over PXE using kickstart Description: I configured a remote machine to allow network installation when the machine is being loaded with PXE. The installation is almost fully automated with a kickstart file. I enabled PXE in the BIOS, started the installation and in the middle of the installation, i got a crash which reported an error. I'm using x86_64 desktop. ====================================================================== ---------------------------------------------------------------------- dotan_bar - 2009-02-17 11:35 ---------------------------------------------------------------------- I attached the kick-start file too. ---------------------------------------------------------------------- tru - 2009-02-17 12:20 ---------------------------------------------------------------------- from your logs: File "/usr/lib/anaconda/iw/progress_gui.py", line 243, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 1045, in handleRenderCallback self.currentWindow.renderCallback() IOError: [Errno 30] Read-only file system ... which was caused by: <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown <3>hda: no DRQ after issuing MULTWRITE_EXT <4>ide0: reset: success <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown <3>hda: no DRQ after issuing MULTWRITE_EXT <4>ide0: reset: success <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown ... <4>ide0: reset: success <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown <4>end_request: I/O error, dev hda, sector 344757 <3>hda: no DRQ after issuing MULTWRITE_EXT <4>hda: status error: status=0x58 { DriveReady SeekComplete DataRequest } <4>ide: failed opcode was: unknown <3>hda: drive not ready for command .... 4>hda: status error: status=0x58 { DriveReady SeekComplete DataRequest } <4>ide: failed opcode was: unknown <3>hda: drive not ready for command <4>ide0: reset: success <3>Aborting journal on device dm-0. <2>ext3_abort called. <2>EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal <2>Remounting filesystem read-only ---------------------------------------------------------------------- tru - 2009-02-17 12:21 ---------------------------------------------------------------------- OP hardware error, not a bug. This is not a support system, but a bug tracker. Please take your questions to either the centos mailing list or the forums. Can anyone help me with this issue? Thanks Dotan