5 Jun
2023
5 Jun
'23
6:21 a.m.
Hi Andy,
Thanks for your most thoughtful reply.
On 05/06/2023 05:32, Andy Smith via BitFolk Users wrote:
Hi Ian,
On Sun, Jun 04, 2023 at 09:52:40PM +0700, Ian Hobson via BitFolk Users wrote:
I did not know that there was a /etc/default/grub.
I thought of omitting /etc/default/grub and /etc/grub.d/* late last night.
8) Reboot. This shows the grub menu, but when I
select ubuntu
I get a black screen - and nothing further.
So I guess you need someone familiar with Proxmox to advise why it
might fail to boot like that. Unfortunately I don't have any
experience of Proxmox.
Your bit with the grub config looks fishy. Are there differences
between the /etc/default/grub that you have after doing a Proxmox
install and the one you're putting in to it? Particularly, a Xen
VM's use of hvc0 as a console is usually being set as a kernel
command line in /etc/default/grub and is likely not appropriate for
Proxmox.
Also unless I misunderstood, you are using rsync against a running
VM to overwrite the VM itself? If so, that's fraught with dangers.
You really should stop the target VM and mount its filesystem
somewhere, then rsync into that.
Your understanding is correct. I don't know
how to mount the VM disk in
Proxmox or Bitfolk - so I tried it anyway.
I generally recommend an approach of using config management to turn
a default install of the OS into something that is ready to serve
your data, and then a restore of data only from the source code
repository and database backups etc that it is stored in.
That is where I started. I have a huge Ansible playlist that I got fed
up with debugging.
I will persist with Ansible and not try to short circuit things!
[snip good advice]
Regards
Ian
--
Ian Hobson
Tel (+66) 626 544 695