04-11-2012
Canīt open /dev/dsk/c1t0d0s0 Clone/mirror
Hello friends,
I Working with Solaris 8 on a SunFireV890, 150 GB SCSI HD's in Raid 1 (mirroring), my problem is that the master disk failed and going to put the slave (mirror) as a Master in the slot 0 (SCSI) will not start.
The original mounting this, mirror in Raid 0:
c1t0d0s0 (master)
c1t1d0s0 (Slave)
Amount slave disk in slot 0 (SCSI) and modify the /etc/vfstab, reboot, and when the machine began to start, tell me..
Can not open / dev/dsk/c1t0d0s0.
I have reviewed the vfstab and its OK, if I do a format tells me that the disk is pinched as c1t1d0s0.
I did another test on another machine with a HD NO MIRROR, is to make a clone/copy with a ufsdump, a virgin HD.
C0t0d0s0 (HD Solaris8)
C0t1d0s0 (HD virgin)
It happens the same, complete clone/copy, dismount the amount and the C0t1 c0t0 instead. I boot the machine and I get the same problem
Can not open / dev/dsk/c0t0d0s0.
Where you change the boot path? What happen with the clone ?
The vfstab is correct / dev/dsk/c0t0d0s0
Thanks a lot !!
Last edited by grymorum; 04-13-2012 at 06:31 AM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello!
When I use "sar -d" I get information about disk activities like:
sd0 ...
sd0,a ...
sd0,b ...
.....
sd22 ...
sd22,a ...
.....
How I can find by , for example sd22,a , what physical disk is it. For example /dev/dsk/c1t3d0s1 easy to read and I can find by it physical disk.... (4 Replies)
Discussion started by: Colf
4 Replies
2. Solaris
I've searched through unix.com and google for this issue I am having on one particular Sun E280R with installing netbackup software from CD. I know the cd is good because i installed the software on 4 other servers right before this one.
This is the issue I am seeing. vold does not mount the CD... (2 Replies)
Discussion started by: dangral
2 Replies
3. Solaris
I use the following command dk -k and get the following output:
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 1587078 56546 1482920 4% /
/dev/dsk/c0t0d0s6 1984230 926199 998505 49% /usr
/proc 0 0 0 ... (1 Reply)
Discussion started by: indianboy08
1 Replies
4. Solaris
Hi all,
I just find some strange device (at least to me) on my Sun Blade server, CP3060, like below:
bash-3.00# cd /dev/dsk
bash-3.00# ls c3*
c3t600A0B80002FA5F50000000000000000d0s0 c3t600A0B80002FA60C0000000000000000d0s4
c3t600A0B80002FA5F50000000000000000d0s1 ... (6 Replies)
Discussion started by: sleepy_11
6 Replies
5. Solaris
I have a Solaris machine running OpenSolaris v5.11.
It came with a hard drive. It's called /dev/dsk/c4d0s0.
I added two new hard drives into the box. I can't figure out what it's called in /dev/dsk. There are 210 filenames in /dev/dsk.
How do I find out which filename corresponds to the... (2 Replies)
Discussion started by: sqa777
2 Replies
6. Solaris
I installed solaris 9u8 and flar image and put on my jumpstart server which is running 10u3. Then I do jumpstart with new image with same hardware. Jumpstart acts like it installs, configures, and looks generally good. However, During the boot process, it reports the following errors.
The / file... (4 Replies)
Discussion started by: rushingfish
4 Replies
7. UNIX for Dummies Questions & Answers
Hi
May I know the meaning of the following command
mount /dev/dsk/c1t0d0s3 /mnt
Will I be able to use my tape drive after that?
Thanks (3 Replies)
Discussion started by: rahmantanko
3 Replies
8. Solaris
how to make less capacity on /dev/dsk/c1t0d0s5
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t0d0s0 9.6G 2.3G 7.2G 25% /
/dev/dsk/c1t0d0s1 9.6G 4.1G 5.4G 44% /usr
/dev/dsk/c1t0d0s4 9.6G 81M 9.4G 1% /var... (1 Reply)
Discussion started by: Cah.Lanang
1 Replies
9. Solaris
Our used size is 83 gb. Total of the folders and documents size is46,2 gb. 83-46=37 gb.
Where is my space. Where was lost?
Could you please I need your opinions?
{root}/space>du -s -h *
308K alaerrm-jprof
1K argerela
20G baerckup_in
1.8G cererm
28M ecerlipselink
... (8 Replies)
Discussion started by: getrue
8 Replies
10. Solaris
So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following:
devfsadm -Cv
powermt -q
luxadm -e offline <drive path>
luxadm probe
All those commands failed to remove the path. The drive stills shows up as <drive... (13 Replies)
Discussion started by: DustinT
13 Replies
LEARN ABOUT LINUX
metaroot
metaroot(1M) metaroot(1M)
NAME
metaroot - setup system files for root (/) metadevice
SYNOPSIS
/usr/sbin/metaroot -h
/usr/sbin/metaroot [-n] [-k system-name] [-v vfstab-name] [-c mddb.cf-name] [-m md.conf-name] [-R root-path] device
The metaroot command edits the /etc/vfstab and /etc/system files so that the system may be booted with the root file system (/) on an
appropriate metadevice. The only metadevices that support the root file system are a stripe with only a single slice or a mirror on a sin-
gle-slice stripe.
If necessary, the metaroot command can reset a system that has been configured to boot the root file system (/) on a metadevice so that it
uses a physical slice.
Root privileges are required for all of the following options except -h.
The following options are supported:
-c mddb.cf-name Use mddb.cf-name instead of the default /etc/lvm/mddb.cf file as a source of metadevice database locations.
-h Display a usage message.
-k system-name Edit a user-supplied system-name instead of the default /etc/system system configuration information file.
-m md.conf-name Edit the configuration file specified by md.conf-name rather than the default, /kernel/drv/md.conf.
-n Print what would be done without actually doing it.
-R root-path When metaroot modifies system files, it accesses them in their relative location under root-path.
The -R option cannot be used in combination with the -c, -k,-m, or -v options.
Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the
global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's
file system. See zones(5).
-v vfstab-name Edit vfstab-name instead of the default /etc/vfstab table of file system defaults.
The following operands are supported:
device Specifies either the metadevice or the conventional disk device (slice) used for the root file system (/).
Example 1: Specifying Root File System on Metadevice
The following command edits /etc/system and /etc/vfstab to specify that the root file system is now on metadevice d0.
# metaroot d0
Example 2: Specifying Root File System on SCSI Disk
The following command edits /etc/system and /etc/vfstab to specify that the root file system is now on the SCSI disk device
/dev/dsk/c0t3d0s0.
# metaroot /dev/dsk/c0t3d0s0
/etc/system System configuration information file. See system(4).
/etc/vfstab File system defaults.
/etc/lvm/mddb.cf Metadevice state database locations.
/kernel/drv/md.conf Configuration file for the metadevice driver, md.
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWmdu |
+-----------------------------+-----------------------------+
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M),
metarecover(1M), metarename(1M), metareplace(1M), metaset(1M), metassist(1M), metastat(1M), metasync(1M), metattach(1M), md.tab(4),
md.cf(4), mddb.cf(4), md.tab(4), attributes(5), md(7D)
6 Apr 2005 metaroot(1M)