boot fails
7 messages · started by Charles Breaux on May 26, 2022
boot fails
From Charles Breaux · May 26, 2022
boot fails
From Charles Breaux · May 26, 2022
Re: boot fails
From Devi Garcia · May 26, 2022
Use cat /proc/partitions or blkidin Busybox to get your partition details. The fsck command should fix your problem in a matter of seconds if not a minute, what follows should be on your screen after the magic takes place.
/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: 497733/30531584 files (0.5% non-contiguous), ........
If everything goes as planned reboot and you’re good to go by typing in “reboot” or “exit” then enter.
Quoted reply (2 lines)
On May 26, 2022, at 7:37 AM, Charles Breaux <chazbreaux@gmail.com> wrote: itrams)_
On May 26, 2022, at 7:37 AM, Charles Breaux <chazbreaux@gmail.com> wrote:
itrams)_
Re: boot fails
From Charles Breaux · May 26, 2022
Use cat /proc/partitions or blkidin Busybox to get your partition details. The fsck command should fix your problem in a matter of seconds if not a minute, what follows should be on your screen after the magic takes place. /dev/sda1: ***** FILE SYSTEM WAS MODIFIED ***** /dev/sda1: 497733/30531584 files (0.5% non-contiguous), ........ If everything goes as planned reboot and you’re good to go by typing in “reboot” or “exit” then enter.
Use cat /proc/partitions or blkidin Busybox to get your partition details. The fsck command should fix your problem in a matter of seconds if not a minute, what follows should be on your screen after the magic takes place.
<span><span>/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****</span><br>/dev/sda1: 497733/30531584 files (0.5% non-contiguous), ........</span>If everything goes as planned reboot and you’re good to go by typing in “reboot” or “exit” then enter.
On May 26, 2022, at 7:37 AM, Charles Breaux <chazbreaux@gmail.com> wrote:
itrams)_
Re: boot fails
From Gene Zastera · May 26, 2022
Charles
Here is my two cents worth. I think what Devi is referring to is that assuming you are in the grub loader or grub rescue, you should be able to type in those commands and get your file system fixed.
I’m certainly no expert on this stuff, but that is my interpretation of what Devi wrote. Try it and see if it works.
Gene
From: cochiselinux-bounce@freelists.org <cochiselinux-bounce@freelists.org> On Behalf Of Charles Breaux
Sent: Thursday, May 26, 2022 8:13 AM
To: cochiselinux@freelists.org
Subject: [cochiselinux] Re: boot fails
Thanks Devi. But, I do not understand. Use "cat /proc/partitions or blkidin Busybox to get your partition details." And " The fsck command should fix your problem" in a matter of seconds if not a minute, what follows should be on your screen after the magic takes place.
Don't know what the Busybox is. I assume the fsck command is entered into the terminal?
on reboot, will there be a prompt where I enter reboot or exit.
On Thu, May 26, 2022 at 8:00 AM Devi Garcia <asphyxiated.god@gmail.com> wrote:
Use cat /proc/partitions or blkid in Busybox to get your partition details. The fsck command should fix your problem in a matter of seconds if not a minute, what follows should be on your screen after the magic takes place. /dev/sda1: ***** FILE SYSTEM WAS MODIFIED ***** /dev/sda1: 497733/30531584 files (0.5% non-contiguous), ........ If everything goes as planned reboot and you’re good to go by typing in “reboot” or “exit” then enter.
Use cat /proc/partitions or blkidin Busybox to get your partition details. The fsck command should fix your problem in a matter of seconds if not a minute, what follows should be on your screen after the magic takes place.
<b><span>/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****</span></b><span><br>/dev/sda1: 497733/30531584 files (0.5% non-contiguous), ........</span>If everything goes as planned reboot and you’re good to go by typing in “reboot” or “exit” then enter.
On May 26, 2022, at 7:37 AM, Charles Breaux <chazbreaux@gmail.com> wrote:
itrams)_
Re: boot fails
From Charles Breaux · May 26, 2022
Charles Here is my two cents worth. I think what Devi is referring to is that assuming you are in the grub loader or grub rescue, you should be able to type in those commands and get your file system fixed.
Charles
Here is my two cents worth. I think what Devi is referring to is that assuming you are in the grub loader or grub rescue, you should be able to type in those commands and get your file system fixed.
I’m certainly no expert on this stuff, but that is my interpretation of what Devi wrote. Try it and see if it works.
Gene
From: cochiselinux-bounce@freelists.org <cochiselinux-bounce@freelists.org> On Behalf Of Charles Breaux
Sent: Thursday, May 26, 2022 8:13 AM
To: cochiselinux@freelists.org
Subject: [cochiselinux] Re: boot fails
Thanks Devi. But, I do not understand. Use "cat /proc/partitions or blkidin Busybox to get your partition details." And " The fsck command should fix your problem" in a matter of seconds if not a minute, what follows should be on your screen after the magic takes place.
Don't know what the Busybox is. I assume the fsck command is entered into the terminal?
on reboot, will there be a prompt where I enter reboot or exit.
On Thu, May 26, 2022 at 8:00 AM Devi Garcia <asphyxiated.god@gmail.com> wrote:
Use cat /proc/partitions or blkidin Busybox to get your partition details. The fsck command should fix your problem in a matter of seconds if not a minute, what follows should be on your screen after the magic takes place.
<b><span>/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****</span></b><span><br>/dev/sda1: 497733/30531584 files (0.5% non-contiguous), ........</span><u></u><u></u>If everything goes as planned reboot and you’re good to go by typing in “reboot” or “exit” then enter.
On May 26, 2022, at 7:37 AM, Charles Breaux <chazbreaux@gmail.com> wrote:
itrams)_
Re: boot fails
From Gene Zastera · May 26, 2022
Charles
This would be my suggestion. If you can’t read all the boot error message, try substituting another monitor. Then try to reboot. The different monitor may be able to display the message better.
After the boot attempt fails, you should be at the boot loader. Try entering the commands Devi suggested. I can’t guarantee that the commands he suggested are intended for the boot loader, but that is my guess. Anyway, if the boot loader doesn’t recognize the commands, they will fail, and I think no harm will be done from trying them. Or, if you don’t feel comfortable with the above suggestion, wait until one of the experts from the CLUG can give you advice that you are more comfortable with.
Gene
From: cochiselinux-bounce@freelists.org <cochiselinux-bounce@freelists.org> On Behalf Of Charles Breaux
Sent: Thursday, May 26, 2022 8:31 AM
To: cochiselinux@freelists.org
Subject: [cochiselinux] Re: boot fails
Thanks Gene. I don't even know what grub loader or rescue is.
On Thu, May 26, 2022 at 8:19 AM Gene Zastera <golfzulu1@gmail.com> wrote:
Charles Here is my two cents worth. I think what Devi is referring to is that assuming you are in the grub loader or grub rescue, you should be able to type in those commands and get your file system fixed.
Charles
Here is my two cents worth. I think what Devi is referring to is that assuming you are in the grub loader or grub rescue, you should be able to type in those commands and get your file system fixed.
I’m certainly no expert on this stuff, but that is my interpretation of what Devi wrote. Try it and see if it works.
Gene
From: cochiselinux-bounce@freelists.org <cochiselinux-bounce@freelists.org> On Behalf Of Charles Breaux
Sent: Thursday, May 26, 2022 8:13 AM
To: cochiselinux@freelists.org
Subject: [cochiselinux] Re: boot fails
Thanks Devi. But, I do not understand. Use "cat /proc/partitions or blkidin Busybox to get your partition details." And " The fsck command should fix your problem" in a matter of seconds if not a minute, what follows should be on your screen after the magic takes place.
Don't know what the Busybox is. I assume the fsck command is entered into the terminal?
on reboot, will there be a prompt where I enter reboot or exit.
On Thu, May 26, 2022 at 8:00 AM Devi Garcia <asphyxiated.god@gmail.com> wrote:
Use cat /proc/partitions or blkidin Busybox to get your partition details. The fsck command should fix your problem in a matter of seconds if not a minute, what follows should be on your screen after the magic takes place.
<b><span>/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****</span></b><span><br>/dev/sda1: 497733/30531584 files (0.5% non-contiguous), ........</span>If everything goes as planned reboot and you’re good to go by typing in “reboot” or “exit” then enter.
On May 26, 2022, at 7:37 AM, Charles Breaux <chazbreaux@gmail.com> wrote:
itrams)_