Thanks for your reply Justin.  I have now resolved the issue by re-loading
with 2.0.2 instead of 1.6.1, but I'll keep a note of your suggestions for
future reference.

The 200Gig drive has given me some problems and is full of disk errors, I've
lost some files, but only music files so they can be re-ripped from my CD
collection anyway.  I did have some suspicions about this drive before
putting it in the Qube, I originally had it in an IcyBox USB2.0/Firewire
caddy and that gave me some problems (Read/Write Delays) under XP but
because of their random nature had I put it down to the IcyBox, but I now
know it's the drive itself.  At least that's cleared up.

Again, thanks for your reply,

Sean.

-----Original Message-----
From: Justin Newcomer [mailto:liquidice5@gmail.com] 
Sent: 28 September 2005 20:12
To: Sean Lennon
Subject: Re: Booting problems.

the root dumps on .... is normal
it means something to the extent of, it will core dump there, its not
supposed to be a file system, and a fsck of it will not work on and
machine (i have the same ending of my dmesg) and mine works fine,
actually i have that on all three of my netBSD boxes

try booting into single user mode?

press space at the boot 1-13 tests

type "bfd /boot/boot.gz -s"

and then make sure the /bin/sh or whatever its looking for is there

either that, or  you ARE booting into single usermode and thats the problem
once you boot, try doing a clean proper reboot

from further analisys of your dmesg, it looks like your 200 gig drive
might have some read errors
i am not quite sure how to scan the disk surface for errors (like you
can with chkdsk in windows)

perhaps even the controller card is dying, and that is leading to read
errors

so to summerize, "root dumps on..." is not a bad thing

your wd1 giving readin errors is

