Very Computer

I have finished doing a restore of a dmp and now I'm not able to boot
in multi-user mode.
This is how I did the restore: I booted with the cdrom and mounted
/dev/dsk/c0t0d0s0 onto /a. Then I restored and umounted /a. When I
rebooted, I get the following below, then I issue the fsck h
/dev/dsk/c0t0d0s0 and still I can reboot. Any suggestions, greatly
appreciated.
=============================================================
/dev/dsk/c0t0d0s1: I/O error
The system is coming up.  Please wait.
checking ufs filesystems
/dev/rdsk/c0t0d0s7: BAD SUPER BLOCK: MAGIC NUMBER WRONG
/dev/rdsk/c0t0d0s7: USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED
INFORMATION;
/dev/rdsk/c0t0d0s7: eg. fsck [-F ufs] -o b=# [special ...]
/dev/rdsk/c0t0d0s7: where # is the alternate super block. SEE
fsck_ufs(1M).

/dev/rdsk/c0t0d0s7: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

THE FOLLOWING FILE SYSTEM(S) HAD AN UNEXPECTED INCONSISTENCY:
/dev/rdsk/c0t0d0s7
 (/local)

WARNING - Unable to repair one or more filesystems.
Run fsck manually (fsck filesystem...).

Quote:> This is how I did the restore: I booted with the cdrom and mounted
> /dev/dsk/c0t0d0s0 onto /a. Then I restored and umounted /a. When I
> rebooted, I get the following below, then I issue the fsck h
> /dev/dsk/c0t0d0s0 and still I can reboot. Any suggestions, greatly
> appreciated.
> =============================================================
> /dev/dsk/c0t0d0s1: I/O error
> The system is coming up.  Please wait.
> checking ufs filesystems
> /dev/rdsk/c0t0d0s7: BAD SUPER BLOCK: MAGIC NUMBER WRONG
> /dev/rdsk/c0t0d0s7: USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED
> INFORMATION;

--

Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

That's because the slice 0 has the hardware configuration of the machine and
the s7 may not available anymore.

In case it's a resore from the same machine, you will have to boot to the
single user mode using the installation cdrom.
- insert the cd 1 of 2 Solaris installation media.
- at ok prompt (STOP + A at POST step)
- type  boot cdrom -s

when logged in:
Get the list of alternate super-block numbers (32 is always one)
% fsck -N /dev/rdsk/c0t0d0s7

Correct the supper block problem by the command:
% fsck -o b=32 /dev/rdsk/c0t0d0s7
if the 32 don't work, use another number from the list.

Confirm the corection when asked for.

Hope this will help.

Quote:> Solaris 8/Sparc

> I have finished doing a restore of a dmp and now I'm not able to boot
> in multi-user mode.
> This is how I did the restore: I booted with the cdrom and mounted
> /dev/dsk/c0t0d0s0 onto /a. Then I restored and umounted /a. When I
> rebooted, I get the following below, then I issue the fsck -h
> /dev/dsk/c0t0d0s0 and still I can reboot. Any suggestions, greatly
> appreciated.
> =============================================================
> /dev/dsk/c0t0d0s1: I/O error
> The system is coming up.  Please wait.
> checking ufs filesystems
> /dev/rdsk/c0t0d0s7: BAD SUPER BLOCK: MAGIC NUMBER WRONG
> /dev/rdsk/c0t0d0s7: USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED
> INFORMATION;
> /dev/rdsk/c0t0d0s7: eg. fsck [-F ufs] -o b=# [special ...]
> /dev/rdsk/c0t0d0s7: where # is the alternate super block. SEE
> fsck_ufs(1M).

> /dev/rdsk/c0t0d0s7: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

> THE FOLLOWING FILE SYSTEM(S) HAD AN UNEXPECTED INCONSISTENCY:
> /dev/rdsk/c0t0d0s7
>  (/local)

> WARNING - Unable to repair one or more filesystems.
> Run fsck manually (fsck filesystem...).

Quote:

> > This is how I did the restore: I booted with the cdrom and mounted
> > /dev/dsk/c0t0d0s0 onto /a. Then I restored and umounted /a. When I
> > rebooted, I get the following below, then I issue the fsck ?h
> > /dev/dsk/c0t0d0s0 and still I can reboot. Any suggestions, greatly
> > appreciated.
> > =============================================================
> > /dev/dsk/c0t0d0s1: I/O error
> > The system is coming up.  Please wait.
> > checking ufs filesystems
> > /dev/rdsk/c0t0d0s7: BAD SUPER BLOCK: MAGIC NUMBER WRONG
> > /dev/rdsk/c0t0d0s7: USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED
> > INFORMATION;

> Did you partition the disk so that all the filesystems and other
> partitions required are available (like slice 1 and slice 7)?
> Did you newfs/restore /dev/dsk/c0t0d0s7 also?

Quote:

> That's because the slice 0 has the hardware configuration of the machine and
> the s7 may not available anymore.

> In case it's a resore from the same machine, you will have to boot to the
> single user mode using the installation cdrom.
> - insert the cd 1 of 2 Solaris installation media.
> - at ok prompt (STOP + A at POST step)
> - type  boot cdrom -s

> when logged in:
> Get the list of alternate super-block numbers (32 is always one)
> % fsck -N /dev/rdsk/c0t0d0s7

> Correct the supper block problem by the command:
> % fsck -o b=32 /dev/rdsk/c0t0d0s7
> if the 32 don't work, use another number from the list.

> Confirm the corection when asked for.

> Hope this will help.

Quote:>> Did you partition the disk so that all the filesystems and other
>> partitions required are available (like slice 1 and slice 7)?
>> Did you newfs/restore /dev/dsk/c0t0d0s7 also?
> I didn't newfs, I did a ufsrestore to the s7 which local was mounted
> on it. After I restored /, I did a ufsrestore on s7

In this case it's complaining about the filesystem.  I can't imagine how
a ufsrestore would work properly, but leave the filesystem corrupt like
this.  Does it fsck?  'fsck /dev/rdsk/c0t0d0s7'.  Even if it did, I
would newfs the slice and perform the restore again.

Quote:>> > /dev/dsk/c0t0d0s1: I/O error

prtvtoc /dev/rdsk/c0t0d0s0

--

Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >