Thanks for all reply me.
I can't rebuild path_to_inst, but I received a solution Sun's support
for my intention
I got success in my problem using the following steps:
1) change the multipack and my second submirror of system (E250) to
another machine (E450);
2) boot -sr
3) metadb -d <device - bad replicas> (ignoring messages about
"Ready-only file system"
4) reboot -- -sr
5) cd /dev/rdsk; rm c2t* c3t* c4t* c5t* c6t* c7t* c8t* c9t* c??t*
6) cd /dev/dsk; rm c2t* c3t* c4t* c5t* c6t* c7t* c8t* c9t* c??t*
7) drvconfig; devlinks; disks
The multipack received the controler 3. I did many tests, and always
received the number of controler that I removed plus 1! I don't known
why, neither Sun support.
> I'm can't rebuild a new path_to_inst. I have a E450 running Solaris 7
> and Solstice DiskSuite 4.2.
> I did the following steps:
> 1) clear the mirroring of all filesystem and the swap;
> 2) mv /etc/rcS.d/S35SUNWmd.init /etc/rcS.d/no.S35SUNWmd.init
> 3) mv /etc/path_to_inst /etc/path_to_inst.<date>
> 4) init 0
> 5) ok boot -ar (I took the default answers to the questions except to
> rebuild the path_to_inst, that I answer yes)
> the messages:
> Configuring network interfaces: hme0
> Hostname: <my_machine>
> mount: /dev/dsk/c0t0d0s3 no such device
> WARNING: /proc could not be mounted
> /sbin/swapadd: expr: not found
> /sbin/swapadd: swap: not found
> 6) the system can't boot and go back to ok prompt
> The /dev/dsk/c0t0d0s3 is the device of my /usr.
> I booted the system from CD, moved /etc/path_to_inst.<date> to
> /etc/path_to_inst and I can boot again normally.
> My intention is to clear the devices controlers and add multipacks to
> use lower number of controler SCSI, because actually I can olny use
> controler SCSI number 6 to up for the multipack.
> Any one can help me?
> H. S. Yann
> System & Network Administrator
-- H. S. Yann email@example.com System & Network Administrator VeritelNet
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:29 CDT