Looks like my mistake was unanimously recognized by the following
people:
Scott Clark <scott.clark@east.sun.com>
Ronald Loftin <reloftin@syr.edu>
Russ Poffenberger <poffen@san-jose.tt.slb.com>
Tim Pointing <Tim.Pointing@dciem.dnd.ca>
Casper Dik <casper@holland.sun.com>
Barry Gamblin <bgamblin@hao.ucar.edu>
Chad Price <cprice@molbio.unmc.edu>
Tim Carlson <tim@santafe.edu>
Fischer Jens <fischjns@ina.de>
Brooke King (6532) <jbking@sandia.gov>
Bruce R. Zimmer <bzimmer@all-phase.com>
Scott F. Woods" <sfw@adc.idt.com>
I hope I didn't leave anyone out.
Here's the solution:
"... /etc/vfstab is incorrect. Check the "raw" column and correct the
filesystem listed there."
You guys are good. Thanks for the awesome assistance!
Here's the original problem:
> Hi. I installed Solaris 7 on a Sparc 5 last week. This old
> workstation has two rather small disk drives. To get the new
> OS to fit on this sparcstation I had to make the boot disk
> target 0 instead of the default target 3. I now have the
> following disk setup :
>
> wtr1-14 > df -k
> Filesystem kbytes used avail capacity Mounted on
> /proc 0 0 0 0% /proc
> /dev/dsk/c0t0d0s0 29978 16724 10257 62% /
> /dev/dsk/c0t0d0s6 488007 431981 7226 99% /usr
> Subject: cannot open dump device
>
>
> Hi. I installed Solaris 7 on a Sparc 5 last week. This old
> workstation has two rather small disk drives. To get the new
> OS to fit on this sparcstation I had to make the boot disk
> target 0 instead of the default target 3. I now have the
> following disk setup :
>
> wtr1-14 > df -k
> Filesystem kbytes used avail capacity Mounted on
> /proc 0 0 0 0% /proc
> /dev/dsk/c0t0d0s0 29978 16724 10257 62% /
> /dev/dsk/c0t0d0s6 488007 431981 7226 99% /usr
> fd 0 0 0 0% /dev/fd
> /dev/dsk/c0t0d0s4 9713 4807 3935 55% /var
> /dev/dsk/c0t0d0s3 15388 10 13840 1% /export
> /dev/dsk/c0t0d0s5 38493 7779 26865 23% /opt
> swap 6800 932 5868 14% /tmp
> /dev/dsk/c0t3d0s7 489702 161407 279325 37% /export/home
>
>
> wtr1-14 > /usr/sbin/ufsdump 0ucf /dev/rmt/0 /export/home
> DUMP: Cannot open dump device `/dev/rdsk/c0t0d0s7': I/O error
>
>
> As you can see the error message refers to c0t0d0s7 instead of
> c0t3d0s7.
>
> Does anyone have an idea what the problem might be?
>
>
> Thanks,
> Martin Meadows
> Indianapolis, IN.
>
>
> -------------------
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:20 CDT