New Debian installation freezes during the black console boot phase.

Alright, I have already asked this question on the Debian subreddit so I will post that link here as to avoid repeating myself.

Once you have read that, I have an update on the situation. I realized that I was using an Intel version of the Debian installation so I changed it to the appropriate installation for my system which is amd64 and I reinstalled it. Now, I was very optimistic about this fixing the issue. However, it didn't. I attempted to boot up into the recovery mode and it produces similar results:

Exhibit A

Exhibit B

HOWEVER, it did manage to get to the root command line ONCE during a recovery boot. In my excitement I rebooted the system hoping to see it work again, sadly, it didn't.

I would really appreciate some help here, thank you all in advance. I hope I can get more help here than on Reddit.

Some hardware info of your system.

HP Pavilion Slimline s5753w Desktop AMD Athlon ll X2 240 2.8GHz 3GB 500GB W10Pro;
ATI Radeon 4200 (per #1 [your reddit post]); Debian 8.5.0? iso link? checksum ok?

Which are you booting in "recovery" mode:
*the iso* [cd? usb-stick?] OR: what you installed *on your hard-disk*?

I don't think the messages in those screenshots give enough 'clues', unfortunately.
Is that 'all' there is, before it 'hangs'?

Can you try a 'simpler' install [choose defaults / 'basic' config]?

Or maybe provide all precise details on each choice/step during install.
(doing an **image** web-search for: debian install tutorial
shows all the precise step-by-step choices being made)

Do you 'dual-boot' it? (Might you try it under VirtualBox?)

Look for boot options for debugging (advice from other LQ'ers welcomed!!!) radeon.modeset=0 single [?]

Basically, more 'clues' are needed. Sorry on getting stuck. Best wishes.

Welcome to the forum. I had a similar problem, detailed here.
http://www.linuxquestions.org/questi...ll-4175572537/

I solved this by a new install.
The Debian installation process is more complex than some other systems, and works best if
you have a wired (ethernet) connection during the install.

Edit: if a wired connection is not an option, you might want to read this thread to see how I worked around that issue.
http://www.linuxquestions.org/questi...fi-4175585967/

If you need more help, please ask, A working Debian OS is well worth the effort.

Originally Posted by Keruskerfuerst Some hardware info of your system.

The link I posted to reddit has a link to my system detailing everything you need to know, I assume you didn't read my topic clearly before you posted this.

In reply to Jjanel

Debian 8.5.0? 8.6.0
iso link? amd64
checksum ok? I don't remember that one

Which are you booting in "recovery" mode:
*the iso* [cd? usb-stick?] OR: what you installed *on your hard-disk*? Booting on the hard disk from GRUB

I don't think the messages in those screenshots give enough 'clues', unfortunately.
Is that 'all' there is, before it 'hangs'? Yes

Can you try a 'simpler' install [choose defaults / 'basic' config]? Besides the hard drive encryption, I didn't do anything fancy.

Do you 'dual-boot' it? (Might you try it under VirtualBox?) No, it was originally running Ubuntu. It is my webserver.

Originally Posted by offgridguy Welcome to the forum. I had a similar problem, detailed here. http://www.linuxquestions.org/questi...ll-4175572537/ I solved this by a new install. The Debian installation process is more complex than some other systems, and works best if you have a wired (ethernet) connection during the install. Edit: if a wired connection is not an option, you might want to read this thread to see how I worked around that issue. http://www.linuxquestions.org/questi...fi-4175585967/ If you need more help, please ask, A working Debian OS is well worth the effort.

I read your topic, it doesn't seem to relate very much if at all to my problem. I am aware of how to install Debian, my main computer is running Debian.
I have an Ethernet connection and I always do the netinst anyway.

Sorry, the only thing I can think of here is:
to somehow 'SEMI-disable' the graphics card, with grub kernel boot options like:
vga=0 nomodeset text etc

Can other LQ'ers help here? I searched the messages in the images (similar here to speed up things for others)

[   10.178477] nouveau W[     DRM] DCB type 4 not known
[   10.178482] nouveau W[     DRM] Unknown-1 has no encoders, removing
[   10.179323] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   10.179325] [drm] Driver supports precise vblank timestamp query.

One 'clue' is that: it gets a bit further on some boots: Exhibit B has only the first two of these messages
And you said: "it did manage to get to the root command line ONCE"

Any chance the *hardware* is bad/intermittent/failing? (probably not)

I'm beginning to think that these messages are ok/semi-normal; other LQ'ers advice??
(can you boot the .iso [cd?] ['single'/to-command-prompt] and look thru dmesg, for these?
Maybe the install picked the wrong nouveau/ati/amd driver [I don't know DRM KMS]:
running the *iso* [command-line-rescue], you can mount the hdd & look around [I think!]
Or try boot-repair-disk [maybe: big effort!], to generate TONS of info on your install!)

So, to generate a vital/key clue, can you try booting with the ATI [?mostly?] disabled?
(sorry, I'm not sure how; post what you use [or post asking for how...])

Originally Posted by Dr.Tyler O. HOWEVER, it did manage to get to the root command line ONCE during a recovery boot. In my excitement I rebooted the system hoping to see it work again, sadly, it didn't.

Judging from different errors at different boots, I wonder if the harddisk has physical error such as bad sectors.

If I were you, I would try booting with system rescue cd or so and check whether there is error in the encrypted harddisk and whether it can be decrypted and whether files in the encrypted harddisk can be recognized.
If they were recognized, I would copy all the necessary files in the encrypted hard disk to a safer place, such as an external USB-HDD.

What partitions are in the harddisk? Is there any separate /boot partition? Are you sure that the loaded initramfs and kernel contain necessary modules to decrypt the encrypted harddisk?