On 9/24/05, Sean Lennon <sean@seanlennon.co.uk> wrote:
>
>
>
> Hi all,
>
>
>
> My Qube2 (1.6.1 - Rushmere style setup) has been running sweetly for a
number of months.  Unfortunately it appeared to die yesterday.  All attempts
to wake it up failed and I had to resort to recycling the power, there after
it failed to do anything beyond showing (and then removing) "Starting Up" on
the LCD.  LCD is now blank.
>
>
>
> Upon connecting the serial cable and watching the boot process on the
console I noted the statement "root on wd0a dumps on wd0b" was present, I
don't recall seeing it before, but then I didn't have problems before.  To
get a command prompt (shell) I had to supply the path (couldn't select
Return as before) as /usr/pkg/bin/bash.  Could the dump of wd0a in wd0b be
the cause of my woes or is it something else?  I have fsck'd wd0a and that
was fine, but wd0b came back with "fsck: /dev/wd0b has unknown file system
type".  As a novice with all things *nix I am at a loss on how to proceed.
>
>
>
> Cheers,
>
>
>
> Sean.
>
>
>
>
>
> My setup is as follows:
>
> OS:                  NetBSD 1.6.1
>
> Memory:           256MB
>
> HDD1:              15GB 2.5" (on Qube onboard IDE controller)
>
> HDD2:              200GB 3.5" (on Promise PCI IDE controller)
>
>
>
> The console log is as follows (apologies for size):
>
> Cobalt Microserver Diagnostics - 'We serve it, you surf it'
>
> Built Tue May 25 15:58:41 PDT 1999
>
>
>
>  1.LCD Test................................PASS
>
>  2.Controller Test.........................PASS
>
>  5.Bank 0:.................................64M
>
>  6.Bank 1:.................................64M
>
>  7.Bank 2:.................................64M
>
>  8.Bank 3:.................................64M
>
>  9.Serial Test.............................PASS
>
> 10.PCI Expansion Slot....................**Unknown Card**
>
> 12.IDE Test....................
>
> 13.Ethernet Test...........................PASS
>
> 16.RTC Test................................PASS
>
> BOOTLOADER ramcode: selected partition /dev/hda1
>
> Decompressing done
>
> Executing bootloader kernel...
>
> Decompressing -- done.
>
>
>
> >> NetBSD/cobalt 1.6U Bootloader, Revision 0.1 [@0x81000000]
>
> >> (cdi@merlin.camelot.net, Fri Jun 27 20:23:25 CEST 2003)
>
> >> Memory:              262144 k
>
> >> PROM boot string:    root=/dev/hda1 ro
>
> Loading: wd0a:netbsd
>
> 1757504+137048 [66800+57677]=0x1ed0ec
>
> Starting at 0x80001000
>
>
>
>  [ no symbols available
>
> Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002919 (wd1 bn
311781833; cn
>
>     The NetBSD Foundation, Inc.  All rights reserved.0: 32KB/
>
> 309307 tn 5 sn 62)wd1: (uncorrect
>
> Copyright (c) 1982, 1986, 1989, 1991, 1993
>
>
>
>
>
> CANNOT READ: BLK
>
>     The Regents of the University of California.  All rights reserved.NUE?
[yn] y
>
> pci0 at gt0
>
>
>
> wd1e: error readin
>
>
>
> NetBSD 1.6.1 (GENERIC) #0: Thu Jun 26 22:22:53 CEST 2003 ret
>
>
cdi@merlin.camelot.net:/misc/home/cdi/src/netbsd/1.6.1/src/sys/arch/cobalt/c
>
> rying-6411
>
> wd1: (uncorrectable data error)
>
> ompile/GENERIC
>
> wd1e
>
> 256 MB memory, 234 MB free, 13208 KB in 3302 buffers309307 tn 5 sn 62),
ret Ethernet, pass 4.1
>
> mainbus0 (root)
>
> com0 at mainbus0 addr 0x1c800000 level 3: st16650a, working fifo: in
>
> wd1: (uncorrectable data error)
>
> lxtphy0 at tlp0 phy 1: LXT970 10/100 media interface, rev. 3ng fsbn
311784128 of 311784096-311784223 (wd1 bn 311784128;
>
> lxtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>
> wd0: 14403 MB, 16383 cyl, 16 head, 63
>
> pcib0 at pci0 dev 9 function 0
>
> 309309 tn 10 sn 26), retryi
>
> pcib0: VIA Technologies VT82C586 (Apollo VP) PCI-ISA Bridge, rev
39interrupti
>
> 309309 tn 10 sn 26),
>
> pciide0 at pci0 dev 9 function 1: VIA Technologies VT82C586 (Apollo VP)
ATA33 coror)e 4, Ultra-DMA mode 2 (Ultra/33
>
> ntroller
>
> pciide0: bus-master DMA support present11784096-311784223 (wd1 bn
311784128; c
>
> pciide0: primary channel configured to compatibility mode
>
> transfers)
>
> pciide0: seco
>
> wd0 at pciide0 channel 0 drive 0: <TOSHIBA MK1517GAP>
>
> 309309 tn 10 sn 26), retrying
>
>  dev
>
> wd1: (uncorrec
>
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DMA
data
>
> pc
>
> wd1e: error reading fsbn 311784120 of 311784096-311784223 (
>
> transfers)
>
> pciide0: secondary channel configured to compatibility moderor reading
fsbn 311784120 (wd1 bn 311784120; cn 309309 tn
>
> pciide0: disabling secondary channel (no drives)s/se
>
> pciide0: disabling secondary channel (no drives)s/se
>
> pciide1: using irq 9 for native-PCI interrupt
>
> wd1 at pciide1 channel 0 drive 0: <Maxtor 6B200P0>
>
> wd1: drive supports 16-sector PIO transfers, LBA48 addressing
>
> wd1: 189 GB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 398297088
sectors
>
> wd1: 32-bit data port
>
> wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
>
> wd1(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DMA
data
>
> transfers)
>
> pciide1: secondary channel configured to native-PCI mode
>
> tlp1 at pci0 dev 12 function 0: DECchip 21143 Ethernet, pass 4.1
>
> tlp1: interrupting at level 2
>
> tlp1: Ethernet address 00:10:e0:00:d9:5b
>
> lxtphy1 at tlp1 phy 1: LXT970 10/100 media interface, rev. 3
>
> lxtphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>
> lcd0 at mainbus0
>
> boot device: wd0
>
> root on wd0a dumps on wd0b
>
> root file system type: ffs
>
> Sep 24 13:08:34 init: /bin/sh on /etc/rc terminated abnormally, going to
single
>
> user mode
>
> Enter pathname of shell or RETURN for sh:
>
> Sep 24 13:08:39 init: single user shell terminated, restarting
>
> Enter pathname of shell or RETURN for sh: /usr/pkg/bin/bash
>
> root@#