I/O error ; Cannot mount /dev/dsk/c1t4d0s0


I have a Sun V880 which contains Solaris 9 previously & now decommissioned.
Just reinstalled Solaris 10 on it & used 'format' to partition one of the disks,
c1t4d0  but after format (& setting various partition sizes & did 'label'), I'm not
able to mount it :

# mount /dev/dsk/c1t4d0s0 /appl
mount: I/O error
mount: Cannot mount /dev/dsk/c1t4d0s0

# prtvtoc /dev/rdsk/c1t4d0s0
* /dev/rdsk/c1t4d0s0 partition map
* Dimensions:
*     512 bytes/sector
*     424 sectors/track
*      24 tracks/cylinder
*   10176 sectors/cylinder
*   14089 cylinders
*   14087 accessible cylinders
* Flags:
*   1: unmountable
*  10: read-only
*                          First     Sector    Last
* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory
       0      0    00          0   6298944   6298943
       1      0    00    6298944  14683968  20982911
       2      5    01          0 143349312 143349311
       3      0    00   20982912 121643904 142626815
       4      0    00   27383616  20972736  48356351
       5      0    00   48356352  20972736  69329087
       6      0    00   79820544  31464192 111284735
       7      0    00  143227200    122112 143349311

I've also tried to "fsck -y /dev/rdsk/c1t4d0s2" &
reattempt mounting it but to no avail.  I'm also facing
this problem with another disk c1t2d0s2 now.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hi sunhux,

Please let me know if you have a created a file system on c1t4d0s0 slice. What is the output of :-

# fstyp /dev/dsk/c1t4d0s0

sunhuxAuthor Commented:
Yes, the slice I'm trying to mount (s0) is ufs (but other slices on the disk
are unknown (though I've partitioned them using 'format')  :

# fstyp /dev/dsk/c1t4d0s0

# fstyp /dev/dsk/c1t4d0s1
Unknown_fstyp (no matches)
# fstyp /dev/dsk/c1t4d0s3
Unknown_fstyp (no matches)
# fstyp /dev/dsk/c1t4d0s7
Unknown_fstyp (no matches)
sunhuxAuthor Commented:

Think I got it working now : I have to do
newfs /dev/rdsk/c1t4d0s0  (as well as the other slices)
then I'm able to mount them.

One last question :
I have allocated s7 for metadb - does this slice needs to
be 'newfs'ed as well if it's not going to be mounted but
used for storing metadb only?

Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

If you are not planning to mount the slice then there is no need for creating a new file system on the slice 7. But if you wish to store some data onto the slice 7, then you need to create a file system first. see below:-
# metadb -a -f c0t0d0s7
 # newfs /dev/rdsk/c0t0d0s7
 # mount /dev/dsk/c0t0d0s7 /mnt

The disk and the slices used above are just examples.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sunhuxAuthor Commented:
So, can I say that there's no harm to do 'newfs' on the
slice (s7) which I'm going to store metadb?

Thanks & pardon my lengthiness
sunhuxAuthor Commented:

Just to clarify what I wanted :
ie I'll newfs /dev/rdsk/c0t0d0s7, then later,
can I still do "metadb -a -f c0t0d0s7"
Hi Sunhux,

It is always recommended that one should create state databases on a dedictaed slice that is atleast 4mb in size for each database replica it will store. Also, you cannot create state database replica on slices containing existing file system or data. So in other words:-

newfs /dev/rdsk/c0t0d0s7, then later,
can I still do "metadb -a -f c0t0d0s7 (No... this will not work ).

You can create state database replicas on slices that will later become part of volumes. Hope this answers your question.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.