From owner-freebsd-questions@FreeBSD.ORG Thu Jun 19 06:58:03 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 037A637B401 for ; Thu, 19 Jun 2003 06:58:03 -0700 (PDT) Received: from smtp0.adl1.internode.on.net (smtp0.adl1.internode.on.net [203.16.214.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EF9243FA3 for ; Thu, 19 Jun 2003 06:58:01 -0700 (PDT) (envelope-from malcolm.kay@internode.on.net) Received: from beta.home (ppp2159.sa.padsl.internode.on.net [150.101.28.110]) h5JDvw7R023887 for ; Thu, 19 Jun 2003 23:27:59 +0930 (CST) Content-Type: text/plain; charset="us-ascii" From: Malcolm Kay Organization: At home To: freebsd-questions@freebsd.org Date: Thu, 19 Jun 2003 23:27:58 +0930 User-Agent: KMail/1.4.3 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200306192327.58306.malcolm.kay@internode.on.net> Subject: vinum? flaky hardware? FreeBSD4.8? ASUS P4SGL-VM? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jun 2003 13:58:03 -0000 Over some time I've installed various versions=20 of FreeBSD. In the past installation has always=20 gone smoothly. Now however, I'm trying to setup a new system on a new machine with software RAID 1 (vinum) and=20 have run into difficulties (which I don't think have anything to do with vinum). The new machine is based on a P4SGL-VM mother=20 board with a 1.7G Celeron processor and 256Mb RAM. Two WDC WD1200JB-00DUA3 (120Gb) drives are=20 installed on the primary and secondary IDE master=20 ports with 80 conductor cables. During installation it seemed to be difficult to move sysinstall on from the fdisk and MBR dialogues=20 to the the disklabel dialogue; it seemed to want to always loop back to the beginning of the fdisk=20 dialogue. But after a number of false starts managed=20 to get a developer (without X) system installed on slice ad0s1 of about 6Gb. After some fiddling with with vinum in ad0s2 and ad2s2 I reset vinum (resetconfig) and discarded these slices. On ad2 I created one large slice and labeled it with a view to vinum with ad2s1a having an offset of 281 blocks and the vinum partition an offset of 16 blocks. After creating a filesystem on ad2s1a and mounting on=20 /mnt I attempted to copy the root partition from the axisting system using: # cd /mnt # dump -0 -a -f - / | restore -f - which reported an error something like: expected file 223455: found 223456 which (unfortunately) I didn't record so is only an approximation. # fsck -n /dev/ad0s1a reported an inconsistency but without any real detail. Rerunning # fsck /dev/ad0s1a whether or not in single user mode reported (NO WRITE) and declined to fix the problem. When attempting to write directly to an unmounted slice or partition: # dd if=3D/dev/zero of=3D/dev/ad0s2 count=3D50 I get a message to the effect that the filesystem is=20 readonly and a console message: fixlabel: invalid magic and on searching the kernel source I find it in /usr/src/kernel/subr_diskslice.c preceded by the comment /* These errors "can't happen" so don't bother reporting details. */ The problem has appeared on both drives. However fdisk and disklabel do not "seem" to have problems writing. History: =3D=3D=3D=3D=3D=3D I first attempted to set this up on another machine with the same=20 brand of mother board but slightly different -- significant to us it had an onboard network interface. On that board (same drives) I was the installation could not access the hard drives until UDMA was=20 disabled in the BIOS. Nor could the installed system operate with UDMA turned on. Stuck with PIO4 I abandoned that machine. (While I considered that a CD as slave on one of the IDE ports might create UDMA difficulties on one hard drive it does not explain, to me, lack of access to the other hard drive.) The above is of course a very much cut down version of events. The cost of the time spent messing about with these system has been much greater than the cost of the hardware! Do I have faulty hardware? Or is the hardware incompatible with FreeBSD? Is the hardware simply rubbish? Am I being stupid? Does any one have good or bad experience with these mother boards? Does anyone understand what is happening? Information: =3D=3D=3D=3D=3D=3D=3D=3D=3D # dmesg -> Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.8-RELEASE #0: Thu Apr 3 10:53:38 GMT 2003 root@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Celeron(R) CPU 1.70GHz (1715.28-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0xf13 Stepping =3D 3 =20 Features=3D0x3febfbff real memory =3D 234864640 (229360K bytes) avail memory =3D 223227904 (217996K bytes) Preloaded elf kernel "kernel" at 0xc051d000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 6 entries at 0xc00f1930 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: mem 0xe8000000-0xebffffff at devic= e 0.0=20 on pci0 pcib2: at device 1.0 on= pci0 pci1: on pcib2 pci1: at 0.0 irq 11 isab0: at device 2.0 on= pci0 isa0: on isab0 ohci0: mem 0xe7000000-0xe7000fff irq 3 at devic= e 2.2=20 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0xe6800000-0xe6800fff irq 6 at devic= e 2.3=20 on pci0 usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered atapci0: port 0xb800-0xb80f at device 2.5 on= pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: (vendor=3D0x1039, dev=3D0x7012) at 2.7 irq 5 rl0: port 0x9800-0x98ff mem 0xe5800000-0xe580= 00ff=20 irq 10 at device 15.0 on pci0 rl0: Ethernet address: 00:50:fc:a8:3e:08 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl1: port 0x9400-0x94ff mem 0xe5000000-0xe500= 00ff=20 irq 12 at device 16.0 on pci0 rl1: Ethernet address: 00:50:fc:a6:f9:f1 miibus1: on rl1 rlphy1: on miibus1 rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib1: on motherboard pci2: on pcib1 orm0: