From: Callum Hughes (Callum.Hughes@sis.securicor.co.uk)
Date: Thu May 09 2002 - 06:47:33 EDT
Hi everyone
I've had a look through the archives and on google and I can't find anything
relavent - if I've missed it, I apologise!
We were brought an Ultra 10 that had a flaky second disk and decided to
replace it. So, we fiddled around and installed it. The target number of the
disk has changed from c0t10d0 to c0t3d0 and we've built a new filesystem on
the new disk. However, on bootup or upon execution of a mountall, fsck comes
back saying that it cannot fsck c0t1d0 (which is no surprise given that it's
not there anymore!).
We've taken all the usual steps (boot -r, edited the /etc/vfstab, checked
/etc/mnttab, checked /dev/rdsk/*) and everything looks how it should be. The
only thing we haven't done is fiddle with the PROM but I can't really think
of a good reason to do this anyway.
The only thing that I can think of is that fsck raises a flag that says,
"Until this file system has been checked, come up with a warning..." I've
looked at the fsck man page and I can't see anything that points at
something like this so I was wondering if anyone had any ideas as to what is
going on and how to stop it happening. Having spoken to some other Unix
admins within our company, they seem to think that reinstalling the OS would
do it but that seems a bit like a Windows fix to me!
Any suggestions?
Kindest regards,
Callum A. Hughes
Unix Systems Engineer
Securicor Information Systems
t: 01249 - 665 -396
e: callum.hughes@sis.securicor.co.uk
**********************************************************************
The information contained in this e-mail message is intended
only for the individuals named above. If you are not the
intended recipient, you should be aware that any
dissemination, distribution, forwarding or other duplication
of this communication is strictly prohibited. The views
expressed in this e-mail are those of the individual author
and not necessarily those of
Securicor Information Systems Limited.
Prior to taking any action based upon this e-mail message
you should seek appropriate confirmation of its authenticity.
If you have received this e-mail in error, please immediately
notify the sender by using the e-mail reply facility.
**********************************************************************
_____________________________________________________________________
This message has been checked for all known viruses on behalf of Securicor Information Systems by the MessageLabs. For further information visit http://www.messagelabs.com or Email: mailsweeper.info@sis.securicor.co.uk
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:18 EDT