Re: [OpenIndiana-discuss] loader doesn't load

[Toomas Soome via openindiana-discuss]

Yep, it is known issue, https://www.illumos.org/issues/16412 and unfortunately 
to understand what is actually going on there, we would need to instrument 
loader to print out whatever debug information we would want to see and iterate 
build/install/test cycles on actual hardware… 

rgds,
toomas

> On 12. Aug 2024, at 13:41, Udo Grabowski (IMK)  wrote:
> 
> Hi,
> 
> hit a strange problem, trying to boot a really simple system (old
> Sun U27, pure BIOS, not that UEFI/GPT/CSM rubbish), ISO loads and runs
> without problems; but from the disk, the loader does not start at all,
> instead outputs one or two empty lines and stops with a blinking cursor.
> Only action accepted there is CTRL-ALT-DEL ... Partition is Solaris 2,
> Option whole disk.
> Tried different options, installboot -mfF ... etc., always the same
> stall. Loader prompt from iso boot gives me these details:
> 
> Active allocators 827/2502
> 41.910.272 reserved, 33.578.256 allocated
> heap base 0xcb726000, top at 0xcdf1e000, upper limit 0xcf726000,
> 4.111.408 fragments
> 
> lsdev
> cd0  bios drv E: 41723824 x 2048
> disk dev. disk0 Bios dev C: 1.000.215.216 x 512
>  disk0s1: Solaris 2
>  disk0s1a: root
>  disk0s1i: boot
> 
>  disk1 Bios dev D: (3.907.029.168 x 512)
>  disk1p1: illumos ZFS
>  disk1p9: reserved
>  (pulled disk1 to avoid confusion, no help)
> lszfs
>   zfs:rpool   (disk0)
>   zfs:Work_SL (disk1)
> 
> But beadm at loader level does not find anything !
> 
> What's wrong here ?
> -- 
> Dr.Udo Grabowski  Inst.of Meteorology & Climate Research IMK-ASF-SAT
> https://www.imk-asf.kit.edu/english/sat.php
> KIT - Karlsruhe Institute of Technology  https://www.kit.edu
> Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026
> 
> ___
> 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] NVME bootable ?

[Toomas Soome via openindiana-discuss]

> On 5. Aug 2024, at 18:24, Udo Grabowski (IMK)  wrote:
> 
> Hi,
> is OI now bootable from a NVME device ? If so: In general, or does
> it still depend on specific controllers ?


In general, UEFI systems support booting from NVME and BIOS systems do not. But 
as usual, check your vendor documentation.

OI booting by itself does not depend on device type other than if we do have 
driver for kernel.

rgds,
toomas


> 
> Trying to get a flash array, but that has only NVME boot devices.
> -- 
> Dr.Udo Grabowski  Inst.of Meteorology & Climate Research IMK-ASF-SAT
> https://www.imk-asf.kit.edu/english/sat.php
> KIT - Karlsruhe Institute of Technology  https://www.kit.edu
> Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026
> 
> ___
> 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] Old Illumos in OI compared to OmniOS

[Toomas Soome via openindiana-discuss]

> On 18. Jun 2024, at 06:48, Joshua M. Clulow via openindiana-discuss 
>  wrote:
> 
> On Mon, 17 Jun 2024 at 19:30, Handojo via openindiana-discuss
>  wrote:
>> is this still persists ?
>> 
>> One of the workaround I have with large Hard Drive, is Partition it using 
>> OmniOS, and then install OI, as the IllumOS in OI is 2013 version
> 
> I'm not sure what issue you're referring to exactly, but OpenIndiana
> ships current illumos software just like OmniOS.  The current
> installation media is for "2024.04", from this year.
> 

And please keep the habit of running 'pkg update; reboot’ in regular basis, 
running OS from 2013 is security risk.

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

Re: [OpenIndiana-discuss] Sun Management Centre

[Toomas Soome via openindiana-discuss]

> On 21. May 2024, at 12:15, Rainer Heilke  wrote:
> 
> -- Original Message --
> From "Toomas Soome via openindiana-discuss" 
>  <mailto:openindiana-discuss@openindiana.org>>
> To "Discussion list for OpenIndiana"  <mailto:openindiana-discuss@openindiana.org>>
> Cc "Toomas Soome" mailto:tso...@me.com>>
> Date 2024-05-21 12:42:46 AM
> Subject Re: [OpenIndiana-discuss] Sun Management Centre
> 
>> 
>> 
>>> On 21. May 2024, at 10:28, Rainer Heilke  wrote:
>>> 
>>> Just a quick update:
>>> I'll still try to see if I can find any OpenIndiana.org references to smc 
>>> (not having found them yet, I suspect they were third party pages), but I 
>>> don't think I'll get to play with RBAC. It seems my test system likes to 
>>> lose any USB drives on reboot, and when/if I get them back, all data is 
>>> gone. zpool is even telling me that one zpool has a property that has never 
>>> existed on this box:
>>> This pool uses the following feature(s) not supported by this system:
>>>com.klarasystems:vdev_zaps_v2
>>> cannot import 'Work': unsupported version or feature
>> 
>> We do not support com.klarasystems:vdev_zaps_v2, so you have used OpenZFS 
>> based implementation to create this pool. To create pool which is supposed 
>> to be shared between different systems, you need to either create it on 
>> illumos, or disable feature flags on creation and enable them as needed.
> I previously used one of the two drives on FreeBSD with OpenZFS, but the 
> current pool (a mirror) was created under OpenIndiana/hipster. It seems zpool 
> -a is seeing the old destroyed FreeBSD/OpenZFS, but not the current OI pool. 
> Interesting. Also annoying. :/
>> 

This can happen when you have previous pool little bit “shifted” on disk, so 
you can read out (some) old pool labels. Typical case with FreeBSD is that pool 
was created on partitionless disk. Destroyed pool shouldn’t cause much grief, 
as the fact itself is recorded in pool labels (so you can still recover from 
accidental destroy), but if the original pool was exported or just left on disk 
as is, then there is high chance of creating mess. zpool destroy, zpool 
labelclear and zpool initialize are your friends in such case, but if you do 
have new data already on disk and want to make sure it is preserved, then more 
careful approach is needed.

rgds,
toomas

>> There is a work to build arm support, there are even some images to allow to 
>> run the current state of the work, but there is still much work ahead about 
>> supporting arm.
> That will be interesting. Thanks for the info.
> Rainer

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

Re: [OpenIndiana-discuss] Sun Management Centre

[Toomas Soome via openindiana-discuss]

> On 21. May 2024, at 10:28, Rainer Heilke  wrote:
> 
> Just a quick update:
> I'll still try to see if I can find any OpenIndiana.org references to smc 
> (not having found them yet, I suspect they were third party pages), but I 
> don't think I'll get to play with RBAC. It seems my test system likes to lose 
> any USB drives on reboot, and when/if I get them back, all data is gone. 
> zpool is even telling me that one zpool has a property that has never existed 
> on this box:
> This pool uses the following feature(s) not supported by this system:
>com.klarasystems:vdev_zaps_v2
> cannot import 'Work': unsupported version or feature

We do not support com.klarasystems:vdev_zaps_v2, so you have used OpenZFS based 
implementation to create this pool. To create pool which is supposed to be 
shared between different systems, you need to either create it on illumos, or 
disable feature flags on creation and enable them as needed.


> It's even losing the internal SSD.
> I'm loath to play around with RBAC, or anything else, on my OmniOS backup 
> server. And I doubt I can get any OpenSolaris flavour running on a Raspberry 
> Pi. :/   I even got a pair of 4TB drives for this (they were surprisingly 
> inexpensive).

There is a work to build arm support, there are even some images to allow to 
run the current state of the work, but there is still much work ahead about 
supporting arm.


> To quote Gary Olman's character in 5th Element, "I'm getting very 
> disappointed!"

you can just as well include this one too: “If you want something done, do it 
yourself” ;)

rgds,
toomas

> Rainer
> I wonder if there's something in the BIOS...
> 
> 
> -- Original Message --
> From "Rainer Heilke" 
> To "Discussion list for OpenIndiana" ; 
> "Discussion list for OpenIndiana" 
> Date 2024-05-14 11:13:24 AM
> Subject Re: [OpenIndiana-discuss] Sun Management Centre
> 
>> 
>> 
>> 
>> -- Original Message --
>> From "Rolf M. Dietze" 
>> To "Discussion list for OpenIndiana" 
>> Date 2024-05-14 12:43:55 AM
>> Subject Re: [OpenIndiana-discuss] Sun Management Centre
>> 
>>> 
>>> Quoting Rainer Heilke :
>>> 
>>>> On 5/13/24 22:50, Toomas Soome via openindiana-discuss wrote:
>>>>> 
>>>>>> On 14. May 2024, at 08:12, Rainer Heilke  
>>>>>> wrote:
>>>>>> 
>>>>>> Hi.
>>>>>> I keep running into documentation that tells me to do a task by  firing 
>>>>>> up the Sun Management Centre, but OI doesn't seem to have  it, nor can I 
>>>>>> find any way of getting/installing it. Is it  available for OpenIndiana? 
>>>>>> Is it maybe in a different repository?
>>>>>> The documentation needs to either explain how to get it, or any  
>>>>>> reference to it needs to be purged, IMNSH opinion. If the former,  I may 
>>>>>> be able to help a bit, as energy levels allow.
>>>>>> ??
>>>>>> Rainer
>>>>> I’m afraid, it is long dead. So yes, if you see the references,  please 
>>>>> do file the issue (and patches are also very welcome!).
>>>>> 
>>>>> thanks,
>>>>> toomas
>>>> 
>>>> I'll look into how to file issues, and make a note of the pages I've  
>>>> already found.
>>>> 
>>>> Unfortunately, that means a number of documents need to be fleshed  out 
>>>> with the proper chain of commands to perform the functions, and  I don't 
>>>> know how much I can help. Aside from limited energy, I never  had to deal 
>>>> with RBAC, etc. This is new-ish territory for me, having  always used sudo 
>>>> when I was working. (I want to learn the "proper"  RBAC way of doing 
>>>> things, even if only for kicks and giggles, which  is why I was looking 
>>>> into this in the first place.)
>>>> 
>>>> Rainer
>>> Hi Rainer,
>>> 
>>> I use RBAC quite often, on Solaris as well as on OpenIndiana since I
>>> am running Sunray desktops for class on Solaris in kiosk mode to have
>>> the students connect to OpenIndiana machines for their tasks to do.
>>> The students have to do admin stuff on the target systems but are all
>>> homed on one OpenIndiana machine to start from. So RBAC and resource
>>> management are needed. If you reference to the old Solaris 10 documentation,
>>> both run sm

Re: [OpenIndiana-discuss] Sun Management Centre

[Toomas Soome via openindiana-discuss]

> On 14. May 2024, at 08:12, Rainer Heilke  wrote:
> 
> Hi.
> I keep running into documentation that tells me to do a task by firing up the 
> Sun Management Centre, but OI doesn't seem to have it, nor can I find any way 
> of getting/installing it. Is it available for OpenIndiana? Is it maybe in a 
> different repository?
> The documentation needs to either explain how to get it, or any reference to 
> it needs to be purged, IMNSH opinion. If the former, I may be able to help a 
> bit, as energy levels allow.
> ??
> Rainer

I’m afraid, it is long dead. So yes, if you see the references, please do file 
the issue (and patches are also very welcome!).

thanks,
toomas


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

Re: [OpenIndiana-discuss] updates and reboots

[Toomas Soome via openindiana-discuss]

> On 8. Jan 2024, at 09:56, Goetz T. Fischer  wrote:
> 
> of course but that raises the question why new libs would require a reboot. 
> the worst that could happen 
> is that programs which depend on that lib would crash if they're restarted. 
> but if they're also updated, 
> then the next time they're restarted or just started it'll be fine.
> let's say there's a new openssl so i simply copy the new one over the old 
> one, restart ssh and i'm good.
> 
> similarly i can for example update rhel for months without a reboot and that 
> works. and i don't mean 
> live kernel patching. basically i only have to reboot for kernel stuff. but 
> for everything else i just 
> don't see a reason for all these reboots.

reboot is needed to verify your setup is still working as supposed after an 
update. You can have different kind of potential issues; if file is 
overwritten, then your currently running app will most likely crash, if the 
file is replaced, then running apps will continue to use old content till the 
apps are restarted and you can have mixture of old and new setup, which can 
give interesting results sometimes (you think your system has security patch 
installed, but actually old code is running and you are still vulnerable for 
example).

Of course, the context can be different, getting your vi or gnu tar updated 
most likely will not affect your system, but there are different scenarios.

Having BE concept actually does imply that you get used to have those BE’s 
created, so that you can actually rely on actually having the option to roll 
back in case of failure from update, or recovery from other kind of corruption. 
And yes, the cost of having those BE’s is needing to actually create those BE’s 
and leave old one functional.

I have seen plenty of cases where people have done those “small changes” on 
live systems over long period of time and ending up unbootable or broken 
systems once they actually reboot the system. Therefore I really encourage to 
have habit to reboot the system, to make sure that everything is still behaving 
as you do expect to.

rgds,
toomas

> 
> On Mon, 8 Jan 2024 08:10:51 +0100, Marcel Telka wrote:
>> many newly built packages will require something from new
>> illumos-gate (typically system/library[*])
> 
> ___
> 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] Is it safe to remove /var/pkg/cache directory?

[Toomas Soome via openindiana-discuss]

> On 14. Dec 2023, at 12:43, Marcel Telka  wrote:
> 
> On Thu, Dec 14, 2023 at 11:37:52AM +0100, Aurélien Larcher wrote:
>> On Thu, Dec 14, 2023 at 10:38 AM Marcel Telka  wrote:
>> 
>>> On Thu, Dec 14, 2023 at 09:30:53AM +0100, Predrag Zečević wrote:
 I understand network - there can be a lot of problems preventing fast
 download, but *pkg* showing packages decreasing...
>>> 
>>> Yes, it looks like a bug.  Feel free to file a bugreport.
>>> 
 Also, is this OK (15GB of OI packages seems too much to me)?
 
 :; pfexec du -sh /var/pkg/publisher/*
 21M /var/pkg/publisher/hipster-encumbered
 15G /var/pkg/publisher/openindiana.org
>>> 
>>> Not sure if it is okay or not.  Here is mine:
>>> 
>>> # du -sh /var/pkg/publisher/*
>>> 2.30M   /var/pkg/publisher/hipster-encumbered
>>> 1019M   /var/pkg/publisher/openindiana.org
>>> #
>>> 
>>> I fully update usually at least once a week with a reboot (and new BE).
>>> This update includes bits from illumos-gate.  I also update daily
>>> (without reboot) to have always up-to-date userland bits.  I do have
>>> (almost) all packages installed.  It is my oi and illumos build machine.
>>> 
>> 
>> I cannot remember which option it is but you can autopurge the cache after
>> successful install using a pkg property.
> 
> It was already discussed.  It is flush-content-cache-on-success.
> I'm not sure if /var/pkg/publisher/openindiana.org is considered as
> content-cache - see pkg(1) man page.
> 

This sounds like there must be some external and/or leftover files (cores?). 
Some of might be possible to clean up with maintenance commands like pkg 
refresh, purge-history etc. can not really suggest anything specific without 
knowing pkg internals.

Of course, one can experiment there — create new BE or backup BE and then you 
have option for quick recovery;)

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

Re: [OpenIndiana-discuss] Is it safe to remove /var/pkg/cache directory?

[Toomas Soome via openindiana-discuss]

> On 13. Dec 2023, at 15:13, Predrag Zecevic 
>  wrote:
> 
> On 2023-12-13 13:35:03, Toomas Soome wrote:
>> 
>> 
>>> On 13. Dec 2023, at 14:30, Predrag Zecevic via openindiana-discuss 
>>>  wrote:
>>> 
>>> Hi all,
>>> 
>>> I have searched for solution first, and could not find it...
>>> 
>>> My /var/pkg is huge:
>>> 
>>> :; pfexec du -shc /var/pkg/*
>>> 13G /var/pkg/cache
>>> 512 /var/pkg/gui_cache
>>> 5,0K/var/pkg/history
>>> 61M /var/pkg/license
>>> 512 /var/pkg/linked
>>> 512 /var/pkg/lock
>>> 512 /var/pkg/modified
>>> 5,5K/var/pkg/pkg5.image
>>> 14G /var/pkg/publisher
>>> 512 /var/pkg/ssl
>>> 346M/var/pkg/state
>>> 28G total
>>> 
>>> I wonder if /var/pkg/cache can be "emptied"?
>>> 
>>> With best regards.
>>> 
>>> -- 
>>> Predrag Zečević
>>> predrag.zecevic.1...@googlemail.com
>>> 
>>> 
>>> ___
>>> openindiana-discuss mailing list
>>> openindiana-discuss@openindiana.org
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>> 
>> 
>> make sure flush-content-cache-on-successis True in pkg property output, then 
>> install one package (and uninstall it if not really needed;), then the cache 
>> should get flushed for you.
>> 
>> rgds,
>> toomas
> 
> Hi Toomas,
> 
> I have that property set since long time ago:
> 
> :; pkg property flush-content-cache-on-success
> PROPERTY   VALUE
> flush-content-cache-on-success True
> 
> ATM:
> :; du -sh /var/pkg/cache/
> 13G /var/pkg/cache/
> 
> :; pkg list mail/opendkim
> 
> pkg list: no packages matching the following patterns are installed:
>   mail/opendkim
> 
> :; pfexec pkg install mail/opendkim
>Packages to install:  2
> Services to change:  2
>Create boot environment: No
> Create backup boot environment: No
> 
> DOWNLOADPKGS FILESXFER (MB)   
> SPEED
> Completed2/2   221/221 1.1/1.1 52.1k/s
> 
> PHASE  ITEMS
> Installing new actions   297/297
> Updating package state database Done
> Updating package cache   0/0
> Updating image stateDone
> Creating fast lookup database   Done
> Reading search indexDone
> Updating search index2/2
> Updating package cache   2/2
> 
> :; pfexec pkg uninstall mail/opendkim
> Packages to remove:  1
> Services to change:  2
>Create boot environment: No
> Create backup boot environment: No
> 
> PHASE  ITEMS
> Removing old actions 249/249
> Updating package state database Done
> Updating package cache   1/1
> Updating image stateDone
> Creating fast lookup database   Done
> Reading search indexDone
> Updating search index1/1
> Updating package cache   2/2
> 
> # Installed 2 packages, but removed only one -- but that is another story...
> 
> :; du -sh /var/pkg/cache/
> 13G /var/pkg/cache/
> 
> So, nothing has happen
> 
> Regards.
> 
> -- 
> Predrag Zečević
> predrag.zecevic.1...@googlemail.com
> 


hm, that is interesting. How old is this BE?

rgds,
toomas



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

Re: [OpenIndiana-discuss] Is it safe to remove /var/pkg/cache directory?

[Toomas Soome via openindiana-discuss]

> On 13. Dec 2023, at 14:30, Predrag Zecevic via openindiana-discuss 
>  wrote:
> 
> Hi all,
> 
> I have searched for solution first, and could not find it...
> 
> My /var/pkg is huge:
> 
> :; pfexec du -shc /var/pkg/*
> 13G /var/pkg/cache
> 512 /var/pkg/gui_cache
> 5,0K/var/pkg/history
> 61M /var/pkg/license
> 512 /var/pkg/linked
> 512 /var/pkg/lock
> 512 /var/pkg/modified
> 5,5K/var/pkg/pkg5.image
> 14G /var/pkg/publisher
> 512 /var/pkg/ssl
> 346M/var/pkg/state
> 28G total
> 
> I wonder if /var/pkg/cache can be "emptied"?
> 
> With best regards.
> 
> -- 
> Predrag Zečević
> predrag.zecevic.1...@googlemail.com
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss


make sure flush-content-cache-on-success  is True in pkg property output, then 
install one package (and uninstall it if not really needed;), then the cache 
should get flushed for you.

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

Re: [OpenIndiana-discuss] installing on 2tb disk

[Toomas Soome via openindiana-discuss]

> On 21. Nov 2023, at 21:49, Toomas Soome  wrote:
> 
>> 
>> On 21. Nov 2023, at 20:24, Goetz T. Fischer  wrote:
>> 
>> hello again,
>> 
>> i just tried to install indiana onto a 2tb disk and the installer crashed. 
>> it claimed the disk had 64tb 
>> and complained about the size. trying to use format from the shell resulted 
>> in a crash as well.
>> then i tried omnios and with that the installation worked. however, after 
>> logging into the installed os, 
>> zfs list reported a 61tb rpool and pkg crashed. so although the installer 
>> went through, it's apparently 
>> not usable.
>> 
>> so what's the trick for using bigger disks as rpool?
>> 
>> thanks in advance as always!
>> 
> This sounds like firmware issue (either system or HBA or disk). My system is 
> (old supermicro X10SAE):
> 
> tsoome@beastie:/code/16034$ zpool status
>   pool: rpool
>  state: ONLINE
>   scan: scrub repaired 0 in 0 days 10:16:24 with 0 errors on Fri May 19 
> 19:42:12 2023
> config:
> 
> NAMESTATE READ WRITE CKSUM
> rpool   ONLINE   0 0 0
>   raidz1-0  ONLINE   0 0 0
> c3t0d0  ONLINE   0 0 0
> c3t1d0  ONLINE   0 0 0
> c3t3d0  ONLINE   0 0 0
> c3t4d0  ONLINE   0 0 0
> 
> errors: No known data errors
> tsoome@beastie:/code/16034$ sudo format
> Password: 
> Searching for disks...done
> 
> 
> AVAILABLE DISK SELECTIONS:
>0. c3t0d0 
>   /pci@0,0/pci15d9,805@1f,2/disk@0,0
>1. c3t1d0 
>   /pci@0,0/pci15d9,805@1f,2/disk@1,0
>2. c3t3d0 
>   /pci@0,0/pci15d9,805@1f,2/disk@3,0
>3. c3t4d0 
>   /pci@0,0/pci15d9,805@1f,2/disk@4,0
> Specify disk (enter its number): ^D
> tsoome@beastie:/code/16034$
> 
> rgds,
> toomas

I forgot to note - you may want to try UEFI boot (remember to switch off secure 
boot).

rgds,
toomas

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

Re: [OpenIndiana-discuss] installing on 2tb disk

[Toomas Soome via openindiana-discuss]

> On 21. Nov 2023, at 20:24, Goetz T. Fischer  wrote:
> 
> hello again,
> 
> i just tried to install indiana onto a 2tb disk and the installer crashed. it 
> claimed the disk had 64tb 
> and complained about the size. trying to use format from the shell resulted 
> in a crash as well.
> then i tried omnios and with that the installation worked. however, after 
> logging into the installed os, 
> zfs list reported a 61tb rpool and pkg crashed. so although the installer 
> went through, it's apparently 
> not usable.
> 
> so what's the trick for using bigger disks as rpool?
> 
> thanks in advance as always!
> 

This sounds like firmware issue (either system or HBA or disk). My system is 
(old supermicro X10SAE):

tsoome@beastie:/code/16034$ zpool status
  pool: rpool
 state: ONLINE
  scan: scrub repaired 0 in 0 days 10:16:24 with 0 errors on Fri May 19 
19:42:12 2023
config:

NAMESTATE READ WRITE CKSUM
rpool   ONLINE   0 0 0
  raidz1-0  ONLINE   0 0 0
c3t0d0  ONLINE   0 0 0
c3t1d0  ONLINE   0 0 0
c3t3d0  ONLINE   0 0 0
c3t4d0  ONLINE   0 0 0

errors: No known data errors
tsoome@beastie:/code/16034$ sudo format
Password: 
Searching for disks...done


AVAILABLE DISK SELECTIONS:
   0. c3t0d0 
  /pci@0,0/pci15d9,805@1f,2/disk@0,0
   1. c3t1d0 
  /pci@0,0/pci15d9,805@1f,2/disk@1,0
   2. c3t3d0 
  /pci@0,0/pci15d9,805@1f,2/disk@3,0
   3. c3t4d0 
  /pci@0,0/pci15d9,805@1f,2/disk@4,0
Specify disk (enter its number): ^D
tsoome@beastie:/code/16034$

rgds,
toomas

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

[OpenIndiana-discuss] anyone with sfe?

[Toomas Soome via openindiana-discuss]

hi!

Is there anyone with sfe network to test 
https://code.illumos.org/c/illumos-gate/+/2887 ?

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

Re: [OpenIndiana-discuss] ZFS disk is full at boot

[Toomas Soome via openindiana-discuss]

> On 5. Nov 2023, at 21:02, private mail openbabel  wrote:
> 
> Dear All,
> 
> I havr had aseveral notices my disk is becomming full. Having liberated space 
> of th rpool with destroy beadm // instructions. I have arrived at the point 
> when at boot up the system refuses to boot due to disk full instruction. I 
> have tried to follow other people who have also encountered similar problem 
> but have been unsuccessful. I am unable to access the zfs files with live 
> media through single user mode. Any help would be appriciated on clearing the 
> snapshots or similar from this position ?
> 
> Regards
> 
> 
> Rob Jones

zfs list -t snapshot and then zfs destroy …

rgds,
toomas


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

Re: [OpenIndiana-discuss] NUC boot

[Toomas Soome via openindiana-discuss]

> On 5. Nov 2023, at 13:41, James  wrote:
> 
> On 31/10/2023 09:38, Toomas Soome wrote:
> 
> Good morning,
> 
>> Could you try this image: http://84.50.115.54/OI-hipster-gui-20231027.usb
> 
> It gets past the previous hurdle.  Thank you for whatever tweak this involved.

The problem is/was that the search for media was done before rebuilding device 
tree - so the disk device nodes were missing from /dev tree. So I did add one 
echo and devfsadm:)

> 
> Now the "however".  It fails to open a graphical login screen.   Does this 
> mean it is without graphics at all?  Would a text install and then "pkg 
> install mate_install" make any difference?


Graphics is probably hard one - sure you can go without graphics. But if there 
is no driver for specific card and if framebuffer/VBE driver will not work, 
there will be no graphics. I have no information about anyone working on 
drivers.

rgds,
toomas

> 
> This is not my machine and if this never works it is not a tragedy but 
> solving this now could help others in future.
> 
> My apologies for using screen pictures.  "tip hardwire" is my preference.
> 
> 
> James.
> <1.jpeg><2.jpeg>___
> 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] NUC boot

[Toomas Soome via openindiana-discuss]

> On 31. Oct 2023, at 11:10, James via openindiana-discuss 
>  wrote:
> 
> On 30/10/2023 15:09, Till Wegmüller wrote:
>> Then it's indeed the USB Key which is not found by the kernel, but found
>> by loader.
>> 
>> Can you try out the back ports where the keyboard is currently plugged
>> in? My NUC has a problem with the USB in early boot but they come online
>> eventually.
> 
> I have tried all 4 external ports.  I was wrong, they are all USB3 so I have 
> not tried on USB2.  3 are blue indicating USB3 and I assumed the other was 
> not.  The other is yellow because it is an always-on special charging port.  
> The remaining ports are controlled by the BIOS and will need power in sleep 
> states if the keyboard is to wake it up.  I have switched it to off in the 
> BIOS, no difference to boot.
> 
> Checking the specification I see all 4 external ports are USB3 and there are 
> 2 internal USB2 available via a header, not that I can clearly identify them 
> and I would need a cable connector.
> 
> 
> ...tribblix boots.
> 


Could you try this image: http://84.50.115.54/OI-hipster-gui-20231027.usb  

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

Re: [OpenIndiana-discuss] NUC boot

[Toomas Soome via openindiana-discuss]

> On 30. Oct 2023, at 12:06, James via openindiana-discuss 
>  wrote:
> 
> On 30/10/2023 09:48, Toomas Soome wrote:
> 
>> are those sdhost0 messages also present with omnios?
> 
> Yes, however it then scans for media and finds.  See image.

What is difference there is ‘Configuring devices’ line which is present with 
omnios, but missing with OI. It means that OI boot is just missing the device 
nodes to scan.

> 
>> The problem with OI install media is that the program to discover removable 
>> media is somewhat fragile and if it will fail, the install media mount will 
>> fail and everything else with it…
> 
> The silly thing is it has already read the USB and opened a text console on 
> the screen to show me that it can read the USB.  Oh dear!
> 

The kernel and “miniroot”  — thats what the boot_archive actually is are loaded 
by boot loader and boot loader is using firmware functions to do that (BIOS 
INT13 or UEFI Block IO). But once we start the kernel, we depend on OS drivers 
and features and at this stage, there is a problem with those.

rgds,
toomas



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

Re: [OpenIndiana-discuss] NUC boot

[Toomas Soome via openindiana-discuss]

> On 30. Oct 2023, at 11:22, James via openindiana-discuss 
>  wrote:
> 
> On 30/10/2023 00:55, John D Groenveld wrote:
>> In message , James writes:
>>> I am playing with an Intel NUC 7PJYH3 [1], J5005 CPU, 16GB RAM.
>>> Openindiana boot from USB fails, text install or live, transcript from
>>> screen grab:
>> 
>> Try an external CDROM drive if you have a free USB port.
> 
> I do not have one.  I will ask around but it might take time to find one and 
> it will next weekend for playtime.
> 
> I tried USB2 and USB3 ports, same result.
> 
> Thank you!
> James.
> 

are those sdhost0 messages also present with omnios?

The problem with OI install media is that the program to discover removable 
media is somewhat fragile and if it will fail, the install media mount will 
fail and everything else with it…  to diagnose and fix it, one must first build 
usb (cd) media, where console login will not depend on install media and you 
get console login. That is, everything needed to get console login, must be 
included on boot_archive.

what you can try to do is to boot with -r (boot -r or boot options menu and 
select reconfigure). 

rgds,
toomas




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

Re: [OpenIndiana-discuss] SMB NFS not sure where to go

[Toomas Soome via openindiana-discuss]

> On 1. Oct 2023, at 15:32, Michelle  wrote:
> 
> http://www.msknight.com/files/capture

Wireshark is suggesting this file is damaged or corrupt. size is 63805 bytes.

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

Re: [OpenIndiana-discuss] SMB NFS not sure where to go

[Toomas Soome via openindiana-discuss]

> On 25. Sep 2023, at 10:29, Michelle  wrote:
> 
> Apologies for the delay. Chores last night and just about to start
> work.
> 
> Previously I had forced the version to 1.0 and then had to step up for
> some reason. I now don't specify a version on the mount and both
> servers connect on 3.1.1
> 
> I think that the current problem was actually causing me to think that
> the version number was the problem... until I'd exhausted all
> versions... but given that experience, I doubt that forcing version
> numbers will help here.
> 


ok, well, this output means, your server is running defaults, and I was asking 
about this because you had this message about 0xFE - not sure if that may or 
may not have any impact on actual session. It may just be some sort of 
informational message to confuse poor users;)

Now, the actual error is concerning locking, I assume you have nbmand=on on 
that share, but it wont hurt to check it. Otherwise we would need network 
packet trace from the moment this error is happening, so we could check what 
request-response information is being passed.

Packet trace could be saved with snoop -O prefix:count:size host hostname and 
port 445, but the tricky part there is to set number of snoop output files + 
size and stopping the snoop to make sure the error moment is actually present 
in recorded file(s). So you want to prepare the conditions, then start snoop, 
re-create the error and stop snoop. 

rgds,
toomas


> root@jaguar:~# sharectl get smb
> system_comment=
> max_workers=1024
> netbios_enable=false
> netbios_scope=
> lmauth_level=4
> keep_alive=0
> wins_server_1=
> wins_server_2=
> wins_exclude=
> signing_enabled=true
> signing_required=true
> restrict_anonymous=false
> pdc=
> ads_site=
> ddns_enable=false
> autohome_map=/etc
> ipv6_enable=false
> print_enable=false
> traverse_mounts=true
> map=
> unmap=
> disposition=
> min_protocol=
> max_protocol=
> encrypt=disabled
> encrypt_ciphers=
> bypass_traverse_checking=true
> oplock_enable=true
> short_names=false
> 
> 
> 
> 
> 
> On Sun, 2023-09-24 at 23:10 +0300, Toomas Soome via openindiana-discuss
> wrote:
>> 
>> Could you paste: 'sharectl get smb’. The ‘unknown response type 0xfe’
>> is hinting that your client is expecting 0xFF there, and you probably
>> need to set server to default to older SMB version.
>> 
>> rgds,
>> toomas 
>> 
>> 
>>> On 24. Sep 2023, at 22:37, Toomas Soome via openindiana-discuss
>>>  wrote:
>>> 
>>>> 
>>>> On 24. Sep 2023, at 22:34, Michelle
>>>> mailto:miche...@msknight.com> 
>>>> <mailto:miche...@msknight.com>> wrote:
>>>> 
>>>> I just updated all packages and tested again...
>>>> 
>>>> Sep 24 20:31:37 mich-desktop kernel: [311047.112078] CIFS: VFS:
>>>> \\192.168.0.2 RFC 1002 unknown response type 0xfe
>>>> Sep 24 20:31:37 mich-desktop kernel: [311047.112114] CIFS: VFS:
>>>> Push
>>>> locks rc = -22
>>>> 
>>>> I'm at the end. Nowhere else to go.
>>>> 
>>>> Michelle.
>>> 
>>> on OI, what you get from 'pkg update -nv’ ? 
>>> 
>>> rgds,
>>> toomas
>>> 
>>>> 
>>>> On Sun, 2023-09-24 at 20:45 +0300, Toomas Soome via openindiana-
>>>> discuss
>>>> wrote:
>>>>> Ou that is sad that hear. Btw, what is the oi build you are
>>>>> using on
>>>>> that server?
>>>>> 
>>>>> Sent from my iPhone
>>>>> 
>>>>>> On 24. Sep 2023, at 17:34, Michelle 
>>>>>> wrote:
>>>>>> 
>>>>>> I would like to give my thanks to all who have run and
>>>>>> maintained
>>>>>> OpenIndiana for the many years it has been available.
>>>>>> 
>>>>>> I have been using it since big red took the reins of Sun and
>>>>>> changed
>>>>>> the license of Open Solaris, as it gave me access to ZFS; a
>>>>>> product
>>>>>> that has made a big difference in my personal computing life.
>>>>>> 
>>>>>> The community has been welcoming and patient with me despite
>>>>>> my
>>>>>> novice
>>>>>> questions. I just wish I had the skills and time to be able
>>>>>> to
>>>>>> contribute to the project but my job, my caring duties and
>>>>>> looking
>>>>>

Re: [OpenIndiana-discuss] SMB NFS not sure where to go

[Toomas Soome via openindiana-discuss]

Could you paste: 'sharectl get smb’. The ‘unknown response type 0xfe’ is 
hinting that your client is expecting 0xFF there, and you probably need to set 
server to default to older SMB version.

rgds,
toomas 


> On 24. Sep 2023, at 22:37, Toomas Soome via openindiana-discuss 
>  wrote:
> 
>> 
>> On 24. Sep 2023, at 22:34, Michelle > <mailto:miche...@msknight.com>> wrote:
>> 
>> I just updated all packages and tested again...
>> 
>> Sep 24 20:31:37 mich-desktop kernel: [311047.112078] CIFS: VFS:
>> \\192.168.0.2 RFC 1002 unknown response type 0xfe
>> Sep 24 20:31:37 mich-desktop kernel: [311047.112114] CIFS: VFS: Push
>> locks rc = -22
>> 
>> I'm at the end. Nowhere else to go.
>> 
>> Michelle.
> 
> on OI, what you get from 'pkg update -nv’ ? 
> 
> rgds,
> toomas
> 
>> 
>> On Sun, 2023-09-24 at 20:45 +0300, Toomas Soome via openindiana-discuss
>> wrote:
>>> Ou that is sad that hear. Btw, what is the oi build you are using on
>>> that server?
>>> 
>>> Sent from my iPhone
>>> 
>>>> On 24. Sep 2023, at 17:34, Michelle  wrote:
>>>> 
>>>> I would like to give my thanks to all who have run and maintained
>>>> OpenIndiana for the many years it has been available.
>>>> 
>>>> I have been using it since big red took the reins of Sun and
>>>> changed
>>>> the license of Open Solaris, as it gave me access to ZFS; a product
>>>> that has made a big difference in my personal computing life.
>>>> 
>>>> The community has been welcoming and patient with me despite my
>>>> novice
>>>> questions. I just wish I had the skills and time to be able to
>>>> contribute to the project but my job, my caring duties and looking
>>>> after a home have left me with little personal time... especially
>>>> in
>>>> this last few years.
>>>> 
>>>> Unfortunately this latest issue with CIFS/SMB has been quite a
>>>> disruption and with little way to make progress, I’ve determined
>>>> that
>>>> as the problems have persisted despite changing the client from
>>>> Mint to
>>>> Ubuntu Cinnamon, I now have to change server platform. I’ll be
>>>> replacing my OI servers with Debian over the coming weeks.
>>>> 
>>>> Thank you all for your patience and help over the years.
>>>> 
>>>> Michelle.
>>>> 
>>>>> On Tue, 2023-09-19 at 20:54 +0100, Michelle wrote:
>>>>> OK, I've now upgraded the client to Ubuntu Cinnamon 22.04
>>>>> 
>>>>> Accessing the text file on the OI share via BlueFish this time,
>>>>> and
>>>>> making changes and saving, I get (in syslog)...
>>>>> 
>>>>> Sep 19 20:49:47 mich-desktop kernel: [13839.060593] CIFS: VFS:
>>>>> \\192.168.0.2 RFC 1002 unknown response type 0xfe
>>>>> Sep 19 20:49:47 mich-desktop kernel: [13839.060714] CIFS: VFS:
>>>>> Push
>>>>> locks rc = -22
>>>>> 
>>>>> Same behaviour as before when using xed on Mint. If I delete and
>>>>> then
>>>>> save, it works. And if I attempt to rename a file that's in use
>>>>> (eg.
>>>>> a
>>>>> video) then I get resource unavailable.
>>>>> 
>>>>> I have no realistic option now other than to conclude that it's
>>>>> the
>>>>> OpenIndiana side of things.
>>>>> 
>>>>> I'd be grateful for guidance on whatever I need to file a bug
>>>>> report
>>>>> please.
>>>>> 
>>>>> 
>>>>> 
>>>>>> On Mon, 2023-08-07 at 22:54 +0100, Michelle wrote:
>>>>>> Apparmor is, indeed running, so I created a profile and put it
>>>>>> to
>>>>>> complain mode... noting that Libre Office is also in complain
>>>>>> mode
>>>>>> already.
>>>>>> 
>>>>>> However, xed still fails with the same issue. It is,
>>>>>> apparently,
>>>>>> writing a temporary file and presumably failing... the same way
>>>>>> that
>>>>>> copying a file from the local machine to the share is
>>>>>> failing...
>>>>>> 
>>>>>> ... copying the file to a temporary .

Re: [OpenIndiana-discuss] SMB NFS not sure where to go

[Toomas Soome via openindiana-discuss]

> On 24. Sep 2023, at 22:34, Michelle  wrote:
> 
> I just updated all packages and tested again...
> 
> Sep 24 20:31:37 mich-desktop kernel: [311047.112078] CIFS: VFS:
> \\192.168.0.2 RFC 1002 unknown response type 0xfe
> Sep 24 20:31:37 mich-desktop kernel: [311047.112114] CIFS: VFS: Push
> locks rc = -22
> 
> I'm at the end. Nowhere else to go.
> 
> Michelle.

on OI, what you get from 'pkg update -nv’ ? 

rgds,
toomas

> 
> On Sun, 2023-09-24 at 20:45 +0300, Toomas Soome via openindiana-discuss
> wrote:
>> Ou that is sad that hear. Btw, what is the oi build you are using on
>> that server?
>> 
>> Sent from my iPhone
>> 
>>> On 24. Sep 2023, at 17:34, Michelle  wrote:
>>> 
>>> I would like to give my thanks to all who have run and maintained
>>> OpenIndiana for the many years it has been available.
>>> 
>>> I have been using it since big red took the reins of Sun and
>>> changed
>>> the license of Open Solaris, as it gave me access to ZFS; a product
>>> that has made a big difference in my personal computing life.
>>> 
>>> The community has been welcoming and patient with me despite my
>>> novice
>>> questions. I just wish I had the skills and time to be able to
>>> contribute to the project but my job, my caring duties and looking
>>> after a home have left me with little personal time... especially
>>> in
>>> this last few years.
>>> 
>>> Unfortunately this latest issue with CIFS/SMB has been quite a
>>> disruption and with little way to make progress, I’ve determined
>>> that
>>> as the problems have persisted despite changing the client from
>>> Mint to
>>> Ubuntu Cinnamon, I now have to change server platform. I’ll be
>>> replacing my OI servers with Debian over the coming weeks.
>>> 
>>> Thank you all for your patience and help over the years.
>>> 
>>> Michelle.
>>> 
>>>> On Tue, 2023-09-19 at 20:54 +0100, Michelle wrote:
>>>> OK, I've now upgraded the client to Ubuntu Cinnamon 22.04
>>>> 
>>>> Accessing the text file on the OI share via BlueFish this time,
>>>> and
>>>> making changes and saving, I get (in syslog)...
>>>> 
>>>> Sep 19 20:49:47 mich-desktop kernel: [13839.060593] CIFS: VFS:
>>>> \\192.168.0.2 RFC 1002 unknown response type 0xfe
>>>> Sep 19 20:49:47 mich-desktop kernel: [13839.060714] CIFS: VFS:
>>>> Push
>>>> locks rc = -22
>>>> 
>>>> Same behaviour as before when using xed on Mint. If I delete and
>>>> then
>>>> save, it works. And if I attempt to rename a file that's in use
>>>> (eg.
>>>> a
>>>> video) then I get resource unavailable.
>>>> 
>>>> I have no realistic option now other than to conclude that it's
>>>> the
>>>> OpenIndiana side of things.
>>>> 
>>>> I'd be grateful for guidance on whatever I need to file a bug
>>>> report
>>>> please.
>>>> 
>>>> 
>>>> 
>>>>> On Mon, 2023-08-07 at 22:54 +0100, Michelle wrote:
>>>>> Apparmor is, indeed running, so I created a profile and put it
>>>>> to
>>>>> complain mode... noting that Libre Office is also in complain
>>>>> mode
>>>>> already.
>>>>> 
>>>>> However, xed still fails with the same issue. It is,
>>>>> apparently,
>>>>> writing a temporary file and presumably failing... the same way
>>>>> that
>>>>> copying a file from the local machine to the share is
>>>>> failing...
>>>>> 
>>>>> ... copying the file to a temporary .gooutputstream file but
>>>>> then
>>>>> somehow failing to delete the file that is about to be
>>>>> replaced.
>>>>> 
>>>>> Michelle.
>>>>> 
>>>>> On Mon, 2023-08-07 at 22:24 +0100, Michelle wrote:
>>>>>> I'm starting to believe that upgrading Linux has installed
>>>>>> apparmor
>>>>>> ...
>>>>>> and it's likely that apparmor is now getting in the way of
>>>>>> various
>>>>>> applications.
>>>>>> 
>>>>>> I hate apparmor. I mean, I understand why it's there and the
>>>>>> theory
>>

Re: [OpenIndiana-discuss] SMB NFS not sure where to go

[Toomas Soome via openindiana-discuss]

Ou that is sad that hear. Btw, what is the oi build you are using on that 
server?

Sent from my iPhone

> On 24. Sep 2023, at 17:34, Michelle  wrote:
> 
> I would like to give my thanks to all who have run and maintained
> OpenIndiana for the many years it has been available.
> 
> I have been using it since big red took the reins of Sun and changed
> the license of Open Solaris, as it gave me access to ZFS; a product
> that has made a big difference in my personal computing life.
> 
> The community has been welcoming and patient with me despite my novice
> questions. I just wish I had the skills and time to be able to
> contribute to the project but my job, my caring duties and looking
> after a home have left me with little personal time... especially in
> this last few years.
> 
> Unfortunately this latest issue with CIFS/SMB has been quite a
> disruption and with little way to make progress, I’ve determined that
> as the problems have persisted despite changing the client from Mint to
> Ubuntu Cinnamon, I now have to change server platform. I’ll be
> replacing my OI servers with Debian over the coming weeks.
> 
> Thank you all for your patience and help over the years.
> 
> Michelle.
> 
>> On Tue, 2023-09-19 at 20:54 +0100, Michelle wrote:
>> OK, I've now upgraded the client to Ubuntu Cinnamon 22.04
>> 
>> Accessing the text file on the OI share via BlueFish this time, and
>> making changes and saving, I get (in syslog)...
>> 
>> Sep 19 20:49:47 mich-desktop kernel: [13839.060593] CIFS: VFS:
>> \\192.168.0.2 RFC 1002 unknown response type 0xfe
>> Sep 19 20:49:47 mich-desktop kernel: [13839.060714] CIFS: VFS: Push
>> locks rc = -22
>> 
>> Same behaviour as before when using xed on Mint. If I delete and then
>> save, it works. And if I attempt to rename a file that's in use (eg.
>> a
>> video) then I get resource unavailable.
>> 
>> I have no realistic option now other than to conclude that it's the
>> OpenIndiana side of things.
>> 
>> I'd be grateful for guidance on whatever I need to file a bug report
>> please.
>> 
>> 
>> 
>>> On Mon, 2023-08-07 at 22:54 +0100, Michelle wrote:
>>> Apparmor is, indeed running, so I created a profile and put it to
>>> complain mode... noting that Libre Office is also in complain mode
>>> already.
>>> 
>>> However, xed still fails with the same issue. It is, apparently,
>>> writing a temporary file and presumably failing... the same way
>>> that
>>> copying a file from the local machine to the share is failing...
>>> 
>>> ... copying the file to a temporary .gooutputstream file but then
>>> somehow failing to delete the file that is about to be replaced.
>>> 
>>> Michelle.
>>> 
>>> On Mon, 2023-08-07 at 22:24 +0100, Michelle wrote:
>>>> I'm starting to believe that upgrading Linux has installed
>>>> apparmor
>>>> ...
>>>> and it's likely that apparmor is now getting in the way of
>>>> various
>>>> applications.
>>>> 
>>>> I hate apparmor. I mean, I understand why it's there and the
>>>> theory
>>>> of
>>>> what it does, but I've never had much luck controlling it.
>>>> 
>>>> I need to read up and find how to tell apparmor to stop
>>>> controlling
>>>> xed
>>>> and nemo, and see if that works.
>>>> 
>>>> Michelle.
>>>> 
>>>> On Mon, 2023-08-07 at 22:20 +0100, Michelle wrote:
>>>>> I've translated up to the same cifs-utils version up to Mint
>>>>> 21.2
>>>>> Victoria kernel 6.2.0-26 which is as far as I can go. I have
>>>>> also
>>>>> turned on nbmand on, on the servers.
>>>>> 
>>>>> Oddly enough, Libre Office Writer can open and save the file on
>>>>> the
>>>>> share. "Text Editor" otherwise known as xed 3.4.3 ... can't. It
>>>>> reports
>>>>> the resource  unavailable error.
>>>>> 
>>>>> Copying a file from network share to local machine using Nemo
>>>>> 5.8.4
>>>>> successfully copies the file, but the progress bar stops at
>>>>> 50%.
>>>>> I've
>>>>> still got the reports of the push locks and ...
>>>>> Aug  7 22:14:23 main-desktop kernel: [ 5181.959778] CIFS: VFS:
>>>>> \\192.168.0.4 RFC 1002 unknown response t

Re: [OpenIndiana-discuss] zpool status rpool not consistent with diskinfo

[Toomas Soome via openindiana-discuss]

Ok, so the bug is that pool labels are not updated on devid change. Please file 
report to illumos.org/issues

For workaround, offline + online on disk should do to trigger label update.

> On 20. Sep 2023, at 16:38, Stephan Althaus  
> wrote:
> 
> On 9/20/23 15:23, Udo Grabowski (IMK) wrote:
>>> 
>>> Hello!
>>> 
>>> Thanks for the hints, but no change with
>>> 
>>> touch /reconfigure
>>> 
>>> zpool reopen
>>> 
>>> rm /etc/zfs/zpool.cache
>>> 
>>> 
>>> should i try to "zpool offline -t c3t2d0s0" one device and reboot?
>> 
>> 
>> It could also be that the label entry is not updated.
>> zdb -l /dev/dsk/cxtyd0s0 should show the correct one
>> at least in the first label. I once had such a case,
>> and had to boot into an older openindiana version to
>> get that fixed, but that depends of course on the
>> available and activated pool features.
>> 
>> -- 
>> Dr.Udo Grabowski   Inst.f.Meteorology & Climate Research IMK-ASF-SAT
>> http://www.imk-asf.kit.edu/english/sat.php
>> KIT - Karlsruhe Institute of Technology http://www.kit.edu
>> Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026
>> 
> Hello!
> 
> I can confirm that the zfs label have not been updated.
> 
> I don't know if it a 'problem' as the root pool is ONLINE,
> but if you use the devices names stated in the zpool status,
> other commands may fail (just like zdb -l ) because the device names are 
> wrong :-/
> 
> However, the possible solution is to boot from live media an import/export 
> the root pool...
> 
> 
> Regards,
> Stephan
> 
> ___
> 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] zpool status rpool not consistent with diskinfo

[Toomas Soome via openindiana-discuss]

You can try 'zpool reopen’, if that will not help, remove /etc/zfs/zpool.cache. 
There is some issue that information in zpool.cache is not updated…

rgds,
toomas

> On 20. Sep 2023, at 14:14, Stephan Althaus  
> wrote:
> 
> Hello!
> 
> I swapped 2 of 3 root-pool drives (after power off)
> to different controllers, (with power-off-saving battery pack)
> and now the device names are inconsistent - the device names in the pool 
> context have not been not updated.
> 
> Boot message was shown: "NOTICE: Performing full ZFS device scan!"
> 
> Messages regarding the move where also in the logs:
> 
> messages:923126:Sep 20 09:24:21 oi genunix: [ID 176336 kern.notice] devid 
> register: devid for 
> /pci@0,0/pci8086,c05@1,1/pci1028,1f1c@0/iport@20/disk@p5,0 does not match. 
> stored: 
> id1,sd@TATA_Patriot_P220_1TBP220HBCB230710002657, 
> new: 
> id1,sd@TATA_EMTEC_X150_480GB511200729140001240__.
> messages:923339:Sep 20 09:24:32 oi zfs: [ID 101897 kern.notice] NOTICE: 
> vdev_disk_open /dev/dsk/c3t2d0s0: update devid from 
> 'id1,sd@SATA_EMTEC_X150_480GB__511200729140001240/a' to 
> 'id1,sd@TATA_EMTEC_X150_480GB511200729140001240__/a'
> 
> ... but not for the "SCSI" ones (sata disks on SAS controller LSI JOBD, 
> driver mpt_sas i believe)
> 
> Pool status is ok.
> 
> Is there a command to update this info?
> 
> Reboot did not change the drive info.
> 
> Importing/exporting the rpool via OI-USB-live-boot-stick would help, do i 
> really have to do so ?
> 
> 
> # diskinfo
> TYPEDISKVID  PID SIZE  RMV SSD
> SCSIc7t5d0  EMTECX150 480GB447.13 GiB   no  
> yes
> SCSIc8t4d0  Patriot  P220 1TB  953.87 GiB   no  
> yes
> SATAc3t3d0  EMTECX150 480GB447.13 GiB   no  
> yes
> 
> $ zpool status
>   pool: rpool1
>  state: ONLINE
>   scan: resilvered 381G in 0 days 00:51:40 with 0 errors on Tue Sep 12 
> 16:36:55 2023
> config:
> 
> NAME  STATE READ WRITE CKSUM
> rpool1ONLINE   0 0 0
>   mirror-0ONLINE   0 0 0
> c3t2d0s0  ONLINE   0 0 0
> c3t3d0s0  ONLINE   0 0 0
> c7t5d0s0  ONLINE   0 0 0
> 
> 
> Regards,
> 
> Stephan
> 
> 
> 
> ___
> 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] SMB NFS not sure where to go

[Toomas Soome via openindiana-discuss]

hi!

I just did test with ubuntu 22.04.01, cifs-utils:
2:6.14-1ubuntu0.1

And seems to behave as expected. My share has nbmand=on, however.

rgds,
toomas

> On 7. Aug 2023, at 19:07, Michelle  wrote:
> 
> After that updating, I now have a problem copying files to and from the
> share and the client.
> 
> Firstly... using command line to go onto the share and use Nano to edit
> a text file... no problem.
> 
> Using Nano to browse to the mounted share, open in Text Editor, edit
> and then save... it gives "resource unavailable."
> 
> When using Nemo to copy from the share to the local Linux machine, it
> copies the small test file successfully, but hangs on the "progress
> bar" which never closes. I have to kill Nemo.
> 
> When using Nemo to copy from the local Linux machine to the server
> share, it copies up the file using the temp name, but can't actually
> replace the file.
> 
> If I manually delete the file from the server, and then copy the file
> up to the share... it works.
> 
> All the time, this...
> Aug  7 16:54:16 main-desktop kernel: [  772.668870] CIFS: VFS:
> \\192.168.0.2 RFC 1002 unknown response type 0xfe
> Aug  7 16:54:16 main-desktop kernel: [  772.668915] CIFS: VFS: Push
> locks rc = -22
> ... is prevalent in the client side syslog when this is happening.
> 
> There was a previous post in mid 2022 about a bug on Linux and that the
> workaround was to force vers=2.0 but I've tried that and there's no
> change in the behaviour.
> 
> From what I've read, my nbmand property is best set to off, which is
> what it is. Or do I have that wrong?
> 
> I'm now at a loss as to where to continue looking.
> 
> OpenIndiana Hipster 2023.05 (powered by illumos)
> 
> Distributor ID:   Linuxmint
> Description:  Linux Mint 21
> Release:  21
> Codename: vanessa
> 
> mount from util-linux 2.37.2 (libmount 2.37.2: selinux, smack, btrfs,
> verity, namespaces, assert, debug)
> 
> 
> 
> On Mon, 2023-08-07 at 10:08 +0100, Michelle wrote:
>> nbmand is off on both servers.
>> 
>> Michelle.
>> 
>> On Mon, 2023-08-07 at 11:54 +0300, Toomas Soome wrote:
>>> 
>>> 
>>>> On 7. Aug 2023, at 11:38, Michelle  wrote:
>>>> 
>>>> I did a quick test after updating and rebooting both servers.
>>>> 
>>>> Copying files from one of the servers (panther - 0.4) to another
>>>> server
>>>> (jaguar - 0.2) via the Linux client ... resulted in the following
>>>> in
>>>> the log on the client, however, there was nothing in the syslog
>>>> on
>>>> either of the servers.
>>>> 
>>>> There does seem to be a mention of a patch in Linux SMB as of
>>>> late
>>>> June
>>>> this year, but having said that, there seem to be a number of
>>>> patches
>>>> throughout the years regarding this, but I'm unable to get a grip
>>>> with
>>>> it.
>>>> 
>>>> Aug  7 09:28:35 main-desktop systemd[1109]: Starting GNOME
>>>> Terminal
>>>> Server...
>>>> Aug  7 09:28:35 main-desktop dbus-daemon[1136]: [session uid=1101
>>>> pid=1136] Successfully activated service 'org.gnome.Terminal'
>>>> Aug  7 09:28:35 main-desktop systemd[1109]: Started GNOME
>>>> Terminal
>>>> Server.
>>>> Aug  7 09:28:35 main-desktop systemd[1109]: Started VTE child
>>>> process
>>>> 1644922 launched by gnome-terminal-server process 1644897.
>>>> Aug  7 09:30:01 main-desktop CRON[1645001]: (root) CMD ([ -x
>>>> /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then
>>>> /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
>>>> Aug  7 09:30:10 main-desktop kernel: [2945189.248744] CIFS: VFS:
>>>> \\192.168.0.4 RFC 1002 unknown response type 0xfe
>>> 
>>> I’m not really sure where is this coming from, probably want to
>>> check
>>> netowk packet with tshark/wireshark.
>>> 
>>>> Aug  7 09:30:10 main-desktop kernel: [2945189.248788] CIFS: VFS:
>>>> Push
>>>> locks rc = -22
>>> 
>>> Do you have zfs nbmand property set on?
>>> 
>>> rgds,
>>> toomas
>>> 
>>>> Aug  7 09:30:20 main-desktop kernel: [2945198.711222] CIFS: VFS:
>>>> \\192.168.0.4 RFC 1002 unknown response type 0xfe
>>>> Aug  7 09:30:25 main-desktop kernel: [2945204.406488] CIFS: VFS:
>>>> \\192.168.0.4 RFC 1002 unknown response typ

Re: [OpenIndiana-discuss] SMB NFS not sure where to go

[Toomas Soome via openindiana-discuss]

> On 7. Aug 2023, at 11:38, Michelle  wrote:
> 
> I did a quick test after updating and rebooting both servers.
> 
> Copying files from one of the servers (panther - 0.4) to another server
> (jaguar - 0.2) via the Linux client ... resulted in the following in
> the log on the client, however, there was nothing in the syslog on
> either of the servers.
> 
> There does seem to be a mention of a patch in Linux SMB as of late June
> this year, but having said that, there seem to be a number of patches
> throughout the years regarding this, but I'm unable to get a grip with
> it.
> 
> Aug  7 09:28:35 main-desktop systemd[1109]: Starting GNOME Terminal
> Server...
> Aug  7 09:28:35 main-desktop dbus-daemon[1136]: [session uid=1101
> pid=1136] Successfully activated service 'org.gnome.Terminal'
> Aug  7 09:28:35 main-desktop systemd[1109]: Started GNOME Terminal
> Server.
> Aug  7 09:28:35 main-desktop systemd[1109]: Started VTE child process
> 1644922 launched by gnome-terminal-server process 1644897.
> Aug  7 09:30:01 main-desktop CRON[1645001]: (root) CMD ([ -x
> /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then
> /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
> Aug  7 09:30:10 main-desktop kernel: [2945189.248744] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe

I’m not really sure where is this coming from, probably want to check netowk 
packet with tshark/wireshark.

> Aug  7 09:30:10 main-desktop kernel: [2945189.248788] CIFS: VFS: Push
> locks rc = -22

Do you have zfs nbmand property set on?

rgds,
toomas

> Aug  7 09:30:20 main-desktop kernel: [2945198.711222] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:30:25 main-desktop kernel: [2945204.406488] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:30:28 main-desktop kernel: [2945206.802407] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:30:30 main-desktop kernel: [2945208.649958] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:30:32 main-desktop kernel: [2945210.907929] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:30:33 main-desktop kernel: [2945212.056828] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:30:36 main-desktop kernel: [2945214.981583] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:30:37 main-desktop kernel: [2945216.163547] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:30:37 main-desktop systemd[1109]: Started VTE child process
> 1645538 launched by gnome-terminal-server process 1644897.
> Aug  7 09:30:39 main-desktop kernel: [2945218.019954] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:30:41 main-desktop kernel: [2945219.860681] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:30:41 main-desktop kernel: [2945220.282600] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:30:41 main-desktop kernel: [2945220.282649] CIFS: VFS: Push
> locks rc = -22
> Aug  7 09:30:44 main-desktop kernel: [2945222.937137] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:30:44 main-desktop kernel: [2945222.937168] CIFS: VFS: Push
> locks rc = -22
> Aug  7 09:30:48 main-desktop kernel: [2945227.269625] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:30:54 main-desktop kernel: [2945233.354499] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:30:57 main-desktop kernel: [2945235.676076] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:31:02 main-desktop kernel: [2945241.140574] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:31:06 main-desktop kernel: [2945244.760306] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:31:06 main-desktop systemd[1]: Started Run anacron jobs.
> Aug  7 09:31:06 main-desktop anacron[1645804]: Anacron 2.3 started on
> 2023-08-07
> Aug  7 09:31:06 main-desktop anacron[1645804]: Normal exit (0 jobs run)
> Aug  7 09:31:06 main-desktop systemd[1]: anacron.service: Deactivated
> successfully.
> Aug  7 09:31:08 main-desktop kernel: [2945247.431492] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:31:14 main-desktop kernel: [2945253.154480] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> Aug  7 09:31:14 main-desktop kernel: [2945253.255401] CIFS: VFS:
> \\192.168.0.4 RFC 1002 unknown response type 0xfe
> e
> 
> 
> On Mon, 2023-08-07 at 11:16 +0300, Toomas Soome wrote:
>> 
>> 
>>> On 7. Aug 2023, at 11:12, Michelle  wrote

Re: [OpenIndiana-discuss] SMB NFS not sure where to go

[Toomas Soome via openindiana-discuss]

> On 7. Aug 2023, at 11:12, Michelle  wrote:
> 
> Hi Toomas,
> 
> Thanks for the feedback.
> 
> I'll update both servers and run more tests.
> 
> Michelle.

For SMB, uid/gid sync is not important, you will access the share with 
authenticated user (or guest).

With NFS auth sys mechanism, the usernames and uid/gid need to match, and your 
nfsv4_domain should match with client system  setting (or your access will be 
mapped to user ’nobody’).

rgds,
toomas

> 
> On Mon, 2023-08-07 at 10:56 +0300, Toomas Soome via openindiana-discuss
> wrote:
>> 
>> 
>>> On 7. Aug 2023, at 09:21, Michelle  wrote:
>>> 
>>> OI server is at...
>>> OpenIndiana Hipster 2022.10 (powered by illumos)
>> 
>> 
>> Please run ‘pkg update’. We have had many updates since 2022.
>> 
>>> 
>>> Client is Linux Mint...
>>> Distributor ID: Linuxmint
>>> Description:Linux Mint 21
>>> Release:21
>>> Codename:   vanessa
>>> 
>>> I'm continuing to have problems with SMB shares. Even mounting with
>>> no
>>> cache...
>>> sudo mount //192.168.0.2/jaguar /mnt/jaguar -o
>>> username=michelle,password=password,file_mode=0777,dir_mode=0777,ca
>>> che=
>>> none
>>> ...
>>> //192.168.0.2/jaguar on /mnt/jaguar type cifs
>>> (rw,relatime,vers=3.0,cache=none,username=michelle,uid=0,noforceuid
>>> ,gid
>>> =0,noforcegid,addr=192.168.0.2,file_mode=0777,dir_mode=0777,soft,no
>>> unix
>>> ,mapposix,rsize=65536,wsize=65536,bsize=1048576,echo_interval=60,ac
>>> time
>>> o=1)
>>> 
>>> (for info, the UID of michelle is the same on client and server)
>>> ...I'm getting, "resource unavailable," on various read-
>>> write/rename
>>> operations including deleting files. Say, sixty files, three will
>>> fail
>>> to delete giving "resource unavailable" and then I have to delete
>>> them
>>> again, and they'll go.
>>> 
>>> When the Linux client hits resource unavaialble, there's nothing in
>>> the
>>> Linux messages and nothing in the OI /var/adm/messages either, that
>>> gives a hint of what's going on.
>>> 
>>> Having hit a brick wall with CIFS, I'm trying to configure an NFS
>>> share
>>> against user rather than machine IP, but I'm getting nowhere.
>>> 
>>> zfs set sharenfs='rw=.:michelle' panther
>> 
>> access list used with rw does not allow to set per user access, see
>> share_nfs(8). It should interpret michelle as hostname, but I’m not
>> sure why it will complain about invalid option below.
>> 
>>> cannot set property for 'panther': 'sharenfs' cannot be set to
>>> invalid
>>> options
>>> 
>>> I'm tying myself in knots because it seems that there's "legacy"
>>> NFS,
>>> ZFS NFS with different options/restrictions and I'm not sure where
>>> to
>>> go. If I read correctly, only ZFS NFS is installed by "default" on
>>> a
>>> new OI installation, but I'm not about to start going installing
>>> stuff
>>> until I have a better idea what I'm doing.
>>> 
>>> One reason I set some shares against user permissions is to protect
>>> against ransomware. I unmount and re-mount rw when I want to write
>>> to
>>> them, hence pure hostip is a problem for me.
>>> 
>>> I don't know where I'm looking for either option.
>>> 
>>> Hence the decision to look to NFS (which I've never really had to
>>> handle before) and I'm hitting trouble there.
>>> 
>>> Grateful for thoughts and advice.
>>> 
>>> Michelle.
>>> 
>> 
>> zfs sharenfs is just one possible way to implement sharing, it is
>> more useful when you are switching pools between different machines -
>> so you would get sharing options with pool and do not have to
>> transfer /etc/dfs/dfstab between the systems.
>> 
>> For debugging, I suggest to test with command ’share’ first - make
>> sure your svc:/network/nfs/server:default is online, then use share
>> command to test the options for specific share. Once happy, you can
>> use either /etc/dfs/dfstab or zfs sharenfs (if you still do get the
>> error, please report the bug in https://www.illumos.org/issues/
>> 
>> And please do keep the system up to date, so we know what to expect -
>> we only do rolling updates and we are not patching old versions.
>> 
>> rgds,
>> toomas
>> 
>> ___
>> 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] SMB NFS not sure where to go

[Toomas Soome via openindiana-discuss]

> On 7. Aug 2023, at 09:21, Michelle  wrote:
> 
> OI server is at...
> OpenIndiana Hipster 2022.10 (powered by illumos)


Please run ‘pkg update’. We have had many updates since 2022.

> 
> Client is Linux Mint...
> Distributor ID:   Linuxmint
> Description:  Linux Mint 21
> Release:  21
> Codename: vanessa
> 
> I'm continuing to have problems with SMB shares. Even mounting with no
> cache...
> sudo mount //192.168.0.2/jaguar /mnt/jaguar -o
> username=michelle,password=password,file_mode=0777,dir_mode=0777,cache=
> none
> ...
> //192.168.0.2/jaguar on /mnt/jaguar type cifs
> (rw,relatime,vers=3.0,cache=none,username=michelle,uid=0,noforceuid,gid
> =0,noforcegid,addr=192.168.0.2,file_mode=0777,dir_mode=0777,soft,nounix
> ,mapposix,rsize=65536,wsize=65536,bsize=1048576,echo_interval=60,actime
> o=1)
> 
> (for info, the UID of michelle is the same on client and server)
> ...I'm getting, "resource unavailable," on various read-write/rename
> operations including deleting files. Say, sixty files, three will fail
> to delete giving "resource unavailable" and then I have to delete them
> again, and they'll go.
> 
> When the Linux client hits resource unavaialble, there's nothing in the
> Linux messages and nothing in the OI /var/adm/messages either, that
> gives a hint of what's going on.
> 
> Having hit a brick wall with CIFS, I'm trying to configure an NFS share
> against user rather than machine IP, but I'm getting nowhere.
> 
> zfs set sharenfs='rw=.:michelle' panther

access list used with rw does not allow to set per user access, see 
share_nfs(8). It should interpret michelle as hostname, but I’m not sure why it 
will complain about invalid option below.

> cannot set property for 'panther': 'sharenfs' cannot be set to invalid
> options
> 
> I'm tying myself in knots because it seems that there's "legacy" NFS,
> ZFS NFS with different options/restrictions and I'm not sure where to
> go. If I read correctly, only ZFS NFS is installed by "default" on a
> new OI installation, but I'm not about to start going installing stuff
> until I have a better idea what I'm doing.
> 
> One reason I set some shares against user permissions is to protect
> against ransomware. I unmount and re-mount rw when I want to write to
> them, hence pure hostip is a problem for me.
> 
> I don't know where I'm looking for either option.
> 
> Hence the decision to look to NFS (which I've never really had to
> handle before) and I'm hitting trouble there.
> 
> Grateful for thoughts and advice.
> 
> Michelle.
> 

zfs sharenfs is just one possible way to implement sharing, it is more useful 
when you are switching pools between different machines - so you would get 
sharing options with pool and do not have to transfer /etc/dfs/dfstab between 
the systems.

For debugging, I suggest to test with command ’share’ first - make sure your 
svc:/network/nfs/server:default is online, then use share command to test the 
options for specific share. Once happy, you can use either /etc/dfs/dfstab or 
zfs sharenfs (if you still do get the error, please report the bug in 
https://www.illumos.org/issues/

And please do keep the system up to date, so we know what to expect - we only 
do rolling updates and we are not patching old versions.

rgds,
toomas

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

Re: [OpenIndiana-discuss] pkg folder size escalated

[Toomas Soome via openindiana-discuss]

> On 18. May 2023, at 11:31, Goetz T. Fischer  wrote:
> 
> that's way too much. i have 520 packages on solaris 11.4 and that's 200mb.
> on indiana i have 388 packages but pkg is 619mb.
> 

those numbers are meaningless without checking what is inside of those files. 
Also, you need to keep in mind that illumos (openindiana) is not solaris. The 
systems are different and we are not intending to be free clone of Solaris.

rgds,
toomas


> On Thu, 18 May 2023 10:15:09 +0200, Stephan Althaus wrote:
>> and pkg update i now have 2.33G.
>> 
>> That may be normal for >1500 packages:
>> 
>> $ pkg list | wc
>>15724742  127355
>> 
>> 
>> ___
>> 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] pkg folder size escalated

[Toomas Soome via openindiana-discuss]

Set it True and then you need to install/remove some packages or run pkg 
update. 

Sent from my iPhone

> On 18. May 2023, at 10:10, Stephan Althaus  
> wrote:
> 
> On 5/18/23 09:08, Toomas Soome via openindiana-discuss wrote:
>> pkg property
> 
> $ pkg property|grep fl
> flush-content-cache-on-success False
> 
> 
> ___
> 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] pkg folder size escalated

[Toomas Soome via openindiana-discuss]

> On 18. May 2023, at 08:22, Goetz T. Fischer  wrote:
> 
> hello everyone,
> 
> after a fresh indiana installation and removing a couple of packages my 
> /var/pkg folder is more than 
> 700mb! doing comparable things with solaris 11.4 leaves me with a /var/pkg 
> size of less than 200.
> how can i clean that up safely and how can i keep it from escalating again in 
> the future?
> 
> thanks in advance for any help
> 

what does ‘pkg property’ output for flush-content-cache-on-success?

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

Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices

[Toomas Soome via openindiana-discuss]

> On 24. Mar 2023, at 10:50, Udo Grabowski (IMK)  wrote:
> 
> 
> 
> On 24/03/2023 09:43, Marc Lobelle wrote:
>> On 3/24/23 08:16, Toomas Soome via openindiana-discuss wrote:
>>> 
>>>> On 24. Mar 2023, at 07:58, Stephan Althaus 
>>>>  wrote:
>>>> 
>>>> On 3/22/23 20:56, Richard Lowe wrote:
>>>>> The challenge of answering that is you often don't know the answer
>>>>> until you see it
>>>>> 
>>>>> The ::stacks command will give you asummarized view of every kernel
>>>>> thread's stack
>>>>> the ::cpuinfo -v command will show you what the CPUs are doing now (or
>>>>> were doing, before you got into kmdb).
>>>>> 
>>>>> Both or either might have a smoking gun of some kind, but it's hard to
>>>>> predict what it might look like.
>>>>> 
>>>>> ___
>>>>> openindiana-discuss mailing list
>>>>> openindiana-discuss@openindiana.org
>>>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>>>> Hello!
>>>> 
>>>> In one of my earlier update-tests i had a problem with the first 
>>>> OI-nvidia-525 version in cooperation with Virtualbox,
>>>> so i had the idea to test this:
>>>> 
>>>> I uninstalled 'userland-incorporation' and 'entire' as prerequisite to  
>>>> install nvidia version 515,
>>>> now it boots!
>>>> 
>>>> So, nvidia in the most recent version 525 stopped the boot process. (?)
>>>> 
>>>> i checked with NVidia Solaris Driver Archive that my chipset (Quadro 
>>>> M1200) is on the supported list for this version:
>>>> https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/
>>>> 
>>>> 
>>>> How/Why should the display driver be able to interrupt the boot process ?
>>>> How/Why should the display driver be able to interrupt the boot process 
>>>> without further notice?
>>>> 
>>> That is something one can work out with debugger. But, this is binary only 
>>> driver? Built *for Oracle Solaris 11.4*? With API interfaces changed inside 
>>> Oracle Solaris? This means, the question is not “if” but “when” - it is 
>>> only question of time when such drivers become unusable for us. Without gfx 
>>> driver development, the desktop variant of illumos is dead end.
>> without desktop, it would unfortunately mean the dead of illumos. If Oracle 
>> solaris drivers become unusable shouldn't illumos move to another driver 
>> interface that is maintained ?
> 
> Maybe we wait until the cause for the problem is known before
> declaring everything dead ?
> 

It is a bit premature to declare everything dead, but, the fact is, we can not 
rely on binary only drivers forever. As soon as Oracle will decide to stop 
distributing Solaris, nvidia will have no reason to distribute those binary 
drivers.

Note, we *still* do rely on few closed binaries to distribute illumos itself.

rgds,
toomas

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

Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices

[Toomas Soome via openindiana-discuss]

> On 24. Mar 2023, at 07:58, Stephan Althaus  
> wrote:
> 
> On 3/22/23 20:56, Richard Lowe wrote:
>> The challenge of answering that is you often don't know the answer
>> until you see it
>> 
>> The ::stacks command will give you asummarized view of every kernel
>> thread's stack
>> the ::cpuinfo -v command will show you what the CPUs are doing now (or
>> were doing, before you got into kmdb).
>> 
>> Both or either might have a smoking gun of some kind, but it's hard to
>> predict what it might look like.
>> 
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> Hello!
> 
> In one of my earlier update-tests i had a problem with the first 
> OI-nvidia-525 version in cooperation with Virtualbox,
> so i had the idea to test this:
> 
> I uninstalled 'userland-incorporation' and 'entire' as prerequisite to  
> install nvidia version 515,
> now it boots!
> 
> So, nvidia in the most recent version 525 stopped the boot process. (?)
> 
> i checked with NVidia Solaris Driver Archive that my chipset (Quadro M1200) 
> is on the supported list for this version:
> https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/
> 
> 
> How/Why should the display driver be able to interrupt the boot process ?
> How/Why should the display driver be able to interrupt the boot process 
> without further notice?
> 

That is something one can work out with debugger. But, this is binary only 
driver? Built *for Oracle Solaris 11.4*? With API interfaces changed inside 
Oracle Solaris? This means, the question is not “if” but “when” - it is only 
question of time when such drivers become unusable for us. Without gfx driver 
development, the desktop variant of illumos is dead end.

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

Re: [OpenIndiana-discuss] Replacing smaller rpool SSD with bigger one - best praxis

[Toomas Soome via openindiana-discuss]

> On 8. Mar 2023, at 02:27, Bill Sommerfeld  wrote:
> 
> On 3/7/23 13:53, gea wrote:
>> I suppose a method based on mirror/clone + autoexpand will not work with 
>> different ashift.
>> A disaster backup/recovery method that should work:
>> - replicate current BE to datapool via zfs send
>>   (you can create daily recoverable backups while OI is running with this 
>> method)
> 
> If you can have all the disks cabled up at the same time, you can use the 
> '-p' option to 'beadm create' to create a BE in a different pool; I've used 
> this to move the root a few times (the root pool on one of my machines is 
> currently named "r3”).
> 

With this method, you need to keep in mind, only dataset tree from ROOT will be 
replicated. You still need to migrate/re-create other datasets like export, 
swap, dump. Also need to update dumpadm and /etc/vfstab (for swap).

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

Re: [OpenIndiana-discuss] VIM 9: lost shell (read bash) syntax

[Toomas Soome via openindiana-discuss]

> On 20. Feb 2023, at 18:05, Predrag Zecevic via openindiana-discuss 
>  wrote:
> 
> On 20.02.2023 16:53, Udo Grabowski (IMK) wrote:
>> On 20/02/2023 16:49, Udo Grabowski (IMK) wrote:
>>> On 20/02/2023 16:20, Predrag Zecevic via openindiana-discuss wrote:
 Hi all,
 
 does anyone has nice .vimrc, which still obey syntax coloring? Especially 
 for
 bash...
 
 Recently, vim was upgrade from version 8 to 9:
 
 :; pkg list *editor/vim*
 NAME (PUBLISHER) VERSIONIFO
 editor/vim 9.0.1300-2023.0.0.0i--
 editor/vim/vim-core 9.0.1300-2023.0.0.0i--
 
 Since then, bash syntax coloring is not working with neither .vimrc (old 
 one,
 and modified one). Or w/o .vimrc.
 Previously, that syntax highlighting could help a lot, when entering shell
 commands to point to the syntax error.
 
 Now, it is completely useless...
 
 Any thoughts? Anyone still uses it?
>>> 
>>> No problem here, with .vimrc
>>> 
>>> set encoding=utf-8
>>> set term=xterm-color
>>> syntax enable
>>> 
>>> everything highlights fine, even bash scripts.
>>> 
>> 
>> You may also need this (one line) :
>> autocmd Syntax * exec("set 
>> dict+=".$VIMRUNTIME."/syntax/".expand('').".vim")
>> 
> Thanks,
> 
> ---8<--
> :; cat ~/.vim/vimrc
> set encoding=utf-8
> set term=xterm-color
> syntax enable
> 
> autocmd Syntax * exec("set 
> dict+=".$VIMRUNTIME."/syntax/".expand('').".vim")
> ---8<--
> 
> and still no luck (tried from within *tmux* session and from pure bash shell).
> Same version from Ubuntu 22.04 (I had to install it from PPA repo) shows test 
> bash file properly.
> 
> So, it could be something on my machine.
> The problem is I have no clue where to start.

pkg verify vim vim-core

then check /etc/vimrc

rgds,
toomas

> 
> Regards.
>> 
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org 
>> 
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> -- 
> Predrag Zečević
> predrag.zecevic.1...@googlemail.com 
> 
> 
> 
> ___
> 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] How should a disk partition layout looks like

[Toomas Soome via openindiana-discuss]

> On 6. Jan 2023, at 12:06, Carsten Grzemba via openindiana-discuss 
>  wrote:
> 
> I have a disk installed with Openindiana and installboot shows bootloader at 
> cxt0d0s1 and has not cxt0d0p1
> The disk will not recognized by BIOS for boot but it boots if selected in 
> loader.
> 
> On other resources shows EFI boot files on cxt0d0p1.
> 
> Is p1 partition necessary for boot?
> How looks like a correct disk partitioning nowadys?
> 

sX is partition from either GPT or VTOC

p0 is whole disk
p1-p4 are MBR primary partitions and p5.. are extended.

With GPT you have MBR in absolute sector 0 and only one partition defined 
(EFI), this is “protective” MBR and meant to tell non-GPT aware partition 
programs that you have partition defined. GPT itself is on absolute sector 1 
and followed by partition array.

Classic Solaris x86 partitioning is MBR + VTOC, you are supposed to have one 
Solaris2 MBR primary partition per disk and on that partition you have VTOC. 

With zpool “whole disk” setup, you will get GPT partitioning, with s0[, s1] and 
s8 defined (GPT does not allow overlapping partitions). Depending if zpool 
create -B was used, you may or may not have efi system partition.

MBR + VTOC scheme is assuming you have single Solaris2 MBR (primary) partition, 
in it you have VTOC table and it has to be manually described (usually has 
root, backup (s2) and boot slices).

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

Re: [OpenIndiana-discuss] problem adding a mirror disk to rpool

[Toomas Soome via openindiana-discuss]

> On 3. Jan 2023, at 21:14, Bob Friesenhahn  
> wrote:
> 
> On Tue, 3 Jan 2023, s...@pandora.be wrote:
>> 
>> The bootadm manpage says that you have to run install-bootloader with the -M 
>> option.
>> 
>> https://illumos.org/man/8/bootadm
>> 
>> "  When disks in the ZFS pool
>>  used for booting the system have been replaced, one should run bootadm
>>  install-bootloader to ensure that all disks in that pool have the system
>>  boot loader installed."
> 
> I am pretty sure that the boot bits are installed on boot disks automatically 
> these days.
> 
> The manual pages are slow to be updated, or perhaps it is because what they 
> say is still true.
> 

Yes, zpool attach will trigger sysevent, handled by 
/etc/sysevent/config/SUNW,EC_zfs,ESC_ZFS_bootfs_vdev_attach,sysevent.conf

rgds,
toomas

> Bob
> -- 
> Bob Friesenhahn
> bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
> GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
> Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt
> 
> ___
> 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] problem adding a mirror disk to rpool

[Toomas Soome via openindiana-discuss]

> On 2. Jan 2023, at 18:11, Marc Lobelle  wrote:
> 
> Hi Toomas,
> 
> Format says this What should I change ?
> 
>   Total disk size is 58369 cylinders
>  Cylinder size is 16065 (512 byte) blocks
> 
> Cylinders
>   Partition   StatusType   Start   End   Length %
>   =  ==         ===
>   1 EFI   0  58368 58369100
> 

this one is all good.

What does format ->  verify report?

rgds,
toomas

> 
> On 1/2/23 12:49, Toomas Soome via openindiana-discuss wrote:
>> Since you are using MBR+VTOC, make sure your new disk has Solaris2 partition 
>> (100%). You can check by running format, select the disk, then enter ‘fdisk'.
>> 
>> rgds,
>> toomas
>> 
>>> On 2. Jan 2023, at 13:45, Marc Lobelle  wrote:
>>> 
>>> Hello,
>>> 
>>> First, Best wished for 2023 to everybody !
>>> 
>>> I tried to add a second 480Gb disk to my rpool (different manufacturer and 
>>> slightly larger)
>>> 
>>> Below is what I did, but apparently there is a problem and the case (adding 
>>> a mirror disk) is not discussed in https://illumos.org/msg/ZFS-8000-4J/
>>> 
>>> Anybody has an idea on how to solve this issue ? I did not yet installgrub 
>>> on the new disk because I fear it would make things worse.
>>> 
>>> Thanks
>>> 
>>> Marc
>>> 
>>> ml@spitfire:/home/ml# zpool status rpool
>>>   pool: rpool
>>>  state: ONLINE
>>>   scan: scrub repaired 0 in 0 days 00:05:41 with 0 errors on Wed Dec 28 
>>> 16:43:12 2022
>>> config:
>>> 
>>> NAMESTATE READ WRITE CKSUM
>>> rpool   ONLINE   0 0 0
>>>   c7d0s0ONLINE   0 0 0
>>> 
>>> errors: No known data errors
>>> ml@spitfire:/home/ml# format
>>> Searching for disks...done
>>> 
>>> 
>>> AVAILABLE DISK SELECTIONS:
>>>0. c5d0 >> 4TB=S5STNF0T406608A-S5STNF0T406608A-0001-3.64TB>
>>>   /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0
>>>1. c6d0 >> 4TB=S5STNF0T406604J-S5STNF0T406604J-0001-3.64TB>
>>>   /pci@0,0/pci-ide@1f,2/ide@1/cmdk@0,0
>>>2. c7d0 
>>>   /pci@0,0/pci-ide@1f,5/ide@0/cmdk@0,0
>>>3. c8d0 
>>>   /pci@0,0/pci-ide@1f,5/ide@1/cmdk@0,0
>>> Specify disk (enter its number): ^C
>>> ml@spitfire:/home/ml# prtvtoc /dev/rdsk/c7d0s0
>>> * /dev/rdsk/c7d0s0 partition map
>>> *
>>> * Dimensions:
>>> * 512 bytes/sector
>>> *  63 sectors/track
>>> * 255 tracks/cylinder
>>> *   16065 sectors/cylinder
>>> *   58368 cylinders
>>> *   58366 accessible cylinders
>>> *   937681920 sectors
>>> *   937649790 accessible sectors
>>> *
>>> * Flags:
>>> *   1: unmountable
>>> *  10: read-only
>>> *
>>> * Unallocated space:
>>> * First   Sector  Last
>>> * Sector   Count  Sector
>>> * 0   16065   16064
>>> *
>>> *First   Sector  Last
>>> * Partition  Tag  Flags  Sector   Count  Sector  Mount Directory
>>>0  20016065   937633725   937649789
>>>2  5010   937649790   937649789
>>>8  1010   16065   16064
>>> ml@spitfire:/home/ml# prtvtoc /dev/rdsk/c7d0s0|fmthard -s - /dev/rdsk/c8d0s0
>>> fmthard: Partition 2 specifies the full disk and is not equal
>>> full size of disk.  The full disk capacity is 937665855 sectors.
>>> fmthard:  New volume table of contents now in place.
>>> ml@spitfire:/home/ml# zpool attach -f rpool c7d0s0 c8d0s0
>>> Make sure to wait until resilver is done before rebooting.
>>> ml@spitfire:/home/ml# zpool status rpool
>>>   pool: rpool
>>>  state: ONLINE
>>> status: One or more devices is currently being resilvered.  The pool will
>>> continue to function, possibly in a degraded state.
>>> action: Wait for the resilver to complete.
>>>   scan: resilver in progress since Mon Jan  2 11:59:05 2023
>>> 56,4G scanned at 2,56G/s, 909M issued at 41,3M/s, 56,4G total
>>> 910M resilvered, 1,57% done, 0 days 00:22:55 to go
>>> config:
>>> 

Re: [OpenIndiana-discuss] problem adding a mirror disk to rpool

[Toomas Soome via openindiana-discuss]

Since you are using MBR+VTOC, make sure your new disk has Solaris2 partition 
(100%). You can check by running format, select the disk, then enter ‘fdisk'.

rgds,
toomas

> On 2. Jan 2023, at 13:45, Marc Lobelle  wrote:
> 
> Hello,
> 
> First, Best wished for 2023 to everybody !
> 
> I tried to add a second 480Gb disk to my rpool (different manufacturer and 
> slightly larger)
> 
> Below is what I did, but apparently there is a problem and the case (adding a 
> mirror disk) is not discussed in https://illumos.org/msg/ZFS-8000-4J/
> 
> Anybody has an idea on how to solve this issue ? I did not yet installgrub on 
> the new disk because I fear it would make things worse.
> 
> Thanks
> 
> Marc
> 
> ml@spitfire:/home/ml# zpool status rpool
>   pool: rpool
>  state: ONLINE
>   scan: scrub repaired 0 in 0 days 00:05:41 with 0 errors on Wed Dec 28 
> 16:43:12 2022
> config:
> 
> NAMESTATE READ WRITE CKSUM
> rpool   ONLINE   0 0 0
>   c7d0s0ONLINE   0 0 0
> 
> errors: No known data errors
> ml@spitfire:/home/ml# format
> Searching for disks...done
> 
> 
> AVAILABLE DISK SELECTIONS:
>0. c5d0  4TB=S5STNF0T406608A-S5STNF0T406608A-0001-3.64TB>
>   /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0
>1. c6d0  4TB=S5STNF0T406604J-S5STNF0T406604J-0001-3.64TB>
>   /pci@0,0/pci-ide@1f,2/ide@1/cmdk@0,0
>2. c7d0 
>   /pci@0,0/pci-ide@1f,5/ide@0/cmdk@0,0
>3. c8d0 
>   /pci@0,0/pci-ide@1f,5/ide@1/cmdk@0,0
> Specify disk (enter its number): ^C
> ml@spitfire:/home/ml# prtvtoc /dev/rdsk/c7d0s0
> * /dev/rdsk/c7d0s0 partition map
> *
> * Dimensions:
> * 512 bytes/sector
> *  63 sectors/track
> * 255 tracks/cylinder
> *   16065 sectors/cylinder
> *   58368 cylinders
> *   58366 accessible cylinders
> *   937681920 sectors
> *   937649790 accessible sectors
> *
> * Flags:
> *   1: unmountable
> *  10: read-only
> *
> * Unallocated space:
> * First   Sector  Last
> * Sector   Count  Sector
> * 0   16065   16064
> *
> *First   Sector  Last
> * Partition  Tag  Flags  Sector   Count  Sector  Mount Directory
>0  20016065   937633725   937649789
>2  5010   937649790   937649789
>8  1010   16065   16064
> ml@spitfire:/home/ml# prtvtoc /dev/rdsk/c7d0s0|fmthard -s - /dev/rdsk/c8d0s0
> fmthard: Partition 2 specifies the full disk and is not equal
> full size of disk.  The full disk capacity is 937665855 sectors.
> fmthard:  New volume table of contents now in place.
> ml@spitfire:/home/ml# zpool attach -f rpool c7d0s0 c8d0s0
> Make sure to wait until resilver is done before rebooting.
> ml@spitfire:/home/ml# zpool status rpool
>   pool: rpool
>  state: ONLINE
> status: One or more devices is currently being resilvered.  The pool will
> continue to function, possibly in a degraded state.
> action: Wait for the resilver to complete.
>   scan: resilver in progress since Mon Jan  2 11:59:05 2023
> 56,4G scanned at 2,56G/s, 909M issued at 41,3M/s, 56,4G total
> 910M resilvered, 1,57% done, 0 days 00:22:55 to go
> config:
> 
> NAMESTATE READ WRITE CKSUM
> rpool   ONLINE   0 0 0
>   mirror-0  ONLINE   0 0 0
> c7d0s0  ONLINE   0 0 0
> c8d0s0  ONLINE   0 0 0  (resilvering)
> 
> errors: No known data errors
> ml@spitfire:/home/ml# zpool status rpool
>   pool: rpool
>  state: DEGRADED
> status: One or more devices could not be used because the label is missing or
> invalid.  Sufficient replicas exist for the pool to continue
> functioning in a degraded state.
> action: Replace the device using 'zpool replace'.
>see: http://illumos.org/msg/ZFS-8000-4J
>   scan: resilvered 34,6G in 0 days 00:06:23 with 0 errors on Mon Jan  2 
> 12:05:28 2023
> config:
> 
> NAMESTATE READ WRITE CKSUM
> rpool   DEGRADED 0 0 0
>   mirror-0  DEGRADED 0 0 0
> c7d0s0  ONLINE   0 0 0
> c8d0s0  UNAVAIL  0 57,4K 0  corrupted data
> 
> errors: No known data errors
> ml@spitfire:/home/ml#
> 
> 
> ___
> 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] ZFS version

[Toomas Soome via openindiana-discuss]

> On 19. Oct 2022, at 14:33, Predrag Zecevic via openindiana-discuss 
>  wrote:
> 
> Hi all,
> 
> how to find out which zfs version we are running on OpenIndiana?
> 
> ZOL have command:
> :; zfs --version
> zfs-2.1.5-2
> 

We haven’t ported the versioning concept from OpenZFS. At this time, the 
feature support is the only way to check.

rgds,
toomas


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

Re: [OpenIndiana-discuss] Dell UEFI BIOS update and OpenIndiana

[Toomas Soome via openindiana-discuss]

> On 28. Sep 2022, at 09:41, s...@pandora.be  wrote:
> 
> 
> Some  of those systems being mentioned here are not in the HCL (hardware comp 
> list), which I'll try to update.
> 
> Basically it would be good if the HCL is extended to also include the 
> firmware BIOS information.
> 
> Also I am using UEFI boot (I am forced to do so, there seems no legacy BIOS 
> support in the Dell 3640),
> but I can imagine that the UEFI boot support is sufficient for simple setups, 
> but still has some issues in more complex setups.
> 
> Regards
> David Stes

We can not exclude the possibility of bugs, but we definitely do want to hear 
about issues asap. (There is one generic issue but so far we have been lucky to 
not get bitten from it;).

rgds,
toomas

> 
> 
> - Op 28 sep 2022 om 7:25 schreef Stephan Althaus 
> stephan.alth...@duedinghausen.eu:
> 
>> On 9/27/22 16:31, Carl Brewer wrote:
>>> On 27/09/2022 6:47 pm, s...@pandora.be wrote:
 
 The Dell UEFI BIOS 1.17 for Dell Precision seems to work fine for me
 (UEFI) with  Secure Boot disabled (which I think is the default for
 Dell Precision).
 
 Is someone keeping a list of supported / tested BIOS firmware versions ?
 
 For me Dell BIOS 1.17 is reported in OpenIndiana as:
 
 # prtdiag -v | head
 System Configuration: Dell Inc. Precision 3640 Tower
 BIOS Configuration: Dell Inc. 1.17.0 08/12/2022
 
  Processor Sockets 
 
 Version  Location Tag
  --
 Intel(R) Core(TM) i3-10100 CPU @ 3.60GHz
 
 
 Perhaps there could be a specific documentation page for community
 provided tested BIOS versions.
>>> 
>>> Once upon a time there was a HCL, but it seems to be long dead.
>>> 
>>> My BIOS's :
>>> 
>>> root@hog:/slow/backups/VMs# prtdiag -v | head
>>> 
>>> System Configuration: Gigabyte Technology Co., Ltd. H370M-D3H
>>> BIOS Configuration: American Megatrends Inc. F2 02/13/2018
>>> 
>>>  Processor Sockets 
>>> 
>>> Version  Location Tag
>>>  --
>>> Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz U3E1
>>> 
>>> 
>>> root@skaro:/slow/backups/VMs#  prtdiag -v | head
>>> System Configuration: Gigabyte Technology Co., Ltd. B460MAORUSPRO
>>> BIOS Configuration: American Megatrends Inc. F4 08/28/2020
>>> 
>>>  Processor Sockets 
>>> 
>>> Version  Location Tag
>>>  --
>>> Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz U3E1
>>> 
>>> And one that's too old for prtdiag! :
>>> 
>>> carl@hostie:~# prtdiag -v | head
>>> prtdiag: failed to open SMBIOS: System does not export an SMBIOS table
>>> carl@hostie:~#
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ___
>>> openindiana-discuss mailing list
>>> openindiana-discuss@openindiana.org
>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
>> 
>> Hi!
>> 
>> My Bios is:
>> 
>> $ prtdiag -v | head
>> System Configuration: Dell Inc. Precision 7720
>> BIOS Configuration: Dell Inc. 1.24.0 03/22/2022
>> 
>>  Processor Sockets 
>> 
>> Version  Location Tag
>>  --
>> Intel(R) Xeon(R) CPU E3-1535M v6 @ 3.10GHz U3E1
>> 
>> I am booting Legacy here (historical reasons, the basic installation is
>> old), this is the last type providing Legacy, the next model 7730 is
>> UEFI only.
>> 
>> On my Fujitsu Primergy T1330 backup server i am using UEFI boot with OI,
>> everything is fine.
>> 
>> Greetings,
>> 
>> Stephan
>> 
>> 
>> ___
>> 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] Dell UEFI BIOS update and OpenIndiana

[Toomas Soome via openindiana-discuss]

> On 27. Sep 2022, at 19:34, s...@pandora.be  wrote:
> 
> 
> When I press ESC or F12 to get into the Dell UEFI BIOS, it reports 
> 
> Boot mode is set to: UEFI; Secure Boot: OFF
> 
> then there is a UEFI Boot menu and option to go into the BIOS setup,
> and also an option to change Boot Mode.
> 
> The only option provided there (under "Change Boot Mode") is UEFI Boot Mode, 
> Secure Boot ON
> (which I didn't test and based on the OpenIndiana docs and suggestions, I am 
> not going to turn on Secure Boot).
> 
> Actually I have tried to find an option to boot without UEFI but have not 
> been able to find such an option on the Dell Precision 3640, so I think the 
> system does not provide a legacy BIOS boot mode; at least I have not been 
> able to find it.
> 
> In the BIOS Setup itself there is a "General" Settings with "Boot Sequence", 
> and under Boot Sequence an editable boot list,
> which I think is the same list as tools such as :
> 
> https://github.com/rhboot/efibootmgr
> 
> EFI bootmgr manipulate.
> 
> However to my knowledge OpenIndiana does not provide a tool like "efibootmgr".
> 
> Nevertheless OpenIndiana seems to work fine with UEFI,
> and the BIOS Setup editable boot list in the Dell BIOS,
> allows to edit the list and remove for example entries that are not needed or 
> to add entries.
> 
> Basically this list specifies the order that the BIOS search devices when 
> trying to find an operating system to boot.
> 
> I am certainly not an expert in UEFI boot, I'm just reporting that it seems 
> to work for OpenIndiana.
> 
> There are open UEFI boot issues at https://www.illumos.org/issues/14807
> 
> I'll file a "feature request" for a efibootmgr tool ...


Yes, we do not currently have “efibootmgr” tool. Just havent had time to add it 
(it also needs efirt kernel module to access UEFI RunTime functions). 
Definitely in todo list - altho with a bit less priority, because the firmware 
setup is existing fallback for it:)

rgds,
toomas


> 
> Regards,
> David Stes
> 
> - Op 27 sep 2022 om 16:31 schreef carl c...@bl.echidna.id.au:
> 
>> On 27/09/2022 6:47 pm, s...@pandora.be wrote:
>>> 
>>> The Dell UEFI BIOS 1.17 for Dell Precision seems to work fine for me (UEFI) 
>>> with
>>> Secure Boot disabled (which I think is the default for Dell Precision).
>>> 
>>> Is someone keeping a list of supported / tested BIOS firmware versions ?
>>> 
>>> For me Dell BIOS 1.17 is reported in OpenIndiana as:
>>> 
>>> # prtdiag -v | head
>>> System Configuration: Dell Inc. Precision 3640 Tower
>>> BIOS Configuration: Dell Inc. 1.17.0 08/12/2022
>>> 
>>>  Processor Sockets 
>>> 
>>> Version  Location Tag
>>>  --
>>> Intel(R) Core(TM) i3-10100 CPU @ 3.60GHz
>>> 
>>> 
>>> Perhaps there could be a specific documentation page for community provided
>>> tested BIOS versions.
>> 
>> Once upon a time there was a HCL, but it seems to be long dead.
>> 
>> My BIOS's :
>> 
>> root@hog:/slow/backups/VMs# prtdiag -v | head
>> 
>> System Configuration: Gigabyte Technology Co., Ltd. H370M-D3H
>> BIOS Configuration: American Megatrends Inc. F2 02/13/2018
>> 
>>  Processor Sockets 
>> 
>> Version  Location Tag
>>  --
>> Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz U3E1
>> 
>> 
>> root@skaro:/slow/backups/VMs#  prtdiag -v | head
>> System Configuration: Gigabyte Technology Co., Ltd. B460MAORUSPRO
>> BIOS Configuration: American Megatrends Inc. F4 08/28/2020
>> 
>>  Processor Sockets 
>> 
>> Version  Location Tag
>>  --
>> Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz U3E1
>> 
>> And one that's too old for prtdiag! :
>> 
>> carl@hostie:~# prtdiag -v | head
>> prtdiag: failed to open SMBIOS: System does not export an SMBIOS table
>> carl@hostie:~#
>> 
>> 
>> 
>> 
>> 
>> ___
>> 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] After locked up zpool scrub, BIOS not recognizing HDDs to boot

[Toomas Soome via openindiana-discuss]

> On 26. Sep 2022, at 16:41, Carl Brewer  wrote:
> 
> On 26/09/2022 9:13 pm, Carl Brewer wrote:
> 
> To add to the list of Heisenbugs 
> 
> It works.  I pulled it out of my rack, set it up on a table, and the BIOS 
> found all 5 HDDs and was happy to use them to boot.
> 
> Erm?!
> 
> The only thing that happened, was ~10 mins of downtime and an HDMI instead of 
> VGA monitor.
> 
> Some weird BIOS thing?  Some weird race condition with BIOS timing and HDDs 
> spinning up?
> 
> It's working now, back in the rack and ok. Until next time?!
> 

I’d suggest to check for firmware update.

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

Re: [OpenIndiana-discuss] After locked up zpool scrub, BIOS not recognizing HDDs to boot

[Toomas Soome via openindiana-discuss]

> On 26. Sep 2022, at 14:13, Carl Brewer  wrote:
> 
> On 26/09/2022 4:41 pm, Toomas Soome via openindiana-discuss wrote:
> 
> This is what I've just done :
> 
> 
> jack@openindiana:/jack$ su -
> Password:
> The illumos Project illumos-bdc24928e6  August 2021
> root@openindiana:~#
> root@openindiana:~#
> root@openindiana:~#
> root@openindiana:~# zpool status
> no pools available
> root@openindiana:~# zpool import rpool
> root@openindiana:~# bootadm install-bootloader -P rpool
> root@openindiana:~# zpool export rpool
> root@openindiana:~#
> root@openindiana:~#
> root@openindiana:~# zpool status
> no pools available
> root@openindiana:~# init 5
> 
> 
> No error messages.
> 
> But, it's just going straight to the BIOS page at boot time.  These newer 
> Gigabyte BIOS setup pages are a nightmare to navigate to find what the 
> settings are.
> 
> 
> I tried it with -f set as well :
> 
> 
> 
> The illumos Project illumos-bdc24928e6  August 2021
> root@openindiana:~# zpool status
> no pools available
> root@openindiana:~# zpool import rpool
> root@openindiana:~# bootadm install-bootloader -f -P rpool
> root@openindiana:~# zpool export rpool
> 
> 
> Also no luck.  I'm a bit stumped.
> 

Is this UEFI boot or BIOS boot? If it is UEFI boot, you need to make sure the 
secure boot is disabled - we do not support it.

rgds,
toomas


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

Re: [OpenIndiana-discuss] After locked up zpool scrub, BIOS not recognizing HDDs to boot

[Toomas Soome via openindiana-discuss]

> On 26. Sep 2022, at 07:59, Carl Brewer  wrote:
> 
> On 25/09/2022 6:59 pm, Toomas Soome via openindiana-discuss wrote:
>>> On 25. Sep 2022, at 02:33, Carl Brewer  wrote:
>>> 
>>> 
>>> I have a ~3 year old PC, generic motherboard, OI hipster 'something', that 
>>> last night, I had to force a reboot on, because a zpool scrub was jammed up 
>>> and nothing would kill it.  The scrub was on a raidz pool, not the boot 
>>> drives, so I figured it would probably be ok. I was wrong!
>> Assuming up to date system, this *may* indicate issue related to disk 
>> controller.
> 
> It's possible, but I think pretty unlikely.  When I booted it off the USB 
> drive, I could import all the existing zpools - that's how I rescued the 
> VirtualBox VDI's and got them up quickly.


scrub can put some solad on system - load on memory at first, then on IO system.

> 
> 
>>> Any hints for how to reinstall a boot environment onto an existing zfs 
>>> mirror?  If I have to do a full reinstall onto it, that's not a total 
>>> disaster, I got what I needed off it, but it would be interesting to do.  I 
>>> haven't yet gone through the BIOS settings to be certain it's not some 
>>> stupid BIOS default around UEFI or something, but I didn't change the BIOS 
>>> myself, I suspect that it isn't the problem.
>>> 
>> With 3 years old, was it actually using UEFI or BIOS boot? If firmware does 
>> not recognize disk as bootable, it may suggest that FAT32 in ESP is damaged 
>> or for BIOS, MBR signature is bad or like. In any case, it should not 
>> require reinstall, bootadm install-bootloader -f might be enough.
> 
> 
> I'm about to pull it out of my racks and get it on a desk and work on it, 
> I'll try that first, thank you - do I need to do it to both drives in the 
> zpool mirror, or does mirroring take care of that for me?

bootadm install-bootloader will walk all the disks by itself. zpool mirror does 
not help you there because bootblocks are outside the [mirrored] data area.

rgds,
toomas

> 
> 
>> If you still do want to reinstall, openindiana installer does provide option 
>> to use existing pool on very first screen (press F5). However, that option 
>> will leave some manual work for you (creating users etc).
> 
> The machine has just the one user, so that's an easy path. All it does is 
> host some VirtualBox guests. I want to update to the latest OI anyway, so not 
> unhappy if I have to go this way.
> 
> Thank you
> 
> Carl
> 
> 
> 
> ___
> 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] After locked up zpool scrub, BIOS not recognizing HDDs to boot

[Toomas Soome via openindiana-discuss]

> On 25. Sep 2022, at 02:33, Carl Brewer  wrote:
> 
> 
> I have a ~3 year old PC, generic motherboard, OI hipster 'something', that 
> last night, I had to force a reboot on, because a zpool scrub was jammed up 
> and nothing would kill it.  The scrub was on a raidz pool, not the boot 
> drives, so I figured it would probably be ok. I was wrong!


Assuming up to date system, this *may* indicate issue related to disk 
controller.


> 
> On reboot, the motherboard's BIOS wasn't seeing the drives as a boot option - 
> it could see them (there's 5, 2 mirrored for zpool, and a raidz array of 3), 
> but wouldn't see them as boot options. It was just jumping straight to the 
> BIOS setup screen at boot-time. A quick poke around in the BIOS confirmed 
> that the BIOS could, at least, see the 5 drives in the box. Then I had to get 
> stuff running, so I didn't have the luxury of time to muck about too much 
> with it.
> 
> I booted it off a USB drive and could zpool import them ok, so I copied off 
> the stuff I needed, a couple of VirtualBox VM's, but now I'd like to recover 
> the machine if possible. I have a Borg backup of the bits I needed too, so 
> this wasn't a complete disaster!
> 
> Any hints for how to reinstall a boot environment onto an existing zfs 
> mirror?  If I have to do a full reinstall onto it, that's not a total 
> disaster, I got what I needed off it, but it would be interesting to do.  I 
> haven't yet gone through the BIOS settings to be certain it's not some stupid 
> BIOS default around UEFI or something, but I didn't change the BIOS myself, I 
> suspect that it isn't the problem.
> 

With 3 years old, was it actually using UEFI or BIOS boot? If firmware does not 
recognize disk as bootable, it may suggest that FAT32 in ESP is damaged or for 
BIOS, MBR signature is bad or like. In any case, it should not require 
reinstall, bootadm install-bootloader -f might be enough.

If you still do want to reinstall, openindiana installer does provide option to 
use existing pool on very first screen (press F5). However, that option will 
leave some manual work for you (creating users etc).

rgds,
toomas


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

Re: [OpenIndiana-discuss] image-update fails with python mediator errors

[Toomas Soome via openindiana-discuss]

> On 5. Jul 2022, at 21:10, Gary Mills  wrote:
> 
> On Tue, Jul 05, 2022 at 07:25:01PM +0300, Toomas Soome via 
> openindiana-discuss wrote:
> 
>> Different issue. You have svm (solaris volume manager) service to
>> be removed….
> 
> What's the exact command?  I recall I had this problem after an
> update.  The boot stopped in single-user mode.  I logged in and
> deleted the bad service.  Then I shut down the system and rebooted
> it.  I got a normal boot.
> 
> This is a well-known problem with OI.
> 
> The command probably came from a web page, but I can no longer
> find it.
> 


last time it was about metainit.

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

Re: [OpenIndiana-discuss] image-update fails with python mediator errors

[Toomas Soome via openindiana-discuss]

> On 5. Jul 2022, at 19:23, Marcel Telka  wrote:
> 
> On Tue, Jul 05, 2022 at 04:11:15PM +, Philip Kime wrote:
>> Thanks for the help. This got the pkg update to run through but 
>> unfortunately, the system doesn't boot to multi-user any more now:
>> 
>> system/filesystem/usr service fails as it "Completes a dependency cycle" ...
> 
> That's ... strange.
> 
> Reboot back to the working BE and try to manually update to
> userland-incorporation@0.5.11-2022.0.0.15875 using something like:
> 
> pkg update -n -v userland-incorporation@0.5.11-2022.0.0.15875
> 
> and share the full output.
> 
> The difference between userland-incorporation@0.5.11-2022.0.0.15873 (you
> are able to install, but it does not boot) and
> userland-incorporation@0.5.11-2022.0.0.15875 (I'm suggesting) is switch
> of default perl from 5.22 to 5.34 and fix of python-39 packaging so I'm
> curious why it is not possible to do the update.
> 

Different issue. You have svm (solaris volume manager) service to be removed…. 

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

Re: [OpenIndiana-discuss] problem replacing a disk by a bigger one: not yet solved

[Toomas Soome via openindiana-discuss]

> On 2. Jul 2022, at 00:08, Marc Lobelle  wrote:
> 
> 
> On 7/1/22 22:55, Toomas Soome via openindiana-discuss wrote:
>> 
>>> On 1. Jul 2022, at 22:16, Marc Lobelle  wrote:
>>> 
>>> 
>>> On 7/1/22 19:57, Toomas Soome via openindiana-discuss wrote:
>>>>> On 1. Jul 2022, at 19:58, Marc Lobelle >>>> <mailto:marc.lobe...@uclouvain.be>> wrote:
>>>>> 
>>>>> 
>>>>> On 7/1/22 13:17, Toomas Soome via openindiana-discuss wrote:
>>>>>>> On 1. Jul 2022, at 13:33, Marc Lobelle >>>>>> <mailto:marc.lobe...@uclouvain.be><mailto:marc.lobe...@uclouvain.be 
>>>>>>> <mailto:marc.lobe...@uclouvain.be>>> wrote:
>>>>>>> 
>>>>>>> Hi Thomas,
>>>>>>> 
>>>>>>> Currently, If I try to boot the openindiana disk (Windows and 
>>>>>>> Openindiana are on 2 different SSD) on this HP elitebook 820G3,
>>>>>>> 
>>>>>>> If I try to boot it uefi, I come back to the general booting menu of HP,
>>>>>> This may be because of secure boot
>>>>> sure
>>>>>> , we do not support secure boot. If your system does provide efi shell, 
>>>>>> you can try to start efi/boot/bootx64.efi manually (should be accessible 
>>>>>> from path like fs*:\… ) - sometimes manual start will tell, why it 
>>>>>> failed to start.
>>>>>> 
>>>>>>> If I try to boot it legacy, I get on the screen
>>>>>>> 
>>>>>>> BIOS drive C: is disk0
>>>>>>> 
>>>>>>> BIOS drive D: is disk1
>>>>>>> 
>>>>>>> ZFS: i/o error - all block copies unavailable
>>>>>>> 
>>>>>>> ZFS: can't read MOS of pool rpool
>>>>>>> 
>>>>>>> Can't find /boot/loader
>>>>>>> 
>>>>>>> Can't find /boot/zfsloader
>>>>>>> 
>>>>>>> illumos/x86 boot
>>>>>>> 
>>>>>>> Default: /boot/loader
>>>>>>> 
>>>>>>> boot:
>>>>>>> 
>>>>>> if you enter on boot: prompt: status - what does it tell?
>>>>> Interesting. If I type "status" at the boot: prompt, it says
>>>>> 
>>>>> devices:
>>>>> 
>>>>> Disk 0: Bios Drice C (234441648 x 512)
>>>>> 
>>>>> disk0s1 Solaris 2 111GB
>>>>> 
>>>>> disk0s1a: root 111 GB
>>>>> 
>>>>> disk0s1i: boot 6172 KB
>>>> There you have MBR + VTOC in Solaris2 partition - we can only boot with 
>>>> BIOS mode with this setup (no MBR EFI partition (type code 239).
>>> yes this the solaris disk and it used to work with MBR+VTOC (legacy boot)
>>>>> Disk 1: Bios Drive D (500118192 x 512
>>>>> 
>>>>> disk1p1: EFI 100 MB
>>>>> 
>>>>> disk1p2: unknown 16MB
>>>>> 
>>>>> disk1p3: DOS/Windows 237 GB
>>>>> 
>>>>> disk1p4: Unknown 522MB
>>>>> 
>>> This disk is windows only. I was the only one when I bought the computer.I 
>>> never modified its microsoft sriucture. I added the second disk to have 
>>> openindiana. Originally I had a 500GB ssd for openindiana but it crashed 
>>> (probably too many bad blocks) and I replaced it temporarily with a 120GB 
>>> ssd I had on a shelf. There I had to reinstall everything from distro and 
>>> back-ups because the old 500GB disk was unusable. Now I bought a new 1TB 
>>> disk. I connected it as external usb disk and made it a mirror of the 120 
>>> GB One but I made the error of run bootadm installboot without -M so it 
>>> garbled the boot structure of both disks. Now I try to fix the boot 
>>> structure, first of the 120Gb then of the 1TB
>>>> This one is interesting - only partition 1 and 3 are known, it should not 
>>>> affect us, its just interesting (we should see illumos ZFS there).
>>>> 
>>>> Much more interesting are partition sizes. If p3 is really windows, then 
>>>> p2 or p4 do not have enough space to store rpool — ould expect to see 
>>>> minimum some 16GB or so (/ file system should take some 5+ GB of space).
>>> rpool is on 

Re: [OpenIndiana-discuss] problem replacing a disk by a bigger one: not yet solved

[Toomas Soome via openindiana-discuss]

> On 1. Jul 2022, at 22:16, Marc Lobelle  wrote:
> 
> 
> On 7/1/22 19:57, Toomas Soome via openindiana-discuss wrote:
>> 
>>> On 1. Jul 2022, at 19:58, Marc Lobelle >> <mailto:marc.lobe...@uclouvain.be>> wrote:
>>> 
>>> 
>>> On 7/1/22 13:17, Toomas Soome via openindiana-discuss wrote:
>>>>> On 1. Jul 2022, at 13:33, Marc Lobelle >>>> <mailto:marc.lobe...@uclouvain.be><mailto:marc.lobe...@uclouvain.be 
>>>>> <mailto:marc.lobe...@uclouvain.be>>> wrote:
>>>>> 
>>>>> Hi Thomas,
>>>>> 
>>>>> Currently, If I try to boot the openindiana disk (Windows and Openindiana 
>>>>> are on 2 different SSD) on this HP elitebook 820G3,
>>>>> 
>>>>> If I try to boot it uefi, I come back to the general booting menu of HP,
>>>> This may be because of secure boot
>>> sure
>>>> , we do not support secure boot. If your system does provide efi shell, 
>>>> you can try to start efi/boot/bootx64.efi manually (should be accessible 
>>>> from path like fs*:\… ) - sometimes manual start will tell, why it failed 
>>>> to start.
>>>> 
>>>>> If I try to boot it legacy, I get on the screen
>>>>> 
>>>>> BIOS drive C: is disk0
>>>>> 
>>>>> BIOS drive D: is disk1
>>>>> 
>>>>> ZFS: i/o error - all block copies unavailable
>>>>> 
>>>>> ZFS: can't read MOS of pool rpool
>>>>> 
>>>>> Can't find /boot/loader
>>>>> 
>>>>> Can't find /boot/zfsloader
>>>>> 
>>>>> illumos/x86 boot
>>>>> 
>>>>> Default: /boot/loader
>>>>> 
>>>>> boot:
>>>>> 
>>>> if you enter on boot: prompt: status - what does it tell?
>>> Interesting. If I type "status" at the boot: prompt, it says
>>> 
>>> devices:
>>> 
>>> Disk 0: Bios Drice C (234441648 x 512)
>>> 
>>> disk0s1 Solaris 2 111GB
>>> 
>>> disk0s1a: root 111 GB
>>> 
>>> disk0s1i: boot 6172 KB
>> 
>> There you have MBR + VTOC in Solaris2 partition - we can only boot with BIOS 
>> mode with this setup (no MBR EFI partition (type code 239).
> yes this the solaris disk and it used to work with MBR+VTOC (legacy boot)
>>> Disk 1: Bios Drive D (500118192 x 512
>>> 
>>> disk1p1: EFI 100 MB
>>> 
>>> disk1p2: unknown 16MB
>>> 
>>> disk1p3: DOS/Windows 237 GB
>>> 
>>> disk1p4: Unknown 522MB
>>> 
> This disk is windows only. I was the only one when I bought the computer.I 
> never modified its microsoft sriucture. I added the second disk to have 
> openindiana. Originally I had a 500GB ssd for openindiana but it crashed 
> (probably too many bad blocks) and I replaced it temporarily with a 120GB ssd 
> I had on a shelf. There I had to reinstall everything from distro and 
> back-ups because the old 500GB disk was unusable. Now I bought a new 1TB 
> disk. I connected it as external usb disk and made it a mirror of the 120 GB 
> One but I made the error of run bootadm installboot without -M so it garbled 
> the boot structure of both disks. Now I try to fix the boot structure, first 
> of the 120Gb then of the 1TB
>> This one is interesting - only partition 1 and 3 are known, it should not 
>> affect us, its just interesting (we should see illumos ZFS there).
>> 
>> Much more interesting are partition sizes. If p3 is really windows, then p2 
>> or p4 do not have enough space to store rpool — ould expect to see minimum 
>> some 16GB or so (/ file system should take some 5+ GB of space).
> 
> rpool is on disk0. The only damage there is probably due to bootadm 
> installboot, so I cannot anymore boot disk0. Also I detached this disk from 
> the mirror I had made to transfer (by resilvering its contents to the bigger 
> one) . Can this harm bootability of this disk , used alone ??
> 


um, if you did detach this disk from rpool, then disk disk has no importable 
pool (data is not wiped, but the pool on it is made inaccessible. You want to 
use zpool split instead - that would create new, accessible pool.

rgds,
toomas

> Best regards
> 
> Marc
> 
>> 
>> rgds,
>> toomas
>> 
>>>> Also, start system from usb/cd media, on boot loader menu, press esc to 
>>>> get ok prompt. From ok prompt, enter lsdev -v.
>>>> 
>>>> lsd

Re: [OpenIndiana-discuss] problem replacing a disk by a bigger one: not yet solved

[Toomas Soome via openindiana-discuss]

> On 1. Jul 2022, at 19:58, Marc Lobelle  wrote:
> 
> 
> On 7/1/22 13:17, Toomas Soome via openindiana-discuss wrote:
>> 
>>> On 1. Jul 2022, at 13:33, Marc Lobelle >> <mailto:marc.lobe...@uclouvain.be>> wrote:
>>> 
>>> Hi Thomas,
>>> 
>>> Currently, If I try to boot the openindiana disk (Windows and Openindiana 
>>> are on 2 different SSD) on this HP elitebook 820G3,
>>> 
>>> If I try to boot it uefi, I come back to the general booting menu of HP,
>> This may be because of secure boot
> sure
>> , we do not support secure boot. If your system does provide efi shell, you 
>> can try to start efi/boot/bootx64.efi manually (should be accessible from 
>> path like fs*:\… ) - sometimes manual start will tell, why it failed to 
>> start.
>> 
>>> If I try to boot it legacy, I get on the screen
>>> 
>>> BIOS drive C: is disk0
>>> 
>>> BIOS drive D: is disk1
>>> 
>>> ZFS: i/o error - all block copies unavailable
>>> 
>>> ZFS: can't read MOS of pool rpool
>>> 
>>> Can't find /boot/loader
>>> 
>>> Can't find /boot/zfsloader
>>> 
>>> illumos/x86 boot
>>> 
>>> Default: /boot/loader
>>> 
>>> boot:
>>> 
>> if you enter on boot: prompt: status - what does it tell?
> 
> Interesting. If I type "status" at the boot: prompt, it says
> 
> devices:
> 
> Disk 0:  Bios Drice C (234441648 x 512)
> 
> disk0s1  Solaris 2  111GB
> 
> disk0s1a: root  111 GB
> 
> disk0s1i: boot  6172 KB


There you have MBR + VTOC in Solaris2 partition - we can only boot with BIOS 
mode with this setup (no MBR EFI partition (type code 239).


> 
> Disk 1:  Bios Drive D (500118192 x 512
> 
> disk1p1:  EFI 100 MB
> 
> disk1p2: unknown  16MB
> 
> disk1p3: DOS/Windows  237 GB
> 
> disk1p4: Unknown 522MB
> 

This one is interesting - only partition 1 and 3 are known, it should not 
affect us, its just interesting (we should see illumos ZFS there).

Much more interesting are partition sizes. If p3 is really windows, then p2 or 
p4 do not have enough space to store rpool — ould expect to see minimum some 
16GB or so (/ file system should take some 5+ GB of space).

rgds,
toomas

> 
>> 
>> Also, start system from usb/cd media, on boot loader menu, press esc to get 
>> ok prompt. From ok prompt, enter lsdev -v.
>> 
>> lsdev -v should output the partitioning, it would be interesting to see it.
> same result as above, just the cd0 is added as bios drive E
>> 
>> Also, does it list your rpool? If it does, you can see default dataset name 
>> from the lsdev output, enter:
>> 
>> ok set currdev=zfs:rpool/ROOT/datasetname:
> 
> it says device not configured, but if I say disk0 instead of zfs, it does not 
> complain
> 
> I typed menu then selected chainload disk0, after some time it went back to 
> the HP greeting screen
> 
>> ok boot
> it boots the dvd when I just type boot  after set currdev=zfs...
>> 
>> make sure you have that trailing colon there. This does not make it 
>> bootable, but we can have some details about setup.
>> 
>> rgds,
>> toomas
>> 
>>> Do you know how to fix it ?
>>> 
>>> Thanks
>>> 
>>> Marc
>>> 
>>> On 7/1/22 12:09, Toomas Soome via openindiana-discuss wrote:
>>>>> On 1. Jul 2022, at 11:24, Marc Lobelle wrote:
>>>>> 
>>>>> I think I know where the problem is: "# bootadm install-bootloader -P 
>>>>> rpool " installs what is needed to boot in UEFI mode and this is not 
>>>>> possible on a computer that can be dual booted with windows, even in my 
>>>>> case where openindiana and windows are on 2 different ssd. And this 
>>>>> operation made all the disks in rpool unbootable on this system. I should 
>>>>> probably have run"# bootadm install-bootloader -Mf -P rpool " to force 
>>>>> installation of a "legacy" MDB boot.
>>>>> 
>>>>> So, at this point, the only way to run openindiana on the system to fix 
>>>>> this issue is running it from the installation dvd. However, if I type 
>>>>> zpool list on that, I do not see any pool even if I boot it with 
>>>>> reconfigure. How can I install the booting stuff on the internal disk of 
>>>>> the system from an openidiana running on the installation dvd. Some 
>>>>> versions of bootadm allow specifying the device on whi

Re: [OpenIndiana-discuss] problem replacing a disk by a bigger one: not yet solved

[Toomas Soome via openindiana-discuss]

> On 1. Jul 2022, at 13:33, Marc Lobelle  wrote:
> 
> Hi Thomas,
> 
> Currently, If I try to boot the openindiana disk (Windows and Openindiana are 
> on 2 different SSD) on this HP elitebook 820G3,
> 
> If I try to boot it uefi, I come back to the general booting menu of HP,

This may be because of secure boot, we do not support secure boot. If your 
system does provide efi shell, you can try to start efi/boot/bootx64.efi 
manually (should be accessible from path like fs*:\… ) - sometimes manual start 
will tell, why it failed to start.

> 
> If I try to boot it legacy, I get on the screen
> 
>  BIOS drive C: is disk0
> 
>  BIOS drive D: is disk1
> 
>  ZFS: i/o error - all block copies unavailable
> 
>  ZFS:  can't read MOS of pool rpool
> 
>  Can't find /boot/loader
> 
>  Can't find /boot/zfsloader
> 
>  illumos/x86 boot
> 
>  Default: /boot/loader
> 
>  boot:
> 

if you enter on boot: prompt:  status - what does it tell?

Also, start system from usb/cd media, on  boot loader menu, press esc to get ok 
prompt. From ok prompt, enter lsdev -v.

lsdev -v should output the partitioning, it would be interesting to see it.

Also, does it list your rpool? If it does, you can see default dataset name 
from the lsdev output, enter:

ok set currdev=zfs:rpool/ROOT/datasetname:
ok boot

make sure you have that trailing colon there. This does not make it bootable, 
but we can have some details about setup.

rgds,
toomas

> Do you know how to fix it  ?
> 
> Thanks
> 
> Marc
> 
> On 7/1/22 12:09, Toomas Soome via openindiana-discuss wrote:
>> 
>>> On 1. Jul 2022, at 11:24, Marc Lobelle  wrote:
>>> 
>>> I think I know where the problem is: "# bootadm install-bootloader -P rpool 
>>> " installs what is needed to boot in UEFI mode and this is not possible on 
>>> a computer that can be dual booted with windows, even in my case where 
>>> openindiana and windows are on 2 different ssd. And this operation made all 
>>> the disks in rpool unbootable on this system. I should probably have run"# 
>>> bootadm install-bootloader -Mf -P rpool " to force installation of a 
>>> "legacy" MDB boot.
>>> 
>>> So, at this point, the only way to run openindiana on the system to fix 
>>> this issue is running it from the installation dvd. However, if I type 
>>> zpool list on that, I do not see any pool even if I boot it with 
>>> reconfigure. How can I install the booting stuff on the internal disk of 
>>> the system from an openidiana running on the installation dvd. Some 
>>> versions of bootadm allow specifying the device on which to install the 
>>> booting  stuff, but not the bootdm on openindiana.
>>> 
>>> Thanks for your help
>>> 
>>> Marc
>> At this time,we do not have an access to EFI runtime functions, so, we only 
>> do install boot loader as generic efi application (/boot/bootx64.efi). 
>> If you have dual/multiboot setupand have this binary from some other OS, you 
>> need to make backup of it first, then after bootloader install/update,you 
>> need to create alternate locationfor it, like /boot/illumos/ and create 
>> UEFIboot manager configuration in firmware setup and restore the original 
>> bootx64.efi.
>> 
>> The problem is without an access to EFI RT functions, we can not 
>> access/create efi bootmanager variables, and thats why we do use default.
>> 
>> Please note, every pkg update may also update the boot loader (depending on 
>> if the bootloader has received some change - see installboot -i).
>> 
>> Also, bootadm does internally use installboot, and we do install boot 
>> support for both UEFI and BIOS boot.
>> 
>> rgds,
>> toomas
>> 
>> 
>>> On 6/28/22 10:38, Marc Lobelle wrote:
>>>> Hello, more information below on this problem
>>>> 
>>>> On 6/27/22 17:33, Marc Lobelle wrote:
>>>>> Hello
>>>>> 
>>>>> Thanks for your help._/I also found a good step by step guide 
>>>>> athttps://omnios.org/info/migrate_rpool. /_(There are other ones, but 
>>>>> over 10 years old) The only change I had to make was using the guid for 
>>>>> the source disk and the complete real path name to the new device ( even 
>>>>> /dev/dsk/..., which is a symlink did not work) in zpool attach. The need 
>>>>> to use the GUID is a known old bug that was supposed to have been fixed. 
>>>>> I do not know why I had the use the full pathname of the new disk. Maybe 
>>>>> it is due to the

Re: [OpenIndiana-discuss] problem replacing a disk by a bigger one: not yet solved

[Toomas Soome via openindiana-discuss]

> On 1. Jul 2022, at 11:24, Marc Lobelle  wrote:
> 
> I think I know where the problem is: "# bootadm install-bootloader -P rpool " 
> installs what is needed to boot in UEFI mode and this is not possible on a 
> computer that can be dual booted with windows, even in my case where 
> openindiana and windows are on 2 different ssd. And this operation made all 
> the disks in rpool unbootable on this system. I should probably have run"# 
> bootadm install-bootloader -Mf -P rpool " to force installation of a "legacy" 
> MDB boot.
> 
> So, at this point, the only way to run openindiana on the system to fix this 
> issue is running it from the installation dvd. However, if I type zpool list 
> on that, I do not see any pool even if I boot it with reconfigure. How can I 
> install the booting stuff on the internal disk of the system from an 
> openidiana running on the installation dvd. Some versions of bootadm allow 
> specifying the device on which to install the booting  stuff, but not the 
> bootdm on openindiana.
> 
> Thanks for your help
> 
> Marc

At this time,we do not have an access to EFI runtime functions, so, we only do 
install boot loader as generic efi application (/boot/bootx64.efi). If you 
have dual/multiboot setupand have this binary from some other OS, you need to 
make backup of it first, then after bootloader install/update,you need to 
create alternate locationfor it, like /boot/illumos/ and create UEFIboot 
manager configuration in firmware setup and restore the original bootx64.efi.

The problem is without an access to EFI RT functions, we can not access/create 
efi bootmanager variables, and thats why we do use default.

Please note, every pkg update may also update the boot loader (depending on if 
the bootloader has received some change - see installboot -i).

Also, bootadm does internally use installboot, and we do install boot support 
for both UEFI and BIOS boot.

rgds,
toomas


> 
> On 6/28/22 10:38, Marc Lobelle wrote:
>> Hello, more information below on this problem
>> 
>> On 6/27/22 17:33, Marc Lobelle wrote:
>>> Hello
>>> 
>>> Thanks for your help._/I also found a good step by step guide at 
>>> https://omnios.org/info/migrate_rpool. /_(There are other ones, but over 10 
>>> years old) The only change I had to make was using the guid for the source 
>>> disk and the complete real path name to the new device ( even /dev/dsk/..., 
>>> which is a symlink did not work) in zpool attach. The need to use the GUID 
>>> is a known old bug that was supposed to have been fixed. I do not know why 
>>> I had the use the full pathname of the new disk. Maybe it is due to the 
>>> fact that the new disk was connected to a usb adaptor.
>> 
>> So what I did is
>> 
>> # zpool attach rpool 9083243097870587132 
>> /devices/pci@0,0/pci103c,807c@14/storage@d/disk@0,0:q
>> 
>> # bootadm install-bootloader -P rpool
>> 
>>> 
>>> However my bios could not boot from this usb disk when I tried to place it 
>>> in the internal slot, so I rebooted the old internal disk, with the usb 
>>> disk connected . Then I detached old internal disk and now the notebook 
>>> runs on the external disk.
>> 
>> # zpool detach rpool c6t0d0s0
>> 
>> 
>> # zpool status
>>   pool: rpool
>>  state: ONLINE
>>   scan: resilvered 30,5M in 0 days 00:00:01 with 0 errors on Mon Jun 27 
>> 16:30:25 2022
>> config:
>> 
>> NAME STATE READ WRITE CKSUM
>> rpool ONLINE   0 0 0
>> /devices/pci@0,0/pci103c,807c@14/storage@d/disk@0,0:q ONLINE 0 0 0
>> 
>> errors: No known data errors
>> 
>>   pool: szpool
>>  state: ONLINE
>>   scan: none requested
>> config:
>> 
>> NAME   STATE READ WRITE CKSUM
>> szpool ONLINE   0 0 0
>>   /dev/lofi/1  ONLINE   0 0 0
>> 
>> errors: No known data errors
>> 
>>> 
>>> Of course, my aim is to put the new inside the notebook at the place where 
>>> the old one was.
>>> 
>>> I assume that there are probably things to change in the new disk before 
>>> putting it in the notebook.
>>> 
>>> Besides, now that the old internal disk has been detached, can I still 
>>> reboot the computer with only the old internal disk
>>> 
>>> My current situation is thus that I booted from the internal disk, attached 
>>> the external one and detached the internal one (at this point everything 
>>> runs fine)
>>> 
>>> My two questions are thus:
>> 
>>> 1. Now that I have detached the disk inside the computer, can I still
>>>reboot with only this disk ? i.e. may I stop the computer, remove the 
>>> usb disk that is now the only one remaining from the mirror consisting of 
>>> the internal and the external disk. ie does the boot know that his disk is 
>>> not part of the mirror ?
>> 
>>> 2. Do I have to change something in the new disk to connect it as sata
>>>drive rather than as usb drive and boot the system from it ?
>>> 
>>> Thanks, I wait for your advice before risking to turn off the notebook
>>> 
>>> Best regar

Re: [OpenIndiana-discuss] problem replacing a disk by a bigger one

[Toomas Soome via openindiana-discuss]

hi!

Ok, first of all, there is no reason to copy zfs pool with dd. It may or may 
not work. For single disk migration, it is better to use either zpool mirror + 
zpool split, or zfs send, as zfs send or beadm create -p poolname beName. 
please note that beadm create does not mirror everything over - only BE related 
datasets, so you would need to recreate swap/dump and copy over rpool/export 
and whatever else you have there.

Now, you got error about error on reading MOS. This means, you have gptzfsboot 
running in memory, but it is in trouble - MOS is like ufs superblock - if you 
can not read it, the whole pool is not accessible.

Why this does happen? In general, there could be 2 reasons - either we can not 
read the sectors with MOS (physical IO, checksum errors, LBA too large for 
bios), or there is some sort of error and we get wrong pointer from uberblock 
in pool label. 

Wrong pointer *may* happen when pool label copies have different updates and 
most recent update is in last 2 copies of the label (should not happen with 
clean shutdown), and we fail to access those 2 last copies (they are stored at 
the end of the pool).

Please note, zfs mirror and dd only can work with same sector size disks 
(apparently your old disk has 512B). The BIOS boot only does support 512B 
sector size, for 4kn you need UEFI boot and zfs send/beadm create, as you need 
to create new pool.

I guess this is pretty much all I can add based on the information below.

thope this helps,
toomas

> On 27. Jun 2022, at 10:00, Guenther Alka  wrote:
> 
> If you want to replace the bootdisk the easiest disaster recovery method is 
> to zfs send the current BE to your datapool, then do a clean install of OI to 
> a new disk, send the BE back, activate then boot into the old BE.
> 
> For a non boot disk (with rpool) do a zpool replace poolname olddisk newdisk.
> 
> With an ongoing sync of the BE via incremental zfs send you always have an up 
> to date BE copy for recovery.
> 
> 
> Gea
> 
> Am 26.06.2022 um 23:52 schrieb Judah Richardson:
>> IIRC dd doesn't work reliably for ZFS.
>> 
>> I tried (& failed, possibly due to a bad source disk) to do this
>> previously, but I think you have to ZFS send all the datasets in the source
>> disk to the destination & then possibly do some beadm stuff on the target
>> disk.
>> 
>> Or do a default installation on the new disk, then ZFS send the
>> non-bootloader datasets from the old disk to the new.
>> 
>> 
>> On Sun, Jun 26, 2022, 16:46 Marc Lobelle  wrote:
>> 
>>> Hello
>>> 
>>> In tried to replace the ssd of my notebook running openindiana (120G) by
>>> a bigger one (1T).
>>> 
>>> I first copied the small ssd on the big one: I connected the big disk on
>>> a usb adapter, ran format to identify the two devices then
>>> 
>>> dd if=/dev/rdsk/c6t0d0p0 of=/dev/rdsk/c4t0d0p0 bs=2048K
>>> 
>>> then I replaced the small internal disk by the big one.
>>> 
>>> However, when booting, I got the following message
>>> 
>>> ZFS:i/o error - all block copies unavailable
>>> 
>>> ZFS: Can't read MOS of pool rpool
>>> 
>>> Can't find /boot/loader
>>> 
>>> Can't find /boot/zfsloader
>>> 
>>> illumos/x86 boot
>>> 
>>> Default: /boot/loader
>>> 
>>> boot:
>>> 
>>> if I type , I get
>>> 
>>> Can't find /boot/loader
>>> 
>>> illumos/x86 boot
>>> 
>>> Default: /boot/loader
>>> 
>>> boot:
>>> 
>>> How can I fix this ? (without reinstalling everything if possible;-)
>>> (after that I plan of course to grow the fs to the whole disk)
>>> 
> 
> 
> ___
> 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] dell 15810 bricked after latest update

[Toomas Soome via openindiana-discuss]

> On 19. Jun 2022, at 20:24, irixuzer  wrote:
> 
> Well I tried a straight dvi cable, no joy. ( vga was useless)
> 
> With the hard drive disconnected I get the UEFI, I think, I’m using a mouse 
> when navigating in the sucker……
> 
> Other people have noticed online that they also couldn’t get past the 
> manufacturer logo — when their hard drive had died! Could this be a dead hard 
> drive?
> 

It could. The question is, does this defect also appear when you have HDD 
connected but also cd or usb stick. This kind of test assumes removable device 
being higher priority than hdd and the bios probing the hdd would survive the 
bad disk….

rgds,
toomas

> -Matt
> 
> 
>> On Jun 19, 2022, at 6:10 AM, Toomas Soome via openindiana-discuss 
>> > <mailto:openindiana-discuss@openindiana.org>> wrote:
>> 
>> 
>> 
>>> On 19. Jun 2022, at 15:28, s...@pandora.be  wrote:
>>> 
>>> 
>>> I have no problem booting UEFI with Dell Precision 
>>> 
>>> http://docs.openindiana.org/community-hcl/systems/#workstations
>>> 
>>> I originally had BIOS 1.2 and updated without problems to BIOS 1.8. I can 
>>> boot UEFI.
>>> (thanks to the Illumos and OpenIndiana developers who make this possible, 
>>> by the way).
>>> 
>>> In my case the integrated graphics Intel UHD 630 does NOT work,
>>> and just a thought : the Dell BIOS has a concept of "primary display",
>>> which is the display adapter that it has to use for the BIOS I think
>>> (sorry, this may be an incorrect description, but the Dell docs are unclear 
>>> about,
>>> primary display is for their BIOS, and they claim the option is only 
>>> relevant for Microsoft Windows).
>>> 
>>> So what may be happening (I have no idea), is that you get a "black screen 
>>> of death",
>>> because the system is displaying the BIOS on a different graphics adapter 
>>> than the one you think it should be using.
>>> 
>>> For systems with many graphics cards and many monitors attached, this may 
>>> be a problem,
>>> I remember that there was a report a year ago of someone who explicitely 
>>> some sort of DP (display port terminator) to make the system think a 
>>> monitor was attached to a specific DP (display port).
>>> 
>>> Is your system using VGA, DP, HDMI ? How many monitors ?
>>> 
>>> Regards,
>>> David Stes
>> 
>> 
>> hi!
>> 
>> Lets try t establish the facts there.
>> 
>> 1. when powered on, can you enter bios setup?
>> 2. Is it set up to boot with UEFI or BIOS? If it is using UEFI, can it be 
>> set to boot with BIOS (UEFI CSM)?
>> 
>> Yes, with UEFI it is possible we do get GOP handle which does not show us 
>> output. To understand if this might be the case, we would need to check 
>> exactly which version of boot loader is installed in ESP (that is, assuming 
>> this system does UEFI boot). If BIOS boot is available, it should be boot 
>> via BIOS boot, and then you can use installboot -i to detect the loader 
>> version.
>> 
>> rgds,
>> toomas
>> 
>> 
>>> 
>>> - Op 19 jun 2022 om 1:36 schreef irixuzer irixu...@gmail.com:
>>> 
>>>> I was finally able to enter BIOS. I unplugged the hdd, and booted without a
>>>> drive. I went through and selected it to use UEFI instead of legacy, and 
>>>> setup
>>>> time, date and went back to defaults . I plugged in the hard drive and got 
>>>> the
>>>> black screen of death even when trying to access the BIOS. This is progress
>>>> though I guess.
>>>> 
>>>> Still not able to boot an os.
>>>> 
>>>> -Matt
>>>> 
>>>>> On Jun 17, 2022, at 12:37 PM, Judah Richardson 
>>>>> wrote:
>>>>> 
>>>>> Dell has a rescue live diagnostic USB on their support site that I've used
>>>>> before:
>>>>> https://www.dell.com/support/kbdoc/en-us/000145519/how-to-create-a-bootable-usb-flash-drive-using-dell-diagnostic-deployment-package-dddp
>>>>> 
>>>>> Might be helpful.
>>>>> 
>>>>> If that doesn't work, do this:
>>>>> 
>>>>> 
>>>>> 1. Disconnect everything from the machine, including the power cable
>>>>> 2. Press the power button for 30 seconds
>>>>> 3. Open the case
>>>>> 4. Unseat the motherboard C

Re: [OpenIndiana-discuss] dell 15810 bricked after latest update

[Toomas Soome via openindiana-discuss]

> On 19. Jun 2022, at 15:28, s...@pandora.be  wrote:
> 
> 
> I have no problem booting UEFI with Dell Precision 
> 
> http://docs.openindiana.org/community-hcl/systems/#workstations
> 
> I originally had BIOS 1.2 and updated without problems to BIOS 1.8.   I can 
> boot UEFI.
> (thanks to the Illumos and OpenIndiana developers who make this possible, by 
> the way).
> 
> In my case the integrated graphics Intel UHD 630 does NOT work,
> and just a thought : the Dell BIOS has a concept of "primary display",
> which is the display adapter that it has to use for the BIOS I think
> (sorry, this may be an incorrect description, but the Dell docs are unclear 
> about,
> primary display is for their BIOS, and they claim the option is only relevant 
> for Microsoft Windows).
> 
> So what may be happening (I have no idea), is that you get a "black screen of 
> death",
> because the system is displaying the BIOS on a different graphics adapter 
> than the one you think it should be using.
> 
> For systems with many graphics cards and many monitors attached, this may be 
> a problem,
> I remember that there was a report a year ago of someone who explicitely some 
> sort of DP (display port terminator) to make the system think a monitor was 
> attached to a specific DP (display port).
> 
> Is your system using VGA, DP, HDMI ? How many monitors ?
> 
> Regards,
> David Stes


hi!

Lets try t establish the facts there.

1. when powered on, can you enter bios setup?
2. Is it set up to boot with UEFI or BIOS? If it is using UEFI, can it be set 
to boot with BIOS (UEFI CSM)?

Yes, with UEFI it is possible we do get GOP handle which does not show us 
output. To understand if this might be the case, we would need to check exactly 
which version of boot loader is installed in ESP (that is, assuming this system 
does UEFI boot). If BIOS boot is available, it should be boot via BIOS boot, 
and then you can use installboot -i to detect the loader version.

rgds,
toomas


> 
> - Op 19 jun 2022 om 1:36 schreef irixuzer irixu...@gmail.com:
> 
>> I was finally able to enter BIOS.  I unplugged the hdd, and booted without a
>> drive.  I went through and selected it to use UEFI instead of legacy, and 
>> setup
>> time, date and went back to defaults .  I plugged in the hard drive and got 
>> the
>> black screen of death even when trying to access the BIOS.  This is progress
>> though I guess.
>> 
>> Still not able to boot an os.
>> 
>> -Matt
>> 
>>> On Jun 17, 2022, at 12:37 PM, Judah Richardson 
>>> wrote:
>>> 
>>> Dell has a rescue live diagnostic USB on their support site that I've used
>>> before:
>>> https://www.dell.com/support/kbdoc/en-us/000145519/how-to-create-a-bootable-usb-flash-drive-using-dell-diagnostic-deployment-package-dddp
>>> 
>>> Might be helpful.
>>> 
>>> If that doesn't work, do this:
>>> 
>>> 
>>>  1. Disconnect everything from the machine, including the power cable
>>>  2. Press the power button for 30 seconds
>>>  3. Open the case
>>>  4. Unseat the motherboard CMOS battery
>>>  5. Wait 30 seconds
>>>  6. Reseat the motherboard CMOS battery
>>>  7. Close the case
>>>  8. Reconnect the power cable, keyboard, mouse, and a single monitor
>>>  9. Attempt to boot into the Dell Diagnostic USB linked to above
>>> 
>>> 
>>> 
>>> On Fri, Jun 17, 2022 at 2:31 PM irixuzer  wrote:
>>> 
 
 
 
 
 
 
 John, Gary, and everyone,
 
 I’ve tried f12- it tells me that it’s setting up a one time boot menu-
 then black screen of death.  I had used
 
 $ sudo pkg update -v
 
 afterwards it told me that I needed to reboot.
 
 I shutdown via the MATE menu.
 
 When I tried to boot again, I keep getting the Dell logo screen then a
 black screen of death.
 
 Could trying a vga cable instead of the dp/dvi adapter cable i’m currently
 using?  I have a NVIDIA Quadro K620.
 
 -Matt
 
 
 
> On Jun 16, 2022, at 5:01 PM, Gary Mills  wrote:
> 
> On Tue, Jun 14, 2022 at 06:15:28PM -0700, irixuzer wrote:
> 
>> I’ve been updating and going since 2019 *I think*.  Now after the
>> latest update, my Dell t5810 is bricked I cannot go past the dell
>> screen,
> 
> What did you update, OI or the BIOS?
> 
>> I’ve tried to downgrade the bios,
> 
> Many systems no longer support BIOS downgrades.
> 
>> no luck cannot go past the
>> dell screen no matter which f key I push, Rescatux is useless.
> 
> 
> --
> -Gary Mills-  -refurb--Winnipeg, Manitoba,
 Canada-
> 
> ___
> 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/listi

Re: [OpenIndiana-discuss] What is the rpool/dump fs?

[Toomas Soome via openindiana-discuss]

> On 12. May 2022, at 14:59, hput via openindiana-discuss 
>  wrote:
> 
> Toomas Soome via openindiana-discuss
>  writes:
> 
> 
>>> Sorry for the lammer question.  Not finding the info that explains it
>>> easily.  Some with just a pointer, url or the like.
>>> 
>>> What does it do?  How should I handle it when replicating an oi
>>> backup server... no backups on it at the moment so thought I might
>>> replicate rpool .. I am excepting rpool/swap and possibly rpool/dump
>>> Depending how important to the other zfs fs it is.
> 
> Toomas S. wrote:
> 
>> See man dumpadm.
> 
> Well I went thru it after your comment but I don't feel much wiser for
> it.
> 
> Off hand it seems to not be important for a replication backup to
> include.  Only if there has been a crash dump of concern.  Even then
> still seems unneccesary for job of recreating a healthy OS from
> backup.  Still it is really not much data.  In my case its reported
> 6.64 GB, so might as well include in a replication backup eh?
> 

This is zvol for storing kernel dump in case of panic. You do not need to store 
it’s content, but in case of system restore, you want to restore the zvol (that 
is, document the zvol size and volblocksize). Same does apply to rpool/swap - 
no point to backup it’s content, but do record the size and volblocksize for 
the case of system restore.

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

Re: [OpenIndiana-discuss] What is the rpool/dump fs?

[Toomas Soome via openindiana-discuss]

See man dumpadm.

Sent from my iPhone

> On 12. May 2022, at 06:49, hput via openindiana-discuss 
>  wrote:
> 
> Sorry for the lammer question.  Not finding the info that explains it
> easily.  Some with just a pointer, url or the like.
> 
> What does it do?  How should I handle it when replicating an oi
> backup server... no backups on it at the moment so thought I might
> replicate rpool .. I am excepting rpool/swap and possibly rpool/dump
> Depending how important to the other zfs fs it is.
> 
> 
> ___
> 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] Problems with some zfs fs unable to mount after shutdown

[Toomas Soome via openindiana-discuss]

> On 14. Jan 2022, at 06:32, hput via openindiana-discuss 
>  wrote:
> 
> Flemming Dalsgaard  writes:
> 
>> The commands
>> zfs create -omountpoint=/exportp0/export
>> zfs create -omountpoint=/export/home   p0/export/home
>> zfs create -omountpoint=/export/home/USER  p0/export/home/USER
>> 
>> Should be sufficient to make the /export/home/USER
>> so you should not pre create the involved folders, zfs take care of that it
>> self.
> 
> [...]
> 
> exactly what I did, and I did not precreate anything.  Not sure where
> that came from. I just ran the zfs create commands and it all mounted
> as expected And once again following this mornings boot up of host
> and then vm in question...
> 
>>> zfs create -omountpoint=/exportp0/export
>>> zfs create -omountpoint=/export/home   p0/export/home
>>> zfs create -omountpoint=/export/home/USER  p0/export/home/USER
> 
> 
> It fails to mount those filesystems and drops into a console login on
> reboot.
> 
> I needed a reboot for host OS due to certain updates that apparently
> need a reboot.  And then booting the oi vm
> 
> 
> I login as root and run:
> 
> zfs mount p0/export
> zfs mount p0/export/home
> zfs mount p0/export/home/reader
> 
> And they all mount fine.
> 
> But yet I'm stuck with a console to work in ... pretty sure if I
> reboot the vm the same thing will happen.
> It seem the OS doesn't mount them from the bottom up or something
> What is causing the failure?
> 
> Attempting to `startx' from console does not work at first but finally
> produces a very primitive X desktop, that near as I can tell is less
> usable for work than the OI console (which is saying something) 
> 
> How can I go into X from the console login.. Logging out does nothing.
> Apparently the only recourse is to reboot the vm again.  Doing that
> now:
> 
> First thing, I see `unable to read pool p0' as the shutdown starts to
> happen.  But, glory be.  With another 12-14 minutes lost to the ether,
> The bootup completed and didn't fail to mount p0/export/home/reader
> 

First thing to remember - command ‘zfs mount’ will fail if mountpoint is not 
empty. This means, if you add new storage for /export, you need to make sure 
the original is not present (rpool/export dataset).

Also, make sure you are not creating cross mounts from different pools/datasets.

And finally, a small nit - if you create /export/home/username tree, your 
dataset tree should look like /export/home/username, and this means, you 
only need to set mountpoint for/export, rest will follow the hierarchy. 
This can help to avoid cross mounts and populated mount points…

rgds,
toomas



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

Re: [OpenIndiana-discuss] Possible to update from 2021.0430 to 2021.1130 with pkg tool?

[Toomas Soome via openindiana-discuss]

> On 4. May 2022, at 11:33, Maurilio Longo via openindiana-discuss 
>  wrote:
> 
> Toomas,
> 
> I'm not aware of any method to update to an exact point in time, which would 
> be a usefull thing when you have really old systems to update.


For this you can use full package name with version (and timestamp) included, 
also this one reason to have “meta” packages such as “entire”. Except that 
unfortunately openindiana repository seems to have stopped updating “entire”…  
So, other option is to try to some core package, such as SUNWcs.

For really early openindiana updates we did need to switch to middle version(s) 
first, but I’m not sure that option is still available (repo size was being a 
problem at some point, for same reason Oracle did drop old Solaris 11 versions;)

rgds,
toomas

> 
> You update your system to the current packages which are newer than 2021.1130
> 
> Being that Hipster is a rolling relase type of OS, you can end up with 
> different systems even if you pkg update them in the same day but in 
> different moments, as far as I know.
> 
> Regards.
> 
> Maurilio
> 
>> Il 04/05/2022 00:01 Toomas Soome via openindiana-discuss 
>>  ha scritto:
>> 
>> 
>>> On 9. Jan 2022, at 06:29, hput via openindiana-discuss 
>>>  wrote:
>>> 
>>> Can one update from one release to another with just the pkg tool.
>>> 
>>> When I run `pkg update' on oi/hipster installed from 2021.0430 does
>>> that install the pkgs that are current in 2021.1130?
>>> 
>> 
>> Yes, thats the purpose of pkg.
>> 
>> rgds,
>> toomas
>> ___
>> 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] Actions unreasonably slow 2021.0430

[Toomas Soome via openindiana-discuss]

> On 4. May 2022, at 15:33, Pierfrancesco Caci  wrote:
> 
> I have a similar setup (host is Debian with KVM), both openindiana and
> omniosce are slower at boot and shutdown than a Linux VM. Omnios is
> marginally faster than OI. openbsd and freebsd are somewhere in between
> Linux and OI. I don't see appreciable differences while using the various
> os.
> 

This all depends on how do you measure the boot process. By console login? 

tsoome@beastie:/code/illumos-gate$ svcs -d console-login | sort -u
disabled   apr_30   svc:/system/auditd:default
online apr_30   svc:/milestone/sysconfig:default
online apr_30   svc:/system/console-login:default
online apr_30   svc:/system/filesystem/minimal:default
online apr_30   svc:/system/identity:node
online apr_30   svc:/system/utmp:default
online apr_30   svc:/system/vtdaemon:default

and

tsoome@beastie:/code/illumos-gate$ svcs -d lightdm
STATE  STIMEFMRI
online apr_30   svc:/application/opengl/ogl-select:default
online apr_30   svc:/application/desktop-cache/gio-module-cache:default
online apr_30   svc:/system/dbus:default
online apr_30   svc:/milestone/sysconfig:default
online apr_30   svc:/system/utmp:default
online apr_30   svc:/application/font/fc-cache:default
online apr_30   svc:/system/hal:default
online apr_30   svc:/system/filesystem/local:default
online apr_30   svc:/application/x11/x11-init:default
online apr_30   svc:/system/consolekit:default
online apr_30   svc:/milestone/multi-user:default

See, the console-login depends on few services and will be running pretty 
quick; lightdm depends on multi-user milestone, which means, everything else 
will bestarted before gui login appears.

So, if you want to compare apples to apples, (oi and omnios), disable the 
lightdm;)

Why lightdm depends on multi-user is another (old) topic.

rgds,
toomas 


> On Wed, 4 May 2022, 00:25 hput via openindiana-discuss, <
> openindiana-discuss@openindiana.org> wrote:
> 
>> Host OS: ubuntu-21.10 running zfs
>> Vbox version: 6.1.30
>> vm OS Openindiana/hipster New install of 2021.0430 with all updates as
>> of Jan 9
>> vm has 12.288 GB or ram
>> ---   ---   ---=---   ---   ---
>> 
>> I can't help but notice what feels like unreasonable waits for such things
>> as bootup and shutdown
>> 
>> At a rough guess it would be something like 300 percent slower
>> compared to other VBox vm running ubuntu on zfs.  With 9GB ram.
>> 
>> Have others noticed excessive time for such processes?
>> 
>> 
>> ___
>> 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] Possible to update from 2021.0430 to 2021.1130 with pkg tool?

[Toomas Soome via openindiana-discuss]

> On 9. Jan 2022, at 06:29, hput via openindiana-discuss 
>  wrote:
> 
> Can one update from one release to another with just the pkg tool.
> 
> When I run `pkg update' on oi/hipster installed from 2021.0430 does
> that install the pkgs that are current in 2021.1130?
> 

Yes, thats the purpose of pkg.

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

Re: [OpenIndiana-discuss] OI Hipster becomes unreachable over network after a certain length of uptime

[Toomas Soome via openindiana-discuss]

> On 13. Apr 2022, at 22:32, s...@pandora.be  wrote:
> 
> 
> - Op 13 apr 2022 om 21:13 schreef Judah Richardson 
> judahrichard...@gmail.com:
> 
>> Speaking as an experimental user (read: OI is not my daily driver) who
>> acknowledges OI inherits a lot of internal functionality from a
>> server/workstation distro (openSolaris): all of this strikes me as
>> anachronistically(?) complicated for something that should by default
>> expect to get an IP address lease from any DHCP server on a network to
>> which it's connected.
> 
> It's not really anachronistic.  It's just that there is an enormous amount of 
> history behind the networking stack and OpenIndiana is the kind of operating 
> system distribution where users appreciate "old conventions" for configuring 
> the network.
> 

This is just bad excuse to have mess about how you configure your network. 

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

Re: [OpenIndiana-discuss] usb key installer

[Toomas Soome via openindiana-discuss]

> On 8. Apr 2022, at 15:34, Gabriele Bulfon  wrote:
> 
> I will doublecheck this, but I discovered that burning the usb key through an 
> illumos phyisical machine with this command:
>  
> /usr/bin/dd if=./XStream-Storage-Chandra-Install-February-2022.usb 
> of=/dev/rdsk/c14t0d0p0 bs=4194304
>  
> it works great.
> I just don't understand why it never works by making it from windows machines.

I guess, that may get revealed with those diagnostics commands. The first 
question would be, is there any sort of “virus” protection, preventing writes 
to MBR?

rgds,
toomas

>  
> Gabriele
>  
>  
> Sonicle S.r.l. : http://www.sonicle.com <http://www.sonicle.com/>
> Music: http://www.gabrielebulfon.com <http://www.gabrielebulfon.com/>
> eXoplanets : https://gabrielebulfon.bandcamp.com/album/exoplanets 
> <https://gabrielebulfon.bandcamp.com/album/exoplanets>
>  
> 
> 
> 
> ------
> 
> Da: Toomas Soome 
> A: Discussion list for OpenIndiana 
> Cc: Gabriele Bulfon 
> Data: 8 aprile 2022 12.16.38 CEST
> Oggetto: Re: [OpenIndiana-discuss] usb key installer
> 
> connect stick to illumos host
> echo | format -e, see which device is your stick
> 
> mdb /dev/rdsk/devicenamep0  — note the p0 at the ned of the name
> ::load disk_label
> ::mbr
> 
> what does ::mbr output?
> 
> fstyp /dev/rdsk/disknames1 — note s1 at the end of the name, it should be 
> your illumos slice (with ufs)
> installboot -i /dev/rdsk/disknames1 — note s1 at the end of the name, it 
> should be your illumos slice (with ufs)
> 
> rgds,
> toomas
> 
> > On 8. Apr 2022, at 12:59, Gabriele Bulfon via openindiana-discuss 
> >  wrote:
> > 
> > Hi, I tried using the OI 2021 usb installer with the suggested 
> > Win32DiskImage, but the usb stick stops with "Can't find boot loader".
> > It used to work in the past with older releases.
> > Same is happening to us with our XStreamOS distro, since 2021 usb files. 
> > Any 2018 usb file works fine with same key and same software.
> >  
> > Anyone had this problem?
> > Any clue?
> > 
> > Thanks,
> > Gabriele
> >  
> >  
> > Sonicle S.r.l. : http://www.sonicle.com
> > Music: http://www.gabrielebulfon.com
> > eXoplanets : https://gabrielebulfon.bandcamp.com/album/exoplanets
> >  
> > 
> > ___
> > 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] usb key installer

[Toomas Soome via openindiana-discuss]

connect stick to illumos host
echo | format -e, see which device is your stick

mdb /dev/rdsk/devicenamep0  — note the p0 at the ned of the name
::load disk_label
::mbr

what does ::mbr output?

fstyp /dev/rdsk/disknames1 — note s1 at the end of the name, it should be your 
illumos slice (with ufs)
installboot -i /dev/rdsk/disknames1 — note s1 at the end of the name, it should 
be your illumos slice (with ufs)

rgds,
toomas

> On 8. Apr 2022, at 12:59, Gabriele Bulfon via openindiana-discuss 
>  wrote:
> 
> Hi, I tried using the OI 2021 usb installer with the suggested 
> Win32DiskImage, but the usb stick stops with "Can't find boot loader".
> It used to work in the past with older releases.
> Same is happening to us with our XStreamOS distro, since 2021 usb files. Any 
> 2018 usb file works fine with same key and same software.
>  
> Anyone had this problem?
> Any clue?
> 
> Thanks,
> Gabriele
>  
>  
> Sonicle S.r.l. : http://www.sonicle.com
> Music: http://www.gabrielebulfon.com
> eXoplanets : https://gabrielebulfon.bandcamp.com/album/exoplanets
>  
> 
> ___
> 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] io errors in rpool, was surprising error when I try to install a package

[Toomas Soome via openindiana-discuss]

> On 10. Mar 2022, at 16:13, Bob Friesenhahn  
> wrote:
> 
> On Thu, 10 Mar 2022, Toomas Soome via openindiana-discuss wrote:
>>> rpool/ROOT/openindiana-2022:02:16@2022-03-04-09:38:53:/var/pkg/state/known/catalog.dependency.C
>>> rpool/ROOT/openindiana-2022:02:16@install:/usr/share/doc/dbus/api/group__DBusMessageInternals.html
>>> rpool/ROOT/openindiana-2022:02:16@install:/usr/share/doc/libsigc++-2.0/reference/html/inherit_graph_24.png
>>> rpool/ROOT/openindiana-2022:02:16@install:/usr/share/doc/libsigc++-2.0/reference/html/modules.html
>>> Loosing a few blocks on a 1 TB ssd is acceptable if the OS can avoid using 
>>> these faulty blocks in the future. What does zpool do if I do a zpool 
>>> clear: the faults will disappear from the status but will the faulty blocs 
>>> be avoided henceforth ?
>>> 
>>> The corrupted files are lost but, if I do "pkg refresh --full; pkg update 
>>> -v", I assume they will be replaced.
>>> 
>>> However if the faulty blocks are not removed from the list of usable 
>>> blocks, the faults will happen again and the drive must be considered as 
>>> lost and to be replaced
>> 
>> 
>> This is basically 'replace ssd and restore from backup’ case, I’m afraid.
> 
> Why would that be?  It does not seem that those files are important. It is 
> true that the listed files are lost/corrupted but if they are overwritten 
> with repaired files, then new blocks would be used.
> 

physical read errors while the scrub is still not done (more is to be expected).

> The main problem could be that it is possible that the SSD is on a permanent 
> downhill trend and more issues will occur later.
> 
> The corrupted files could also be a product of RAM memory which lacks ECC 
> protection and has taken a hit.  A thorough memory test is in order to make 
> sure that all is ok.
> 
> It seems to me that clear is definitely worth trying but it is important to 
> consider this to be an early warning of possible doom.

Yep. If anything, keep important files backed…

rgds,
toomas

> 
> Bob
> -- 
> Bob Friesenhahn
> bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
> GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
> Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt
> ___
> 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] io errors in rpool, was surprising error when I try to install a package

[Toomas Soome via openindiana-discuss]

> On 10. Mar 2022, at 12:09, Marc Lobelle  wrote:
> 
> Hi Toomas,
> 
> Indeed I have problems with the local storage. This notebook has a single ssd 
> drive (rpool) and scrubbing it finds unrecoverable errors
> 
> ml@mosquito:/export/home/ml# zpool status -v
>   pool: rpool
>  state: DEGRADED
> status: One or more devices has experienced an error resulting in data
> corruption.  Applications may be affected.
> action: Restore the file in question if possible.  Otherwise restore the
> entire pool from backup.
>see: http://illumos.org/msg/ZFS-8000-8A
>   scan: scrub in progress since Wed Mar  9 18:41:08 2022
> 141G scanned at 179M/s, 31,0G issued at 39,2M/s, 142G total
> 0 repaired, 21,91% done, 0 days 00:48:07 to go
> config:
> 
> NAMESTATE READ WRITE CKSUM
> rpool   DEGRADED 2 0 3
>   c6t0d0s0  DEGRADED 2 0 6  too many errors
> 
> errors: Permanent errors have been detected in the following files:
> 
> rpool/ROOT/openindiana-2022:02:16:<0x881c0>
> rpool/dump:<0x1>
> rpool/swap:<0x1>
> /export/home/ml/.local/share/Trash/files/Capture du 2022-03-03 
> 15-11-12.png
> rpool/export/home/ml:<0x147d>
> rpool/ROOT/openindiana-2022:02:16@2022-03-04-09:38:53:/var/pkg/state/known/catalog.summary.C
> rpool/ROOT/openindiana-2022:02:16@2022-03-04-09:38:53:/var/pkg/state/known/catalog.dependency.C
> rpool/ROOT/openindiana-2022:02:16@install:/usr/share/doc/dbus/api/group__DBusMessageInternals.html
> rpool/ROOT/openindiana-2022:02:16@install:/usr/share/doc/libsigc++-2.0/reference/html/inherit_graph_24.png
> rpool/ROOT/openindiana-2022:02:16@install:/usr/share/doc/libsigc++-2.0/reference/html/modules.html
> Loosing a few blocks on a 1 TB ssd is acceptable if the OS can avoid using 
> these faulty blocks in the future. What does zpool do if I do a zpool clear: 
> the faults will disappear from the status but will the faulty blocs be 
> avoided henceforth ?
> 
> The corrupted files are lost but, if I do "pkg refresh --full; pkg update 
> -v", I assume they will be replaced.
> 
> However if the faulty blocks are not removed from the list of usable blocks, 
> the faults will happen again and the drive must be considered as lost and to 
> be replaced


This is basically 'replace ssd and restore from backup’ case, I’m afraid.

rgds,
toomas



> 
> On 3/9/22 09:22, Toomas Soome via openindiana-discuss wrote:
>>> On 9. Mar 2022, at 10:15, Marc Lobelle  wrote:
>>> 
>>> Hello,
>>> 
>>> I got a surprising error when trying to install packages (any package, even 
>>> xeyes) on one of my computers running openindiana: *Error encountered while 
>>> retrieving data from: [Errno 5] I/O error.*
>>> 
>>> Anybody knows what to do ?
>>> 
>>> Thanks and best regards
>>> 
>>> Marc
>> there are two possible causes, either it is some sort of network issue 
>> (truss -f pkg…. and see what will get EIO), or it is issue with local 
>> storage (zpool scrub?).
>> 
>> rgds,
>> toomas
>> 
>> 
>> ___
>> 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] surprising error when I try to install a package

[Toomas Soome via openindiana-discuss]

> On 9. Mar 2022, at 10:15, Marc Lobelle  wrote:
> 
> Hello,
> 
> I got a surprising error when trying to install packages (any package, even 
> xeyes) on one of my computers running openindiana: *Error encountered while 
> retrieving data from: [Errno 5] I/O error.*
> 
> Anybody knows what to do ?
> 
> Thanks and best regards
> 
> Marc

there are two possible causes, either it is some sort of network issue (truss 
-f pkg…. and see what will get EIO), or it is issue with local storage (zpool 
scrub?).

rgds,
toomas


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

Re: [OpenIndiana-discuss] Zstandard vs lz4

[Toomas Soome via openindiana-discuss]

> On 15. Jan 2022, at 05:13, hput via openindiana-discuss 
>  wrote:
> 
> How do I use Zstandard compression with openindiana/hipster?
> 


zstd command is there, but we do not yet have zstd support in zfs.

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

Re: [OpenIndiana-discuss] gcc, binutils

[Toomas Soome via openindiana-discuss]

Latest is gcc-10.

Sent from my iPhone

> On 14. Nov 2021, at 17:31, Socat Project  wrote:
> 
> Hello,
> 
> I have just installed OI-hipster-minimal-20210430 in a KVM. Now I want
> to compile some C code, but I fail to install gcc.
> 
> pkg install gcc does not help much; my best result was:
> 
> # pkg install pkg:/developer/gcc-8
> Creating Plan (Solver setup): |
> pkg install: No matching version of developer/gcc-8 can be installed:
>   Reject:  pkg://openindiana.org/developer/gcc-8@8.4.0-2020.0.1.2
>   Reason:  No version matching 'require' dependency developer/gnu-binutils 
> can be installed
> 
> Reject:  pkg://openindiana.org/developer/gnu-binutils@2.37-2020.0.1.1
> Reason:  This version is excluded by installed incorporation 
> consolidation/userland/userland-incorporation@0.5.11-2020.0.1.14081
> 
> 
> Please help!
> 
> - Gerhard
> 
> 
> ___
> 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] how to install open indiana on a single partition

[Toomas Soome via openindiana-discuss]

> On 14. Oct 2021, at 22:32, Coalson, Timothy Scott (S&T-Student) 
>  wrote:
> 
> This page says in a couple places that UEFI isn't supported, if it only means 
> the installer media, it should be rephrased:
> 
> http://docs.openindiana.org/handbook/getting-started/#creating-a-hipster-usb-drive
>  
> <http://docs.openindiana.org/handbook/getting-started/#creating-a-hipster-usb-drive>
> 
> Tim
> 


That section is outdated and should be rephrased, UEFI is supported with secure 
boot switched off.

rgds,
toomas

> 
> From: Toomas Soome via openindiana-discuss 
>  <mailto:openindiana-discuss@openindiana.org>>
> Sent: Thursday, October 14, 2021 12:13 PM
> To: s...@pandora.be <mailto:s...@pandora.be>  <mailto:s...@telenet.be>>
> Cc: Toomas Soome mailto:tso...@me.com>>; Discussion list for 
> OpenIndiana  <mailto:openindiana-discuss@openindiana.org>>
> Subject: Re: [OpenIndiana-discuss] how to install open indiana on a single 
> partition
>  
> WARNING: This message has originated from an External Source. This may be a 
> phishing expedition that can result in unauthorized access to our IT System. 
> Please use proper judgment and caution when opening attachments, clicking 
> links, or responding to this email.
> 
> > On 14. Oct 2021, at 19:58, s...@pandora.be  wrote:
> >
> >
> >>
> >> We certainly do support UEFI
> >
> > I can confirm this.  I installed OI 2021.04 on a system with UEFI and it 
> > works.
> 
> 
> I am the one to be blamed for this;) So, if it does not, just drop a note…
> 
> rgds,
> toomas
> 
> >
> > As the docs explain the option "install into a partition" has some 
> > limitations.  See the docs at:
> >
> > https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.openindiana.org%2Fhandbook%2Fgetting-started%2F%23installing-openindiana&data=04%7C01%7Ctsc5yc%40mst.edu%7Cbc82bc61b87d48e4dbe508d98f35faac%7Ce3fefdbef7e9401ba51a355e01b05a89%7C0%7C0%7C637698284271938598%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jmGDXuUUsU9Ta9xjbn%2Fb8Qecs7dlPE8Cie83G97pIbQ%3D&reserved=0
> >  
> > <https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.openindiana.org%2Fhandbook%2Fgetting-started%2F%23installing-openindiana&data=04%7C01%7Ctsc5yc%40mst.edu%7Cbc82bc61b87d48e4dbe508d98f35faac%7Ce3fefdbef7e9401ba51a355e01b05a89%7C0%7C0%7C637698284271938598%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jmGDXuUUsU9Ta9xjbn%2Fb8Qecs7dlPE8Cie83G97pIbQ%3D&reserved=0>
> >
> > Regards,
> > David Stes
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org 
> <mailto:openindiana-discuss@openindiana.org>
> https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenindiana.org%2Fmailman%2Flistinfo%2Fopenindiana-discuss&data=04%7C01%7Ctsc5yc%40mst.edu%7Cbc82bc61b87d48e4dbe508d98f35faac%7Ce3fefdbef7e9401ba51a355e01b05a89%7C0%7C0%7C637698284271948592%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=O54ZFpbKEWXFBKy499pbEcSVQT%2Bp33fNrI4IeK26DPU%3D&reserved=0
>  
> <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fopenindiana.org%2Fmailman%2Flistinfo%2Fopenindiana-discuss&data=04%7C01%7Ctsc5yc%40mst.edu%7Cbc82bc61b87d48e4dbe508d98f35faac%7Ce3fefdbef7e9401ba51a355e01b05a89%7C0%7C0%7C637698284271948592%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=O54ZFpbKEWXFBKy499pbEcSVQT%2Bp33fNrI4IeK26DPU%3D&reserved=0>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] how to install open indiana on a single partition

[Toomas Soome via openindiana-discuss]

> On 14. Oct 2021, at 19:58, s...@pandora.be  wrote:
> 
> 
>> 
>> We certainly do support UEFI
> 
> I can confirm this.  I installed OI 2021.04 on a system with UEFI and it 
> works.


I am the one to be blamed for this;) So, if it does not, just drop a note…

rgds,
toomas

> 
> As the docs explain the option "install into a partition" has some 
> limitations.  See the docs at:
> 
> http://docs.openindiana.org/handbook/getting-started/#installing-openindiana
> 
> Regards,
> David Stes


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

Re: [OpenIndiana-discuss] how to install open indiana on a single partition

[Toomas Soome via openindiana-discuss]

> On 14. Oct 2021, at 02:40, Coalson, Timothy Scott (S&T-Student) 
>  wrote:
> 
> I haven't tried to do a partition setup with openindiana, and as far as I 
> know, the bootloader it uses doesn't support UEFI.
> 
> Tim
> 

We certainly do support UEFI, but with few exceptions - we do not (yet) support 
secure boot - it should be switched off. And secondly, we do not currently have 
way to set EFI boot manager variables, so the boot program is installed as 
generic binary on ESP/efi/boot/bootx64.efi. If there are multiple systems, one 
would need to create vendor tree on ESP, copy bootx64.efi there and set up UEFI 
boot manager variables accordingly.

rgds,
toomas

> 
> From: Mario Marietto mailto:marietto2...@gmail.com>>
> Sent: Wednesday, October 13, 2021 6:10 PM
> To: Discussion list for OpenIndiana  <mailto:openindiana-discuss@openindiana.org>>
> Subject: Re: [OpenIndiana-discuss] how to install open indiana on a single 
> partition
> 
> WARNING: This message has originated from an External Source. This may be a 
> phishing expedition that can result in unauthorized access to our IT System. 
> Please use proper judgment and caution when opening attachments, clicking 
> links, or responding to this email.
> 
> Is there something that I should do to get the bootloader (better if it is
> UEFI) to recognize the other partition ?
> 
> Il giorno gio 14 ott 2021 alle ore 01:07 Mario Marietto <
> marietto2...@gmail.com> ha scritto:
> 
>> Unfortunately I don't have any more disk and I'm out of money :(
>> 
>> Il giorno gio 14 ott 2021 alle ore 00:54 Coalson, Timothy Scott
>> (S&T-Student)  ha scritto:
>> 
>>> Would adding another internal disk (or maybe even external) and
>>> installing to that not be satisfactory?  That would make the step of
>>> getting a bootloader to recognize the other partition entirely optional, as
>>> you could just have the bios boot from the other disk.
>>> 
>>> Tim
>>> 
>>> 
>>> From: Mario Marietto 
>>> Sent: Wednesday, October 13, 2021 2:02 PM
>>> To: Discussion list for OpenIndiana 
>>> Subject: Re: [OpenIndiana-discuss] how to install open indiana on a
>>> single partition
>>> 
>>> WARNING: This message has originated from an External Source. This may be
>>> a phishing expedition that can result in unauthorized access to our IT
>>> System. Please use proper judgment and caution when opening attachments,
>>> clicking links, or responding to this email.
>>> 
>>> For me its ok to use ZFS at the end,but I'm forced to install it on a
>>> single partition. But I should partition and format the disk to give the
>>> 50% to OI before starting the installer ?
>>> 
>>> Il giorno mer 13 ott 2021 alle ore 20:55 Toomas Soome via
>>> openindiana-discuss  ha scritto:
>>> 
>>>> 
>>>> 
>>>>> On 13. Oct 2021, at 19:16, Mario Marietto 
>>>> wrote:
>>>>> 
>>>>> I never used ZFS. Is it doable even using another FS that I don't know
>>>>> which type it is ?. For example on FreeBSD the basic FS is ufs. So
>>>> usually
>>>>> when I install it I choose ufs instead of ZFS. Maybe I will study ZFS
>>>>> later,since now I don't want to make things more complicated than they
>>>>> already are.
>>>>> 
>>>> 
>>>> Installer does not let you use anything else than zfs; but the installer
>>>> does let you select either whole disk or partition. Technically you can
>>> set
>>>> up system on ufs, but all normal management tools (pkg update, beadm)
>>> are
>>>> assuming zfs.
>>>> 
>>>> rgds,
>>>> toomas
>>>> 
>>>> 
>>>>> Il giorno mer 13 ott 2021 alle ore 18:10 Jim Klimov >>> <mailto:jimkli...@cos.ru>> ha
>>>>> scritto:
>>>>> 
>>>>>> On October 13, 2021 3:55:06 PM UTC, Mario Marietto <
>>>> marietto2...@gmail.com>
>>>>>> wrote:
>>>>>>> Hello to everyone.
>>>>>>> 
>>>>>>> I would like to know if any of you has tried to install open
>>> indiana in
>>>>>>> a
>>>>>>> specific partition and not on the whole hard disk. Do you have some
>>>>>>> suggestions ? some tutorial that I can learn how to do that ?
>>

Re: [OpenIndiana-discuss] how to install open indiana on a single partition

[Toomas Soome via openindiana-discuss]

> On 13. Oct 2021, at 19:16, Mario Marietto  wrote:
> 
> I never used ZFS. Is it doable even using another FS that I don't know
> which type it is ?. For example on FreeBSD the basic FS is ufs. So usually
> when I install it I choose ufs instead of ZFS. Maybe I will study ZFS
> later,since now I don't want to make things more complicated than they
> already are.
> 

Installer does not let you use anything else than zfs; but the installer does 
let you select either whole disk or partition. Technically you can set up 
system on ufs, but all normal management tools (pkg update, beadm) are assuming 
zfs.

rgds,
toomas


> Il giorno mer 13 ott 2021 alle ore 18:10 Jim Klimov  > ha
> scritto:
> 
>> On October 13, 2021 3:55:06 PM UTC, Mario Marietto 
>> wrote:
>>> Hello to everyone.
>>> 
>>> I would like to know if any of you has tried to install open indiana in
>>> a
>>> specific partition and not on the whole hard disk. Do you have some
>>> suggestions ? some tutorial that I can learn how to do that ? thanks.
>> 
>> It would probably have to be a primary partition (if on MBR) of type
>> Solaris2, but should be doable. IIRC from live/install media you can
>> manually create an rpool, and then feed it to installer as a done thing. It
>> was a while since I saw the installer :)
>> 
>> Actually the installer would probably ask about partitioning; the trick
>> above could be more a step to colocate zfs-aware OSes in datasets of same
>> rpool.
>> 
>> Jim
>> 
>> --
>> Typos courtesy of K-9 Mail on my Android
>> 
> 
> 
> -- 
> Mario.
> ___
> 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] GUI performance - update 2

[Toomas Soome via openindiana-discuss]

> On 6. Sep 2021, at 23:14, russell  wrote:
> 
> Hi
> 
> Thank you for the all the advice and suggestions.
> After overclocking the Memory and CPU from 3.7GHz to 4GHz I managed to reduce 
> the previous login by 20 seconds, so it now 1 minute 30 seconds.
> 
> In an effort to discovery why the logout time is so long I login in via ssh 
> and ran both iostat 1 and zpool iostat -lv 1 before logging out on the GUI
> 
> Apologises the long email I thave tried to remove as much unnecessary 
> information
> 
> iostat results are below

iostat -xn [-M] is more useful. however, it does not look like anything too big 
is going on with disks. So it must be something else. I am shooting in the dark 
there, but in many cases, name resolver timeouts can be cause of delays (3x 
nameserver with timeouts).

I wonder, if there is anything in logs…

rgds,
toomas


> 
>tty   rpool1 sd0   sd1 sd2cpu
>  tin tout kps tps serv  kps tps serv  kps tps serv  kps tps serv us sy dt id
>1  467 2485  613  1221  300  1264  3200   0 01  1  0 98
>0 2649   0   000   000   000   0 00  0  0 100
>0 2495   0   000   000   000   0 00  0  0 100
>0 2493   0   000   000   000   0 00  0  0 100  
> <- line repeats 19 times
> 
>  tin tout kps tps serv  kps tps serv  kps tps serv  kps tps serv   us sy dt id
>0 2494   0   000   000   000   0 00  0  0 100
>0 2649  48   60   40   408   200   0 01  0  0 99
>0 2493   0   000   000   000   0 00  0  0 100
>0 2492   0   000   000   000   0 02  3  0 96   
> <- logout started
>0 2496 8473  296  4240  163  4232  1530   0 02  6  0 92
>0 2494 3966 1912  1991  990  1975  9600   0 05 12  0 83
>0 2495   0   000   000   000   0 05 12  0 83
>0 2494   0   000   000   000   0 05 12  0 83  
> <- line repeats 13 times
> 
> tin tout kps tps serv  kps tps serv  kps tps serv  kps tps serv us sy dt id
>0 2493   0   000   000   000   0 05 12  0 83
>0 2649 1184 1091  592  550  592  5800   0 05 12  0 83
>0 2494   0   000   000   000   0 05 12  0 83   
>   <- line repeats 16 times
> 
> tty   rpool1 sd0   sd1 sd2cpu
>  tin tout kps tps serv  kps tps serv  kps tps serv  kps tps serv us sy dt id
>0 2493   0   000   000   000   0 05 12  0 83
>0 2649   0   000   000   000   0 05 12  0 83
>0 2493 1232 1141  616  590  616  5900   0 05 12  0 83
>0 2493   0   000   000   000   0 05 12  0 83   
><- line repeats 24 times
> 
>0 2493 1096 1201  548  620  548  6200   0 05 12  0 83
>0 2494   0   000   000   000   0 05 12  0 83   
>   <- line repeats 34 times
> 
>0 2493 1712 1351  856  690  856  7000   0 05 12  0 83
>0 2494   0   000   000   000   0 05 12  0 83   
> 0 2493   0   000   000   0 00   005 12  0 83
>0 2493   0   000   000   000   0 05 12  0 83
>0 2493   0   000   000   000   0 05 12  0 83
>0 2492 1272 1171  636  610  636  6000   0 05 12  0 83
>0 2495   0   000   000   000   0 05 12  0 83
>0 2493   0   000   000   000   0 05 12  0 83
>0 2493   0   000   000   000   0 05 12  0 83
>0 2492   8   214   204   200   0 05 11  0 84
>0 2493 1528 1461  764  750  764  7500   0 05 10  0 84
>0 2493   8   214   204   200   0 06  5  0 89
>0 2619  24   60   12   60   12   600   0 09  4  0 87
>0 2494   0   000   000   000   0 06  3  0 91
>tty   rpool1 sd0   sd1 sd2cpu
>  tin tout kps tps serv  kps tps serv  kps tps serv  kps tps serv us sy dt id
>0 2493   0   000   000   000   0 06  3  0 91
>0 2648 4256 1843  2128  930  2128  9500   0 05  3  0 91
>0 2497   0   000   000   000   0 06  3  0 91
>0 2492   0   000   000   000   0 05  3  0 91
>0 2493   0   000   000   000   0 06  3  0 91
>0 2494   0   000   000   000   0 06  3  0 91
>1 2523   0   000   000   000   0 06  3  0 91
>0   80   0   000   0 

Re: [OpenIndiana-discuss] resolved - sort of, now a reproduce-able bug was Re: A KVM switch broke my server?! Lightdm is panic'ing the kernel

[Toomas Soome via openindiana-discuss]

> On 4. Sep 2021, at 10:15, Carl Brewer  wrote:
> 
> Ok, the trigger for the fault, reproduce able, is to boot the box without 
> anything plugged into the HDMI port on the GFX card. That seems to break 
> something in the BIOS, then the only way to get it to start X11 without a 
> kernel panic is to restore the BIOS from a previous saved version.
> 
> Tried without KBD & mouse, and HDMI monitor plugged in, and despite the O/S 
> not being smart enough to notice and then use the kbd or mouse after 
> re-connecting, which while annoying, isn't a show stopper. But if nothing's 
> plugged into the HDMI port, it does something weird to the BIOS and we're 
> busted. The only way to get X11 working again is to revert the BIOS.
> 
> It will run ok if you disable X11 (disable lightdm), but if you try to start 
> X11, you get a kernel panic. The only way I've found to 'fix' it is to revert 
> the BIOS.
> 
> Is there something in the NVidia driver that could muck with the BIOS?
> 
> This is odd.  Very odd.
> 
> Carl

The nvidia driver is closed source binary blob, built for Oracle Solaris, and 
only accidentally is able to run with illumos.

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

Re: [OpenIndiana-discuss] GUI performance

[Toomas Soome via openindiana-discuss]

> On 4. Sep 2021, at 11:37, russell  wrote:
> 
> Hi
> 
> I have been wondering about the time it takes the GUI Login screen to appear 
> on boot my computer and after logout to return to the GUI Login screen.
> This morning I decided to time this and the timings are pretty consistent.
> 
> So from boot timing the display of the text login: prompt, the screen blanks 
> and then the GUI Login appears takes on average 1 minute 54 seconds to appear.
> 
> After logout from the GUI, timing from press of the Log out button to the GUI 
> Login appearing takes on average 1 minute 50 seconds to appear.
> 
> I have a Ryzen 5 5600X, MSI MPG B550 Gaming Plus system board, Geforce 1650 
> PCI-e Gen 3 card,  64GB RAM, SSD ZFS boot pool and ZFS Raidz2 HDD home 
> directory pool.
> 
> How can speed up the appearance of the GUI login?
> 
> Would overclocking the CPU help or buying the fast RAM significantly improve 
> the performance?
> Is the Graphics Card the problem as it handling a 4K screen? However looking 
> at the information in the Nvidia X Server Settings the graphics card is only 
> peaking around 46% CPU utilisation.
> 
> 

Those are different questions.

time to login on boot:

Text mode console login depends on:

tsoome@beastie:~$ svcs -d console-login:default
STATE  STIMEFMRI
disabled   sept_01  svc:/system/auditd:default
online sept_01  svc:/system/identity:node
online sept_01  svc:/system/filesystem/minimal:default
online sept_01  svc:/milestone/sysconfig:default
online sept_01  svc:/system/utmp:default
tsoome@beastie:~$ 

This is rather minimal set of services, and if you attempt to login with your 
user as soon as the prompt appears, you may end up homeless (home is not yet 
mounted, or mounting local file systems is still in progress).

Now GUI login is much more interesting:

tsoome@beastie:~$ svcs -d lightdm
STATE  STIMEFMRI
online sept_01  svc:/application/opengl/ogl-select:default
online sept_01  svc:/application/desktop-cache/gio-module-cache:default
online sept_01  svc:/system/dbus:default
online sept_01  svc:/milestone/sysconfig:default
online sept_01  svc:/system/utmp:default
online sept_01  svc:/application/font/fc-cache:default
online sept_01  svc:/system/filesystem/local:default
online sept_01  svc:/application/x11/x11-init:default
online sept_01  svc:/system/consolekit:default
online sept_01  svc:/system/hal:default
online sept_01  svc:/milestone/multi-user:default
tsoome@beastie:~$ 

there, milestone/multi-user means that basically every enabled service must be 
started. local file systems need to be mounted, few other services too. I 
think, we could drop milestone/multi-user, but this would need testing. 
Probably autofs should be listed as well (even if there seem to be less and 
less people understanding autofs…).

Essentially, GUI login should have the services actually needed to get access 
to users home and to make it possible to start up desktop session.

The time from logout to new login screen is different question — all the 
services should be there and the login manager running, so the question would 
be about how much time it does take to actually logout and prepare login screen 
for next user. It may be, your raidz2 is not as fast as you would like to be 
for storing session states etc.

To debug logout activities, you would need to have ssh session over network or 
like,  check iostat and other metrics in attempt to find out what is going on 
there.

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

Re: [OpenIndiana-discuss] Rpool uncorrectable error

[Toomas Soome via openindiana-discuss]

> On 29. Aug 2021, at 14:31, Michelle  wrote:
> 
> I'm sat here, not knowing quite what I'm dealing with.
> 
> OI recent build on HP N54L, as you may remember I hit a problem on the
> 8th August with rpool encountering an error on the SSD with the OS.
> 
> I replaced the drive and had the same thing straight away. Replaced
> with another drive and took the unit down to basics including a RAM
> check and rebuilt it. It's been running until today... same thing.
> 
> On the messages screen I see at just gone 00:00 this morning...
> Sense Key: aborted command
> Vendor Gen-ATA error code 0x3
> Rpool has encountered an uncorrectable IO failure and has been
> suspended. Zpool clear will be required before the pool can be written
> to
> 
> The rpool message repeated at 00:05, 00:22, 02:54 and at 08:54 ...and
> it's now stopped responding.
> 
> So... I've now got no idea where to take this. On the face of it, the
> hardware is fine... on the face of it. However, there's something wrong
> here and given the history, I'm not sure where to start.
> 
> Part of me thinks I'm looking at hardware...
> 
> Power? Hmmm... why does the SSD fail instead of the spinning rust
> drives?
> 
> Yet another hard drive? This is number three now, throwing suspicion at
> other aspects.
> 
> I am reticent to just replace with another hard drive and carry on. I
> think it may not be to blame here.
> 
> Grateful for people's thoughts.
> 
> Michelle.
> 


Apparently this can be multiple things… Does your system allow to set AHCI 
(SATA) mode from BIOS setup? This may help.

also see https://docs.oracle.com/cd/E19253-01/820-7273/ggmsj/index.html 
 

In general, you really want to keep away from IDE…

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

Re: [OpenIndiana-discuss] Installing on Intel B460M chipset intel i5-10400F

[Toomas Soome via openindiana-discuss]

> On 13. Aug 2021, at 14:21, Carl Brewer  wrote:
> 
> 
> If it helps, here's a photo of the screen when it was looping
> 
> http://aboc.net.au/oi_hang.png/image_view_fullscreen
> 
> 

boot -rs, can it get to single user prompt?

rgds,
toomas


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

Re: [OpenIndiana-discuss] Installing on Intel B460M chipset intel i5-10400F

[Toomas Soome via openindiana-discuss]

> On 13. Aug 2021, at 12:07, Carl Brewer  wrote:
> 
> On 13/08/2021 6:59 pm, Peter Tribble wrote:
>> 
>> As I recall, the keyboard prompt comes fairly late in the process -
>> certainly after
>> accessing the USB media to pull in /usr from it, so that would imply it's
>> found the
>> USB stick and is happy with it. The question then would be which smf
>> service is
>> getting stuck.
> 
> 
> Yeah, I've tried a different USB slot and no difference.
> 
> The verbosity is from the, I don't know what you call it, boot option 
> selector?  It's a curses-ish screen that you get when you select "5" (sorry, 
> the machine is in a different room to me) that lets you select a few things - 
> single/multi user, "verbose" etc
> 
> Where would I get to a menu or prompt that let me "boot -v" ?  I can get to 
> an "ok" prompt, is that it?
> 

press esc on first menu screen to get to OK prompt.

rgds,
toomas

> 
>> 
>> By verbose, was that 'boot -v'? If so, you can track progress through smf
>> with
>> 'boot -m verbose' or 'boot -m debug' (I think - it's been a while).
>> 
> 
> ___
> 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] Installing on Intel B460M chipset intel i5-10400F

[Toomas Soome via openindiana-discuss]

> On 13. Aug 2021, at 11:13, Carl Brewer  wrote:
> 
> The furthest I got was to use the minimal install 20210430 USB image, it 
> booted, albeit slowly.
> 
> I ran the boot in verbose mode, it got as far as prompting for the type of 
> keyboard, which I confirmed as US English (47).
> 
> It then sat there, I left it for 30 minutes, no change.  The screen responds 
> to keyboard input, by echoing the keystrokes, but ^C and ^Z do nothing more 
> than echo to the screen.
> 
> Since it's on a standalone machine, I can't easily show the screen, I did 
> take a photo of it though, but not good list manners to post it. It found the 
> HDD (WD black 1TB) and didn't seem upset about it, but there was no more 
> verbosity to see what it was hung up on.  I don't expect 30 minutes was 
> insufficient time for it to do whatever it was trying to do.  Text mode, so I 
> don't think the Nvidia card would have made much difference?
> 
> I'm not going to give up on it, but I need some guidance as to what to try 
> next. OI and OpenSolaris have been my go to for rock solid platforms for the 
> best part of 20 years now. I don't want to give up and resort to some flaky 
> linux distro just to get ZFS and Virtualbox running!
> 
> "help"
> 
> Thank you!
> 
> Carl
> 

This does sound like problems reading out the usb stick, can you try different 
stick and slot, especiall if the system has usb 2 and usb 3.

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

Re: [OpenIndiana-discuss] rpool mirror disk problems when moved to different slot

[Toomas Soome via openindiana-discuss]

The bootability is supposed to be fixed by syseventd, see /etc/sysevent/config/.

rgds,
toomas

> On 6. Aug 2021, at 14:07, Stephan Althaus  
> wrote:
> 
> On 8/6/21 12:59 PM, Michelle wrote:
>> Ah, if you're moving a live rpool, that's a bit more complex.
>> 
>> I'd have destroyed the mirror, moved the drive and then re-mirrored...
>> but only if I'd put another boot on the other drive.
>> 
>> After all, if you've mirrored your rpool, but there's no boot on the
>> mirror drive, then it will still not boot the mirror drive.
>> 
>> 
>> 
>> On Fri, 2021-08-06 at 12:54 +0200, Stephan Althaus wrote:
>>> On 8/6/21 12:47 PM, Michelle wrote:
 Did you export the zpool before moving the drives and then import
 again
 after?
 
 If I don't export before I move things, then I wouldn't expect ZFS
 to
 be able to track it automatically.
 
 
 
 On Fri, 2021-08-06 at 11:19 +0200, Stephan Althaus wrote:
> Hello!
> 
> i just added a new disk to my system, which i put into the slot
> where
> a
> mirror disk of my rpool resided.
> 
> The mirror disk of my rpool went to a other slot, so the device
> name
> was
> changed c27t1d0 -> c27t0d0
> 
> Booting into my OI system, the zpool was found as the first
> mirror
> disk
> was there,
> but the second partition was not found.
> 
> 
> Is there a chance that the rpool mount procedure could try harder
> to
> find the mirrors, even when moved ??
> 
> 
> Yes i know this may be a rare case :-/
> 
> 
> Greetings,
> 
> Stephan
> 
> 
> ___
> 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
>>> Hi!
>>> 
>>> This is my root pool, is it exported on shutdown? i would think so..
>>> 
>>> I think, if i move the mirror drive to a different slot and leave the
>>> origin-slot empty, it could work..
>>> 
>>> I should have imported and exported the pool with a illumos-live-
>>> USB, 
>>> _before_ trying to boot the installed system with the change.
>>> 
>>> i had no live-medium at hand so i just gave it a try..
>>> 
>>> Stephan
>>> 
>>> BTW, the mirrored pool is up and working:
>>> 
>>> $ zpool status rpool
>>>  pool: rpool
>>> state: ONLINE
>>>  scan: resilvered 194G in 0 days 00:50:39 with 0 errors on Fri Aug 
>>> 6
>>> 12:04:20 2021
>>> config:
>>> 
>>>NAME STATE READ WRITE CKSUM
>>>rpoolONLINE   0 0 0
>>>  mirror-0   ONLINE   0 0 0
>>>c9t002538B471B9EFD3d0s8  ONLINE   0 0 0
>>>c27t0d0s0ONLINE   0 0 0
>>> 
>>> 
>>> 
>>> ___
>>> 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
> 
> Yes, Michelle, you're right.
> 
> The intention of my thread was to enhance the automagically discovered
> changes.
> 
> There have been efforts to re-import pools that have been im- and
> exported on linux and changed the device names.
> 
> My case is just another one that (maybe) could be handled automagically,
> without user intervention.
> 
> ...
> 
> Stephan
> 
> 
> 
> ___
> 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] rpool mirror disk problems when moved to different slot

[Toomas Soome via openindiana-discuss]

> On 6. Aug 2021, at 12:44, Stephan Althaus  
> wrote:
> 
> On 8/6/21 11:33 AM, Toomas Soome via openindiana-discuss wrote:
>> 
>>> On 6. Aug 2021, at 12:19, Stephan Althaus 
>>>  wrote:
>>> 
>>> Hello!
>>> 
>>> i just added a new disk to my system, which i put into the slot where a
>>> mirror disk of my rpool resided.
>>> 
>>> The mirror disk of my rpool went to a other slot, so the device name was
>>> changed c27t1d0 -> c27t0d0
>>> 
>>> Booting into my OI system, the zpool was found as the first mirror disk
>>> was there,
>>> but the second partition was not found.
>>> 
>>> 
>>> Is there a chance that the rpool mount procedure could try harder to
>>> find the mirrors, even when moved ??
>>> 
>>> 
>>> Yes i know this may be a rare case :-/
>>> 
>>> 
>> What does zpool status report?
>> 
>> rgds,
>> toomas
>> 
>> 
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org
>> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> Meanwhile, i detached the 'corrupted' mirror disk partition, attached
> the correct partition - resilver is running...
> 
> zpool status  did report "corrupt data", as the partition ('zpool
> import' used  its name without checking zfs signatures) did not contain
> a zfs dataset.
> 
> 'ZFS' should not have tried it, as there is no zfs signature on that
> disk, in any partition..
> 
> Instead the import should look around for the correct zpool members,
> just like the usual zpool import does…
> 

It normally does scan all available devices. Or at least, should do that… 

rgds,
toomas



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

Re: [OpenIndiana-discuss] rpool mirror disk problems when moved to different slot

[Toomas Soome via openindiana-discuss]

> On 6. Aug 2021, at 12:19, Stephan Althaus  
> wrote:
> 
> Hello!
> 
> i just added a new disk to my system, which i put into the slot where a
> mirror disk of my rpool resided.
> 
> The mirror disk of my rpool went to a other slot, so the device name was
> changed c27t1d0 -> c27t0d0
> 
> Booting into my OI system, the zpool was found as the first mirror disk
> was there,
> but the second partition was not found.
> 
> 
> Is there a chance that the rpool mount procedure could try harder to
> find the mirrors, even when moved ??
> 
> 
> Yes i know this may be a rare case :-/
> 
> 

What does zpool status report?

rgds,
toomas


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

Re: [OpenIndiana-discuss] Errors without errors

[Toomas Soome via openindiana-discuss]

> On 5. Aug 2021, at 11:11, Michelle  wrote:
> 
> I removed the drive in order to a backup before I start messing around
> with things, which is why it isn't in the iostat. The backup will take
> probably until early evening.
> 
> This is what happened from messages around that time. Almost looks like
> whatever happened, it rebooted.
> 

From those, I’d say, you need to replace that disk. 

rgds,
toomas

> 
> Aug  5 01:55:01 jaguar smbd[601]: [ID 617204 daemon.error] Can't get
> SID for ID=0 type=1, status=-9977
> Aug  5 01:58:00 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0:
> ahci port 3 has task file error
> Aug  5 01:58:00 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0:
> ahci port 3 is trying to do error recovery
> Aug  5 01:58:00 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0:
> ahci port 3 task_file_status = 0x4041
> Aug  5 01:58:00 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0:
> error recovery for port 3 succeed
> Aug  5 01:58:09 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0:
> ahci port 3 has task file error
> Aug  5 01:58:09 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0:
> ahci port 3 is trying to do error recovery
> Aug  5 01:58:09 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0:
> ahci port 3 task_file_status = 0x4041
> Aug  5 01:58:09 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0:
> error recovery for port 3 succeed
> Aug  5 02:00:15 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0:
> ahci port 3 has task file error
> Aug  5 02:00:15 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0:
> ahci port 3 is trying to do error recovery
> Aug  5 02:00:15 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0:
> ahci port 3 task_file_status = 0x4041
> Aug  5 02:00:16 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0:
> error recovery for port 3 succeed
> Aug  5 02:00:20 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0:
> ahci port 3 has task file error
> Aug  5 02:00:20 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0:
> ahci port 3 is trying to do error recovery
> Aug  5 02:00:20 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0:
> ahci port 3 task_file_status = 0x4041
> Aug  5 02:00:20 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0:
> error recovery for port 3 succeed
> Aug  5 02:00:24 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0:
> ahci port 3 has task file error
> Aug  5 02:00:24 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0:
> ahci port 3 is trying to do error recovery
> Aug  5 02:00:24 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0:
> ahci port 3 task_file_status = 0x4041
> Aug  5 02:00:24 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0:
> error recovery for port 3 succeed
> Aug  5 02:00:24 jaguar ahci: [ID 811322 kern.info] NOTICE: ahci0:
> ahci_tran_reset_dport port 3 reset device
> Aug  5 02:00:29 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0:
> ahci port 3 has task file error
> Aug  5 02:00:29 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0:
> ahci port 3 is trying to do error recovery
> Aug  5 02:00:29 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0:
> ahci port 3 task_file_status = 0x4041
> Aug  5 02:00:29 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0:
> error recovery for port 3 succeed
> Aug  5 02:00:34 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0:
> ahci port 3 has task file error
> Aug  5 02:00:34 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0:
> ahci port 3 is trying to do error recovery
> Aug  5 02:00:34 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0:
> ahci port 3 task_file_status = 0x4041
> Aug  5 02:00:34 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0:
> error recovery for port 3 succeed
> Aug  5 02:00:38 jaguar ahci: [ID 296163 kern.warning] WARNING: ahci0:
> ahci port 3 has task file error
> Aug  5 02:00:38 jaguar ahci: [ID 687168 kern.warning] WARNING: ahci0:
> ahci port 3 is trying to do error recovery
> Aug  5 02:00:38 jaguar ahci: [ID 693748 kern.warning] WARNING: ahci0:
> ahci port 3 task_file_status = 0x4041
> Aug  5 02:00:38 jaguar ahci: [ID 657156 kern.warning] WARNING: ahci0:
> error recovery for port 3 succeed
> Aug  5 02:00:53 jaguar fmd: [ID 377184 daemon.error] SUNW-MSG-ID: ZFS-
> 8000-FD, TYPE: Fault, VER: 1, SEVERITY: Major
> Aug  5 02:00:53 jaguar EVENT-TIME: Thu Aug  5 02:00:53 UTC 2021
> Aug  5 02:00:53 jaguar PLATFORM: ProLiant-MicroServer, CSN: 5C7351P4L9,
> HOSTNAME: jaguar
> Aug  5 02:00:53 jaguar SOURCE: zfs-diagnosis, REV: 1.0
> 
> 
> On Thu, 2021-08-05 at 11:03 +0300, Toomas Soome via openindiana-discuss 
> wrote:
>>> On 5. Aug 2021, at 10:52, Michelle  wrote:
>>> 
>>> Thanks for this. So I'm poss

Re: [OpenIndiana-discuss] Errors without errors

[Toomas Soome via openindiana-discuss]

> On 5. Aug 2021, at 10:52, Michelle  wrote:
> 
> Thanks for this. So I'm possibly better off rolling back the OS
> snapshot after my backup has finished?

maybe, maybe not. first of all, I have no idea to what point the rollback would 
be.

secondly; the system has seen some errors, at this time, the fault is, it does 
not tell us if those were checksum errors or something else, and it seems to 
me, it is something else.

and this is why: if you look on your zpool output, you see report about c6t3d0, 
but iostat -En below, it does not include c6t3d0. It seems to be missing.

what do you get from: 'iostat -En c6t3d0’ ?

Also, it would be good idea to check /var/adm/messages, are there any SATA or 
IO related messages around august 05. 02:00? 

FMA definitely has recorded an issue about pool, so there must be something 
going on.

rgds,
toomas

> 
> I have removed the drive for the moment, and am running a backup. Just
> in case :-)
> 
> mich@jaguar:~$ iostat -En
> c5d1 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
> Model: INTEL SSDSA2M04 Revision:  Serial No: CVGB949301PC040 
> Size: 40.02GB <40019116032 bytes>
> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
> Illegal Request: 0 
> c6t1d0   Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
> Vendor: ATA  Product: WDC WD40EZRZ-00G Revision: 0A80 Serial No:
> WD-WCC7K5UK24LJ 
> Size: 4000.79GB <4000787030016 bytes>
> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
> Illegal Request: 0 Predictive Failure Analysis: 0 
> c6t0d0   Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
> Vendor: ATA  Product: WDC WD60EFRX-68L Revision: 0A82 Serial No:
> WD-WX21DA84EH0F 
> Size: 6001.18GB <6001175126016 bytes>
> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
> Illegal Request: 0 Predictive Failure Analysis: 0 
> c6t2d0   Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 
> Vendor: ATA  Product: WDC WD60EFRX-68L Revision: 0A82 Serial No:
> WD-WX51DB880RJ4 
> Size: 6001.18GB <6001175126016 bytes>
> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 
> Illegal Request: 0 Predictive Failure Analysis: 0 
> 
> 
> ---   -- --
> ---
> TIMEEVENT-ID  MSG-
> ID SEVERITY
> ---   -- --
> ---
> Aug 05 02:00:53 c5934fd6-5f4b-409e-b0f8-8f44ea8f99c4  ZFS-8000-
> FDMajor 
> 
> Host: jaguar
> Platform: ProLiant-MicroServer  Chassis_id  : 5C7351P4L9
> Product_sn  : 
> 
> Fault class : fault.fs.zfs.vdev.io
> Affects : zfs://pool=jaguar/vdev=740c01ae0d3c3109
>  faulted and taken out of service
> Problem in  : zfs://pool=jaguar/vdev=740c01ae0d3c3109
>  faulted and taken out of service
> 
> Description : The number of I/O errors associated with a ZFS device
> exceeded
> acceptable levels.  Refer to
>  http://illumos.org/msg/ZFS-8000-FD for more information.
> 
> Response: The device has been offlined and marked as faulted.  An
> attempt
> will be made to activate a hot spare if
> available. 
> 
> Impact  : Fault tolerance of the pool may be compromised.
> 
> Action  : Run 'zpool status -x' and replace the bad device.
> 
> 
> 
> On Thu, 2021-08-05 at 10:22 +0300, Toomas Soome via openindiana-discuss 
> wrote:
>>> On 5. Aug 2021, at 09:35, Michelle  wrote:
>>> 
>>> Hi Folks,
>>> 
>>> About a month ago I updated my Hipster...
>>> SunOS jaguar 5.11 illumos-ca706442e6 i86pc i386 i86pc
>>> 
>>> This morning it was absolutely crawling. Couldn't even connect via
>>> SSH
>>> and had to bounce the box.
>>> 
>>> It was reporting a drive as faulted, but didn't give any numbers...
>>> everything was 0. I'm now not sure what happened and whether the
>>> drive
>>> is good, or whether I should roll back the OS.
>>> 
>>> (and the drive WD Red 6TB (not shingle) went out of warrantee a
>>> week
>>> ago. How about that, eh?)
>>> 
>>> Grateful for any opinions please.
>>> 
>>> Thu  5 Aug 04:00:01 UTC 2021
>>> NAME   SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUP  
>>>  HE
>>> ALTH  ALTROOT
>>> lion  5.45T  5.28T   176G- - 4%96%  1.00x  
>>> DEGR
>>> ADED  -
>>> pool: jaguar
>>> state: DEGRADED
>>> status: One or mo

Re: [OpenIndiana-discuss] Errors without errors

[Toomas Soome via openindiana-discuss]

> On 5. Aug 2021, at 09:35, Michelle  wrote:
> 
> Hi Folks,
> 
> About a month ago I updated my Hipster...
> SunOS jaguar 5.11 illumos-ca706442e6 i86pc i386 i86pc
> 
> This morning it was absolutely crawling. Couldn't even connect via SSH
> and had to bounce the box.
> 
> It was reporting a drive as faulted, but didn't give any numbers...
> everything was 0. I'm now not sure what happened and whether the drive
> is good, or whether I should roll back the OS.
> 
> (and the drive WD Red 6TB (not shingle) went out of warrantee a week
> ago. How about that, eh?)
> 
> Grateful for any opinions please.
> 
> Thu  5 Aug 04:00:01 UTC 2021
> NAME   SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAGCAP  DEDUPHE
> ALTH  ALTROOT
> lion  5.45T  5.28T   176G- - 4%96%  1.00x  DEGR
> ADED  -
>  pool: jaguar
> state: DEGRADED
> status: One or more devices are faulted in response to persistent
> errors.
>   Sufficient replicas exist for the pool to continue functioning
> in a
>   degraded state.
> action: Replace the faulted device, or use 'zpool clear' to mark the
> device
>   repaired.
>  scan: scrub in progress since Thu Aug  5 00:00:00 2021
>   6.00T scanned at 428M/s, 5.02T issued at 358M/s, 7.90T total
>   1M repaired, 63.59% done, 0 days 02:20:17 to go
> config:
>   NAMESTATE READ WRITE CKSUM
>   jaguar  DEGRADED 0 0 0
> raidz1-0  DEGRADED 0 0 0
>   c6t0d0  ONLINE   0 0 0
>   c6t2d0  ONLINE   0 0 0
>   c6t3d0  FAULTED  0 0 0  too many
> errors  (repairing)
> 

Can you postoutput from: 
iostat -En
fmadm faulty

in any case, there definitely is bug about error reporting - counters are zero 
while “too many errors” is reported.

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

Re: [OpenIndiana-discuss] warning - don't update OI

[Toomas Soome via openindiana-discuss]

> On 25. Jul 2021, at 12:04, Richard L. Hamilton  wrote:
> 
> Please let also the openindiana-discuss list know when the real 2.37 binutils 
> is safe and included; some of us don't subscribe to the oi-dev list.
> 
> I'd also admit to some curiosity what the problem with 2.37 was, once that's 
> understood.
> 
> Not to mention whether there's anything that one can do at the "ok" prompt 
> when something like that happens. Booting the optical media image and 
> activating a good BE saved me, but it'd be nice to know all my options.


gptzfsboot(5), loader(5). 

it does start with boot(1M), kernel(1M), installboot(1M), but there is first 
bug - installboot should also refer to gptzfsboot(5) and loader(5).

This issue about binutils 2.37 is about the linker set feature; the 
Xcommand_set and Xficl_compile_set functions are dropped by gld 2.37 and 
resulting sets are empty - so builtin C functions are not available. This issue 
is only affecting BIOS loader, UEFI loader is ok.

rgds,
toomas


> 
>> On Jul 24, 2021, at 16:08, Andreas Wacknitz  wrote:
>> 
>> Hi all,
>> 
>> It is now safe again to update.
>> 
>> I had to revert the binutils-2.37 update and instead created a fake 2.37
>> package version that delivers the older 2.36.1 version.
>> With that I have re-published the latest illumos-gate packages and
>> successfully installed them on my machines.
>> Thanks to Toomas Soome for helping me and analyzing the problem.
>> 
>> Andreas
>> 
>> Am 7/24/21 um 9:55 AM schrieb Andreas Wacknitz:
>>> Hi all,
>>> 
>>> something bad has happened with the last updates and rendered two of my
>>> build servers unbootable. They are both stuck in the boot loader ("start
>>> not found") such that
>>> booting with an old BE won't fix that!
>>> 
>>> SO DON'T UPDATE YOUR SYSTEMS FOR NOW!
>>> 
>>> I fear that my update of binutils-2.37 may be the culprit.
>>> 
>>> Regards
>>> Andreas
>>> 
>>> ___
>>> 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
>> 
> 
> -- 
> eMail:mailto:rlha...@smart.net
> 
> 
> 
> 
> ___
> 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] Insufficient Disk space for updates reported

[Toomas Soome via openindiana-discuss]

  - - 4.98M   
>> static 2021-04-03 09:14
>> openindiana-2021:04:03-backup-1- - 180K
>> static 2021-04-04 16:15
>> openindiana-2021:04:03-backup-2- - 183K
>> static 2021-04-05 14:39
>> openindiana-2021:04:06 - - 64.00M  
>> static 2021-04-06 12:44
>> openindiana-2021:04:07 - - 3.96M   
>> static 2021-04-07 15:01
>> openindiana-2021:04:08 - - 5.08M   
>> static 2021-04-08 09:39
>> openindiana-2021:04:10 - - 3.97M   
>> static 2021-04-10 08:54
>> openindiana-2021:04:13 - - 3.98M   
>> static 2021-04-13 22:05
>> openindiana-2021:04:14 - - 4.10M   
>> static 2021-04-14 11:17
>> openindiana-2021:04:14-backup-1- - 170K
>> static 2021-04-15 11:08
>> openindiana-2021:04:16 - - 576.99M 
>> static 2021-04-16 10:00
>> openindiana-2021:04:18 - - 4.37M   
>> static 2021-04-18 11:30
>> openindiana-2021:04:18-backup-1- - 170K
>> static 2021-04-19 10:10
>> openindiana-2021:04:21 - - 4.07M   
>> static 2021-04-21 11:15
>> openindiana-2021:04:21-backup-1- - 177K
>> static 2021-04-22 09:03
>> openindiana-2021:04:21-backup-2- - 170K
>> static 2021-04-23 09:08
>> openindiana-2021:04:26 - - 4.06M   
>> static 2021-04-26 09:15
>> openindiana-2021:04:27 - - 64.31M  
>> static 2021-04-27 11:39
>> openindiana-2021:05:01 - - 4.11M   
>> static 2021-05-01 11:07
>> openindiana-2021:05:03 - - 4.17M   
>> static 2021-05-03 12:09
>> openindiana-2021:05:09 - - 4.21M   
>> static 2021-05-09 11:09
>> openindiana-2021:05:11 - - 4.43M   
>> static 2021-05-11 10:41
>> openindiana-2021:05:13 - - 4.03M   
>> static 2021-05-13 19:51
>> openindiana-2021:05:14 - - 64.16M  
>> static 2021-05-14 15:59
>> openindiana-2021:05:15 - - 180.31M 
>> static 2021-05-15 16:18
>> openindiana-2021:05:15-backup-1- - 179K
>> static 2021-05-16 12:34
>> openindiana-2021:05:17 - - 4.20M   
>> static 2021-05-17 15:05
>> openindiana-2021:05:18 R - 153.56G 
>> static 2021-05-18 13:35
>> openindiana-2021:05:18-backup-1- - 184K
>> static 2021-05-19 13:34
>> openindiana-2021:05:18-backup-2- - 178.95M 
>> static 2021-07-01 17:58
>> openindiana-2021:05:18-backup-3- - 211K
>> static 2021-07-01 18:33
>> openindiana-2021:05:18-backup-4- - 1K  
>> static 2021-07-02 09:33
>> openindiana-2021:05:18-backup-5- - 1K  
>> static 2021-07-02 10:02
>> openindiana-2021:05:18-backup-6- - 1K  
>> static 2021-07-02 10:18
>> openindiana-2021:05:18-backup-2-backup-1   - - 304.18M 
>> static 2021-07-02 15:54
>> openindiana-2021:05:18-backup-7- - 1K  
>> static 2021-07-02 17:30
>> openindiana-2021:05:18-backup-8- - 11.31M  
>> static 2021-07-02 18:19
>> openindiana-2021:05:18-backup-2-backup-1-backup-1  - - 384.84M 
>> static 2021-07-02 19:26
>> openindiana-2021:05:18-backup-2-backup-1-backup-1-backup-1 - - 19.88M  
>> static 2021-07-03 08:36
>> openindiana-2021:05:18-backup-2-backup-1-backup-1-backup-2 - - 205K
>> static 2021-07-03 08:50
>> openindiana-2021:05:18-backup-2-backup-1-backup-1-backup-3 - - 11.47M  
>> static 2021-07-03 08:52
>> openindiana-2021:05:18-backup-2-backup-1-backup-1-backup-4 - - 164K
>> static 2021-07-03 09:56
>> openindiana-2021:05:18-backup-2-backup-1-backup-1-backup-5 - - 148.82M 
>> static 2021-07-03 12:29
>> openindiana-2021:05:18-backup-2-backup-1-backup-1-backup-6 - - 465.75M 
>> static 2021-07-04 11:03
>> openindiana-2021:05:18-backup-2-backup-1-backup-1-backup-7 - - 441.61M 
>> static 2021-07-06 10:21
>> openindiana-2021:05:18-backup-2-backup-1-backup-1-backup-8 N / 191.36M 
>> static 2021-07-07 17:18
>> tools used
>> pkg fix
>> pkg verify
>> pkg rehydrate
>> pkg dehydrate
>> Is this project able to be compiled on Oi ? 
>> https://github.com/bahamas10/zfs-prune-snapshots 
>> <https://github.com/bahamas10/zfs-prune-snapshots>
>> additional error
>> error pkg://openindiana.org/library/security/openssl 
>> 
>> pkg://openindiana.org/system/kernel/dtrace/providers/xdt 
>>  ERROR
>> driver: xdt
>> ERROR: etc/name_to_major: 'xdt' entry not present
>> On 13/07/2021 08:53, bscuk2 wrote:
>>> 
>>> 
>>> On 10/07/2021 12:02, Toomas Soome via openindiana-discuss wrote:
>>>> 
>>>>> On 10. Jul 2021, at 13:20, bscuk2  wrote:
>>>>> 
>>>>> Dear All,
>>>>> 
>>>>> After recent updates this is the information on the system. Insufficient 
>>>>> disk space available (648.02 MB) for estimated need (2.48 GB) for 
>>>>> Download cache
>>>>> 
>>>>> The disk is a Samsung Pro 250 SSD M.2 with an estimated 71 GB used in 
>>>>> total.
>>>>> I have deleted legacy snapshots,files etc but not further space is 
>>>>> detected.
>>>>> After running PKg rehydrate,fix etc the situation has not improved.
>>>>> I am wondering if the disk space is not been reported correctly,memory 
>>>>> swaps,
>>>>> or connected with Bob Friesenhahn current threat on system monitor issues 
>>>>> ?
>>>>> I am not a developer but would appriciate any advice on how to proceed.
>>>>> 
>>>>> Regards,
>>>>> 
>>>>> 
>>>>> Robert
>>>>> 
>>>> What does zpool list and zfs list report?
>>>> 
>>>> rgs,
>>>> toomas
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>> ___
>> openindiana-discuss mailing list
>> openindiana-discuss@openindiana.org 
>> <mailto:openindiana-discuss@openindiana.org>
>> https://openindiana.org/mailman/listinfo/openindiana-discuss 
>> <https://openindiana.org/mailman/listinfo/openindiana-discuss>
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org 
> <mailto:openindiana-discuss@openindiana.org>
> https://openindiana.org/mailman/listinfo/openindiana-discuss 
> <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] Insufficient Disk space for updates reported

[Toomas Soome via openindiana-discuss]

> On 10. Jul 2021, at 13:20, bscuk2  wrote:
> 
> Dear All,
> 
> After recent updates this is the information on the system. Insufficient disk 
> space available (648.02 MB) for estimated need (2.48 GB) for Download cache
> 
> The disk is a Samsung Pro 250 SSD M.2 with an estimated 71 GB used in total.
> I have deleted legacy snapshots,files etc but not further space is detected.
> After running PKg rehydrate,fix etc the situation has not improved.
> I am wondering if the disk space is not been reported correctly,memory swaps,
> or connected with Bob Friesenhahn current threat on system monitor issues ?
> I am not a developer but would appriciate any advice on how to proceed.
> 
> Regards,
> 
> 
> Robert
> 

What does zpool list and zfs list report?

rgs,
toomas




> 
> # echo ::memstat | mdb -k
> Page SummaryPagesMB  %Tot
>      
> Kernel 573167  2238   14%
> Boot pages147 00%
> ZFS File Data  284407  11107%
> Anon   617118  2410   15%
> Exec and libs1813 70%
> Page cache  97732   3812%
> Free (cachelist)98271   3832%
> Free (freelist)   2508266  9797   60%
> 
> Total 4180921 16331
> Physical  4180920 16331
> 
> # vmstat 5 5
> kthr  memorypagedisk faults  cpu
> r b w   swap  free  re  mf pi po fr de sr ro s0 s1 s2   in   sy cs us
> sy id
> 0 0 0 4651392 8648332 646 3029 54 48 90 0 10507 517 -0 -1 518 4786
> 30789 6948 28 26 46
> 0 0 0 3555004 10394368 252 1583 0 0 0 0 0 48  0  0 48 2530 23181 1027
> 29 19 52
> 0 0 0 3558672 10399384 378 915 0 0 0 0  0 49  0  0 50 2535 16221 1171
> 21 12 67
> 0 0 0 3556604 10396764 392 1090 0 0 0 0 0 37  0  0 38 2488 18850 807
> 19 16 65
> 0 0 0 3552712 10392784 231 1392 0 0 0 0 0 28  0  0 28 2535 20377 1270
> 30 16 54
>  PID USERNAME  SIZE   RSS STATE  PRI NICE  TIME  CPU PROCESS/NLWP
> 18249 oi 49M   13M cpu1 0   19   0:00:00 1.2%
> tracker-extract/16
>  1031 oi110M   42M sleep   590   0:01:51 0.9% Xorg/3
> 16493 root 4568K 3460K cpu0590   0:00:14 0.9% prstat/1
> 13595 oi 84M   38M sleep   360   0:00:03 0.4% mate-terminal/5
> 10463 oi942M  520M sleep   490   0:01:37 0.4% firefox/44
>  1906 oi149M   38M sleep   590   0:00:22 0.2% marco/6
>  2004 oi   8380K 5244K sleep   590   0:00:15 0.2% gvfsd-metadata/4
> 15642 oi508M  286M sleep   590   0:00:06 0.1% firefox/22
>  1882 oi   3888K 2332K sleep   540   0:00:12 0.1% dbus-daemon/1
>  1985 oi 75M   31M sleep   580   0:00:13 0.1%
> mate-typing-mon/5
>  1927 oi 12M 5732K sleep   590   0:00:04 0.1% xscreensaver/4
> 5 root0K0K sleep   98  -20   0:03:12 0.1% zpool-rpool/232
> 10567 oi   6598M  186M sleep   590   0:00:18 0.0% firefox/29
>  1923 oi 75M   32M sleep   590   0:00:07 0.0% wnck-applet/5
> 10733 oi550M  319M sleep   590   0:00:09 0.0% firefox/21
> 10579 oi414M  187M sleep   490   0:00:03 0.0% firefox/19
>  1948 oi   8172K 5328K sleep   590   0:00:06 0.0%
> gvfs-hal-volume/4
> 12291 oi866M  324M sleep   590   0:00:12 0.0% firefox/20
>  1946 oi129M   68M sleep   12   19   0:02:27 0.0%
> tracker-miner-f/6
>  1926 oi   1045M  702M sleep   490   0:00:49 0.0% thunderbird/46
>   617 redis7924K 2292K sleep   590   0:00:01 0.0% redis-server/4
>  1989 oi 71M   29M sleep   590   0:00:01 0.0%
> notification-ar/5
> 10565 oi   6526M  156M sleep   590   0:00:08 0.0% firefox/19
>  1904 oi   8656K 4340K sleep   580   0:00:01 0.0% gvfsd/4
>  1634 root 4472K 1820K sleep   590   0:00:01 0.0% bash/1
> 10568 oi404M  184M sleep   590   0:00:02 0.0% firefox/20
>  1943 oi 53M   26M sleep   590   0:00:01 0.0% applet.py/2
>  1938 oi 60M   17M sleep   590   0:00:17 0.0% tracker-store/9
>  1902 oi140M   31M sleep   590   0:00:01 0.0%
> mate-settings-d/6
>  1863 oi 69M   25M sleep   590   0:00:01 0.0% mate-session/5
>   183 root 3988K 2220K sleep   590   0:00:01 0.0% dbus-daemon/1
>  3253 root 9088K 4968K sleep   590   0:00:01 0.0% nscd/32
>  1901 oi 13M 4476K sleep   590   0:00:00 0.0%
> gnome-keyring-d/5
> ZONEIDNPROC  SWAP   RSS MEMORY  TIME  CPU ZONE
> 0  122   15G 3653M22%   0:14:44 4.8% global
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss


___
openindiana-discuss mailing

Re: [OpenIndiana-discuss] Question about System Monitor

[Toomas Soome via openindiana-discuss]

From vmstat, the sr (scan rate) is better indicator - if you see sr column > 0, 
it means the kernel is spending time searching for usable memory pages, and if 
this does happen often, it is time to review the memory consumers/add more RAM.

Toomas

> On 8. Jul 2021, at 17:55, Richard L. Hamilton  wrote:
> 
> Because of the way swap is implemented on Solaris and descendants (on SVR4 
> in general, maybe), the vmstat "swap" column is very misleading; check output 
> of swap -l (lower-case L option) instead, and if the free column is the same 
> as the blocks column, no real swap is actually being used.
> 
> Likewise, all block disk I/O (including filesystem) goes though the paging 
> mechanism, so the vmstat "pi" column just reflects reads or access via mmap. 
> Given that the "po" column is zero, I doubt that you're actually paging out 
> just to make room, although that's not a great indication, as file or block 
> disk writes or pages written due to msync() would also probably count there.
> 
> I suspect some of the misleading "swap" column change may also be due to 
> files being created and written, or deleted, in tmpfs filesystems like /tmp 
> and /var/run.
> 
>> On Jul 8, 2021, at 10:40, russell  wrote:
>> 
>> Hi,
>> 
>> I am running Hipster 2021.04 with illumos-3f770aab81 and running System 
>> Monitor 1.24.2.
>> System monitor is reporting Memory utilisation of 17.5GiB (27.5%) of 
>> 63.9GiB, however it is reporting 115.7MiB (0.7%) of 15.9GiB of swap it being 
>> used.
>> I have always thought that swapping occurred when there is insufficient 
>> memory for an application so another application or pages of an application 
>> could be swapped to disk to free RAM.
>> Given that there at least 32GB of RAM free, surely it would not need to page.
>> 
>> $ vmstat 30
>> kthr  memory page disk   
>>faults  cpu
>> r b wswap  free   re   mfpi po   fr de sr ro   s0 s1 s2  
>>  in   sy   cs   us sy id
>> 0 0 0 68532576 60872200 33 244   41 0  0   0  55   8   4   4 -0   4516   
>> 11765  66891 0 99
>> 0 0 0 49794916 48173452 1   431 344 0  0   00 49 23 25   0 18812 119079 
>> 53181   9 3 88
>> 0 0 0 49782568 48159484 2   725 300 0  0   00 32 16 17   0 16908 121531 
>> 53655 10 3 87
>> 0 0 0 49762892 48139892 0   754 218 0  0   00 33 17 17   0 20269 118644 
>> 52612 10 3 87
>> 0 0 0 49735940 48112244 3   595 407 0  0   00 54 28 27   0 19599 119165 
>> 53390 10 3 87
>> 0 0 0 49712360 48086132 2   476 244 0  0   00 37 19 19   0 19248 119117 
>> 53090 10 3 87
>> 0 0 0 49692084 48064828 17 444 435 0  0   00 43 22 21   0 19950 119938 
>> 53753 10 3 87
>> 
>> While it is only around 100MB can I tweak the system to avoid paging when 
>> there is so much ram?
>> 
>> TIA
>> 
>> Russell
>> 
>> 
>> 
>> 
>> ___
>> 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] Installing a new Openindiana via usb

[Toomas Soome via openindiana-discuss]

> On 7. Jul 2021, at 11:13, david allan finch  wrote:
> 
> On 07/07/21 09:02 AM, Toomas Soome via openindiana-discuss wrote:
>> disk-1: is error about boot loader stage 1 being unable to identify the boot 
>> disk (partition read failure or filesystem read failure or disk read failure 
>> - but then you should see additional error messages).
>> usb image does have GPT partition table, you could try to enter: status and 
>> see what device names will be printed.
> 
> Thanks for that. Attached is screenshot. Is there any docs for the boot 
> loader?
> 

there are several manuals, boot(1M), gptzzfsboot(5), loader(5).

in your case, the problem starts from the  fact that we do not get information 
about partitions, on screenshot, all disks are listed without partitioning 
information.

We would like to see something like:

disk0:  BIOS drive C (….)
  disk0p1:  EFI 256MB
  disk0p2: ….

and so on. I’m not really sure what did happen while usb image was written to 
the stick, but something seems to be wrong there. Does windows see any 
partitions there?

rgs,
toomas


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

Re: [OpenIndiana-discuss] Installing a new Openindiana via usb

[Toomas Soome via openindiana-discuss]

> On 7. Jul 2021, at 10:53, david allan finch  wrote:
> 
> Hi,
> 
> I have not installed openindiana on real hardware for sometime, done it lots 
> of times via a iso on virtualbox.
> 
> I copied the latest usb image with Win32DiskImager on to a usb thumbdrive.
> 
> When it boot I get:
> 
> list of c: ... and disk-x
> 
> illumos/x86 boot
> Can't find disk-1:/boot/loader
> 
> I have tried disk-0:/boot/loader etc and it still does nothing. Can some one 
> point me to what I am doing wrong?
> 
> TIA


disk-1: is error about boot loader stage 1 being unable to identify the boot 
disk (partition read failure or filesystem read failure or disk read failure - 
but then you should see additional error messages).

usb image does have GPT partition table, you could try to enter: status and see 
what device names will be printed.

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

Re: [OpenIndiana-discuss] Prerelease version of OpenIndiana Hipster 2021.04 for SPARC available for testing

[Toomas Soome via openindiana-discuss]

Also please note:

https://code.illumos.org/c/illumos-gate/+/1408 
<https://code.illumos.org/c/illumos-gate/+/1408>

rgds,
toomas

> On 17. Jun 2021, at 12:49, Volker A. Brandt  wrote:
> 
> Hello all!
> 
> 
> A new prerelease version of OpenIndiana Hipster 2021.04 for SPARC is
> available for testing.  The ISO image can be downloaded here:
> 
>  https://dlc.openindiana.aurora-opencloud.org/SPARC/
> 
> The corresponding IPS repository is here:
> 
>  https://pkg.openindiana.aurora-opencloud.org/oi-sparc/
> 
> There are a few issues during installation, so be sure to read the file
> 
>  OpenIndiana_Text_SPARC_06_2021.README
> 
> available in the download area above.
> 
> Note that this is not an official release of the OpenIndiana project.
> With your help, it could become one!
> 
> This prerelease is intended to provide a base for further development and
> testing.  In particular, the next step will be to make OpenIndiana for
> SPARC self-hosting using gcc7.  This is a fair amount of work yet.
> 
> The prerelease can be installed on a wide range of SPARC-based servers
> and workstations, both on bare metal and in an LDOM.   However, it is
> not yet possible to run a full desktop.
> 
> We would be happy to hear installation reports!
> 
> If you have questions, suggestions, or bug reports, please send an email
> to openindiana-discuss@openindiana.org or join the #openindiana IRC
> channel on libera.chat.
> 
> Many thanks to all who contributed!  The heavy lifting was done by Klaus
> Ziegler, with help from Toomas Soome, Andreas Wacknitz, Olaf Bohlen, Gary
> Mills, Peter Tribble, Till Wegmüller, and many others.  Thanks to Till
> for hosting both the download files and the repository!
> 
> 
> Have fun using OpenIndiana for SPARC!
> 
> 
> Best regards -- Volker
> -- 
> 
> Volker A. BrandtConsulting and Support for Solaris-based Systems
> Brandt & Brandt Computer GmbH   WWW: http://www.bb-c.de/
> Am Wiesenpfad 6, 53340 Meckenheim, GERMANYEmail: v...@bb-c.de
> Handelsregister: Amtsgericht Bonn, HRB 10513  Schuhgröße: 46
> Geschäftsführer: Rainer J.H. Brandt und Volker A. Brandt
> 
> "When logic and proportion have fallen sloppy dead"
> 
> ___
> 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] no new boot environment?

[Toomas Soome via openindiana-discuss]

> On 5. Jun 2021, at 11:47, Pierfrancesco Caci  wrote:
> 
> Hello,
> I see that OI is not creating a new boot environment since april, just the
> backup ones. Is this normal?
> 

it depends on package(s). installing/updating package(s) may not create 
anything, may create backup be or may create new be. This can also be 
controlled by command line options, see pkg(1).

rgds,
toomas


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

Re: [OpenIndiana-discuss] improving ZFS latency with hard disks

[Toomas Soome via openindiana-discuss]

> On 16. May 2021, at 06:54, d...@loud-mouth.net wrote:
> 
> Le me know if ZFS questions should be asked to another group.
> 
> Problem: A documentation application takes several minutes to open documents 
> containing large numbers of links to images. Aparently, the application is 
> making many separate file attribute queries, so the sum of all the separate 
> disk rotation latencies are adding up.
> 
> The obvious solution is to move the zfs pool over to SSDs, but since the 
> entire documentation collection is less than 10GB, I was wondering if there 
> was a way to address the problem with RAM. As far as I can tell from the 
> documentation, the ARC and L2ARC are based on recently used data, so it 
> doesn't sound like accessing attributes from all of the linked files to a 
> document would be helped by a larger ARC when the document is first opened.
> 
> Is there a way I can get more of the proximity files in the cache with any 
> tuning parameters, or even utilize some sort of RAM disk for the files in the 
> directory of concern?
> 


How much RAM do you have, what is arcstat reporting while accessing those 
files? Are files accessed locally or via NFS/SMB (where from the actual 
slowness is appearing)?

First open from slow media is always depending on media speed; however, the 
experience also depends on block sizes and fragmentation - does read ahead have 
chance to help etc.

With persistent L2ARC, the less actively used data is on L2 (active data is on 
ARC), but the L2 wont be empty after reboot. However, pointers to L2 are also 
in ARC, with low RAM situation, this may complicate things even more…

ramdisk versus ssd - I’d go for ssd there.

rgds,
toomas


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

Re: [OpenIndiana-discuss] The Register today

[Toomas Soome via openindiana-discuss]

> On 10. May 2021, at 12:05, Volker A. Brandt  wrote:
> 
> Toomas Soome writes:
>> The immediate issue is https://www.illumos.org/issues/2757. In core, this
>> issue means that negative 32-bit numbers are not translated to negative
>> 64-bit numbers. Currently used gcc 4.4.4 does implement such translation in
>> compiler, there is no such patch for more recent compilers (firstly, the
>> code path in more recent compilers has changed a lot, and secondly, such
>> translation should be done by OS). This effectively does block switch from
>> gcc 4.4.4. I actually am running gcc 7 built system, knowingly, keeping in
>> mind that I may be bitten by problems cause by this issue.
> 
> In other words, when that issue is fixed, the primary compiler could be
> switched to gcc 7?


yes, assuming the needed cleanups are done;) but then again, this issue has 
been open for ~10 years.


> 
>> Secondly, there are SPARC optimizer issues in gcc 7 and gcc 9 (likely with
>> 10 as well), crashing compiler while building specific parts of illumos
>> tree. One example:
> [...]
> 
> Could this be worked around by selectively turning off -O2 until that
> is fixed?

I have -O1 in my local patch, yes. But, the implication of this issue is, we do 
not really know how much, or to what extent, we can count on gcc. I do realize 
this does sound like FUD, but we do depend on external compiler and projects 
are rather removing SPARC support...

> 
>> I haven’t had time to open bugreport with gcc.
> 
> Fair enough.
> 
> [...]
>> As a side note, it is interesting to see SPARC related discussion in this 
>> list; there is no package repository for SPARC by OpenIndiana;)
> 
> Yes.  However, there are people working on new infrastructure for OI;
> as soon as that is in place there will be a public repo for OI/SPARC.
> 

Yes, I am aware of that too. From one hand it is nice, but from other hand, 
there is a reason *why* I would vote for removing SPARC support.

And the reason is, I do think we should stop looking backward and start looking 
forward. I’d rather spend my time on building support for things like arm64 or 
risc-v or some quantum computer or something what really matters for future of 
this OS.

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

Re: [OpenIndiana-discuss] The Register today

[Toomas Soome via openindiana-discuss]

> On 10. May 2021, at 10:33, Volker A. Brandt  wrote:
> 
> Toomas Soome via openindiana-discuss writes:
>> Please note that while IPD is filed, there is not yet line drawn, at least I
>> want to get few updates integrated so whoever will decide to create fork,
>> will get those bits too. That includes support for cpio boot archive (needs
>> forth boot code to read cpio), code to recognize T4 cpu properties and
>> perhaps few other bits.
> 
> We appreciate your work, Toomas!
> 
> What I find strange is that "public" reactions (like The Register) all
> mention lack of hardware.  There is a lot of hardware available, and
> hosting has been offered as well.
> 
> IMHO it's not hardware, it's people.
> 
> I would be interested in a description of the compiler problem that
> needs to be fixed to move SPARC forward, preferably in layman's terms.
> :-)  Or is it a number of unrelated issues?
> 
> TBH I never paid much attention because I just assumed that my skillset
> isn't up to understanding the problem anyway, let alone fixing it.
> 
> We are very close to having a self-hosted OpenIndiana for SPARC, and I
> would like to investigate how to leverage that.
> 
> 

The immediate issue is https://www.illumos.org/issues/2757. In core, this issue 
means that negative 32-bit numbers are not translated to negative 64-bit 
numbers. Currently used gcc 4.4.4 does implement such translation in compiler, 
there is no such patch for more recent compilers (firstly, the code path in 
more recent compilers has changed a lot, and secondly, such translation should 
be done by OS). This effectively does block switch from gcc 4.4.4. I actually 
am running gcc 7 built system, knowingly, keeping in mind that I may be bitten 
by problems cause by this issue.

Secondly, there are SPARC optimizer issues in gcc 7 and gcc 9 (likely with 10 
as well), crashing compiler while building specific parts of illumos tree. One 
example:

libcurses: gcc 9 bug with -O2

../screen/tparm.c: In function 'tparm':
../screen/tparm.c:727:1: error: insn does not satisfy its constraints:
  727 | }
  | ^
(insn:TI 66 1769 1770 (set (reg:DI 8 %o0)
(mem/u/c:DI (plus:DI (reg:DI 13 %o5)
(symbol_ref:DI ("result.4619") [flags 0x2] )) [0  S8 A64])) 125 {*movdi_insn_sp64}
 (expr_list:REG_EQUAL (symbol_ref:DI ("result.4619") [flags 0x2] 
)
(nil)))
during RTL pass: final
../screen/tparm.c:727:1: internal compiler error: in final_scan_insn_1, at 
final
.c:3013
0x6ba95b _fatal_insn(char const*, rtx_def const*, char const*, int, char 
const*)

/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/rtl-error.c:1
08
0x6ba997 _fatal_insn_not_found(rtx_def const*, char const*, int, char 
const*)

/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/rtl-error.c:1
18
0x42a623 final_scan_insn_1

/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/final.c:3013
0x42a6bf final_scan_insn(rtx_insn*, __FILE*, int, int, int*)

/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/final.c:3153
0x429fb7 final_scan_insn_1

/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/final.c:2759
0x42a6bf final_scan_insn(rtx_insn*, __FILE*, int, int, int*)

/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/final.c:3153
0x42a943 final_1

/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/final.c:2021
0x42c3cb rest_of_handle_final

/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/final.c:4659
0x42c3cb execute

/code/oi-userland/components/developer/gcc-9/gcc-9.3.0/gcc/final.c:4737
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.


I haven’t had time to open bugreport with gcc. 

And then there are some other issues related to optimizations/hacks created to 
support specific network cards, and so on. A lot of work to get those issues 
fixed, so that we wont be blocking illumos-gate, and unfortunately, very small 
group of users.

As a side note, it is interesting to see SPARC related discussion in this list; 
there is no package repository for SPARC by OpenIndiana;)

Considering all the above, I was also one of those asking if it is really good 
for illumos to keep this baggage. Perhaps it is time to let go.

rgds,
toomas


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

Re: [OpenIndiana-discuss] The Register today

[Toomas Soome via openindiana-discuss]

> On 10. May 2021, at 09:55, Tony Brian Albers  wrote:
> 
> https://www.theregister.com/2021/05/10/illumos_deprecates_sparc_support/?td=keepreading-btm
> 
> Sad, but that's the way it is.
> 

Please note that while IPD is filed, there is not yet line drawn, at least I 
want to get few updates integrated so whoever will decide to create fork, will 
get those bits too. That includes support for cpio boot archive (needs forth 
boot code to read cpio), code to recognize T4 cpu properties and perhaps few 
other bits.

rgds,
toomas


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