Summary: Mounting disk after booting from cdrom

From: Andreas Höschler <ahoesch_at_smartsoft.de>
Date: Mon Feb 04 2008 - 11:40:40 EST
Dear mangers,

thanks to all your responses:

When booting from cdrom with "boot cdrom -s" the SVM stuff is not 
loaded so

	mount /dev/md/rdsk/d0 /a

does not work. However,

	mount /dev/dsk/cXtXdXs0 /a

should work. The reason why it did not for me first was that I used 
c0t0d0s0. A call of format revealed that I should have used c1t0d0s0 
instead. I could not mount

	mount /dev/dsk/c1t0d0s0 /a

either since the filesystem was unclean. Unfortunately "fsck -F ufs  
/dev/dsk/c1t0d0s0" was not able to repair the filesystem. I get 
"unrepairable cyinder". I have given up on c1t0t0d0. Thankfully the 
really valuable data is in slice 6. I will therefore reinstall Solaris 
10 in c1t0d0s0 and then mount /dev/dsk/c1t0d0s6 in order to copy the 
data over the network to another machine.

Thanks for all your help!

Regards,

   Andreas



>>> I am playing with a Solaris machine to get some practice in rescuing
>>> died file systems. I booted the machine from disk into single user 
>>> mode
>>> and ran
>>>
>>> 	fsck -F ufs /dev/md/rdsk/d0
>>>
>>> The file system check went through. I now want to mount the disk read
>>> write to e.g. reset the root password or delete /etc/defaultdomain. I
>>> tried
>>>
>>> 	mount /dev/md/rdsk/d0 /a
>>>
>>> and got "No block device". I tried
>>>
>>> 	mount /dev/md/dsk/d0 /a
>>>
>>> and got "Mount point /a" does not exist". I tried
>>>
>>> 	mount /dev/md/dsk/d0 /tmp
>>>
>>> and got "/tmp is already used". I also tried "mkdir /a" but this 
>>> fails
>>> with "filesystem is read only". :-(
>>>
>>> What am I doing wrong?
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Mon Feb 4 11:41:34 2008

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:44:10 EST