[OpenIndiana-discuss] Creating .volsetid without mkisofs

[Alexander Eremin]

On 26 нояб. 2013 г., at 14:35, Rainer Heilke <rheilke at dragonhearth.com> wrote:
> 
> I'm going to bed right now, but what does this do, set my system to try to boot in minimal state? And then what? The OS is already installed.

Installed but still use boot services from LiveCD, where logic of mounting root and usr filesystems differs from installed system.

Alex

> 
> Rainer
> 
>> On 11/26/2013 2:30 AM, Alexander Eremin wrote:
>> svcadm disable root:media usr:media sysidcfg:live-media root-minimal
>> svcadm enable root:default usr:default
>> svcadm enable sysidcfg:system sysidcfg:net
>> 
>> See http://wiki.openindiana.org/oi/Advanced+-+Manual+installation+of+OpenIndiana+from+LiveCD+media
>> 
>> Alexander
>> 
>>>> On 26 нояб. 2013 г., at 14:21, Rainer Heilke <rheilke at dragonhearth.com> wrote:
>>>> 
>>>> I'm trying to clean up this error:
>>>> rheilke at hastur:~$ svcs -xv
>>>> svc:/system/filesystem/root:media (root file system mount)
>>>> State: maintenance since November 25, 2013 03:10:44 PM PST
>>>> Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
>>>>   See: http://illumos.org/msg/SMF-8000-KS
>>>>   See: /var/svc/log/system-filesystem-root:media.log
>>>> Impact: This service is not running.
>>>> rheilke at hastur:~$ cat /var/svc/log/system-filesystem-root\:media.log
>>>> [ Nov 25 06:43:13 Enabled. ]
>>>> [ Nov 25 06:43:13 Rereading configuration. ]
>>>> [ Nov 25 06:43:13 Rereading configuration. ]
>>>> [ Nov 25 06:43:14 Executing start method ("/lib/svc/method/media-fs-root"). ]
>>>> /lib/svc/method/media-fs-root: line 60: /.volsetid: cannot open [No such file or directory]
>>>> ** FATAL **: Unable to access media
>>>> [ Nov 25 06:43:21 Method "start" exited with status 95. ]
>>>> [ Nov 25 15:10:27 Enabled. ]
>>>> [ Nov 25 15:10:36 Executing start method ("/lib/svc/method/media-fs-root"). ]
>>>> /lib/svc/method/media-fs-root: line 60: /.volsetid: cannot open [No such file or directory]
>>>> ** FATAL **: Unable to access media
>>>> [ Nov 25 15:10:44 Method "start" exited with status 95. ]
>>>> 
>>>> That is directly from the installed OS on the harddrive. If .volsetid isn't needed, why the errors? Is there some other way around this?
>>>> 
>>>> And it's beddy-bye for this bonzo...
>>>> Rainer
>>>> 
>>>> 
>>>>> On 11/26/2013 1:12 AM, Peter Tribble wrote:
>>>>> On Tue, Nov 26, 2013 at 9:03 AM, Rainer Heilke <rheilke at dragonhearth.com>wrote:
>>>>> 
>>>>> I've found the beginnings of my problems (thanks, Stefan). The 151a8
>>>>> LiveCD did not lay down a /.volsetid on my root filesystem (rpool). The one
>>>>> on the LiveCD doesn't work. So, how do I create one (with the right value)
>>>>> from scratch? I don't think mkisofs will work.
>>>>> 
>>>> What are you trying to do?
>>>> 
>>>> All that .volsetid is used for is to ensure that when you boot from
>>>> the Live CD, it can find the actual CD that matches the booted
>>>> image. (Just in case you have multiple CDs, it can identify the right
>>>> one.) The file isn't relevant to an installed system.
>>>> 
>>> -- 
>>> Mind the Gap
>>> Web: http://www.dragonhearth.com
>>> 
>>> _______________________________________________
>>> OpenIndiana-discuss mailing list
>>> OpenIndiana-discuss at openindiana.org
>>> http://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> -- 
> Mind the Gap
> Web: http://www.dragonhearth.com
>