fsck and disk problems

2007-12-25 11:08:00

Original Post:

Situation:

An Ultra 1 Creator 3D machine running Solaris 2.5.1. This machine has two

internal hard drives as indicated below from the output of df.

Filesystem kbytes used avail capacity Mounted on

/dev/dsk/c0t0d0s0 1828341 374031 1271480 23% /

/proc 0 0 0 0% /proc

fd 0 0 0 0% /dev/fd

/dev/dsk/c0t1d0s6 4036007 651566 3303721 17% /export/home

swap 402360 200 402160 1% /tmp

/local/proeng/.cfs_mnt_points/snowhite:_opt_proeng

                     1828336 1281360 364144 78% /opt/proeng

I restarted the machine last night after doing some Pro/E license

management and upon reboot I get the following message:

DKIOCINFO: Inappropriate ioctl for device

device:/dev/dsk/c0t1d0s6

Then fsck complains about the same disk (c0t1d0s6) and I get the prompt to

run fsck manually on it. Now here is the confusing part: I run fsck on

c0t1d0s6 and no problems are reported. However, fsck does report problems

on c0t0d0s0. I respond appropriately to correct the problems but to no

avail. When the machine reboots it does the same thing all over again and

reports the same bad blocks. I used format to try to repair the bad blocks

but it indicates that they are ok.

I have reformatted and recreated the file system on c0t1d0 but this did not

make a difference. It appears from reading the Answerbook that DKIOCINFO

refers to the disk controller and it's attributes.

The machine is up and running but I would like to fix this problem. Any

suggestions would be appreciated.

Answer:

I didn't have the raw device name in the "device to fsck" column of

/etc/vfstab.

Many thanks to the following people:

Casper Dik

Jeff Wasilko

Joel Lee

Bill Crane

Russ Poffenberger

****************************************************************

Leo Crombach System / Network Administrator

Tropel Corporation Phone: (716) 388-3566

60 O'Connor Road Email: lcrombach@tropel.com

Fairport, New York 14450 URL: http://www.tropel.com

****************************************************************

Comments

Got something to say?

You must be logged in to post a comment.