[ubuntu] Error: "The ext3 file system creation in partition #1 of SCSI1 (0,0,0) (sda) failed"

Bug #378501 reported by xGutsAndGloryx
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: ubiquity

Hello,
I am trying to install linux on my computer. I have tried installing using a cd that came in the mail from Ubuntu and a cd download from Ubuntu website. It will boot to the live cd and function properly. It encounters the problem during the formatting and partition on the hard drive. It encounters the error at 5%. The error message is: Error: "The ext3 file system creation in partition #1 of SCSI1 (0,0,0) (sda) failed" . I have tried swapping out optical drives and all the hardware is brand new. I tried following instructions on Bug # 99908. It didn't work. Please help me out. I have hopefully included all the necessary information. Thanks in advance.

p.s sorry about the multiple post about the same topic

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
Package: ubiquity 1.10.10 [modified: lib/partman/automatically_partition/question]
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
Uname: Linux 2.6.27-7-generic i686

Revision history for this message
xGutsAndGloryx (jeffrey-bearden) wrote :
Revision history for this message
xGutsAndGloryx (jeffrey-bearden) wrote :

is anyone going to help me?

Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

Hi,
 The logs seem to show a lot of errors that look like disk related errors:

May 19 21:58:49 ubuntu kernel: [ 438.344060] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
May 19 21:58:49 ubuntu kernel: [ 438.344076] ata1.00: cmd 35/00:80:cf:0f:34/00:00:70:00:00/e0 tag 0 dma 65536 out
May 19 21:58:49 ubuntu kernel: [ 438.344079] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
May 19 21:58:49 ubuntu kernel: [ 438.344086] ata1.00: status: { DRDY }
May 19 21:58:54 ubuntu kernel: [ 443.384032] ata1: link is slow to respond, please be patient (ready=0)
May 19 21:58:59 ubuntu kernel: [ 448.368020] ata1: device not ready (errno=-16), forcing hardreset
May 19 21:58:59 ubuntu kernel: [ 448.368034] ata1: soft resetting link
.....
May 19 21:59:59 ubuntu kernel: [ 508.472519] ata1: SRST failed (errno=-16)
May 19 21:59:59 ubuntu kernel: [ 508.472531] ata1: reset failed, giving up
May 19 21:59:59 ubuntu kernel: [ 508.472535] ata1.00: disabled
May 19 21:59:59 ubuntu kernel: [ 508.472552] ata1: EH complete
May 19 21:59:59 ubuntu kernel: [ 508.472590] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May 19 21:59:59 ubuntu kernel: [ 508.472598] end_request: I/O error, dev sda, sector 1882460111
May 19 21:59:59 ubuntu kernel: [ 508.472606] Buffer I/O error on device sda1, logical block 1882460048
May 19 21:59:59 ubuntu kernel: [ 508.472610] lost page write due to I/O error on sda1

May 19 21:59:59 ubuntu kernel: [ 508.472871] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
May 19 21:59:59 ubuntu kernel: [ 508.472877] end_request: I/O error, dev sda, sector 1882718287
May 19 21:59:59 ubuntu kernel: [ 508.473035] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK

I suggest you check the cabling in your computer and possibly find some diagnostic programmes for your disk to see if a hardware problem is the cause.

Revision history for this message
xGutsAndGloryx (jeffrey-bearden) wrote :

where could i find some diagnostic programs? could it be raid related?

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that there is a problem with the disk to which you are trying to install Ubuntu. I'd recommend performing a back up of your existing operating system and then investigating the situation. Measures you might take include checking cable connections for your disks and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck!

Changed in ubiquity (Ubuntu):
status: New → Invalid
importance: Undecided → Low
tags: added: hardware-error
tags: added: intrepid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.