[Nix-dev] NixOps on VServer (update)

[Tomasz Czyż]

Usually you have the layout like

disk
disk/partition1
disk/partition2

so you install grub on disk (/dev/sda, /dev/xvda) or something like that
(generally block device with partition table I think).
New grub also requires boot partition I think (but not 100% sure).

There are other methods how you can install grub or other boot loader, for
example gummibot. Now I think it's more general issue, not nixos specific
so maybe you can get infro from other sources.

I, in my setups, use that layout, block device + boot partition + other
partition

2017-03-28 0:55 GMT+01:00 <mb at thought2.de>:

> nice, this got me a step further. Now I face this however:
>
> network> closures copied successfully
> webserver> updating GRUB 2 menu...
> webserver> installing the GRUB 2 boot loader on /dev/disk/by-uuid/49dd2ea0-
> e795-4b57-b45a-0649794a804d...
> webserver> Installing for i386-pc platform.
> webserver> /nix/store/wvmch6hwsz5ls592c1qcjk0qcb8w8a
> jh-grub-2.x-2015-11-16/sbin/grub-install: warning: File system `ext2'
> doesn't support embedding.
> webserver> /nix/store/wvmch6hwsz5ls592c1qcjk0qcb8w8a
> jh-grub-2.x-2015-11-16/sbin/grub-install: warning: Embedding is not
> possible.  GRUB can only be installed in this setup by using blocklists.
> However, blocklists are UNRELIABLE and their use is discouraged..
> webserver> /nix/store/wvmch6hwsz5ls592c1qcjk0qcb8w8a
> jh-grub-2.x-2015-11-16/sbin/grub-install: error: will not proceed with
> blocklists.
> webserver> /nix/store/ivy5afbs8xrqm71xdqsll7z4kv37llh2-install-grub.pl:
> installation of GRUB on /dev/disk/by-uuid/49dd2ea0-e795-4b57-b45a-0649794a804d
> failed
> webserver> error: unable to activate new configuration
> error: activation of 1 of 1 machines failed (namely on ‘webserver’)
>
>
> I  just added the following copied from the remote hardware config to the
> deploy cfg:
>
>
>       fileSystems."/" =
>         { fsType = "ext4";
>           device = "/dev/disk/by-uuid/49dd2ea0-e795-4b57-b45a-0649794a804d";
> };
>
>       boot.loader.grub.devices = ["/dev/disk/by-uuid/49dd2ea0-
> e795-4b57-b45a-0649794a804d"];
>
> There's only one partition remote, is this maybe wrong? I mean should I
> either provide a separate boot partition or have the one of another type?
>
> thanks a lot for the hints!
>
>
>
>
>
> On 28.03.2017 01:34, Tomasz Czyż wrote:
>
> You are missing few required parts in your configuration.
>
> If you are deploying to the VM installed from CD or somethign like that
> you should get that in /etc/nixos/hardware-configuration.nix (or you can
> generate that with some command). There are settings about filesystems and
> boot options. Copy that to your config (or just put in "import" section).
>
> 2017-03-28 0:21 GMT+01:00 <mb at thought2.de>:
>
>> Here are more details to my previous message:
>>
>> I'm getting the following error, when deploying this
>> (http://lpaste.net/353990) config to a remote nix machine:
>>
>> nixops deploy -d network
>> building all machine configurations...
>> error:
>> Failed assertions:
>> - The ‘fileSystems’ option does not specify your root file system.
>> - You must set the option ‘boot.loader.grub.devices’ or
>> 'boot.loader.grub.mirroredBoots' to make the system bootable.
>> (use ‘--show-trace’ to show detailed location information)
>> error: unable to build all machine configurations
>>
>> Does anybody have an idea how to fix this?
>>
>> _______________________________________________
>> nix-dev mailing list
>> nix-dev at lists.science.uu.nl
>> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>>
>
>
>
> --
> Tomasz Czyż
>
>
>


-- 
Tomasz Czyż
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.science.uu.nl/pipermail/nix-dev/attachments/20170328/bcfa4265/attachment.html>