Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "boot failure"
-
(Written March 13th at 2am.)
This morning (yesterday), my computer decided not to boot again: it halts on "cannot find firmware rtl-whatever" every time. (it has booted just fine several times since removing the firmware.) I've had quite the ordeal today trying to fix it, and every freaking step along the way has thrown errors and/or required workarounds and a lot of research.
Let's make a list of everything that went wrong!
1) Live CD: 2yo had been playing with it, and lost it. Not easy to find, and super smudgy.
2) Unencrypt volume: Dolphin reports errors when decrypting the volume. Research reveals the Live CD doesn't incude the cryptsetup packages. First attempts at installing them mysteriously fail.
3) Break for Lunch: automatic powersaving features turned off the displays, and also killed my session.
4) Live CD redux: 25min phonecall from work! yay, more things added to my six-month backlog.
5) Mount encrypted volume: Dolphin doesn't know how, and neither do I. Research ensues. Missing LVM2 package; lvmetad connection failure ad nauseam; had to look up commands to unlock, clone, open, and mount encrypted Luks volume, and how to perform these actions on Debian instead of Ubuntu/Kali. This group of steps took four hours.
6) Chroot into mounted volume group: No DNS! Research reveals how to share the host's resolv with the chroot.
7) `# apt install firmware-realtek`: /boot/initrd.img does not exist. Cannot update.
8) Find and mount /boot, then reinstall firmware: Apt cannot write to its log (minor), listed three install warnings, and initially refused to write to /boot/initrd.img-[...]
9) Reboot!: Volume group not found. Cannot process volume group. Dropping to a shell! oh no..
(Not listed: much research, many repeated attempts with various changes.)
At this point it's been 9 hours. I'm exhausted and frustrated and running out of ideas, so I ask @perfectasshole for help.
He walks me through some debugging steps (most of which i've already done), and we both get frustrated because everything looks correct but isn't working.
10) Thirteenth coming of the Live CD: `update-initramfs -u` within chroot throws warnings about /etc/crypttab and fsck, but everything looks fine with both. Still won't boot. Editing grub config manually to use the new volume group name likewise produces no boots. Nothing is making sense.
11) Rename volume group: doubles -'s for whatever reason; Rebooting gives the same dreaded "dropping to a shell" result.
A huge thank-you to @perfectasshole for spending three hours fighting with this issue with me! I finally fixed it about half an hour after he went to bed.
After renaming the volume group to what it was originally, one of the three recovery modes managed to actually boot and load the volume. From there I was able to run `update-initramfs -u` from the system proper (which completed without issue) and was able to boot normally thereafter.
I've run updates and rebooted twice now.
After twelve+ hours... yay, I have my Debian back!
oof.rant nightmare luks i'm friends with grub and chroot now realtek realshit at least my computer works again :< initrd boot failure8 -
"Hello R., how are you?"
"Hi M.! I'm at the beach now, finally relaxing after months of work."
"I wanted to ask you this: did you remember, three years ago, when you helped me move the downloaded movies to my external hard disk?"
"Er... yes?"
"Well, today I tried to start my computer and it's showing me a black screen telling \"disk boot failure, insert system disk\", do you know how to solve it? Before you worked on it, it used to work as a charm..."1 -
It all started on a nice summer afternoon. I was minding my own business just using my wonderful laptop with Windows 10 software installed. Then I woke up and realized the truth. I am sick of the scams, the lies, and the games. Today you will all see the same colors as me.
Most of you are probably on a Microsoft device and have had problems with it. A great example of Microsoft's failure is the line of phones they attempted to market. I was forced to own one for a period of time and it is absolute agony. Never force this way of life on another human being. While we are here, why the fuck is Optifine only available for Java Minecraft. Why even have two versions of the game when they cost the same?
These petty offenses are nothing compared to what I am about to tell you. As we all know, Bill Gates is friends with Mark Zuccerberg. Mark is known for his cult of reptile info scammers. Just this association alone is a red flag. This means that Bill Gates is a reptile as well. Reptiles only trust other reptiles.
These "people" are lying to us! Bill Gates just wants you to think he stepped down so he doesn't get the hate and shunning that comes with liking Microsoft. It was just an excuse to get his cult followers to do his job for him so he could run the new world order and the pedophile ring that he co-owns with Jeffrey Epstein. You think Satya Nadella is the "New CEO"?! Bullshit. He is just another Microsoft fleshlight.
Not only is Bill a disgusting liar, but he predicts the future and uses it to his advantage. This is how he has built his cult following and his multi-company empire.
You people need to wake the fuck up and boycott Microsoft. You are all being subliminally brainwashed into thinking it's okay and that "It's just the software" NO. Stop supporting pedophiles. Stop supporting reptiles. Stop supporting shitty products, and STOP LICKING THE CORPORATE BOOT. In conclusion, fuck Microsoft.10