Sorry for the disturbance,
It was because fstab had btrfs
>
> Hello,
>
> file -Ls /dev/sdc5
> /dev/sdc5: Linux rev 1.0 ext4 filesystem data,
> UUID=1ea2d462-244f-4959-9a62-99a7288aa38c, volume name "root_sec" (extents)
> (64bit) (large files) (huge files)
>
> but
> fsck /dev/sdc5
> fsck from u
On Fri, 22 Apr 2022 at 07:05, wrote:
> On Thu, 2022-04-21 at 21:09 -0400, Jonathan Billings wrote:
> > On Apr 21, 2022, at 11:24, andreas.fourn...@runbox.com wrote:
> > >
> > > Anyway so I have a laptop that only boots to emergency shell. There
> > > journalctl says that fsck failed with exit sta
On Thu, 2022-04-21 at 21:09 -0400, Jonathan Billings wrote:
> On Apr 21, 2022, at 11:24, andreas.fourn...@runbox.com wrote:
> >
> > Anyway so I have a laptop that only boots to emergency shell. There
> > journalctl says that fsck failed with exit status 4 for
> > /dev/mapper/fedora-root
> > If I r
On Apr 21, 2022, at 11:24, andreas.fourn...@runbox.com wrote:
>
> Anyway so I have a laptop that only boots to emergency shell. There
> journalctl says that fsck failed with exit status 4 for
> /dev/mapper/fedora-root
> If I run fsck I only get back 'fsck from util-linux 2.37.4'
>
> Any advice ho
On Sat, Jan 17, 2015 at 3:06 AM, Kevin Wilson wrote:
> Chris,
> Thanks for your quick resonse!
>
> I do have /work in my /etc/fstab:
> /dev/sda3 /work ext3
>defaults1 1
Consider 2 for the last column, since it's not the root filesystem
Chris,
Thanks for your quick resonse!
I do have /work in my /etc/fstab:
/dev/sda3 /work ext3
defaults1 1
I will run the e2fsck -f on it very soon,,
Regards,
Kevin
On Sat, Jan 17, 2015 at 11:38 AM, Chris Murphy wrote:
> On Sat, Jan 17
On Sat, Jan 17, 2015 at 2:29 AM, Kevin Wilson wrote:
> It is ext4 on /work
OK so it's not root, which means you can just umount it and run e2fsck
without booting from alternate media.
I can't tell from the journal output, which appears incomplete as it
has no mention of the fsck at all, why you'
On Sat, Jan 17, 2015 at 2:01 AM, Ed Greshko wrote:
> On 01/17/15 16:55, Kevin Wilson wrote:
>> I should have mentioned also, that after fsck is completed, the
>> following messages is displayed:
>> Welcome to emergency mode! After logging in, type:
>> "journalctl -xb" to view system logs,
>>
It is ext4 on /work
journalctl -xb returns:
-- Unit user@0.service has finished starting up.
--
-- The start-up result is done.
Jan 02 02:41:40 amd systemd[1]: Sent message type=signal sender=n/a
destination=n/a object=/org/f
Jan 02 02:41:40 amd systemd-logind[499]: Got message type=signal
sender
On Sat, Jan 17, 2015 at 1:46 AM, Kevin Wilson wrote:
> Hello,
> I had installed Fedora 21. Each time I boot the system,
> fsck is running, which takes almost 5 minutes.
>
> What is the reason ? Can I avoid it ?
It sounds like the file system isn't cleanly unmounting in a fairly
bad way, because n
On 01/17/15 16:55, Kevin Wilson wrote:
> I should have mentioned also, that after fsck is completed, the
> following messages is displayed:
> Welcome to emergency mode! After logging in, type:
> "journalctl -xb" to view system logs,
> Give toot password for maintenance
> (or press Control-D to
I should have mentioned also, that after fsck is completed, the
following messages is displayed:
Welcome to emergency mode! After logging in, type:
"journalctl -xb" to view system logs,
Give toot password for maintenance
(or press Control-D to continue)
On Sat, Jan 17, 2015 at 10:46 AM, Kevin
On 09/26/2011 06:49 PM, Rick Stevens wrote:
> On 09/26/2011 06:29 PM, JD wrote:
>> On 09/26/2011 06:07 PM, Rick Stevens wrote:
>>> On 09/26/2011 05:55 PM, JD wrote:
On 09/26/2011 01:49 PM, Rick Stevens wrote:
> On 09/26/2011 01:25 PM, JD wrote:
>> On 09/26/2011 12:09 PM, Rick Stevens w
On 09/26/2011 06:29 PM, JD wrote:
> On 09/26/2011 06:07 PM, Rick Stevens wrote:
>> On 09/26/2011 05:55 PM, JD wrote:
>>> On 09/26/2011 01:49 PM, Rick Stevens wrote:
On 09/26/2011 01:25 PM, JD wrote:
> On 09/26/2011 12:09 PM, Rick Stevens wrote:
>> On 09/26/2011 11:59 AM, JD wrote:
On 09/26/2011 06:07 PM, Rick Stevens wrote:
> On 09/26/2011 05:55 PM, JD wrote:
>> On 09/26/2011 01:49 PM, Rick Stevens wrote:
>>> On 09/26/2011 01:25 PM, JD wrote:
On 09/26/2011 12:09 PM, Rick Stevens wrote:
> On 09/26/2011 11:59 AM, JD wrote:
>> kernel-2.6.35.14-96.fc14.i686
>>
>
On 09/26/2011 05:55 PM, JD wrote:
> On 09/26/2011 01:49 PM, Rick Stevens wrote:
>> On 09/26/2011 01:25 PM, JD wrote:
>>> On 09/26/2011 12:09 PM, Rick Stevens wrote:
On 09/26/2011 11:59 AM, JD wrote:
> kernel-2.6.35.14-96.fc14.i686
>
> During boot, when the time comes for fsck'ing
>
On 09/26/2011 01:49 PM, Rick Stevens wrote:
> On 09/26/2011 01:25 PM, JD wrote:
>> On 09/26/2011 12:09 PM, Rick Stevens wrote:
>>> On 09/26/2011 11:59 AM, JD wrote:
kernel-2.6.35.14-96.fc14.i686
During boot, when the time comes for fsck'ing
the file systems, whatever script is d
On 09/26/2011 01:49 PM, Rick Stevens wrote:
> On 09/26/2011 01:25 PM, JD wrote:
>> On 09/26/2011 12:09 PM, Rick Stevens wrote:
>>> On 09/26/2011 11:59 AM, JD wrote:
kernel-2.6.35.14-96.fc14.i686
During boot, when the time comes for fsck'ing
the file systems, whatever script is d
On 09/26/2011 01:25 PM, JD wrote:
> On 09/26/2011 12:09 PM, Rick Stevens wrote:
>> On 09/26/2011 11:59 AM, JD wrote:
>>> kernel-2.6.35.14-96.fc14.i686
>>>
>>> During boot, when the time comes for fsck'ing
>>> the file systems, whatever script is doing that,
>>> is exiting with an error status, even
On 09/26/2011 12:09 PM, Rick Stevens wrote:
> On 09/26/2011 11:59 AM, JD wrote:
>> kernel-2.6.35.14-96.fc14.i686
>>
>> During boot, when the time comes for fsck'ing
>> the file systems, whatever script is doing that,
>> is exiting with an error status, even though no
>> errors are displayed, and I
On 09/26/2011 11:59 AM, JD wrote:
> kernel-2.6.35.14-96.fc14.i686
>
> During boot, when the time comes for fsck'ing
> the file systems, whatever script is doing that,
> is exiting with an error status, even though no
> errors are displayed, and I am prompted to either
> enter the root password, or
21 matches
Mail list logo
