SCSI device bug with kernel 2.6.12+ only

SCSI based system controlled by an Adaptec 29320A card. 4 optical drives, 3 SCSI and 1 IDE. Install from the IDE DVD drive. 4 SCSI HDs in system but just 1 turned on at time of install, ID 15. Install now runs to about 70% then crashes with the below info. This is REPEATABLE with all releases using kernel 2.6.12, but there are NO problems installing using any kernel version 2.6.11 or earlier.

Because Novell claimed the problem with my system was too many optical drives when I attempted to upgrade from SuSE 9.3 to 10.0, I next retried performing the same install after having removed all 3 SCSI optical drives leaving ONLY the 1 IDE DVD install drive and one SCSI HD (ID #15) on line. The error messages beow are from that attempt.

----------------------------------

--- BEGIN: Traceback
Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 55, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 309, in run
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 524, in progress_loop
    raise RuntimeError, ("Install failed with exit code %s; see "
RuntimeError: Install failed with exit code 1; see /var/log/installer/syslog and /var/log/syslog
--- END: Traceback

--- BEGIN: /var/log/partman

/bin/partman: *******************************************************
/lib/partman/init.d/01unsupported: *******************************************************
/lib/partman/init.d/30parted: *******************************************************
parted_server: ======= Starting the server
parted_server: main_loop: iteration 1
parted_server: Opening infifo
/lib/partman/init.d/30parted: IN: OPEN =dev=sda /dev/sda
parted_server: Read command: OPEN
parted_server: command_open()
parted_server: Request to open =dev=sda
parted_server: Opening outfifo
parted_server: OUT: OK

parted_server: OUT: OK

parted_server: Note =dev=sda as unchanged
parted_server: Closing infifo and outfifo
parted_server: main_loop: iteration 2
parted_server: Opening infifo
/lib/partman/init.d/35dump: *******************************************************
/lib/partman/init.d/35dump: IN: DUMP =dev=sda
parted_server: Read command: DUMP
parted_server: command_dump()
parted_server: Opening outfifo
parted_server: OUT: OK

parted_server: Closing infifo and outfifo
parted_server: main_loop: iteration 3
parted_server: Opening infifo
Device: yes
Model: QUANTUM ATLAS10K3_73_WLS
Path: /dev/sda
Sector size: 512
Sectors: 143666192
Sectors/track: 63
Heads: 255
Cylinders: 8942
Partition table: yes
Type: msdos
Partitions: # id length type fs path name
(0,0,0) (0,0,62) -1 0-32255 32256 primary label /dev/sda-1
(0,1,0) (8754,254,62) 1 32256-72012326399 72012294144 primary ext3 /dev/sda1
(8755,0,0) (8941,254,62) 2 72012326400-73550453759 1538127360 primary extended /dev/sda2
(8755,0,0) (8755,0,62) -1 72012326400-72012358655 32256 logical label /dev/sda-1
(8755,1,0) (8941,254,62) 5 72012358656-73550453759 1538095104 logical linux-swap /dev/sda5
(8942,0,0) (8942,205,46) -1 73550453760-73557090303 6636544 primary labe...

Hi,

When reporting bugs, and providing log files, please use the webpage and the "Include Attachement" option to attach the logs as seperate files. This makes debugging mush easier. Thank you for the bug report :)

Carthik Sharma wrote:

>Hi,
>
>When reporting bugs, and providing log files, please use the webpage and
>the "Include Attachement" option to attach the logs as seperate files.
>This makes debugging mush easier. Thank you for the bug report :)
>
>
>
sorry; i'll try better next time. been shot at so many time for doing
attachments I guess I just figured it best to not do attachments

I believe the installer problems here have been fixed in Feisty. Reassigning to the kernel team so that they can have a look at the SCSI device overruns filling up your syslog.

Thank your for your bug report. Do you still have this issue with the latest release of Ubuntu ?

Any news on this ?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!