Hi, "Al Slater" <al.sla...@scluk.com> írta 2018-07-25 10:08-kor: > The problem is caused, I think, by device numbering differences in xen > versus ec2. > > I solved this problem when creating my AMIs by the following procedure. > > 1. Create an extra volume in EC2 with the same size as the instance > boot volume. > > 2. Attach the extra volume to the instance. > > 3. zpool attach the extra volume (c1t1d0?) > zpool attach rpool c4t0d0 c1t1d0 > > 4. zpool detach the original volume with incorrect name (c4t0d0) > zpool detach rpool c4t0d0 > > 5. zpool attach the original volume with the proper name (c1t0d0) > zpool attach rpool c1t1d0 c0t0d0 > > 6. zpool detach the extra volume. > zpool detach rpool c1t1d0 > > 7. Detach the extra volume from the instance and delete it. > > Double check all disk names in your instances first!
Nice trick tho! Checked, worked. I mean at least if I run a beadm activate omnios-1 it says Activated succesfully. And on omnios-1, the installboot is not diverted to true. -> I could clean up the garbage now, and destroy the old omnios be. Cheers, Gyu _______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss