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 [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
