Bug#272546: marked as done (Debian RAID almost working. Fsck failure on reboot.)
Your message dated Fri, 8 Oct 2004 19:49:23 -0400
with message-id <20041008234923.GD11850@kitenet.net>
and subject line FWD: Re: Bug#272546: Debian RAID almost working. Fsck failure on reboot.
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; 20 Sep 2004 18:06:04 +0000
>From sergioicai@gmail.com Mon Sep 20 11:06:04 2004
Return-path: <sergioicai@gmail.com>
Received: from rproxy.gmail.com (mproxy.gmail.com) [64.233.170.206]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1C9SY8-0003Df-00; Mon, 20 Sep 2004 11:06:04 -0700
Received: by mproxy.gmail.com with SMTP id 75so687327rnk
for <submit@bugs.debian.org>; Mon, 20 Sep 2004 11:06:03 -0700 (PDT)
Received: by 10.38.24.80 with SMTP id 80mr623019rnx;
Mon, 20 Sep 2004 11:06:03 -0700 (PDT)
Received: by 10.38.59.6 with HTTP; Mon, 20 Sep 2004 11:06:03 -0700 (PDT)
Message-ID: <4028d2e004092011063a457de6@mail.gmail.com>
Date: Mon, 20 Sep 2004 20:06:03 +0200
From: Sergio <sergioicai@gmail.com>
Reply-To: Sergio <sergioicai@gmail.com>
To: submit@bugs.debian.org
Subject: Debian RAID almost working. Fsck failure on reboot.
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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=-6.0 required=4.0 tests=BAYES_20,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: installation-reports
INSTALL REPORT
Debian-installer-version: Date - 17 sept 2004, URL:
http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20040917/
uname -a: Linux (none) 2.6.8-1-386 #1 Sat Aug 28 13:18:58 EDT 2004
i686 GNU/Linux
Date: 18 and 19 september 2004
Method: Installed from CD.
Machine: Packard Bell - Bora Pro 6168 v2 motherboard
Processor: Intel Pentium III - 667 MHz
Memory: 64 MB
Root Device: IDE Seagate - 2 x (ST380021A)
Root Size/partition table:
proc /proc proc defaults 0 0
/dev/md0 / ext3 defaults,errors=remount-ro 0 1
/dev/md1 none swap sw 0 0
/dev/md2 /usr ext3 defaults 0 2
/dev/md3 /var ext3 defaults 0 2
/dev/md4 /home ext3 defaults 0 2
/dev/md5 /usr/local ext3 defaults 0 2
/dev/md6 /tmp ext3 defaults 0 2
/dev/hdb /media/cdrom0 iso9660 ro,user,noauto 0 0
Output of lspci: command not found
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]
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [O]
Reboot: [E]
Comments/Problems:
- I am trying to install a RAID 1 system with two identical 80GB IDE
hard drives. The only
parameter I introduce in the boot option is: _linux26_
- During install, both hard drives were partitioned exactly in the
same order and size:
First /dev/hda1, next /dev/hdc1; second /dev/hda2, next /dev/hdc2...
- Most of the install was perfect. Everything worked as spected:
network, partition, RAID 1,
even boot loader worked (GRUB).
PROBLEM: REBOOT
===============
- Once I try to get into my new Debian system, I get an error related
to fsck. As I have
done a 'fresh install', there is nothing I can do from here.
- I guess there is something missing in the custom kernel 2.6 image.
- Please note the lines starting by 'mdadm:'. I am surprised mdadm
tries to look for
/dev/md/X instead of /dev/mdX which would be more logical...
- One more comment: I tried to install the same linux26 system in ONE
of the hard drives,
by NOT switching on the second one: and everything went perfect.
- I guess this is the last step before being able to run a RAID Debian
system directly
from Sarge installer 'out-of-the-box'. :-)
- Thanks a lot for an awesome work!!!
Sergio
- These are the boot messages:
(...)
Capability LSM initialized
Starting raid devices:
mdadm: error opening /dev/md/6: No such file or directory
mdadm: error opening /dev/md/5: No such file or directory
mdadm: error opening /dev/md/4: No such file or directory
mdadm: error opening /dev/md/3: No such file or directory
mdadm: error opening /dev/md/2: No such file or directory
mdadm: error opening /dev/md/1: No such file or directory
mdadm: error opening /dev/md/0: No such file or directory
done.
Checking all file systems...
fsck 1.35 (28-feb-2004)
fsck.ext3: Invalid argument while trying to open /dev/md6
/dev/md6:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternative superblock:
e2fsck -b 8193 <device>
fsck.ext3: Invalid argument while trying to open /dev/md5
/dev/md5:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternative superblock:
e2fsck -b 8193 <device>
fsck.ext3: Invalid argument while trying to open /dev/md4
/dev/md4:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternative superblock:
e2fsck -b 8193 <device>
fsck.ext3: Invalid argument while trying to open /dev/md3
/dev/md3:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternative superblock:
e2fsck -b 8193 <device>
fsck.ext3: Invalid argument while trying to open /dev/md2
/dev/md2:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternative superblock:
e2fsck -b 8193 <device>
fsck.ext3: Invalid argument while trying to open /dev/md0
/dev/md0:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternative superblock:
e2fsck -b 8193 <device>
fsck failed. Please repair manually.
CONTROL-D will exit from this shell and continue system startup.
Press enter for maintenance
(or type Control-D to continue):
(...END...)
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.
---------------------------------------
Received: (at 272546-done) by bugs.debian.org; 9 Oct 2004 00:26:08 +0000
>From joey@kitenet.net Fri Oct 08 17:26:08 2004
Return-path: <joey@kitenet.net>
Received: from kitenet.net [64.62.161.42] (postfix)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CG53o-0005cP-00; Fri, 08 Oct 2004 17:26:08 -0700
Received: from dragon.kitenet.net (unknown [66.168.94.144])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "Joey Hess", Issuer "Joey Hess" (verified OK))
by kitenet.net (Postfix) with ESMTP id C2BAC186CB
for <272546-done@bugs.debian.org>; Fri, 8 Oct 2004 23:48:01 +0000 (GMT)
Received: by dragon.kitenet.net (Postfix, from userid 1000)
id 4AC336E0EE; Fri, 8 Oct 2004 19:49:23 -0400 (EDT)
Date: Fri, 8 Oct 2004 19:49:23 -0400
From: Joey Hess <joeyh@debian.org>
To: 272546-done@bugs.debian.org
Subject: FWD: Re: Bug#272546: Debian RAID almost working. Fsck failure on reboot.
Message-ID: <20041008234923.GD11850@kitenet.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="NklN7DEeGtkPCoo3"
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: 272546-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:
--NklN7DEeGtkPCoo3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Looks like this bug can be closed.
----- Forwarded message from Sergio <sergioicai@gmail.com> -----
=46rom: Sergio <sergioicai@gmail.com>
Date: Sat, 9 Oct 2004 01:03:44 +0200
To: Joey Hess <joeyh@debian.org>
Cc: 272546@bugs.debian.org
Subject: Re: Bug#272546: Debian RAID almost working. Fsck failure on reboot.
Reply-To: Sergio <sergioicai@gmail.com>
Hi Joey,
I have tried once again to set the RAID system... and IT WORKED!!!
I used a Pre-RC2 image to do the test.
Hopefully it works for other filesystems as well, meaning that RAID
bugs are definitely closed... Thanks a lot for your effort!!!
Sergio
On Fri, 24 Sep 2004 19:50:31 +0200, Joey Hess <joeyh@debian.org> wrote:
> Sergio wrote:
> > http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20040917/
> >
> > - Once I try to get into my new Debian system, I get an error related
> > to fsck. As I have
> > done a 'fresh install', there is nothing I can do from here.
> >
> > - I guess there is something missing in the custom kernel 2.6 image.
> >
> > - Please note the lines starting by 'mdadm:'. I am surprised mdadm
> > tries to look for
> > /dev/md/X instead of /dev/mdX which would be more logical...
>=20
> I know that this is fixed in newer cd images than the rather old one you
> used. Can you please try with a current netinst image and see if it
> works? It sounds like it's closer to software raid working for the root
> partition than I thought.
>=20
> --
> see shy jo
>=20
>=20
>
----- End forwarded message -----
--=20
see shy jo
--NklN7DEeGtkPCoo3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFBZyeCd8HHehbQuO8RAu79AKCzR8F61FT6iFYY9c6UjIrQOUMAUACfYqHY
NJn45SwPLsBD269MnpT+r4U=
=LoFE
-----END PGP SIGNATURE-----
--NklN7DEeGtkPCoo3--
Reply to: