Bug#411170: marked as done (SATA failures with amd64 version of Etch)
Your message dated Fri, 16 Feb 2007 13:43:43 -0700
with message-id <[🔎] 20070216204343.GD31792@colo>
and subject line Bug#411170: SATA failures with amd64 version of Etch
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: kernel
Severity: critical
Multiple attempts to install Etch fail. The syslog file is filled with
failure messages along these lines:
Feb 16 01:09:27 debootstrap: Unpacking replacement base-files ...
Feb 16 01:09:57 kernel: ata1: command 0xca timeout, stat 0x50 host_stat 0x24
Feb 16 01:09:57 kernel: ata1: status=0x50 { DriveReady SeekComplete }
Feb 16 01:09:57 kernel: sda: Current: sense key: No Sense
Feb 16 01:09:57 kernel: Additional sense: No additional sense
information
Feb 16 01:09:57 kernel: Info fld=0x0
Feb 16 01:09:57 kernel: ata2: command 0x35 timeout, stat 0x50 host_stat 0x24
Feb 16 01:09:57 kernel: ata2: status=0x50 { DriveReady SeekComplete }
Feb 16 01:09:57 kernel: sdb: Current: sense key: No Sense
Feb 16 01:09:57 kernel: Additional sense: No additional sense
information
Feb 16 01:10:27 kernel: ata1: command 0x35 timeout, stat 0x50 host_stat 0x24
Feb 16 01:10:27 kernel: ata1: status=0x50 { DriveReady SeekComplete }
Feb 16 01:10:27 kernel: sda: Current: sense key: No Sense
Feb 16 01:10:27 kernel: Additional sense: No additional sense
information
Feb 16 01:10:27 kernel: ata2: command 0x35 timeout, stat 0x50 host_stat 0x24
Feb 16 01:10:27 kernel: ata2: status=0x50 { DriveReady SeekComplete }
Feb 16 01:10:27 kernel: sdb: Current: sense key: No Sense
Feb 16 01:10:27 kernel: Additional sense: No additional sense
information
I have saved as much of syslog as was flushed right before giving up (at
the rate it was going it would have taken days to finish -- if ever --
what completed successfully in under a half hour using the i386 version)
on the last attempt (I also have the complete partman log), and will be
happy to post them (or make them available via HTTP) if you believe they
will be of any use.
I have run hardware diagnostic tests on the drives and on the memory,
and everything is reported as healthy. I did the same installation
successfully using the i386 version of Etch. For the successful
installation only two changes were made:
1. I left the results of partitioning the hardware disks from the
last pass with the amd64 installer, and picked up with doing
the RAID configuration as before; and
2. i selected a different ethernet device.
Debian versions:
Debian GNU/Linux testing "Etch" - Official Snapshot amd64 Binary-1
(20061110) [failed]
Debian GNU/Linux testing "Etch" - Official Snapshot i386 Binary-1
20070215-23:10 [succeeded]
Hardware:
ASUS A8N-VN motherboard
AMD Athlon(tm) 64 Processor 3800+ (single processor)
2GB dual-channel PC3200 DDR 400
2 x ATA WDC WD2500JS-60N Rev: 10.0 disks
[configured using Linux software RAID level 1; the RAID support on the
motherboard is disabled]
I'll be glad to supply any other information that will help track down
the cause for the failure.
--
Bob Kline
http://www.rksystems.com
mailto:bkline@rksystems.com
--- End Message ---
--- Begin Message ---
On Fri, Feb 16, 2007 at 03:33:58PM -0500, Bob Kline wrote:
> dann frazier wrote:
> >hey Bob,
> > Its very likely that the success of the i386 install wasn't due to
> >the architecture, but rather to a newer kernel used (kernel has changed
> >significantly between 20061110 and 20070215). Please try the 20070215
> >amd64 installer.
> >
>
> Thanks, Dann. I'll give it a try. I was trying (but I guess didn't succeed very well) to pull
> down the frozen release candidate of Etch when I downloaded the 20061110 images. (I've been
> planning a switch from RedHat to Debian for my main server, and was trying to time it with the
> release of Debian 4.0. I figured I'd do my part by testing it before the release to see if I
> could catch any bugs before it went out the door. Can you tell me which version is the release
> candidate for 4.0?)
> I'll report back the results with the newer kernel.
Your best bet is one of these images:
http://www.debian.org/devel/debian-installer/
RC1 is no longer usable (see the News section) - RC2 should be
available Real Soon Now.
I'm going to go ahead and close this bug as I'm fairly certain it has
been fixed, but don't hestitate to reopen if you run into it again w/
the latest build.
--
dann frazier
--- End Message ---
Reply to: