On Wed 03 Feb 2021 at 15:56:58 (-0500), Greg Wooledge wrote:
> On Wed, Feb 03, 2021 at 02:06:04PM -0600, David Wright wrote:
> > >From foo/main/init where foo is
> > $ unmkinitramfs /boot/initrd.img foo/
>
> Interesting I used locate --regex to find where this is coming
> from, and it seems
On Wed, Feb 03, 2021 at 02:06:04PM -0600, David Wright wrote:
> >From foo/main/init where foo is
> $ unmkinitramfs /boot/initrd.img foo/
Interesting I used locate --regex to find where this is coming
from, and it seems there's a copy in /usr/share/initramfs-tools/init
which I'm guessing is
On Wed 03 Feb 2021 at 11:24:38 (-0500), Greg Wooledge wrote:
> On Wed, Feb 03, 2021 at 10:02:42AM -0600, David Wright wrote:
> > T'other way, I think, but no matter. For the record, there are
> > two different "strengths" for fsck:
> >
> > fastboot|fsck.mode=skip)
> > fastboot=y
> > ;;
> There are no man pages for "grub" or for "grubenv" on my system.
> There is a /boot/grub/grubenv file but it consists of one comment line,
> ending in a newline, and then enough # characters to make the file size
> exactly 1024 bytes. Incomprehensible.
This is just a place holder to make sure
On Wed, Feb 03, 2021 at 10:02:42AM -0600, David Wright wrote:
> T'other way, I think, but no matter. For the record, there are
> two different "strengths" for fsck:
>
> fastboot|fsck.mode=skip)
> fastboot=y
> ;;
> forcefsck|fsck.mode=force)
> forcefsck=y
> ;;
>
On Wed 03 Feb 2021 at 07:32:25 (-0500), Greg Wooledge wrote:
> On Tue, Feb 02, 2021 at 10:01:30PM -0600, David Wright wrote:
> > > # touch /forcefsck
> >
> > I think this is somewhat out of date, is it not.
>
> It is, yes. That no longer works in systemd.
>
> > I force fsck by adding
On Tue, Feb 02, 2021 at 10:01:30PM -0600, David Wright wrote:
> > # touch /forcefsck
>
> I think this is somewhat out of date, is it not.
It is, yes. That no longer works in systemd.
> I force fsck by adding forcefsck in grub, ie press e in
> the grub menu, move the cursor to the end of
On 03/02/2021 04:01, David Wright wrote:
> On Wed 03 Feb 2021 at 01:41:54 (+), Andy Smith wrote:
>> On Tue, Feb 02, 2021 at 07:13:16PM -0500, hobie of RMN wrote:
>>> My brother's Debian system suddenly says on attempt to boot, "/dev/sda1:
>>> UNEXPECTED INCONSISTENCY:Runfsck manually", and,
> On Wed, Feb 03, 2021 at 01:41:54AM +, Andy Smith wrote:
>> On Tue, Feb 02, 2021 at 07:13:16PM -0500, hobie of RMN wrote:
>> > He enters "fsck" or "fsck /dev/sda1", and in a short while gets fsck
>> > identifying it's version, and nothing else.
>>
>> There can be issues trying to run fsck on
On Wed 03 Feb 2021 at 01:41:54 (+), Andy Smith wrote:
>
> On Tue, Feb 02, 2021 at 07:13:16PM -0500, hobie of RMN wrote:
> > My brother's Debian system suddenly says on attempt to boot, "/dev/sda1:
> > UNEXPECTED INCONSISTENCY:Runfsck manually", and, "inodes that were part of
> > a corrupted
On Wed, Feb 03, 2021 at 01:41:54AM +, Andy Smith wrote:
> On Tue, Feb 02, 2021 at 07:13:16PM -0500, hobie of RMN wrote:
> > He enters "fsck" or "fsck /dev/sda1", and in a short while gets fsck
> > identifying it's version, and nothing else.
>
> There can be issues trying to run fsck on a
> You might have to boot from a recovery CD image, such as a Debian live
> install image, or GParted Live. You can't actually run fsck on a drive
> while said drive is mounted.
Thank, Jeremy. But - is /dev/sda1 mounted at this point? Isn't it being
indicated to us that it can't be successfully
Hi,
On Tue, Feb 02, 2021 at 07:13:16PM -0500, hobie of RMN wrote:
> My brother's Debian system suddenly says on attempt to boot, "/dev/sda1:
> UNEXPECTED INCONSISTENCY:Runfsck manually", and, "inodes that were part of
> a corrupted orphan linked list found."
>
> He enters "fsck" or "fsck
You might have to boot from a recovery CD image, such as a Debian live
install image, or GParted Live. You can't actually run fsck on a drive
while said drive is mounted.
On Tue, 2 Feb 2021 at 19:24, Stefan Monnier
wrote:
> >> My brother's Debian system suddenly says on attempt to boot,
>> My brother's Debian system suddenly says on attempt to boot, "/dev/sda1:
>> UNEXPECTED INCONSISTENCY:Runfsck manually", and, "inodes that were part of
>> a corrupted orphan linked list found."
>>
>> He enters "fsck" or "fsck /dev/sda1", and in a short while gets fsck
>> identifying it's
On 2/2/21 19:13, hobie of RMN wrote:
My brother's Debian system suddenly says on attempt to boot, "/dev/sda1:
UNEXPECTED INCONSISTENCY:Runfsck manually", and, "inodes that were part of
a corrupted orphan linked list found."
He enters "fsck" or "fsck /dev/sda1", and in a short while gets fsck
My brother's Debian system suddenly says on attempt to boot, "/dev/sda1:
UNEXPECTED INCONSISTENCY:Runfsck manually", and, "inodes that were part of
a corrupted orphan linked list found."
He enters "fsck" or "fsck /dev/sda1", and in a short while gets fsck
identifying it's version, and nothing
/dev/hda1 I
get another error:
/dev/hda1: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.
so how do I fix this? Was this coaused by Hale Life I installed? And how do
I run fsck?
Thanks guys
]
To: debian-user@lists.debian.org
Sent: Tuesday, June 20, 2000 5:16 PM
Subject: /dev/hda1: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.
Hello Group,
I am having a problem getting my Potato box to boot. I just installed a
Half
Life Game server and it has been working great all day. I tried to read my
it comes to checking /dev/hda1 I
get another error:
/dev/hda1: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY.
Just as a sanity check: you did reboot by way of a clean shutdown,
didn't you? If not, do; if so, then you may have hardware problems, so
make sure you have backups of anything important.
so
Joseph de los Santos [EMAIL PROTECTED] wrote:
man fsck? lol just kidding.. try to use e2fsck if you have it. e2fsck is
much better (in my opinion) in fixing file system problems.
e2fsck and fsck are identical on an ext2 filesystem, and on anything
else e2fsck won't work.
# In actuality,
[EMAIL PROTECTED] (Colin Watson) wrote:
Jay Kelly [EMAIL PROTECTED] wrote:
And how do I run fsck?
'man fsck'.
Hmm, sorry, I suppose you might not be able to get to the man pages
(though you should be able to find them somewhere on the web). Try 'fsck
/dev/hda1'.
--
Colin Watson
22 matches
Mail list logo
