2:46 a.m.
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 ?
Regards,
Kevin
3:01 a.m.
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 continue)
What file system was being checked? And did you type "journalctl -xb" to view
system logs....
--
If you can't laugh at yourself, others will gladly oblige.
2:55 a.m.
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 Wilson <wkevils(a)gmail.com> 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 ?
Regards,
Kevin
4:06 a.m.
Chris,
Thanks for your quick resonse!
I do have /work in my /etc/fstab:
/dev/sda3 /work ext3
defaults 1 1
I will run the e2fsck -f on it very soon,,
Regards,
Kevin
On Sat, Jan 17, 2015 at 11:38 AM, Chris Murphy <lists(a)colorremedies.com> wrote:
On Sat, Jan 17, 2015 at 2:29 AM, Kevin Wilson
<wkevils(a)gmail.com> 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're dropped to rescue
kernel. If /work is in fstab then it's required for basic.target
unless you have nofail or noauto as a mount option, so I'm guessing
the fsck preen failed to fix the problem and so basic.target fails.
So yeah, run e2fsck -f on this volume, and then take a cell phone
photo and put it up somewhere. That's easier than typing it all out.
--
Chris Murphy
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
3:20 a.m.
On Sat, Jan 17, 2015 at 1:46 AM, Kevin Wilson <wkevils(a)gmail.com> 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 normally journal replay is sufficient. If there's an
inconsistency between the journal and superblock, this triggers a
preen, which based on the time it takes is probably what's happening
in your case. The first thing I'd do is boot from alternate media and
do an e2fsck -f <dev> which hopefully fixes the problems, and on
reboot there should be no long fsck again. Reboot again, and see if
there's a long fsck. If there is, you'll need to investigate the
shutdown as a culprit.
--
Chris Murphy
3:29 a.m.
It is ext4 on /work
journalctl -xb returns:
-- Unit user(a)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=:1.0 destination=n/a obje
Jan 02 02:41:40 amd systemd[1]: Sent message type=method_call
sender=n/a destination=org.freedesk
Jan 02 02:41:40 amd systemd-logind[499]: Sending reply about created
session: id=1 object_path=/o
Jan 02 02:41:40 amd systemd[1]: user(a)0.service: got STATUS=Startup
finished in 236ms.
Jan 02 02:41:40 amd systemd-logind[499]: Sent message
type=method_return sender=n/a destination=:
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=org.freedesktop.DBus dest
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=:1.0 destination=n/a obje
Jan 02 02:41:40 amd systemd[1]: Got message type=signal
sender=org.freedesktop.DBus destination=n
Jan 02 02:41:40 amd systemd-logind[499]: Got message type=signal
sender=:1.0 destination=n/a obje
Jan 02 02:41:40 amd login[533]: pam_unix(login:session): session
opened for user root by LOGIN(ui
Jan 02 02:41:40 amd login[533]: ROOT LOGIN ON tty1
Jan 02 02:41:47 amd kernel: forcedeth 0000:00:08.0: irq 30 for MSI/MSI-X
Jan 02 02:41:47 amd kernel: forcedeth 0000:00:08.0 eth0: MSI enabled
Jan 02 02:41:54 amd fprintd[564]: ** Message: No devices in use, exit
Jan 02 02:41:54 amd systemd[1]: Got notification message for unit
systemd-journald.service
Jan 02 02:41:54 amd systemd[1]: systemd-journald.service: Got
notification message from PID 336 (
Jan 02 02:41:54 amd systemd[1]: systemd-journald.service: got WATCHDOG=1
Jan 02 02:41:54 amd systemd-logind[499]: Got message type=signal
sender=org.freedesktop.DBus dest
Jan 02 02:41:54 amd systemd-logind[499]: Got message type=signal
sender=org.freedesktop.DBus dest
Jan 02 02:41:54 amd systemd[1]: Got notification message for unit
systemd-logind.service
Jan 02 02:41:54 amd systemd[1]: systemd-logind.service: Got
notification message from PID 499 (WA
Jan 02 02:41:54 amd systemd[1]: systemd-logind.service: got WATCHDOG=1
Jan 02 02:41:54 amd systemd[1]: Received SIGCHLD from PID 564 (fprintd).
Jan 02 02:41:54 amd systemd[1]: Child 564 (fprintd) died (code=exited,
status=0/SUCCESS)
Jan 02 02:41:54 amd systemd[1]: Child 564 belongs to fprintd.service
Jan 02 02:41:54 amd systemd[1]: fprintd.service: main process exited,
code=exited, status=0/SUCCE
Jan 02 02:41:54 amd systemd[1]: fprintd.service changed running -> dead
Jan 02 02:41:54 amd systemd[1]: fprintd.service: cgroup is empty
Jan 02 02:41:54 amd systemd[1]: Collecting fprintd.service
Jan 02 02:41:54 amd systemd[1]: Sent message type=signal sender=n/a
destination=n/a object=/org/f
Jan 02 02:41:54 amd systemd-logind[499]: Got message type=signal
sender=:1.0 destination=n/a obje
Jan 02 02:41:54 amd systemd[1]: Got message type=signal
sender=org.freedesktop.DBus destination=n
Jan 02 02:41:54 amd systemd[1]: Accepted new private connection.
Jan 02 02:41:54 amd systemd[1]: Got message type=signal
sender=org.freedesktop.DBus destination=n
Jan 02 02:41:54 amd systemd[1]: Got message type=signal sender=n/a
destination=n/a object=/org/fr
Jan 02 02:41:54 amd systemd[1]: Sent message type=signal sender=n/a
destination=n/a object=/org/f
Jan 02 02:41:54 amd systemd-cgroups-agent[613]: Sent message
type=signal sender=n/a destination=n
Jan 02 02:41:54 amd systemd[1]: Got disconnect on private connection.
Jan 02 02:42:04 amd sshd[614]: Accepted publickey for root from
192.168.2.10 port 54040 ssh2: DSA
Jan 02 02:42:04 amd systemd[1]: Got message type=signal
sender=org.freedesktop.DBus destination=n
Jan 02 02:42:04 amd systemd-logind[499]: Got message type=signal
sender=org.freedesktop.DBus dest
Jan 02 02:42:04 amd systemd-logind[499]: Got message type=method_call
sender=:1.10 destination=or
Jan 02 02:42:04 amd systemd-logind[499]: Sent message type=method_call
sender=n/a destination=org
Jan 02 02:42:04 amd systemd-logind[499]: Sent message type=method_call
sender=n/a destination=org
Jan 02 02:42:04 amd systemd[1]: Got message type=method_call
sender=:1.1 destination=org.freedesk
Jan 02 02:42:04 amd systemd[1]: Sent message type=method_call
sender=n/a destination=org.freedesk
Jan 02 02:42:04 amd systemd[1]: Failed to load configuration for
session-2.scope: No such file or
Jan 02 02:42:04 amd systemd[1]: Trying to enqueue job session-2.scope/start/fail
Jan 02 02:42:04 amd systemd[1]: Installed new job session-2.scope/start as 629
Jan 02 02:42:04 amd systemd[1]: Enqueued job session-2.scope/start as 629
Jan 02 02:42:04 amd systemd[1]: Sent message type=method_call
sender=n/a destination=org.freedesk
Jan 02 02:42:04 amd systemd[1]: Sent message type=method_call
sender=n/a destination=org.freedesk
Jan 02 02:42:04 amd systemd[1]: Sent message type=method_return
sender=n/a destination=:1.1 objec
Jan 02 02:42:04 amd systemd[1]: Sent message type=signal sender=n/a
destination=n/a object=/org/f
Jan 02 02:42:04 amd systemd[1]: Sent message type=signal sender=n/a
destination=n/a object=/org/f
Jan 02 02:42:04 amd systemd[1]: Starting Session 2 of user root.
-- Subject: Unit session-2.scope has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-2.scope has begun starting up.
Jan 02 02:42:04 amd systemd[1]: session-2.scope changed dead -> running
Jan 02 02:42:04 amd systemd[1]: Job session-2.scope/start finished, result=done
Jan 02 02:42:04 amd systemd[1]: Started Session 2 of user root.
-- Subject: Unit session-2.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-2.scope has finished starting up.
--
-- The start-up result is done.
Jan 02 02:42:04 amd systemd-logind[499]: New session 2 of user root.
-- Subject: A new session 2 has been created for user root
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 2 has been created for the user root.
--
-- The leading process of the session is 614.
Jan 02 02:42:04 amd systemd-logind[499]: Sent message type=signal
sender=n/a destination=n/a obje
Jan 02 02:42:04 amd systemd-logind[499]: Sent message type=signal
sender=n/a destination=n/a obje
Jan 02 02:42:04 amd systemd-logind[499]: Got message type=signal
sender=:1.0 destination=n/a obje
Jan 02 02:42:04 amd systemd-logind[499]: Sending reply about created
session: id=2 object_path=/o
Jan 02 02:42:04 amd systemd-logind[499]: Sent message
type=method_return sender=n/a destination=:
Jan 02 02:42:04 amd systemd-logind[499]: Got message type=signal
sender=org.freedesktop.DBus dest
Jan 02 02:42:04 amd systemd[1]: Sent message type=signal sender=n/a
destination=n/a object=/org/f
Jan 02 02:42:04 amd systemd[1]: Sent message type=method_call
sender=n/a destination=org.freedesk
Jan 02 02:42:04 amd systemd-logind[499]: Got message type=signal
sender=:1.0 destination=n/a obje
Jan 02 02:42:04 amd systemd[1]: Sent message type=signal sender=n/a
destination=n/a object=/org/f
Jan 02 02:42:04 amd systemd[1]: Sent message type=signal sender=n/a
destination=n/a object=/org/f
Jan 02 02:42:04 amd systemd-logind[499]: Got message type=signal
sender=:1.0 destination=n/a obje
Jan 02 02:42:04 amd systemd[1]: Got message type=signal
sender=org.freedesktop.DBus destination=n
Jan 02 02:42:04 amd sshd[614]: pam_unix(sshd:session): session opened
for user root by (uid=0)
Jan 02 02:42:25 amd systemd[1]: Got notification message for unit
systemd-logind.service
Jan 02 02:42:25 amd systemd[1]: systemd-logind.service: Got
notification message from PID 499 (WA
Jan 02 02:42:25 amd systemd[1]: systemd-logind.service: got WATCHDOG=1
Jan 02 02:42:25 amd systemd[1]: Got notification message for unit
systemd-journald.service
Jan 02 02:42:25 amd systemd[1]: systemd-journald.service: Got
notification message from PID 336 (
Jan 02 02:42:25 amd systemd[1]: systemd-journald.service: got WATCHDOG=1
lines 4366-4402/4402 (END)
On Sat, Jan 17, 2015 at 11:01 AM, Ed Greshko <ed.greshko(a)greshko.com> 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,....
> Give toot password for maintenance
> (or press Control-D to continue)
What file system was being checked? And did you type "journalctl -xb" to view
system logs....
--
If you can't laugh at yourself, others will gladly oblige.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
5:23 p.m.
On Sat, Jan 17, 2015 at 3:06 AM, Kevin Wilson <wkevils(a)gmail.com> wrote:
Chris,
Thanks for your quick resonse!
I do have /work in my /etc/fstab:
/dev/sda3 /work ext3
defaults 1 1
Consider 2 for the last column, since it's not the root filesystem. I
don't know if it really matters, because systemd runs fsck.<foo> on
the unmounted root no matter what. But in your case a 2 might cause
fsck to run later than it is now.
An additional option, which I use for /boot/efi, is mount option
'x-systemd.automount,noauto' which makes it only mount when accessed,
and does an fsck right before mounting. It's normally quite fast. And
this way, if there are problems, it won't hang boot.
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1077984
--
Chris Murphy
3:38 a.m.
On Sat, Jan 17, 2015 at 2:29 AM, Kevin Wilson <wkevils(a)gmail.com> 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're dropped to rescue
kernel. If /work is in fstab then it's required for basic.target
unless you have nofail or noauto as a mount option, so I'm guessing
the fsck preen failed to fix the problem and so basic.target fails.
So yeah, run e2fsck -f on this volume, and then take a cell phone
photo and put it up somewhere. That's easier than typing it all out.
--
Chris Murphy
3:31 a.m.
On Sat, Jan 17, 2015 at 2:01 AM, Ed Greshko <ed.greshko(a)greshko.com> 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,....
> Give toot password for maintenance
> (or press Control-D to continue)
What file system was being checked? And did you type "journalctl -xb" to view
system logs....
I'm assuming ext4 just because XFS and Btrfs don't have
unattended/boot time fsck. I suppose it could be a FAT or HFS+ EFI
System partition, but weirdly Fedora doesn't fsck a FAT ESP by
default.
https://bugzilla.redhat.com/show_bug.cgi?id=1077917
--
Chris Murphy
3423
days inactive
3423
days old
8 comments
3 participants
participants (3)
-
Chris Murphy -
Ed Greshko -
Kevin Wilson