I have a ultra 10 machine and get the following error when trying to
startup the system
THE FOLLOWING FILE SYSTEM(S) HAD AN UNEXPECTED INCONSISTYENCY:
/dev/rdsk/c0t0d0s7 (export/home)
WARNING- Unable to repair one or more filesystems.
Run fsck manually(fsck filesystem...)
I then gave the following command (read the soltion from a similar
post)
fsck /dev/rdsk/c0t0d0s7 -y
Then it asked me the following question
**/dev/rdsk/c0t0d0s7
**Last Mounted on /export/home
**Phase 1 - check Blocks and sizes
**Phase 2 - check pathnames
**Phase3 - check connectivity
UNREF DIR i=875237 owner=ORACLE mode=40775
size=512 mtime=JUN 16 02:38 2002
reconnect?
I hit enter at reconnect and again it came up with a similar message
but with a different I=
I kept on hitting enter around 1000 times and finally it gav me
Phase 5- Check Cyl groups
21677 files, 436539 used , 6752762 free(18770 frags, 841749 blocks,
0.2%fragmentation)
fsck:operation not applicable to FSType nfs.
After this i rebooted the machine an am still getting Unexpected
Inconsistency.
Please suggest.
Thanks
Ronnie
you had your command reversed a little.....try-
fsck -y /dev/rdsk/c0t0d0s7
do it two or three times in a row. then reboot (init 6). should boot
fine after that.
Make sure you are in single user mode.
Hi,
How do I login as a single user mode.
When I start my system it gives me hunderds of error and asks me to
enter the root password or reboot.
I am a total newbee when it comes to Solaris/Unix.
Also why should doing it 2-3 times help, if it doesnt work the first
time.
also whats init 6 in your reply above.
Please suggest.
Thanks
Ronnie
--
Posted via Mailgate.ORG Server - http://www.Mailgate.ORG
Ronnie Yours wrote:
>>you had your command reversed a little.....try-
>>fsck -y /dev/rdsk/c0t0d0s7
>>
>>do it two or three times in a row. then reboot (init 6). should boot
>>fine after that.
>>
>>Make sure you are in single user mode.
>
>
>
> Hi,
>
> How do I login as a single user mode.
If at the "ok" prompt, type "boot -s". If on a running system, type
"reboot -- -s".
> When I start my system it gives me hunderds of error and asks me to
> enter the root password or reboot.
> I am a total newbee when it comes to Solaris/Unix.
>
> Also why should doing it 2-3 times help, if it doesnt work the first
> time.
You don't need to do it 2-3 times. Just do it once. If it works, it
works. If not, your disk is beyond repair by "fsck" and you will need
to have it replaced.
> also whats init 6 in your reply above.
It reboots the system. Just type "reboot" instead. It will be easier
for you to remember.
Hope this helps,
Don
--
*********************** You a bounty hunter?
* Rev. Don McDonald * Man's gotta earn a living.
* Baltimore, MD * Dying ain't much of a living, boy.
*********************** "Outlaw Josey Wales"
Thanks for the response. Shouldnt fsck tell me that its beyong repair.
According to the error message i am getting it looks that some files are
corrupted.
In my case its ok to lose the data, infact if need be I can reinstall
the whole O/S.
Please suggest.
Thanks
"Rev. Don Kool" <old...@comcast.net> wrote in message
news:3D0F69E...@comcast.net
>
>
> Ronnie Yours wrote:
> >>you had your command reversed a little.....try-
> >>fsck -y /dev/rdsk/c0t0d0s7
> >>
> >>do it two or three times in a row. then reboot (init 6). should boot
> >>fine after that.
> >>
> >>Make sure you are in single user mode.
> >
> >
> >
> Hi Don,
>
> Thanks for the response. Shouldnt fsck tell me that its beyong repair.
Well yes and no. The "fsck" command is 'file system check'. It checks
the filesystem installed on the disk, not the actual disk itself. Of
course these are related. You could have a failure, do the "fsck" and
never have a failure again. Then again, you could have a failure, run
the "fsck" and then have the disk fail again next week. It all depends
on why the disk failed in the first place.
> According to the error message i am getting it looks that some files are
> corrupted.
>
> In my case its ok to lose the data, infact if need be I can reinstall
> the whole O/S.
>
> Please suggest.
Well if "fsck" has to do extensive repairs, you probably are going to
have corrupted files. The problem is that you don't know what's
corrupted and what isn't. If reinstalling the OS is a relatively
painless option, that might be your best bet. If you reinstall the OS,
you might want to keep extra good backups for a month or so just in case
the disk does have a hardware problem that caused this in the first place.
So, backups are not needed in my case at all because there is nothing
installed in the first place other than the O/S.
So is reinstalling the O/S is the only option I have or is there
something else I should try before doing that.
Also if reinstalling is the only option can you and others please point
me to some articles where i get the instructions on how to format and
install the O/S.
Thanks a lot for the Help
Ronnie
OK. At that login prompt, give the root password and you'll be in single user
mode.
Stuart
Dr. Stuart A. Weinstein
Ewa Beach Institute of Tectonics
"To err is human, but to really foul things up
requires a creationist"
Ronnie Yours wrote:
> Thanks for the reply Don...
> I got this macjust for learning purposes. I wanted to learn Solaris and
> Oracle on Solaris.
>
> So, backups are not needed in my case at all because there is nothing
> installed in the first place other than the O/S.
>
> So is reinstalling the O/S is the only option I have or is there
> something else I should try before doing that.
If there were critical data on the disk, you might want to spend time
getting the system back up and saving it off, etc. Since this is just a
learning system with just the OS on it, you'll be better off in the long
run just doing a reinstall. That way any files that might have gotten
corrupted won't show up to bite you later on. Of course if the disk
continues to corrupt the file system in the future, then you should look
at replacing it.
> Also if reinstalling is the only option can you and others please point
> me to some articles where i get the instructions on how to format and
> install the O/S.
Since you're new to it, I would suggest that you simply insert the
installation disk and allow the installatin menus to guide you through
it. As you say, you're in it to learn.
> Thanks a lot for the Help
No problem.
Just wondering, fsck got better? In the old days it took multiple passes
if, for example, it was fixing a directory entry. The theory I thought was
that until it fixed the directory entry it could not check the files in the
directory. I can't swear to seeing this written anywhere. The rule of
thumb I came away with was run fsck until there were not errors and then to
be safe reboot. I started on AT&T's so I could easily be behind the times.
Thanks!
I'm a bit old and long in the tooth as well. Been doing this since the
80's and I have always run fsck thus :
fsck -F ufs -Y /dev/rdsk/cntndnsn
and if there was any problem, run it again until there isn't one!
I thought that was the way to go, unless I'm "behind the times" as well?
Dennis
ps: the -Y option is a simple convenience feature.
You are both "behind the times". Run "fsck" once and reboot.
Are you guys still doing "sync;sync;halt" also? :-)
Thanks a lot guys,
placing -y before /dev/rdsk/c0t0d0s7 did the trick.
Thanks a lot