problem with /dev/sda 82801EB (ICH5) SATA Controller

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the crash report that you received? This will allow us to better troubleshoot your crash. Thanks in advance.

Could you please attach /var/log/syslog and /var/log/partman to this bug, following the directions in http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in advance.

I am very sorry, because at this moment, I can't attache this log files - I
gave this CD with UBUNTU FF HERD 5 my friend and installed this (with succes)
in her new computer. I apologize that I don't remembered about this earlier.

My hardware:
motherboard: Gigabyte Pentium 4 Titan Series GA-8I865P(-G) [socked 478, Intel
865P,ICH5
proc: Intel Celeron D 2,4
SATA Samsung 120GB SATA 8MB
SP1213C
(+ ATA WD800BB-88JHC0)
yast SuSE 10.2: Giga-byte GA-8IP1000 Pro2 motherboard 865PE (piix)

Best regards
PiotrG

Dnia czwartek, 22 marca 2007 20:37, Colin Watson napisał:
> Could you please attach /var/log/syslog and /var/log/partman to this
> bug, following the directions in
> http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in
> advance.
>
> ** Changed in: ubiquity (Ubuntu)
> Assignee: (unassigned) => Colin Watson
> Status: Unconfirmed => Needs Info

ubuntu-7.04-beta-desktop-i386.iso = no bug, no crash, no problem :)
Thank you.

Dnia czwartek, 22 marca 2007 20:37, Colin Watson napisał:
> Could you please attach /var/log/syslog and /var/log/partman to this
> bug, following the directions in
> http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in
> advance.
>
> ** Changed in: ubiquity (Ubuntu)
> Assignee: (unassigned) => Colin Watson
> Status: Unconfirmed => Needs Info

I'm afraid that there is nothing I can do about this without the requested log files. If you (the original reporter) can reproduce this bug with a current release and can get me the log files, feel free to reopen this bug. (Anyone else reading this who believes they have a similar problem should open a new bug instead.)

I'm glad it worked for you with the beta release.