Hi, This is my fist call (or call

[austin123]

Hi,
This is my fist call (or call for help) to tek-tips, great site.

1 of our SSP's connected to our E10k's had failed, it was displaying cntl'd & root P/W for maintenance etc!, I logged on as root and ran a :- fsck -y /dev/dsk/c0t0d0s0 notice the error!, /DSK/ not /RDSK/ I am getting constant failures on blocks when I tried to reload. Is it Ok to run a fsck on /dev aswell as /rdsk.
Any help would be much appreciated

 

[SamBones]

No, fsck expects the raw device (/dev/rdsk), not the block device (/dev/dsk). The only difference is that /dev/dsk uses buffers for all I/O and /dev/rdsk is unbuffered. It's the same device, just different way to access it. Using /dev/rdsk gives fsck byte-by-byte access to the device. The program fsck needs the raw byte-by-byte access to do what it needs to do.

I don't know if fsck'ing a /dev/dsk will cause any problems though.

The prompting for Ctrl-D and root password for maintenance (if I'm undertsanding your post) only means it's booting to single user mode. This could be a boot prom environment variable problem. (or a lot of other things). It does sound like it is booting though.

Did you see driver errors in the boot messages?

Hope this helps.

 

[mikeclark]

What error messages did you see on the screen?
There might be another partitian that has problems.

 

[akcrxnj]

Austin,

Did you make any changes prior to this happening? Did the ssp autoboot? how did you come across having this error?

Also just to clarify something about fsck after the release of solaris 8 I believe release date 12/02 you no longer have to specify /dev/rdsk if you mistakinly put /dev/dsk solaris will realize you meant rdsk.

 

[austin123]

To all replied, Thanks.
After all the invetigations it was found that the disk c0t0d0 was duff. We had the disc replaced and I done a ufs restore.
Cheers.