How to Repair Linux With Boot Failure

preview_player
Показать описание
This video shows you how to repair Linux when you have boot failure.

Рекомендации по теме
Комментарии
Автор

I like that you pronounce it "f-stab" like I always do in my mind. I have no idea how long it was until I realized it was "f.s.-tab" for "file system table".

kevinklement
Автор

12:06 This is why some people say that dd stands for "disk destroyer".
By the way, you can add the option status=progress to see a progress indicator.

tsundoku
Автор

It should be noted with chroot that if you're doing upgrade fixes and stuff you may need access to devices, in this case you will need to bind mount (mount --bind) /proc and /dev into the chroot environment first, failure to do so may come up with errors)

digitalsparky
Автор

For Debian-based, just use *boot-repair* if the issue is a GRUB issue (via a Live Session).

ThatLinuxDude
Автор

hahaha! watching on full screen then went blank screen i thought my laptop failed.

paulphoenix
Автор

This is a great lesson. I've screwed up installations and then apparently made them even worse using automated tools. It's always better to understand what's happening under the covers so you recover intelligently. Thanks!


EDIT: BTW I've started using Manjaro/XFCE and absolutely love how well it performs on all my machines.

Supperconductor
Автор

Another trick that often saved my ass, especially on systems that does not have a CD/DVD drive or when you don't have a USB pendrive with you, is to boot directly into an ISO image file.

Suppose that you have an bootable Live ISO image of the distro of your choice in your /home/user/Downloads/ folder or suppose that you have the foresight to put a Live ISO on your /boot/ folder. You can use Grub Shell to loopback mount the ISO image and boot directly into that disk image; this has the exact same effect as booting from USB drive without needing any extra hardware (or access to the USB port, if that matters). From the Live system, you can edit files on the installed system or chroot into the installed system, and if you used Live ISOs that boots into a graphical environment for installer, you would be able to do your fixing from a GUI environment (which has the benefit of having a working networking and a web browser).

yvrelna
Автор

Thank you man I was just fucked up with my Display Manager and Now I Saved My System Booting in bash just Worked out For Me

HarshYadav-yitv
Автор

11:37 "dd" stands for "data duplicator".
At 11:58 you can see why its alternative (and way more popular) name is "disk destroyer".

frenk
Автор

WOW I have a lot to learn. Thanks for the great lesson Chris

hypnosisauthority
Автор

Very nice. Few weeks ago I deleted my boot partition by accident, had to remember manual commands for partition creation, format, etc. I suggest a presentation for a disaster recovery when you disk has to be replaced and you need your OS back. What are the best tools, procedures, etc. for this kind of situation?

frclayton
Автор

OMG! I've been trying to solve this issue for weeks now, and finally stumble into your video IT WORKED!! Thank you very much.
I've installed W11 to my lap, because I needed to use proprietary software (only available in windows) did dual boot but my GrubHub disappeared and could boot back into Linux! But this fixed it thanks again!

ROLOGamingOfficial
Автор

Installing 32bit debian on Hyper-V is quite a headache, thankfully this video helps me

KangJangkrik
Автор

exactly yesterday I would have needed the recovery tricks as my filesystem had some errors that fsck didn't fix itself. :D

I already figured it out but this video would have saved me around 2 hours.

thanks for the vid, know more ways to fix it now! <3

alexandramiller
Автор

I realize this is an OLD video-- but I just found it and NEED IT.. THANKS

davidwayne
Автор

Thanks .. this was a real cool video. I had to do mount from CD to fix sudoers file. Another time, our VM crashed b/c it ran out of disk space. It wouldn't boot b/c of no disk space left. So, we booted of live CD and cleared space in /var/log and added more space to that logical volume.

maxsterling
Автор

Thank you Chris for this beautiful explanation of chroot. I asked you on Twitch about this. Greetings, Patrick. AKA SquadraMunter

squadramunter
Автор

Thank you for teaching me how to access the shell from grub! My problem was the nvidia drivers. I purged all nvidia content from my install and got back in 👌

AJMarraffa
Автор

Thank You!!! Was about to reinstall my OS but chroot fixed my problem!

andrewmerrin
Автор

Hey... how about a video on how to upgrade to a larger hard disk on an arch linux pc (without reinstalling)?

ckscullion