Bug#270395: marked as done (install report: kernel 2.4 on dual xeon, problems with raid1 and pdc202xx_new)
Your message dated Wed, 27 Oct 2004 16:10:27 +0200
with message-id <200410271610.27984.aragorn@tiscali.nl>
and subject line Bug#270395: install report: kernel 2.4 on dual xeon, problems with raid1 and pdc202xx_new
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 7 Sep 2004 07:49:24 +0000
>From abel@foi.se Tue Sep 07 00:49:24 2004
Return-path: <abel@foi.se>
Received: from custos.foi.se (mercur-smtp.foi.se) [150.227.16.253]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1C4ajD-0007X9-00; Tue, 07 Sep 2004 00:49:24 -0700
Received: from mercur.foi.se (localhost [127.0.0.1])
by mercur-smtp.foi.se (8.12.9/8.12.9) with ESMTP id i877nJle006749
for <submit@bugs.debian.org>; Tue, 7 Sep 2004 09:49:19 +0200 (CEST)
Received: from mercur.foi.se (localhost [127.0.0.1])
by localhost.foi.se (Postfix) with ESMTP id 9B9AE29D
for <submit@bugs.debian.org>; Tue, 7 Sep 2004 09:49:19 +0200 (CEST)
Received: from mythos.foi.se (mythos.foi.se [150.227.60.30])
by mercur.foi.se (Postfix) with ESMTP id 7893C295
for <submit@bugs.debian.org>; Tue, 7 Sep 2004 09:49:19 +0200 (CEST)
Received: from lie.foi.se (Debian-exim@lie.foi.se [150.227.64.72])
by mythos.foi.se (8.12.9/8.12.9) with ESMTP id i877nIoq001258;
Tue, 7 Sep 2004 09:49:18 +0200 (CEST)
Received: from abel by lie.foi.se with local (Exim 4.34)
id 1C4aj8-0005Ap-Nv; Tue, 07 Sep 2004 09:49:18 +0200
Date: Tue, 7 Sep 2004 09:49:18 +0200
From: Anders Lennartsson <anders.lennartsson@foi.se>
To: submit@bugs.debian.org
Subject: install report: kernel 2.4 on dual xeon, problems with raid1 and pdc202xx_new
Message-ID: <20040907074918.GA19801@lie.foi.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040722i
Sender: Anders Lennartsson <abel@foi.se>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: installation-reports
I have a dual Xeon server with an Intel motherboard that will be
deployed as a file-server.
This report is written after several installation attempts. I know
trying with root on raid1 is not officially supported, but I have some
experience and google at hand so I set out to do it. Have one running
already installed by hacked woody cd and raid compiled into
kernel. Need to use 2.4 kernel because of openafs.
I have experienced mainly three problems:
1) Initiating raid devices at boot.
2) Detecting disks attached to the Promise IDE card.
3) mdadm fails to make superblock??
Details towards the end.
INSTALL REPORT
Debian-installer-version: sarge netinst iso image dated 2004-09-05
uname -a: during the install the 2.4.26 kernel used on the cd,
and after the first reboot a 2.4.27-1-386
Date: 2004-09-06 daytime CET
Method: Booted off iso-image (cdrw media), networked behind proxy,
but no problems with reaching mirror. Also have local mirror
which works ok without proxy.
Machine: Built from parts, Intel SE7501HG2 motherboard with onboard 2xSCSI,
2xIDE (hda-hdd), and extra Promise PCI IDE card (hde-hdh)
Processor: Dual Xeon 2.0GHz
Memory: 2GiB
Root Device: Four disks:
/dev/hde 185GB Hitachi PATA attached to promise card
/dev/hdg 185GB Hitachi PATA attached to promise card
/dev/sda 36GB Hitachi SCSI attached to scsi 0
/dev/sdb 36GB Hitachi SCSI attached to scsi 1
Goal is to have root, tmp, var, and swap on raid1, based on 4x2 partitions on the SCSI disks.
/ 12GB on raid 1 with /dev/sda1 and /dev/sdb1
/tmp 6GB on raid 1 with /dev/sda2 and /dev/sdb2
swap 2GB on raid 1 with /dev/sda3 and /dev/sdb3
/var 14GB on raid 1 with /dev/sda5 and /dev/sdb5
Further, the two PATA disks in a raid1 config:
/misc1 185GB on raid 1 with /dev/hde1 and /dev/hdg1
Output of lspci:
0000:00:00.0 Host bridge: Intel Corp. E7501 Memory Controller Hub (rev 01)
0000:00:00.1 ff00: Intel Corp. E7500/E7501 Host RASUM Controller (rev 01)
0000:00:03.0 PCI bridge: Intel Corp. E7500/E7501 Hub Interface C PCI-to-PCI Bridge (rev 01)
0000:00:03.1 ff00: Intel Corp. E7500/E7501 Hub Interface C RASUM Controller (rev 01)
0000:00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 02)
0000:00:1d.2 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #3) (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 42)
0000:00:1f.0 ISA bridge: Intel Corp. 82801CA LPC Interface Controller (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 82801CA Ultra ATA Storage Controller (rev 02)
0000:00:1f.3 SMBus: Intel Corp. 82801CA/CAM SMBus Controller (rev 02)
0000:01:0a.0 Unknown mass storage controller: Promise Technology, Inc. 20269 (rev 02)
0000:01:0c.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
0000:02:1c.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04)
0000:02:1d.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04)
0000:02:1e.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04)
0000:02:1f.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04)
0000:03:04.0 SCSI storage controller: Adaptec AIC-7902 U320 (rev 03)
0000:03:04.1 SCSI storage controller: Adaptec AIC-7902 U320 (rev 03)
0000:04:02.0 RAID bus controller: 3ware Inc 3ware 7000-series ATA-RAID (rev 01)
0000:04:05.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
0000:04:05.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [O]
Configure network HW: [O]
Config network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O] more or less
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [O] well, some hand tuning for root on raid1
Reboot: [E/O]
Comments/Problems:
Install logs and other status info is available in /var/log/debian-installer/.
Once you have filled out this report, mail it to submit@bugs.debian.org.
Overall work-path:
Booted with expert prompt for some more options. Works like a charm up
to partition stage. I did load the mdcfg package. Partman does
miss to show the name of the scsi disk /dev/sdb, but the size is
correctly identified.
Partition and creation of raid devices works ok.
Root on raid1 not supported, go ahead with warning, install base
system and kernel-2.4.27-1-386, but first add mdadm, initrd-tools,
dash, cramfsprogs and libdevmapper1.00 to the
/usr/lib/debootstrap/scripts/sarge base line. (shamlessly stolen from
debian-boot list in May [1]).
Copy lilo package to /target/root and chroot into target
mount -t proc proc /proc
Install lilo after manually adding /etc/lilo.conf with approximately
boot=/dev/md0
root=/dev/md0
raid-extra-boot="/dev/hde,/dev/hdg,/dev/sda,/dev/sdb"
delay=20
vga=normal
image=/vmlinuz
read-only
initrd=/initrd.img
(probably forgot some line now, but it all worked ok)
Run lilo, then dpkg-reconfigure mdadm and make it autostart the raid
devices by default. Funny thing is that mdadm -E /dev/md/0 reports
that the newly created device lacks a superblock??? Same thing for the
other raid devices.
Back to d-i and continue without boot-loader.
Problems encountered:
1) Initiating raid devices at boot.
First and later reboot with several raid devices defined fails the
fsck at boot. Root is correctly identified and started. After stepping
into the recovery mode, and using the command mdrun ; exit, boot
continues ok.
This problem persists even after install is completed.
If I use only two partitions on each scsi disk, with everything
installed into one partition and the others for swap boot works ok.
There is a bug with mdadm that it doesn't start the extra devices but it has
been closed [2]. However, other people have also experienced problems with
starting raid devices [3][4]. I'm not sure this has been resolved.
(I have zeroed the disks between install attempts to not have invalid
superblocks lying around.)
2) Detecting disks attached to the Promise IDE card.
The Promice IDE PCI card is identified by the 2.4.26 kernel on the CD,
and the disks are recognized. However, after booting into the
installed kernel, these disks are not initiated or recognized. For
instance I cannot do cfdisk /dev/hde. Yet the module pdc202xx_new is
loaded, marked as unused in the lsmod list.
This problems is the same with 2.4.27-1-386 and 2.4.27-1-686-smp.
But I think it worked about a week ago. I'll try to dig up my rc1 CD.
3) mdadm fails to make superblock??
Well, both after using partman and the choices below configure raid devices,
as well as manually creating raid1 devices with (in shell during boot off cd)
modprobe raid1
mdadm --create /dev/md/0 --level=1 --raid-devices=2 /dev/scsi/host0/../part1 /dev/scsi/host1/../part1
mdadm -E /dev/md/0 reports no superblock on this device?
[1] http://lists.debian.org/debian-boot/2004/05/msg03643.html
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=250792
[3] http://lists.debian.org/debian-user/2004/07/msg03897.html
[4] http://lists.debian.org/debian-user/2004/08/msg05619.html
Anders
---------------------------------------
Received: (at 270395-done) by bugs.debian.org; 27 Oct 2004 14:10:56 +0000
>From aragorn@tiscali.nl Wed Oct 27 07:10:56 2004
Return-path: <aragorn@tiscali.nl>
Received: from (elrond.fjphome.nl) [195.240.184.66]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CMoVr-0004UC-00; Wed, 27 Oct 2004 07:10:56 -0700
Received: from strider.fjphome.nl ([10.19.66.86] ident=fjp)
by elrond.fjphome.nl with esmtp (Exim 3.35 #1 (Debian))
id 1CMoVN-0006r2-00
for <270395-done@bugs.debian.org>; Wed, 27 Oct 2004 16:10:25 +0200
From: Frans Pop <aragorn@tiscali.nl>
To: 270395-done@bugs.debian.org
Subject: Re: Bug#270395: install report: kernel 2.4 on dual xeon, problems with raid1 and pdc202xx_new
Date: Wed, 27 Oct 2004 16:10:27 +0200
User-Agent: KMail/1.6.2
References: <[🔎] 20041027131924.GA20925@lie.foi.se>
In-Reply-To: <[🔎] 20041027131924.GA20925@lie.foi.se>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200410271610.27984.aragorn@tiscali.nl>
Delivered-To: 270395-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
On Wednesday 27 October 2004 15:19, Anders Lennartsson wrote:
> I have just tried with the 2004-10-26 netinst cd. I mainly works with
> kernel 2.4.27 on the Dual Xeon machine described earlier. I recommend
> this bug to be closed.
Thanks for following up. Closing the report.
Reply to: