Re: [OpenIndiana-discuss] Download Oracle SRUs / pkgrecv

2020-06-22 Thread Christian Meier 
Hello Sven

could you solve this issue?
I could receive entire of sru22 with latest OI bits today
Best Regards
Christian

On 29/05/2020 12:00, Sven Schmeling wrote:
> Hello,
>
> in our company we use 2 zones to hold the repositories for Solaris and
> Openindiana/Hipster-systems.
>
> The 2 servers are running with Openindiana/Hipster.
>
> For downloading i use a script:
>
> Solaris SRU part:
> --- snip ---
>
> ...
> pkgrecv -s https://pkg.oracle.com/solaris/support
>  -d
> file:///var/share/pkg/repositories/solaris-clone --cert
> /var/pkg5mirror/pkg.oracle.com.certificate.pem --key
> /var/pkg5mirror/pkg.oracle.com.key.pem '*'
> ...
>
> --- snip ---
>
> All worked fine until 2020-05-07 (including SRU 20)
> At this day the servers (and zones) were updated.
>
> Now the "pkgrecv" stop without an error after downloading the catalog.
> => $? =>  0
>
> A "pkcrecv" with the option "--clone" end with:
> Adding publisher solaris ...
> Processing packages for publisher solaris ...
> No packages to add.
>
> -
>
> Information:
>
> beadm list:
> BE Active Mountpoint Space   Policy Created
> openindiana    -  -  8.50M   static 2016-09-08 18:56
> openindiana-1  -  -  995.15M static 2016-10-12 13:18
> openindiana-2  -  -  9.02M   static 2016-10-12 13:21
> openindiana-3  -  -  15.51M  static 2017-02-21 14:06
> openindiana-4  -  -  8.49M   static 2017-06-15 09:15
> openindiana-5  -  -  7.66M   static 2019-04-16 13:19
> openindiana-2019:09:05 -  /mnt   16.61M  static 2019-09-05 15:08
> openindiana-2020:05:07 NR /  33.43G  static 2020-05-07
> 12:12
>
>
> -
>
> pkg info pkg:
>     Name: package/pkg
>  Summary: Image Packaging System
>  Description: The Image Packaging System (IPS), or pkg(5), is the
>   software delivery system used on OpenIndiana.  This
>   package contains the core command-line components and
>   pkg.depotd server.
>     Category: System/Packaging
>    State: Installed
>    Publisher: openindiana.org
>  Version: 0.5.11
>   Branch: 2020.0.1.5533
>   Packaging Date: Mon Mar 30 04:07:40 2020
>    Last Install Time: Tue Feb 21 13:08:03 2017
>     Last Update Time: Thu May  7 10:20:08 2020
>     Size: 14.30 MB
>     FMRI:
> pkg://openindiana.org/package/pkg@0.5.11-2020.0.1.5533:20200330T040740Z
> Repository Changeset: a051dce4
>
>   Source URL: https://github.com/OpenIndiana/pkg5/
>
> -
>
> zfs list:
> NAME  
> USED 
> AVAIL  REFER  MOUNTPOINT
> localstripe   
> 701G   637G  28.2K  /localstripe
> localstripe/applications
>  6.76G   637G  34.9K 
> /localstripe/applications
> localstripe/applications/olga5153
> 34.9K   637G  34.9K  /localstripe/applications/olga5153
> localstripe/zones
>  693G   637G  34.9K 
> /localstripe/zones
> localstripe/zones/olga5153
> 668G   637G  34.9K  /localstripe/zones/olga5153
> localstripe/zones/olga5153/ROOT 
>   668G   637G  34.9K  legacy
> localstripe/zones/olga5153/ROOT/VARSHARE  
> 535G   637G  34.9K  legacy
> localstripe/zones/olga5153/ROOT/VARSHARE/pkg  
> 535G   637G  34.9K  legacy
> localstripe/zones/olga5153/ROOT/VARSHARE/pkg/repositories 
> 535G   637G  38.2K  /var/share/pkg/repositories
> localstripe/zones/olga5153/ROOT/VARSHARE/pkg/repositories/IPSpkgrepos
> 91.5G   637G  91.5G  /var/share/pkg/repositories/IPSpkgrepos
> localstripe/zones/olga5153/ROOT/VARSHARE/pkg/repositories/bits-extra 
> 43.5M   637G  43.5M  /var/share/pkg/repositories/bits-extra
> localstripe/zones/olga5153/ROOT/VARSHARE/pkg/repositories/bits-extra-oi  
> 6.55M   637G  6.55M  /var/share/pkg/repositories/bits-extra-oi
> localstripe/zones/olga5153/ROOT/VARSHARE/pkg/repositories/hipster 
> 121G   637G   115G  /var/share/pkg/repositories/hipster
> localstripe/zones/olga5153/ROOT/VARSHARE/pkg/repositories/hipster-encumbered 
> 1.16G   637G  1.16G  /var/share/pkg/repositories/hipster-encumbered
> localstripe/zones/olga5153/ROOT/VARSHARE/pkg/repositories/openindiana
> 35.7K   637G  35.7K  /var/share/pkg/repositories/openindiana
> localstripe/zones/olga5153/ROOT/VARSHARE/pkg/repositories/solaris 
> 155G   637G   154G  /var/share/pkg/repositories/solaris
>

Re: [OpenIndiana-discuss] What's the easiest, straight-shot way to upgrade to a new boot SSD?

2020-06-22 Thread Jonathan Adams 
Yep, that's the idea.

Depending on how old your system was, you may need to zfs upgrade once
you've finished, but it should all work like that.

You'll need to: zfs snapshot -r rpool2@upgrade

But that's the essential plan.

I hope that the new install creates the correct ashift on the new pool.

Jon

On Mon, 22 Jun 2020, 16:40 Judah Richardson, 
wrote:

> On Mon, Jun 22, 2020 at 3:26 AM Jonathan Adams 
> wrote:
>
> > Unfortunately I'm currently redundant
>
> Ugh, I'm sorry to hear that. I've been made redundant myself 3 times :(
>
> and don't have access to what was my
> > illumos hardware ...
> >
> > I'd suggest you use the nappit suggestion, and do the backup from within
> > the old system before swapping the disks over ...
> >
> > As for the ashift, it's been a few years since I did a fresh install, and
> > I've forgotten how to force an ashift on a device during installation ...
> >
> Out of curiosity, is the method I described here
> <
> https://forums.servethehome.com/index.php?threads/how-do-i-migrate-openindiana-hipster-installation-from-512k-mbr-legacy-boot-32-gb-ssd-to-4k-gpt-uefi-boot-128-gb-ssd.29223/post-270825
> >
> in line with your previous suggestion of installing a default OI and then
> zfs
> send-ing the old SSD's rpool snapshot to the new SSD's rpool? Does that
> look like it would work?
>
> >
> > Jon
> >
> > On Mon, 22 Jun 2020, 08:10 Guenther Alka,  wrote:
> >
> > > hello Judah
> > >
> > > Am 22.06.2020 um 05:00 schrieb Judah Richardson:
> > > > On Sat, Jun 20, 2020 at 2:29 AM Guenther Alka 
> > > wrote:
> > > >
> > > >> Another option is to backup the current BE
> > > > How would I determine which one is current?
> > > >
> > > > to the datapool via zfs send.
> > >
> > > In napp-it, check menu Snapshots > Bootenvironment, at console beadm
> list
> > > Look in the list for N=curreNt, R=Reboot. Normally you find one with NR
> > > that is current and the one for next reboot.
> > >
> > > If you create a napp-it replication job, it automatically shows only
> the
> > > current BE as filesystem source together with all other regular
> > > filesystems.
> > >
> > > >> This can be done continously via incremental send for ongoing
> backups.
> > > >> If the system disk fails (or you want to replace), add a new disk,
> > > >> install a default OS, import the datapool and restore the BE
> > > > What exactly are the commands for this?
> > > >
> > > > via zfs
> > >
> > > Use napp-it menu Jobs > Replicate > create then start the job. On first
> > > run it replicates the whole filesystem, on next run only modified
> > > datablock (incremental zfs send)
> > >
> > > On console, create a snapshot of the current BE filesystem and use it
> > > for a zfs send
> > > Look at https://docs.oracle.com/cd/E36784_01/html/E36835/gbinw.html or
> > > other basic ZFS manuals
> > >
> > > >> send.
> > > > What would a command for this look like?
> > > >
> > > > Could folks kindly be more specific and detailed in their replies,
> > > please?
> > > > A lot of these are just really generic and I'm not really sure how to
> > > > proceed based on them.
> > > >
> > > > Then activate this BE and reboot to have the exact former OS
> > >
> > > After you restored the BE filesystem via another replication job or zfs
> > > send on the new installation use napp-it menu Snaps > Bootenvironment
> or
> > > "beadm activate bename" to set a BE active for next reboot. In beadm
> > > list you show the current marked with N and the activated one marked
> > > with R (will become current after a Reboot).
> > >
> > > >> installation restored.
> > > >>
> > > >>Gea
> > > >> @napp-it.org
> > > >>
> > > >>
> > >
> > > ___
> > > openindiana-discuss mailing list
> > > openindiana-discuss@openindiana.org
> > > https://openindiana.org/mailman/listinfo/openindiana-discuss
> > >
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> >
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] What's the easiest, straight-shot way to upgrade to a new boot SSD?

2020-06-22 Thread Judah Richardson 
On Mon, Jun 22, 2020 at 3:26 AM Jonathan Adams 
wrote:

> Unfortunately I'm currently redundant

Ugh, I'm sorry to hear that. I've been made redundant myself 3 times :(

and don't have access to what was my
> illumos hardware ...
>
> I'd suggest you use the nappit suggestion, and do the backup from within
> the old system before swapping the disks over ...
>
> As for the ashift, it's been a few years since I did a fresh install, and
> I've forgotten how to force an ashift on a device during installation ...
>
Out of curiosity, is the method I described here

in line with your previous suggestion of installing a default OI and then zfs
send-ing the old SSD's rpool snapshot to the new SSD's rpool? Does that
look like it would work?

>
> Jon
>
> On Mon, 22 Jun 2020, 08:10 Guenther Alka,  wrote:
>
> > hello Judah
> >
> > Am 22.06.2020 um 05:00 schrieb Judah Richardson:
> > > On Sat, Jun 20, 2020 at 2:29 AM Guenther Alka 
> > wrote:
> > >
> > >> Another option is to backup the current BE
> > > How would I determine which one is current?
> > >
> > > to the datapool via zfs send.
> >
> > In napp-it, check menu Snapshots > Bootenvironment, at console beadm list
> > Look in the list for N=curreNt, R=Reboot. Normally you find one with NR
> > that is current and the one for next reboot.
> >
> > If you create a napp-it replication job, it automatically shows only the
> > current BE as filesystem source together with all other regular
> > filesystems.
> >
> > >> This can be done continously via incremental send for ongoing backups.
> > >> If the system disk fails (or you want to replace), add a new disk,
> > >> install a default OS, import the datapool and restore the BE
> > > What exactly are the commands for this?
> > >
> > > via zfs
> >
> > Use napp-it menu Jobs > Replicate > create then start the job. On first
> > run it replicates the whole filesystem, on next run only modified
> > datablock (incremental zfs send)
> >
> > On console, create a snapshot of the current BE filesystem and use it
> > for a zfs send
> > Look at https://docs.oracle.com/cd/E36784_01/html/E36835/gbinw.html or
> > other basic ZFS manuals
> >
> > >> send.
> > > What would a command for this look like?
> > >
> > > Could folks kindly be more specific and detailed in their replies,
> > please?
> > > A lot of these are just really generic and I'm not really sure how to
> > > proceed based on them.
> > >
> > > Then activate this BE and reboot to have the exact former OS
> >
> > After you restored the BE filesystem via another replication job or zfs
> > send on the new installation use napp-it menu Snaps > Bootenvironment or
> > "beadm activate bename" to set a BE active for next reboot. In beadm
> > list you show the current marked with N and the activated one marked
> > with R (will become current after a Reboot).
> >
> > >> installation restored.
> > >>
> > >>Gea
> > >> @napp-it.org
> > >>
> > >>
> >
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> >
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] What's the easiest, straight-shot way to upgrade to a new boot SSD?

2020-06-22 Thread Judah Richardson 
On Mon, Jun 22, 2020 at 2:10 AM Guenther Alka  wrote:

> hello Judah
>
> Am 22.06.2020 um 05:00 schrieb Judah Richardson:
> > On Sat, Jun 20, 2020 at 2:29 AM Guenther Alka 
> wrote:
> >
> >> Another option is to backup the current BE
> > How would I determine which one is current?
> >
> > to the datapool via zfs send.
>
> In napp-it, check menu Snapshots > Bootenvironment, at console beadm list
> Look in the list for N=curreNt, R=Reboot. Normally you find one with NR
> that is current and the one for next reboot.
>
> If you create a napp-it replication job, it automatically shows only the
> current BE as filesystem source together with all other regular
> filesystems.
>
> >> This can be done continously via incremental send for ongoing backups.
> >> If the system disk fails (or you want to replace), add a new disk,
> >> install a default OS, import the datapool and restore the BE
> > What exactly are the commands for this?
> >
> > via zfs
>
> Use napp-it menu Jobs > Replicate > create then start the job. On first
> run it replicates the whole filesystem, on next run only modified
> datablock (incremental zfs send)
>
> On console, create a snapshot of the current BE filesystem and use it
> for a zfs send
> Look at https://docs.oracle.com/cd/E36784_01/html/E36835/gbinw.html or
> other basic ZFS manuals
>
> >> send.
> > What would a command for this look like?
> >
> > Could folks kindly be more specific and detailed in their replies,
> please?
> > A lot of these are just really generic and I'm not really sure how to
> > proceed based on them.
> >
> > Then activate this BE and reboot to have the exact former OS
>
> After you restored the BE filesystem via another replication job or zfs
> send on the new installation use napp-it menu Snaps > Bootenvironment or
> "beadm activate bename" to set a BE active for next reboot. In beadm
> list you show the current marked with N and the activated one marked
> with R (will become current after a Reboot).
>
Alright. Since the source SSD is currently disconnected, I'm going to try
the method I detailed at your STH forum here
.


>
> >> installation restored.
> >>
> >>Gea
> >> @napp-it.org
> >>
> >>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] What's the easiest, straight-shot way to upgrade to a new boot SSD?

2020-06-22 Thread Jonathan Adams 
Unfortunately I'm currently redundant and don't have access to what was my
illumos hardware ...

I'd suggest you use the nappit suggestion, and do the backup from within
the old system before swapping the disks over ...

As for the ashift, it's been a few years since I did a fresh install, and
I've forgotten how to force an ashift on a device during installation ...

Jon

On Mon, 22 Jun 2020, 08:10 Guenther Alka,  wrote:

> hello Judah
>
> Am 22.06.2020 um 05:00 schrieb Judah Richardson:
> > On Sat, Jun 20, 2020 at 2:29 AM Guenther Alka 
> wrote:
> >
> >> Another option is to backup the current BE
> > How would I determine which one is current?
> >
> > to the datapool via zfs send.
>
> In napp-it, check menu Snapshots > Bootenvironment, at console beadm list
> Look in the list for N=curreNt, R=Reboot. Normally you find one with NR
> that is current and the one for next reboot.
>
> If you create a napp-it replication job, it automatically shows only the
> current BE as filesystem source together with all other regular
> filesystems.
>
> >> This can be done continously via incremental send for ongoing backups.
> >> If the system disk fails (or you want to replace), add a new disk,
> >> install a default OS, import the datapool and restore the BE
> > What exactly are the commands for this?
> >
> > via zfs
>
> Use napp-it menu Jobs > Replicate > create then start the job. On first
> run it replicates the whole filesystem, on next run only modified
> datablock (incremental zfs send)
>
> On console, create a snapshot of the current BE filesystem and use it
> for a zfs send
> Look at https://docs.oracle.com/cd/E36784_01/html/E36835/gbinw.html or
> other basic ZFS manuals
>
> >> send.
> > What would a command for this look like?
> >
> > Could folks kindly be more specific and detailed in their replies,
> please?
> > A lot of these are just really generic and I'm not really sure how to
> > proceed based on them.
> >
> > Then activate this BE and reboot to have the exact former OS
>
> After you restored the BE filesystem via another replication job or zfs
> send on the new installation use napp-it menu Snaps > Bootenvironment or
> "beadm activate bename" to set a BE active for next reboot. In beadm
> list you show the current marked with N and the activated one marked
> with R (will become current after a Reboot).
>
> >> installation restored.
> >>
> >>Gea
> >> @napp-it.org
> >>
> >>
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] What's the easiest, straight-shot way to upgrade to a new boot SSD?

2020-06-22 Thread Guenther Alka 

hello Judah

Am 22.06.2020 um 05:00 schrieb Judah Richardson:

On Sat, Jun 20, 2020 at 2:29 AM Guenther Alka  wrote:


Another option is to backup the current BE

How would I determine which one is current?

to the datapool via zfs send.


In napp-it, check menu Snapshots > Bootenvironment, at console beadm list
Look in the list for N=curreNt, R=Reboot. Normally you find one with NR 
that is current and the one for next reboot.


If you create a napp-it replication job, it automatically shows only the 
current BE as filesystem source together with all other regular filesystems.



This can be done continously via incremental send for ongoing backups.
If the system disk fails (or you want to replace), add a new disk,
install a default OS, import the datapool and restore the BE

What exactly are the commands for this?

via zfs


Use napp-it menu Jobs > Replicate > create then start the job. On first 
run it replicates the whole filesystem, on next run only modified 
datablock (incremental zfs send)


On console, create a snapshot of the current BE filesystem and use it 
for a zfs send
Look at https://docs.oracle.com/cd/E36784_01/html/E36835/gbinw.html or 
other basic ZFS manuals



send.

What would a command for this look like?

Could folks kindly be more specific and detailed in their replies, please?
A lot of these are just really generic and I'm not really sure how to
proceed based on them.

Then activate this BE and reboot to have the exact former OS


After you restored the BE filesystem via another replication job or zfs 
send on the new installation use napp-it menu Snaps > Bootenvironment or 
"beadm activate bename" to set a BE active for next reboot. In beadm 
list you show the current marked with N and the activated one marked 
with R (will become current after a Reboot).



installation restored.

   Gea
@napp-it.org




___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss