My original question is below. Thanks to all the many many responses.
The result ended being really lame, and one or two responses came close.
The device files for the disks in question were gone ... where and how,
I have no idea. As a result, and in hindsight, obviously, fsck was not
able to stat the device files.
At any rate I tried doing a 'b -r' from the boot prompt (remember this
is an x86 box, not a SPARC) thinking that that would effect a
reconfiguration boot just like a boot -r on SPARC. Apparently not.
I then touched /reconfigure, rebooted, and all was well.
Some notes on the responses ... the target number (t#) was not missing
from the device names ... these were IDE disks which only have a three
part device name. Brett Lymn, Kitty Ferguson and David Beard did hit on
doing the reconfig reboot.
Anyway, thanks again, all is well, the world is saved.
Mark Drummond wrote:
> I have a Solaris 2.6 x86 box here. It was compromised recently.
> Recovered from backups and the machine seemed to be running fine after
> that. I find out today that it is toast (I'm contracting part-time for
> as local shop). On boot I get:
> checking ufs filesystems
> /dev/rdsk/c0d1s7: No such file or directory
> Can't stat /dev/rdsk/c0d1s7
> /dev/rdsk/c0d1s7: CAN'T CHECK FILE SYSTEM
> /dev/rdsk/c0d1s7: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
> Then I get the same errors on two other slices (s6, s5). I'm at a loss
> here. The devices, and their relevent counterparts under /devices do
> exist. I hope someone can shed some light here ... still plugging away
> at it.
-- ______________________________________________________ Mark Drummond|ICQ#19153754|mailto:email@example.com Gang Warily|http://signals.rmc.ca/ Kingston Linux Users Group|http://signals.rmc.ca/klug/
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:04 CDT