Disconnected PC for travel - Windows boots correctly but Ubuntu grub stops.
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Did you try one of the grub menu entries in advance option?
At the grub menu entry, press e for edit add to the end of the line that begins with linux:
noresume
Distribution: Ubuntu based stuff for the most part
Posts: 1,174
Rep:
Your grub is working fine, the error you posted was from the kernel recovering the filesystem journal, which is normal for an improper shutdown. As to why the kenrnel stops there we would need more info.
Ubuntu includes a handy recovery mode in grub in the Advanced menu. Boot from that and it will give you some recovery options.
I tried your suggestion by adding noresume at the end of the line which started with linux /boot etc and ended with $svt_handoff after leaving a space.
I rebooted and the result was the same, grub just stopped
Your grub is working fine, the error you posted was from the kernel recovering the filesystem journal, which is normal for an improper shutdown. As to why the kenrnel stops there we would need more info.
Ubuntu includes a handy recovery mode in grub in the Advanced menu. Boot from that and it will give you some recovery options.
I remembered that when I restarted the machine after reconnecting everything that I found the keyboard was not lit and saw that the cable was not correctly connected the the usbc port.
I looked at the first recovery option and tried some of the things listed but one gave Download errors another completed but when I dropped to root I was lost.
Before you disconnected the computer did you completely shutdown Ubuntu or was it just sleeping?
I would boot up into recovery mode or boot from a Ubuntu live USB and run fsck against all of your partition/filesystems to check for errors.
I disconnected the computer after it had been turned off/shutdown via the system overnight.
I used fsck from recovery mode and it suggested there were 9 obsolete file which should be removed. Other than removing those it did nothing to assist.
You don't have to chroot. Your just running a fsck and the filesystems shouldn't be mounted.
I know I don't need to chroot to fsck, as I said, I ran fsck from advanced grub options but it did not help. I was looking considering chroot to backup /home should I have to install Ubuntu, either reinstall 21.10 or the new LTS.
Your grub is working fine, the error you posted was from the kernel recovering the filesystem journal, which is normal for an improper shutdown. As to why the kenrnel stops there we would need more info.
Ubuntu includes a handy recovery mode in grub in the Advanced menu. Boot from that and it will give you some recovery options.
You don't have to chroot. Your just running a fsck and the filesystems shouldn't be mounted. Did you run fsck on your home and data partitions?
I did not see any option in the list of options to choose on which partitions to fsck. It just gave a 'run fsck' option and I assumed that was the whole system.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.