Crash during install of Ubuntu 9.10. Not harddisc found during installation dialog. fdisk -l lists all partitions of the sata hd.......

[NihilBaxter]

during installation the install routine shows not found hard disc.
fdisk -l shows all partitions on the disc as seen below:

ubuntu@ubuntu:~$ sudo fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000099c5

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 5099 40957686 7 HPFS/NTFS
/dev/sda2 5100 60800 447418282+ f W95 Ext'd (LBA)
/dev/sda5 5100 8923 30716248+ 83 Linux
/dev/sda6 8924 12747 30716248+ 83 Linux
/dev/sda7 12748 13002 2048256 82 Linux swap / Solaris
/dev/sda8 13003 60800 383937403+ 7 HPFS/NTFS

Hard disc is set up as IDE Mode. With the same Bios setup the install routine on ubuntu 9.04 the hard disc and its partitions.

ProblemType: Crash
.var.log.jockey.log:

Architecture: i386
Date: Thu Nov 5 12:40:06 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/jockey-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: System manufacturer System Product Name
Package: jockey-gtk 0.5.5-0ubuntu2
PackageArchitecture: all
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --
ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk --check 60
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/bin/jockey-gtk', '--check', '60']
SourcePackage: jockey
Title: jockey-gtk crashed with DBusException in call_blocking()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/07/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1903
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3A32-MVP DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1903:bd10/07/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A32-MVPDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[NihilBaxter (sebastian-merkel)]

Additional Info:

ubuntu@ubuntu:~$ sudo dmraid -r
ERROR: pdc: identifying /dev/sda, magic_0: 0x11e1d7/0x121f0f, magic_1: 0x11e1d7/0x0, total_disks: 0
/dev/sda: nvidia, "nvidia_faiedeic", stripe, ok, 976773166 sectors, data@ 0

And from messages:

Nov 5 12:29:31 ubuntu ubiquity: ERROR: pdc: identifying /dev/sda, magic_0: 0x11e1d7/0x121f0f, magic_1: 0x11e1d7/0x0, total_disks: 0
Nov 5 12:29:31 ubuntu ubiquity: ERROR: pdc: identifying /dev/sda, magic_0: 0x11e1d7/0x121f0f, magic_1: 0x11e1d7/0x0, total_disks: 0
Nov 5 12:29:31 ubuntu ubiquity: ERROR: pdc: identifying /dev/sda, magic_0: 0x11e1d7/0x121f0f, magic_1: 0x11e1d7/0x0, total_disks: 0
Nov 5 12:29:31 ubuntu ubiquity: ERROR: pdc: identifying /dev/sda, magic_0: 0x11e1d7/0x121f0f, magic_1: 0x11e1d7/0x0, total_disks: 0
Nov 5 12:29:31 ubuntu ubiquity: ERROR: pdc: identifying /dev/sda, magic_0: 0x11e1d7/0x121f0f, magic_1: 0x11e1d7/0x0, total_disks: 0
Nov 5 12:29:31 ubuntu ubiquity: ERROR: pdc: identifying /dev/sda, magic_0: 0x11e1d7/0x121f0f, magic_1: 0x11e1d7/0x0, total_disks: 0
Nov 5 12:29:31 ubuntu ubiquity: ERROR: pdc: identifying /dev/sda, magic_0: 0x11e1d7/0x121f0f, magic_1: 0x11e1d7/0x0, total_disks: 0

Booting without dmraid does not fix the problem.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #403955, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.