> > > Thinking this would be simple, I removed > BE_disk2_slice4 and rebooted. > > I did get messages that update_archive couldn't be > written to BE_disk1_slice0 on going down. > > Perhaps that is why on the reboot, I find I am in > the same spot? > > When you say reboot, I presume you mean init 0 or > init 6 and actually > not reboot ?
Yes. An init 6. > > It could be that the sync process is punting. Can > you capture a log of > what it is saying ? I'll try. The message flies by quickly, but I believe part of the message was that it couldn't mount BE_disk1_slice0, which makes sense. That slice is already mounted, but because lustatus "thinks" it is on BE_disk2_slice4 it tries to mount BE_disk1_slice0 to synchronize the two boot_archives. It all makes sense but I have no idea how to undo it. > > > findroot (BE_disk2_slice0,0,a) -> findroot > (hd1,0,a) > > Close. It would be root(hd1,0,a) > > > findroot (BE_disk2_slice3,0,d) -> findroot > (hd1,0,d) > > root(hd1,0,d) > > > findroot (BE_disk2_slice4,0,e) -> findroot > (hd1,0,e) > > root (hd1,0,e) > > > findroot (BE_disk1_slice0,0,a) -> findroot > (hd0,0,a) > > root (hd0,0,a) > Okidok. thanks again. > > Bob > > _______________________________________________ > sysadmin-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/sysadmin- > discuss -- This message posted from opensolaris.org _______________________________________________ sysadmin-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss
