New MBoard & CPU, ==> fsck problem(s)

[Joseph Maxwell]

Hello,
I've just upgraded MBoard & CPU, original disks, Maxtor 40 & 80 Gb.
Machine on boot, goes through hardware probe and report HARDWARE
INCONSISTENCY & to RUN fsck MANUALLY and enters single user mode.
Partitions unmounted, either can't get fsck to run or remains in 'hung'
state.

Output:
/dev/ad0s1f    5904120 DUP I=1428544
/dev/ad0s1f    UNEXPECTED INCONSISTENCY:   RUN fsck MANUALLY
/dev/ad1s1e   LINK COUNT DIR I=8935936  OWNER=35543   MODE=40755
/dev/ad1s1e   SIZE = 512  MTME=Mar22 10:43 2001 COUNT should be 2
/dev/ad1s1e   LINK COUNT INCREASING
/dev/ad1s1e   UNEXPECTED INCONSISTENCY :  RUN fsck MANUALLY
            |
            |
Enter full pathname of shell or RETURN for /bin/sh:
_____________
"RETURN" ==> no change, system just hangs
On a few occasions, got past this stage to the '/' directory level.
Running fsck /dev/faultypartition runs through a few steps & hangs
_____________

Booting from CDROM, distr Disk #2 ==>
Mounting from ufs: /dev/md0c
/stand/sysinstall running as init on vty0

2nd mount attempt from same CDROM ==>
dscheck(# md/2): b_count 521 is not on a sector bounday (ssize 512)
dscheck(# md/2): b_count 521 is not on a sector bounday (ssize 512)
dscheck(# md/2): b_count 521 is not on a sector bounday (ssize 512)

_____________
3 copies of dscheck line spat out, then hung, no keyboard response etc.
_____________


Suggestion on how to get over this hump will be greatly appreciated
Thanks

--   Joe  --