On 10/02/2015 10:26 AM, Dirk Steinberg wrote:
Am 02.10.2015 um 14:40 schrieb Nahum Shalman
<[email protected] <mailto:[email protected]>>:
https://wiki.smartos.org/display/DOC/Installing+Joyent+SmartOS+onto+a+Bootable+Disk+Partition
I'm guilty of having written the current version of that document as
well...
Nahum,
regarding your above document:
——-
This doesn't work to upgrade an existing SmartOS installation. ONLY do
this on a fresh system. These instructions are for a mirrored pair of
spindles.
1. Boot SmartOS in "noinstall" mode and log in as root.
2. Pick your disks from the output of the "diskinfo" command (e.g.
c0d0, d0d1, c0t0d0, c0t1d0, etc.), in this example, c0d0 and c0d1:
here we should see the code section: „zpool create zones mirror c0d0 c0d1"
1. Reboot the system normally from the CD, and go through the
installer, but don't specify any disks. The system should import
and use your existing zones pool. Let it reboot again.
———
My question: why not use the installer to create the zones pool? Just
because of the mirroring?
I thought that nowadays we have a new installer with expanded
capabilities…
Anyway, for my current case I do not need mirroring.
Probably because the older version of the instructions required
partitioning the drives because grub only relatively recently learned
how to be installed on and to boot from GPT labeled drives. I haven't
gone back to do a full audit of that page and don't intend to. It's an
unsupported configuration so if you can't understand how it works and
how to do it you shouldn't be doing it...
Also, I infer from that document the in the meantime SmartOS has
inherited from Illumos the
support for booting from EFI-labeled disks, including large disks and
whole-disk vdevs.
(Illumos features 5560, 5561, and 5664). Is that right?
Yes. Again, the wiki page was lightly updated when those commits landed
and hasn't really been touched since.
Will it matter if the disk names (c0d0t0) on the target system are
different as compared
to the system I create the image on? I.e. the source system uses
c1d0t0 and the target
c0d0t0, will it still auto-import the zones pool at boot?
Import will be just fine. Automating your "zpool online" would be
trickier. You'd have to pull the drive identifier out of "zpool status"
I have to think about all these issues ahead of time since after the
remote
deployment during the actual boot I am completely blind and will not
be able to see any error messages. Only if everything works perfectly
will I be able to login via ssh.
Right, again, test everything in VMs on your local system first.
-Nahum
-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription:
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com
