You are not logged in.
So, I tried to install the newest version a week ago. Everything went smooth to the point when there was the time to install/configure Grub and then I got an error (failed to install Grub). On the same laptop I have managed to install succesfully Mint and several Debian-based distros. Is this a known issue?
-mod edit- added [RESOLVED] to thread title
Last edited by hhh (2025-06-01 00:10:35)
Offline
Did you check TTY4 for the full error message?
Use <ctrl>+<alt>+F4 from the graphical installer or <alt>+F4 from the newt (text-based) installer.
Offline
I did not, unfortunately. Since I didn't have any issues with other Debian-based distros I assumed that there must have been a problem with the installer. The installer is not the easiest one and I accidentaly choose the option to override the disk (it was completely unnecessary) and when, after several hours, the installation process failed, I just gave up. I'm willing to try again in the future and wonder if any other users have had the same experience.
Offline
That particular generic message from the installer is not unusual. We would need the full error message from TTY4 or the install log to perform any diagnostics.
Offline
Good to know it's a known issue. Thanx!
Offline
Since I didn't have any issues with other Debian-based distros I assumed that there must have been a problem with the installer.
The BunsenLabs installer is the Debian installer.
There are just a few preseeded configurations:
d-i passwd/root-login boolean false
d-i passwd/user-default-groups string audio video cdrom floppy plugdev dip lp sudo lpadmin scanner bluetooth netdev systemd-journal
d-i mirror/country string manual
d-i mirror/protocol string https
d-i mirror/https/hostname string deb.debian.org
d-i mirror/https/directory string /debian
d-i mirror/https/proxy string
d-i apt-setup/use_mirror boolean true
d-i apt-setup/non-free boolean true
d-i apt-setup/non-free-firmware boolean true
d-i apt-setup/contrib boolean true
d-i apt-setup/services-select multiselect updates
d-i apt-setup/local0/repository \
string https://deb.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
d-i apt-setup/local0/comment string Debian security updates
d-i apt-setup/enable-source-repositories boolean false
d-i apt-setup/disable-cdrom-entries boolean true
d-i clock-setup/utc boolean true
d-i partman-auto/cap-ram string false
d-i preseed/late_command string \
if [ -e /cdrom/.disk/info ]; then cp /cdrom/.disk/info /target/tmp/disk_info ; fi;\
apt-install bunsen-os-release bunsen-python-apt-template ;\
in-target /usr/local/bin/bunsen_preseed ;\
in-target rm -f /usr/local/bin/bunsen_preseed
and the referred bunsen_preseed:
#!/bin/sh
# Grub menu top entry will now show "BunsenLabs".
update-grub
# recommends have been disabled in live-build, now restore
rm -f /etc/apt/apt.conf.d/00recommends
# add data to bunsen_install
mkdir -p /etc/bunsen
# disk_info has been copied to /tmp by a d-i late_command
if [ -r /tmp/disk_info ]
then
printf '%s' 'Disk info: ' | cat - /tmp/disk_info >> /etc/bunsen/bunsen_install
fi
rm -f /tmp/disk_info
echo "Install date: $(date --utc +%FT%T)" >> /etc/bunsen/bunsen_install
# make sure icon caches are all generated
# gtk-update-icon-cache may not have been installed in time for some icon themes
update-icon-caches /usr/share/icons/*
I can't see anything there that would make the grub install fail, and there have been no reports of such failures from other users.
As HoaS said, we would need to see the error log...
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Actually, I may have had the same problem in the past and it was related to the encryption. When I tried to encrypt my installation there was an issue with Grub, but everything worked fine without encryption. I don't remember if that was BunsenLabs, though. Well, I'll try it again and we'll see.
Last edited by Pirx (2025-03-02 12:53:07)
Offline
So, I tried once again on a different laptop and this time the instalation was successful, but I couldn't boot from the hard drive. All I got was a blinking cursor in the left top corner of the screen. Then I tried again, this time without encryption. And finally I've got a working BunsenLabs. Unfortunately, the problem with encryption is a major security issue and it looks like the Debian installer is to blame.
Offline
All I got was a blinking cursor in the left top corner of the screen
Did you try switching to a TTY? That sounds like the graphical desktop failed to load.
How about the installer log? You should be able to mount the root partition and share the file from the live ISO image. The journal of the installed system can also be read from the live environment using the --root=
option for journalctl(1).
Anyway, I'll see if I can reproduce this in QEMU...
EDIT: if you can reproduce this with a Debian image it's probably best to report it to them — the BunsenLabs devs can't fix the installer themselves.
EDIT2: encrypted installation works just fine under QEMU/KVM, I just selected the automated options because I don't use encryption myself so it even seems fairly idiot-proof.
Scrot or it didn't happen:
Last edited by Head_on_a_Stick (2025-03-03 21:55:00)
Offline
Did you try switching to a TTY? That sounds like the graphical desktop failed to load.
It was totally irresponsive a couple of seconds after the power button was pressed. That sounds like everything failed to load...
How about the installer log?
This time installer didn't report any problems.
EDIT: if you can reproduce this with a Debian image it's probably best to report it to them — the BunsenLabs devs can't fix the installer themselves.
They could replace it with something else... Some other Debian-based distros don't have this problem, but they use Calamares. It seems that the solution provided by Debian team doesn't always have to be the best one... Of course, it may look completely different on someone elses hardware.
Well, I've got working BunsenLabs. Now it's time for customizing.
Last edited by Pirx (2025-03-04 00:22:03)
Offline
It was totally irresponsive a couple of seconds after the power button was pressed
What does "totally irresponsive" mean, exactly? Did you try <ctrl>+<alt>+F4? Did the caps lock key light toggle when the key was pressed?
There is also the option of forcing a console boot from the GRUB screen with the systemd.unit=multi-user.target
kernel parameter.
Did you see the encryption password prompt? That was displayed on the TTY for my (fully functional) encrypted installation.
This time installer didn't report any problems
The log would contain important diagnostic information and the journal would show exactly what happened during the boot process. We can't troubleshoot without information.
They could replace it with something else
That would be a shitty way for BunsenLabs to treat Debian, don't you think? If a "major security issue" is found in the Debian installer BunsenLabs should try to track it down and fix it rather than just abandoning it.
Offline
That would be a shitty way for BunsenLabs to treat Debian, don't you think?
I don't. Things like that are widely accepted and happen all the time in Linux world. I'm pretty sure Debian people wouldn't mind.
To answer your questions. There was no password prompt, there was no grub menu. All I could see was my laptop manufacturer's logo for one sec. and then a black screen with a character blinking in the very top right corner. No working keyboard, mouse or touchpad. I could use the live version and, possibly, fix it, but do I really want to time travel back to 90s/early 00s? Nah.
Thanx anyway!
Last edited by Pirx (2025-03-04 08:38:28)
Offline
So, I tried it once again and... it worked!
Offline
Cool, marking the thread [RESOLVED].
BTW, we're not changing the installer based off one report of failure on one machine where the install eventually worked. Hope you understand.
I don't care what you do at home. Would you care to explain?
Offline
So, I tried it once again and... it worked!
With or without encryption?
You must unlearn what you have learned.
-- yoda
Offline
With encryption. The first attempt failed with an information that the changes to the disk have been written, but there was no way to inform the kernel about it. I tried to ignore the message, but the installation failed. I restarted the laptop, did everything again from scratch and this time it worked.
I've never expected the installer to be changed just because it failed on my machine. I don't think I'm that important. Just wanted you to know that Debian installer is not the easiest to use. I've tried it three times and every attempt resulted with a different output on exactly the same machine, which is a mystery to me.
Last edited by Pirx (2025-06-01 10:32:37)
Offline