Ubuntu recovery option - opinions wanted.
-
After unpleasant experience win "new and improved" version of Ubuntu, I am back "experimenting" with Linux / Ubuntu recovery mode. So far I have this link Mastering Recovery and Rescue Mode in Ubuntu | FOSS Linux[^] It tells nothing new, and I am looking for a resource actually describing what Linux does when in "recovery mode". Especially when the process stops and there in no instruction on how to proceed / restart. Most of the time I end with "three fingers salute" and it generally reboots and I can start over. I have some shots of the failures, unfortunately I have no clue how to post them here. I am familiar using dmesg and wondering if there is way to do same when the "recovery mode" is abandoned using reboot. Thanks for reading.
-
After unpleasant experience win "new and improved" version of Ubuntu, I am back "experimenting" with Linux / Ubuntu recovery mode. So far I have this link Mastering Recovery and Rescue Mode in Ubuntu | FOSS Linux[^] It tells nothing new, and I am looking for a resource actually describing what Linux does when in "recovery mode". Especially when the process stops and there in no instruction on how to proceed / restart. Most of the time I end with "three fingers salute" and it generally reboots and I can start over. I have some shots of the failures, unfortunately I have no clue how to post them here. I am familiar using dmesg and wondering if there is way to do same when the "recovery mode" is abandoned using reboot. Thanks for reading.
-
After unpleasant experience win "new and improved" version of Ubuntu, I am back "experimenting" with Linux / Ubuntu recovery mode. So far I have this link Mastering Recovery and Rescue Mode in Ubuntu | FOSS Linux[^] It tells nothing new, and I am looking for a resource actually describing what Linux does when in "recovery mode". Especially when the process stops and there in no instruction on how to proceed / restart. Most of the time I end with "three fingers salute" and it generally reboots and I can start over. I have some shots of the failures, unfortunately I have no clue how to post them here. I am familiar using dmesg and wondering if there is way to do same when the "recovery mode" is abandoned using reboot. Thanks for reading.
Well, since this forum is aimed at developers (mostly Windows), you would probably do better in the Ubuntu forums. I see this on one:
Quote:
What is the use of recovery mode options? There are a total of 8 options: resume: Resumes to the normal boot with the selected kernel. clean: As the name suggests, it is used to free up some storage space. dpkg: If you installed a package and due to some reason, it wasn't installed properly, or is broken and your system is malfunctioning, then, you can use this option. fsck: It will perform an intensive file check on your drives and attempt to solve if found any. grub: Update the grub config file. network: Activates the internet so you can perform all the operations like updating packages, or upgrading to a new version of Ubuntu, etc. root: Drops you in the root shell with all the privileges you would ever need to modify or troubleshoot the system. system-summary: Prints system information including partitions, RAM, network config, and more.
You can also use it for forgotten password. Personally, running debian, I use a live CD/USB when I screw things up. I also use a free imaging program to back my system up. Lou
>64 It’s weird being the same age as old people. Live every day like it is your last; one day, it will be.
-
Well, since this forum is aimed at developers (mostly Windows), you would probably do better in the Ubuntu forums. I see this on one:
Quote:
What is the use of recovery mode options? There are a total of 8 options: resume: Resumes to the normal boot with the selected kernel. clean: As the name suggests, it is used to free up some storage space. dpkg: If you installed a package and due to some reason, it wasn't installed properly, or is broken and your system is malfunctioning, then, you can use this option. fsck: It will perform an intensive file check on your drives and attempt to solve if found any. grub: Update the grub config file. network: Activates the internet so you can perform all the operations like updating packages, or upgrading to a new version of Ubuntu, etc. root: Drops you in the root shell with all the privileges you would ever need to modify or troubleshoot the system. system-summary: Prints system information including partitions, RAM, network config, and more.
You can also use it for forgotten password. Personally, running debian, I use a live CD/USB when I screw things up. I also use a free imaging program to back my system up. Lou
>64 It’s weird being the same age as old people. Live every day like it is your last; one day, it will be.
Thanks for the reply, appreciate that. Unfortunately that is not what I am asking. You did describe the recovery options, I am asking what to do when ANY of these options STOPS posting "progress messages". There is one and it is pretty clear ...to continue ... press... ...to stop... press "enter" Some messages get stopped in ...timed out... doing whatever Anyway - I need to find a way to convert these messages to text and post them here...
-
Thanks for the reply, appreciate that. Unfortunately that is not what I am asking. You did describe the recovery options, I am asking what to do when ANY of these options STOPS posting "progress messages". There is one and it is pretty clear ...to continue ... press... ...to stop... press "enter" Some messages get stopped in ...timed out... doing whatever Anyway - I need to find a way to convert these messages to text and post them here...
Like I said, this is probably not the best forum for that.
>64 It’s weird being the same age as old people. Live every day like it is your last; one day, it will be.
-
After unpleasant experience win "new and improved" version of Ubuntu, I am back "experimenting" with Linux / Ubuntu recovery mode. So far I have this link Mastering Recovery and Rescue Mode in Ubuntu | FOSS Linux[^] It tells nothing new, and I am looking for a resource actually describing what Linux does when in "recovery mode". Especially when the process stops and there in no instruction on how to proceed / restart. Most of the time I end with "three fingers salute" and it generally reboots and I can start over. I have some shots of the failures, unfortunately I have no clue how to post them here. I am familiar using dmesg and wondering if there is way to do same when the "recovery mode" is abandoned using reboot. Thanks for reading.
I had challenges and they were related to two things: 1. firefox playing media (usually video) 2. running a NVIDIA Corporation TU116 [GeForce GTX 1660] video card. My machine would lock up for no apparent reason when I ran Firefox and viewed youtube videos. I have never had any problems except when I ran firefox. I was kind of bummed out bec I liked Firefox but something with the NVIDIA drivers and firefox would lock up every time. Also, have to run NVIDIA proprietary drivers -- under Software & Updates "Using Nvidia Server Driver metapackage from nvidia-driver-535-server properiatary" If you have an NVIDIA video it is probably the root of the issue. Good luck
-
I had challenges and they were related to two things: 1. firefox playing media (usually video) 2. running a NVIDIA Corporation TU116 [GeForce GTX 1660] video card. My machine would lock up for no apparent reason when I ran Firefox and viewed youtube videos. I have never had any problems except when I ran firefox. I was kind of bummed out bec I liked Firefox but something with the NVIDIA drivers and firefox would lock up every time. Also, have to run NVIDIA proprietary drivers -- under Software & Updates "Using Nvidia Server Driver metapackage from nvidia-driver-535-server properiatary" If you have an NVIDIA video it is probably the root of the issue. Good luck
-
oh, my Ubuntu installation would complete FREEZE when certain media was played. The screens were frozen but I could still see the cursor move around the screen, but nothing else. Recreated the issue numerous times with Firefox. No other browser causes the problem. unfortunately left firefox behind.