07-15-2009
|
|
Registered User
|
|
|
Join Date: Jun 2008
Location: Texas
Posts: 142
|
|
Quote:
Originally Posted by Sapfeer
Sorry for delays, I didn't receive notification about your answer. Try fsck on c0d1
|
No problem,
Quote:
-bash-3.00# fsck /dev/rdsk/c0d1
fsck: could not stat /dev/rdsk/c0d1: No such file or directory
|
Quote:
fsck /dev/rdsk/c0d1s2
** /dev/rdsk/c0d1s2
BAD SUPERBLOCK AT BLOCK 16: MAGIC NUMBER WRONG
LOOK FOR ALTERNATE SUPERBLOCKS WITH MKFS? ^C
|
Quote:
-bash-3.00# fsck -y /dev/rdsk/c0d1s2
** /dev/rdsk/c0d1s2
BAD SUPERBLOCK AT BLOCK 16: MAGIC NUMBER WRONG
LOOK FOR ALTERNATE SUPERBLOCKS WITH MKFS? yes
LOOK FOR ALTERNATE SUPERBLOCKS WITH NEWFS? yes
SEARCH FOR ALTERNATE SUPERBLOCKS FAILED.
USE GENERIC SUPERBLOCK FROM MKFS? yes
CALCULATED GENERIC SUPERBLOCK WITH MKFS
If filesystem was created with manually-specified geometry, using
auto-discovered superblock may result in irrecoverable damage to
filesystem and user data.
CANCEL FILESYSTEM CHECK? yes
Please verify that the indicated block contains a proper
superblock for the filesystem (see fsdb(1M)).
FSCK was running in YES mode. If you wish to run in that mode using
the alternate superblock, run `fsck -y -o b=1213632 /dev/rdsk/c0d1s2'.
|
/var/adm/messages
Quote:
|
Cluster.devices.did: [ID 230304 daemon.notice] cldev: (C507896) Inquiry on device "/dev/rdsk/c0d1s2" failed
|
Any idea? Thanks!!
Last edited by upengan78; 07-15-2009 at 01:16 PM..
|
