[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: After installing no access to the installed system.



Am Mo., 18.März.2024 um 16:44:32 schrieb Greg Wooledge:
On Mon, Mar 18, 2024 at 03:24:14PM +0100, Thomas Schweikle wrote:
Package: Debian installer
Version: As on Debian live-CD/DVD for Debian 12.5
Severity: critical

Note that you sent this email to the debian-user list, not to the bug
tracking system.

I know. The bog tracking system wants me to use reportbug, but since I do not have access to the installed system i cant use reportbug to report a bug.

6. For User and Passwort enter
     Full name: demo Demo
     Username: de-de
     Password 1st: start123
     Password 2nd: start123
7. Click install
8. Wait until the installer finishes and reboots into this newly installed
system
9. Try to login with the credentials given above:
     User: de-de
     Password: start123

The newly installed system just tells: unknown user or password, user or
password wrong. You wont be able to login.

I wonder if it's the hyphen character.  Maybe the installer transforms
that into an underscore, or omits it entirely?  That's just a guess.

Thought it too, but it is not. The user isn't created even if i just name it without any specials. I've even tried to install using en_US. But without success: same problem. The user account is not created.

Anyway, try logging in as "dede" or "de_de", just to see if one of those
works.  Otherwise, you'll need to boot in rescue mode (or any equivalent
of your choice), and look at the /etc/passwd and /etc/shadow files.
See what happened.

It is even more wired: if the installed system is rebooted from install media -- after finishing installation the system does boot, but is not accessible. In lack of any useable user account created.

If i then remove installation media and reboot, the system just does not find anything to boot into: the bootloader is not installed at all! Grub is missing!

The after-install-reboot is triggered without going the whole way: they "boot" by loading the kernel from the running install system kernel using kexec. This is faster and avoids rebooting into the install system again, but it wont work if the boot system is just about to be missing, because neither grub nor systemd.boot are installed.
--
Thomas

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


Reply to: