You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-12-11 00:30:36
The new version is currently in beowulf-proposed-updates and will be moved to the main beowulf repository very soon. You could install it from there in the live session and then do the installation.
That's awesome, thanks so much!
#2 Re: Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-12-09 22:46:45
No worries. Good to know that the netinstall ISO works in this case, thanks.
#3 Re: Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-12-08 23:12:27
Finally moved from the grub rescue prompt :)
I've done:
grub-install /dev/sda
update-grub...then fixed the UUID in grub.cfg and rebooted. I got the theme warning, then the boot menu, entered the disk password, and then:
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /run on /root/run failed: No such file or directory
run-init: can't execute '/sbin/init': No such file or directory
Target filesystem doesn't have requested /sbin/init.
run-init: can't execute '/sbin/init': No such file or directory
run-init: can't execute '/etc/init': No such file or directory
run-init: can't execute '/bin/init': No such file or directory
run-init: can't execute '/bin/sh': No such file or directory
run-init: can't execute '': No such file or directory
No init found. Try passing init= bootarg.
BusyBox v1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)I've tried going back and doing "update-initramfs.orig.initramfs-tools -u -k all" again, but it's the same. The crypttab and fstab configs are unchanged.
I'll check out the test ISO when I get the time, thanks for the link :)
#4 Re: Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-12-08 11:53:03
Ok, so I did:
update-initramfs.orig.initramfs-tools -u -k all...which returned no errors, then rechecked grub.cfg (as per Jafa's post), rebooted, but I still get the same result.
This is the current fstab:
/dev/mapper/crypt / ext4 errors=remount-ro 0 1
UUID=37a1d9e9-2597-4fc7-ad7f-95def918c030 /boot ext4 defaults,noatime, 0 2
/swapfile none swap sw 0 0...and the current crypttab:
# <target name> <source device> <key file> <options>
crypt UUID=b23b7722-8c39-47f1-a49b-cd6cc7ac4eae none luks,discard#5 Re: Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-12-08 00:03:50
Running either "update-initramfs -u" or "update-initramfs -u -k all" results in:
I: update-initramfs is disabled (live system is running without media mount on /lib/live/mount/medium).I tried doing "apt-get install --reinstall linux-image-${kernel_ver}-generic linux-signed-image-${kernel_ver}-generic" and also managed to do "mkinitramfs -o /boot/initrd.img-${kernel_ver}-generic ${kernel_ver}-generic" without any errors, but I get the exact same grub rescue prompt when trying to boot, with the wrong UUID (and I've checked grub.cfg before rebooting).
#6 Re: Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-12-07 09:37:16
Hey, thanks for the input :)
I've tried replacing "05eb424f-c4f8-4a5e-88d4-7a95764f7e58" with "37a1d9e9-2597-4fc7-ad7f-95def918c030" in grub.cfg, but it's as if no changes were made:
error: no such device: 05eb424f-c4f8-4a5e-88d4-7a95764f7e58
error: unknown filesystem.
Entering rescue mode...
grub rescue>I'm assuming an "update-grub" is required, but that reverts the changes in grub.cfg.
I still haven't booted into the OS, but I've entered chroot again and modified crypttab and fstab as you said, but I can't figure out the "mkinitramfs" part...
#7 Re: Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-11-20 21:51:45
The error message about grub-pc already being the newest version makes no sense. (Unless it said grub-pc-bin) because grub-pc is not installed in the amd64 desktop-live iso.
As in, it shouldn't be there in the installed system? The deb package is included in the ISO, though. The second step during installation states:
### WARNING ###
grub-pc is not installed but you booted in bios mode.If you have the grub-pc deb packages, you will be given a chance to install them into the new system.
grub package(s) found in /grub-pc_2.02+dfsg1-20_amd64.deb
Comment out this line in /etc/default/grub:
I could've guessed that it was there. Sorry, should've taken a look before asking.
I haven't tried copying the theme folder, but it doesn't bother me, as I usually disable the GRUB timeout anyway.
I know why you didn't get asked where to put the bootloader. That was a change in grub and a later version of refractainstaller corrects for that.
Oh, good to know. Looking forward to Chimaera, then :D
At least the second method works. It's an extra step during installation, but easy enough. Thanks!
#8 Re: Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-11-19 19:57:51
Ok, so I've tried both methods in separate VMs.
Method 1 - I've done as follows (not sure if correct):
cryptsetup luksOpen /dev/sda2 root
mount /dev/mapper/root /mnt
mount /dev/sda1 /mnt/boot
mount --bind /dev/ /mnt/dev
mount --bind /dev/pts /mnt/dev/pts
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt
apt install grub-pc...which resulted in:
grub-pc is already the newest version
Then I did:
apt update
apt install grub-pc
update-grubThe only two files that appeared after that were "grub.cfg" and "unicode.pf2" in /boot/grub. Then:
exit
umount /mnt/sys
umount /mnt/proc
umount /mnt/dev/pts
umount /mnt/dev
umount /mnt/boot
umount /mnt
rebootAnd I got the exact same result:
error: no such device: 05eb424f-c4f8-4a5e-88d4-7a95764f7e58
error: unknown filesystem.
Entering rescue mode...
grub rescue>
Method 2:
apt update
apt install grub-pcSkipped installing the bootloader, but again I got "Copy Files", not "Install Bootloader", during installation.
Chose "Copy Files", which installed GRUB without asking me where I want to install it, though without errors. Rebooted, and it actually works :)
The only thing is, before seeing GRUB, I see this for a few seconds every time:
error: no such device: [UUID]
error: file `/usr/share/desktop-base/grub-themes/cinnabar-grub/unifont-regular-16.pf2' not found.
error: file `/usr/share/desktop-base/grub-themes/cinnabar-grub/theme.txt' not found.Press any key to continue...
The UUID above refers to /dev/mapper/root. I get that if I disabled GRUB theming, this wouldn't be an issue, but I don't know how to do that.
I've also sent you an email with the installer log.
Thanks
#9 Re: Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-11-18 22:50:19
No, the partition table is msdos:
Disklabel type: dosroot seems to be fine:
total 262413
drwxr-xr-x 2 root root 4096 May 30 17:28 bin
drwxr-xr-x 3 root root 1024 Nov 18 15:41 boot
drwxr-xr-x 15 root root 3380 Nov 18 23:22 dev
drwxrwxr-x 132 root root 12288 Nov 18 15:43 etc
drwxrwxr-x 2 root root 4096 Feb 11 2019 firmware
-rw-r--r-- 1 root root 39768 Jun 25 2019 grub-efi-ia32_2.02+dfsg1-20_amd64.deb
-rw-r--r-- 1 root root 130960 Jun 25 2019 grub-pc_2.02+dfsg1-20_amd64.deb
drwxrwxr-x 3 root root 4096 Nov 18 15:43 home
lrwxrwxrwx 1 root root 30 May 30 17:36 initrd.img -> boot/initrd.img-4.19.0-9-amd64
drwxr-xr-x 20 root root 4096 May 30 17:36 lib
drwxr-xr-x 2 root root 4096 May 30 16:31 lib64
drwx------ 2 root root 16384 Nov 18 15:38 lost+found
drwxr-xr-x 2 root root 4096 May 30 16:30 media
drwxr-xr-x 2 root root 4096 May 30 16:30 mnt
drwxr-xr-x 2 root root 4096 May 30 16:30 opt
dr-xr-xr-x 153 root root 0 Nov 18 23:21 proc
drwxr-xr-x 4 root root 4096 Nov 18 17:57 root
drwxr-xr-x 5 root root 4096 Nov 18 15:41 run
drwxr-xr-x 2 root root 12288 May 30 17:25 sbin
drwxr-xr-x 2 root root 4096 May 30 16:30 srv
-rw------- 1 root root 268435456 Nov 18 15:40 swapfile
dr-xr-xr-x 13 root root 0 Nov 18 23:21 sys
drwxr-xr-x 2 root root 4096 Nov 18 15:37 target_boot
drwxrwxrwt 2 root root 4096 Nov 18 15:41 tmp
drwxr-xr-x 10 root root 4096 May 15 2020 usr
drwxr-xr-x 11 root root 4096 May 30 16:30 var
lrwxrwxrwx 1 root root 27 May 30 17:36 vmlinuz -> boot/vmlinuz-4.19.0-9-amd64...but /boot definitely isn't:
total 49530
-rw-r--r-- 1 root root 206157 Apr 29 2020 config-4.19.0-9-amd64
-rw-r--r-- 1 root root 41807144 Nov 18 15:41 initrd.img-4.19.0-9-amd64
drwx------ 2 root root 12288 Nov 18 15:37 lost+found
-rw-r--r-- 1 root root 3411358 Apr 29 2020 System.map-4.19.0-9-amd64
-rw-r--r-- 1 root root 5278960 Apr 29 2020 vmlinuz-4.19.0-9-amd64In regards to /var/log/refractainstaller.log - would manually creating the /boot/grub/ directory (before trying to install GRUB during the installation process) help?
Or is there another way of fixing this?
Thanks
#10 Installation » Separate, non-encrypted /boot on BIOS/MBR » 2020-11-18 16:53:29
- user1120
- Replies: 20
Hi everyone,
First time poster here. Just wanted to start off by saying that I really appreciate the great work of everyone involved in this project. This is an awesome distro!
I've been using it for some time and now I wanted to try out a new setup, but I seem to be stuck.
I'm trying to set up a BIOS/MBR installation with an encrypted root and /home on a single partition (/dev/sda2), and a separate non-encrypted /boot on another partition (/dev/sda1). I'm using the "devuan_beowulf_3.0.0_amd64_desktop-live.iso" image (haven't tested any of this in Ascii). During the installation process, when prompted to install GRUB, I choose the "Copy files" option and select "/dev/sda" as the location (even if I select both "/dev/sda" and "/dev/dm-0", the result is the same). This results in an error:
Error detected: 2
See /var/log/refractainstaller.log for details.
This may not be fatal.. Press "Continue" to proceed anyway
The part of the log which refers to this is as follows:
+ [[ grub-pc*.deb =~ grub-pc ]]
+ grubversion=grub-pc
+ [[ grub-pc*.deb =~ grub-efi ]]
+ install_grub
+ echo 'Setting up grub bootloader.. Please wait..'
+ [[ -n /dev/sda1 ]]
+ chroot /target mount /dev/sda1 /boot
+ [[ -n '' ]]
+ [[ '' = \e\f\i ]]
+ [[ -n '' ]]
+ chroot /target update-grub
/usr/sbin/grub-mkconfig: 253: /usr/sbin/grub-mkconfig: cannot create /boot/grub/grub.cfg.new: Directory nonexistent
+ check_exit
+ exit_code=2After finishing the installation and rebooting, the system drops to GRUB rescue mode:
error: no such device: 05eb424f-c4f8-4a5e-88d4-7a95764f7e58
error: unknown filesystem.
Entering rescue mode...
grub rescue>This is the fstab:
/dev/mapper/root_fs / ext4 defaults,noatime 0 1
UUID=37a1d9e9-2597-4fc7-ad7f-95def918c030 /boot ext4 defaults,noatime, 0 2
/swapfile none swap sw 0 0This is the crypttab:
# <target name> <source device> <key file> <options>
root_fs UUID=b23b7722-8c39-47f1-a49b-cd6cc7ac4eae none luksAnd this is the output of blkid:
/dev/sda1: UUID="37a1d9e9-2597-4fc7-ad7f-95def918c030" TYPE="ext4" PARTUUID="df76ca67-01"
/dev/sda2: UUID="b23b7722-8c39-47f1-a49b-cd6cc7ac4eae" TYPE="crypto_LUKS" PARTUUID="df76ca67-02"
/dev/mapper/crypt: UUID="05eb424f-c4f8-4a5e-88d4-7a95764f7e58" TYPE="ext4"I've tried multiple solutions found on the web, but I didn't get anywhere. I've done another reinstall, so in case anyone has any suggestions, we're on a clean slate.
Interestingly enough, if I perform a UEFI/GPT installation with the exact same settings (apart from an additional partition for EFI), GRUB is installed without errors and everything works as expected. Just to make sure it wasn't a BIOS settings issue, I've performed identical installations in VirtualBox, but the result is the same - UEFI works, BIOS doesn't. The reason why I insist on BIOS is because the machine that I'm planning to install this kind of a setup on doesn't have UEFI.
Before any of this, I've tried the full disk encryption (FDE) setup, /boot included, and, ironically, both BIOS and UEFI work as expected, but I had to give up on it, as typing the same password twice at every boot would be a real PITA for the end user.
Apologies for the wall of text. Any help is greatly appreciated! :)
Pages: 1
Board footer
