You are not logged in.
Pages: 1
Thank you for the video fsmithred, though, being use to crypt Debian based OS, that's already what I did.
I retried with the latest installer of the I386 server and it failed installing the same way it did with the previous version from January.
As it use to work with Chimaera server version (almost 2 years ago), I've tried the last version and the installation of it by using encryption works (so, the problem is specific to Daedalus, or at least, to its server version), so, I can use it in case I can't use Daedalus, but I'd prefer to use this last one.
Hi,
A few month ago, I could no more do up-dates with the server version of Chimaera because of some PGP issues (I tried a couple of times in a couple of days in case this would be a temporary problem, but it was not).
As my website was closed anyway and not really having time to fix that, I just shutdown the server until yesterday.
So, having time, I first looked at the website and saw that there's a Daedalus server version, so I thought it would be easier to make a fresh install from it. But I couldn't install it with encrypted partitions. I've tried many different things but it always stops at the same point with this error message:
[!!] Partitionner les disques
Échec de la configuration des volumes chiffrés
Une erreur s'est produite lors de la configuration des volumes chiffrés.
La configuration a été interrompue.
Here is my translation of that error message:
[!!]Disks partition
Encrypted volumes' configuration failure
An error happened while encrypting volumes' configuration.
The configuration has been interrupted.
Moreover, I noted something when trying to encrypt some volumes: when I go to “Configurer les volumes chiffrés” (That I translate: “Configure the encrypted volumes”), the next screen has a choice between “Créer des volumes chiffrés” (that I translate: “Create encrypted volumes”) and “Terminer” (That translates to “End”) and when I create those volume, instead of going to the next step, it goes back to that choice screen that I just described with “Créer des volumes chiffrés” preselected, so I go to “Terminer” and then it goes to the next step. Then, it fails and when I try again to create an encrypted volume, that screen that I described has “Terminer” preselected and each time I go to this screen, it has the last choice I did selected.
It might be the normal behaviour of the installer, but having then a failure with the encryption of some volumes, I noticed that and thought that this might be an abnormal behaviour that points more precisely to a bug causing that failure. I don't know, but just in case I'm not wrong, I thought it worth telling it.
When I read zapper and prospero, I'm kind of ashamed I completely stopped following this forum just because all just worked fine. I hope I'll take the time to follow the advancement of GNUinOS here and maybe in the Dng mailing list (I'm not decided about that now).
Whatever, thanks a lot to aitor for all his work.
Bye.
Did you install the server iso?
Yes.
If so, I recommend you to beep up the wired device using ifupdown
How is it that with the regular ISO the systems connects automatically and with the server ISO, it doesn't?
and install simple-netaid-cdk afterwards, that is the ncurses interface for simple-netaid. But don't forget to add yourself to the netaid group in order to get ubus working in simple-netaid. In doing so, you'll be able to make use of some networking tools such as wpasupplicant, ifupdown, ip, etc, without root permissions.
I prefer to set my server with root and when it's production ready, tie it to the domain name and then use root permission only if necessary.
Also, I prefer to learn by doing my own BASh starting-script. Why not re-inventing the wheels when it helps having a better understanding of the wheels you're using?
I've reinstall the server ISO, it looks like all works fine. Next step is to configure it.
By the way, for each installation I made, didn't check the “Console productivity” task in the installation, what does it contains?
Pay attention to your /etc/network/interfaces.
I forgot about that, I'll do it while configuring.
and the netinstall choice seems logical for a web server (that doesn't need a desktop environment).
Except there's a server ISO image…
Well, indeed, I saw the CD2, 3 and 4 and not knowing if this was only for the desktop ISO or for the server ISO too, I thought, well, the netinstall certainly doesn't need those and I went for the netinstall (and that forgot about that).
And now, seeing the size of the desktop ISO, I realize those CD2, 3 and 4 are not for the desktop.
So, I'll try the server ISO and see what will happen.
Edition: I've tried and it installed correctly but then, I can't use apt, there must be some problem with the repository, I'll look at that later, I must sleep now…
Bye.
Hi,
I tried to install GNUinOS chimaera 2023.05.08 i386 netinstall on an x86_64 old computer (I hope the i386 doesn't mean 32 bits or else that explains where the problem comes from).
I decided to use Chimaera because I want to do a web server and I prefer to have PHP 7 for a certain time before the big jump into PHP 8… and the netinstall choice seems logical for a web server (that doesn't need a desktop environment).
The first strange thing that happened was this message:
No Kernel modules found
No kernel modules were found. This probably is due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive.You should make sure that your installation image is up-to-date, or - if that's the case - try a different mirror, preferably deb.devuan.org
I continued anyway, but I think it explains what happened further.
Moreover, there where no root nor first user's creation (but I noticed that later).
Also, it was impossible to have a mount point if not choosing one of the few file system that for ext stopped in ext2.
After the crypt partitions' creation, ext4 was proposed but then no mount point was accessible, to render it accessible, the file system had to be changed.
Then, at the end of the installation, I had this message:
Aucun programme de démarrage installé
Aucun programme de démarrage n'a été installé, soit parce que vous avez volontairement choisi de ne pas le faire, soit parce qu'aucun ne gère actuellement l'architecture que vous utilisez.Vous devrez démarrer manuellement avec le noyau /vmlinuz qui se trouve sur la partition /dev/mapper/sda3_crypt et root=/dev/mapper/sda3_crypt quit passé en argument à ce noyau.
That I translate in English that way:
No starting software is installed
No starting software is installed, either because you voluntary chose not to do it, or because none are presently managing the architecture that you use.You'll have to start manually the kernel /vmlinuz that is in the /dev/mapper/sda3_crypt partition and root=/dev/mapper/sda3_crypt quit passed in argument to this kernel [sic].
And when I restarted the computer, of course:
GRUB loading..
Welcome to GRUB!error: no such cryptodisk found.
error: disk 'cryptouuid/(…)' not found.
Entering rescue mode...
grub rescue> _
Using GRUB's rescue is out of what I'm able to do, but I guess the problem couldn't be solved anyway.
Pages: 1