Bug#285859: Installation-Report on Dual P4 with SATA Raid1 -
Ooops typo below in kernel version:
> Package: installation-reports
>
> Debian-installer-version: 21Nov04 sarge-i386-netinst.iso rc2
> uname -a: Linux Mars 2.6.8-1-386 #1 Thu Nov 25 04:24:08 UTC 2004 i686
> GNU/Linux
>
> Date: 15Dec04 19.00
> Method: Netinst http://mirror.ox.ac.uk
>
> Machine: ProServe MLS
> Processor: 3.2GHz 3.2GHz Intel P4 Prescott (dual)
> Memory:512Mb
> Root Device: ATA Disk Maxtor 6Y080P0
>
> Root Size/partition table:
> Device Boot Start End Blocks Id System
> /dev/hda1 * 1 543 273640+ 83 Linux
> /dev/hda2 544 19813 9712080 f W95 Ext'd
> (LBA)
> /dev/hda5 544 10231 4882720+ 83 Linux
> /dev/hda6 10232 16044 2929720+ 83 Linux
> /dev/hda7 16045 19038 1508944+ 82 Linux swap
> /dev/hda8 19039 19813 390568+ 83 Linux
>
>
> Output of lspci and lspci -n:
> 0000:00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM
> Controller/Host-Hub Interface (rev 02)
> 0000:00:01.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to AGP
> Controller (rev 02)
> 0000:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB
> UHCI #1 (rev 02)
> 0000:00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB
> UHCI #2 (rev 02)
> 0000:00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB
> UHCI #3 (rev 02)
> 0000:00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB
> UHCI #4 (rev 02)
> 0000:00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2
> EHCI Controller (rev 02)
> 0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2)
> 0000:00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC
> Bridge (rev 02)
> 0000:00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra
> ATA 100 Storage Controller (rev 02)
> 0000:00:1f.2 RAID bus controller: Intel Corp. 82801EB (ICH5R) SATA
> (cc=RAID) (rev 02)
> 0000:00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus
> Controller (rev 02)
> 0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER
> (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
> 0000:01:00.0 VGA compatible controller: nVidia Corporation: Unknown
> device 0326 (rev a1)
> 0000:02:01.0 Communication controller: NetMos Technology: Unknown
> device 9805 (rev 01)
> 0000:02:03.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
> 0000:02:04.0 Communication controller: Intel Corp. 536EP Data Fax
> Modem
> 0000:02:07.0 FireWire (IEEE 1394): Lucent Microelectronics FW323 (rev
> 61)
> 0000:02:08.0 Ethernet controller: Intel Corp. 82562EZ 10/100 Ethernet
> Controller (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] Chose to manually configure
> Config network: [O]
> Detect CD: [O]
> Load installer modules: [O]
> Detect hard drives: [O]
> Partition hard drives: [0]
> Create file systems: [O]
> Mount partitions: [E] Problem mounting RAID device - see below
> Install base system: [O]
> Install boot loader: [O]
> Reboot: [O]
> Comments/Problems:
>
> 2 SATA 120Gb drives configured during install as RAID1 device - all
> seemed fine with the partitioning
>
> However, during the first reboot, it failed to fsck /dev/md0
> and therefore wouldn't mount it - from dmesg:
> SCSI subsystem initialized
> sbp2: $Rev: 1219 $ Ben Collins <bcollins@debian.org>
> Capability LSM initialized
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: md0 stopped.
> EXT3-fs: unable to read superblock
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on hda8, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on hda5, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on hda6, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
>
> I hit Cntl-D to continue booting. The system installed OK with /home
> on the / partition instead of /dev/md0 as per partitioning during
> install.
>
> Looking back through the archive I found a post from Laurent CARON
> re: raid which explained how to manually create a raid array and so I
> did the following:
> cma@Mars:~$ sudo mdadm -Cv /dev/md0 -n2 -l1 /dev/sda1 /dev/sdb1
> mdadm: /dev/sda1 appears to be part of a raid array:
> level=1 devices=2 ctime=Wed Dec 15 23:43:56 2004
> mdadm: /dev/sdb1 appears to be part of a raid array:
> level=1 devices=2 ctime=Wed Dec 15 23:43:56 2004
> mdadm: size set to 120053632K
> Continue creating array? y
> mdadm: array /dev/md0 started.
>
> I then edited /etc/fstab and did:
> $ mount -a
> $ df -h
> which gave the right result:
> Filesystem Size Used Avail Use% Mounted on
> /dev/hda1 251M 110M 129M 46% /
> tmpfs 252M 0 252M 0% /dev/shm
> /dev/hda8 358M 8.1M 331M 3% /tmp
> /dev/hda5 4.6G 299M 4.1G 7% /usr
> /dev/hda6 2.8G 94M 2.6G 4% /var
> /dev/md0 113G 33M 107G 1% /home
>
> However, after reboot I get the same error:
> EXT3-fs: unable to read superblock
>
> So, I'm a bit stuck. Googling produced posts on booting from
> a RAID partition. All I'm trying to do is mount a RAID1
> partition on an installed system. Any pointers would be
> appreciated.
>
> The other problem that arose was when installing the
> 2.6.8-1-386-smp kernel - I got a kernel panic. I've yet to
> tackle this but will post in due course.
**Correction: 2.6.8-1-686-smp kernel
> For the install I booted "expert26" and it dealt with the
> SATA drives with no problem - great thanks ;)
>
> Regards
>
> Clive
--
www.clivemenzies.co.uk ...
...strategies for business
Reply to: