[SOLVED] Systemd stuck at "Starting File system check"

Hi all
Backstory
My hardware:
Mobo: Gigabyte X99 2011v3 with UEFI and dual bios.
GFX: MSI GTX 970 4GB Gaming OC
HDD: Samsung 850 Pro 1TB SSD
CPU: intel 5820k
I have been using arch for about 2 years now. I recently bought new hardware, Gigabyte X99 motherboard uefi dual bios. I have tried a couple of times to install arch the old way, i.e. legacy mode or normal bios mode, however after a successful install, when I reboot my bios says "Select Proper Boot Device". Then I decided to put everything in UEFI mode and install arch using the uefi install disc. At first, I was not very successful, because I followed the arch wiki to the bone but when it comes to UEFI, instructions are a bit vague. In any case, I managed to install Arch and get uefi to work 100% by using this guide http://jorisvandijk.com/2014/installing … pt-system/ .
Problem
After installing arch successfully using UEFI mode, arch starts booting up, everything shows [OK] at the side, no errors, however, it hangs after a line that reads "Starting File system check ". I am not at home right now, however I thought I could start troubleshooting and maybe get some ideas.
I have tried the following.
- Chrooted back into my arch install using the live cd and mounting my partitions.
- Updated and synced pacman.
- Removed all journal log files.
- reinstalled Systemd.
- rebuilt kernel modules.
none of the above worked. It still hangs at "Starting fiel system check"
Any ideas.
SOLUTION
Solved by using
nolapic
Still had other problems after that, however, the initial problem was solved.
Last edited by janpansa (2015-02-26 20:04:24)

jasonwryan wrote:Taking the time to read through the relevant pages and working through the Beginners' Guide methodically is the best (and only) way to both install Arch and also bed in a sound understanding of how your system is put together. It is an investment that will continue to pay you back as long as you run a Linux/UNIX box.
Hi Jason,
thx for your help so far. I have printed out the Arch beginners install and followed it to the bone and focusing on the UEFI parts. Arch installed without a single error, everything went smooth. Aftwerwards, I exited from the chroot environmount, unmount and reboot and again, it hangs on the startup. This time I took screenshots.
I present to the board, exhibit A, arch starting up after a fresh install :
http://oi61.tinypic.com/2m4x82o.jpg
I now present to the board, exhibit B, arch starting up for a second time, after restarting the pc :
http://oi59.tinypic.com/10ehvki.jpg
Afterwards, I restarted again. Went into bios setup and checked my boot priorities. This is what I saw:
I now present exhibit C, my bios boot options :
http://oi62.tinypic.com/24ys0bd.jpg
I tried all the options listed for my Samsung SSD, with and without UEFI as well as the option that was the default aka Linux boot manage". Each one did exactly the same.
I have a few ideas :
1.) Leave out swap.
2.) Disable fscheck.
3.) I have a feeling that my SSD is reading/writing too fast and that fscheck is having trouble ?
I am now trying option 1. In other words, I am reinstalling arch, again, following the beginners guide to the bone and focusing specifically on the UEFI parts. This time, I am leaving out swap. (I have 16GB of DDR4 memory). I have about a 70% feeling that the outcome will be the same. However, I will be back after that to comment on the outcome. Please leave feedback and help me through this where you can ! Thanks
Last edited by jasonwryan (2015-02-23 19:34:21)

Similar Messages

File system checking exit code 8

Hi guys ... after done a filesystem checking I've got:
+0100: Incorrect number of file hard links
+0100: Checking catalog hierarchy.
+0100: Checking extended attributes file.
+0100: Checking volume bitmap.
+0100: Checking volume information.
+0100: The volume Macintosh HD was found corrupt and needs to be repaired.
+0100: File system check exit code is 8.
+0100: Error: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.
After restart the machine as suggested, my filesystem check exit without finding any problem, so ... what is the problem in fact? ...
By the way: I do not have any strange behaviour on my mac, I normally run filesystem and permissions repairs in order to keep "him" clean and healthy.
Thanks in advanced,
Jorge

This seems to be a bug. You may be able to work around it by starting up from another physical device. Make sure you have a current backup before doing anything.
If you have a "clone" backup on another drive—not a partition on the same drive—start up from it by holding down the option key at the startup chime and selecting its icon in the Startup Manager display. Launch Disk Utility and repair your primary startup volume—not the one you started from.
If you have a Time Machine backup on a locally-attached storage device—not a network device such as a Time Capsule—there should already be a Recovery system on that device. Start up from it and repair in the same way as above.
Otherwise, use Recovery Disk Assistant to create a Recovery system on a spare storage device, such as a USB flash drive, and start up from that device. All existing data on the Recovery device will be permanently erased.

BSD Root - File System Check

My 2.8Ghz iMac has being running very slow recently.
I performed a File System Check and noted that my hard drive had the following message against it.
Major 14 Minor 2
Does that mean it is about to fail?

yes.
Have backups for ALL your data.
Take to nearest Apple Authorized Repair Center for new drive.

Start-up system check

Does anyone know the start-up keystroke command to check and repair the system?
A while ago, one of the gurus at the "guru bar" gave me a key command to bring up the terminal and force a system check. I have forgotten that info.
Anyone remember?
Thanks.
JL - Santa Monica

Ahh, OK, to boot to Single User Mode, CMD+s, when prompt comes up, type...
/sbin/fsck -fy
Repeat until it shows no errors fixed.
Resolve startup issues and perform disk maintenance with Disk Utility and fsck...
http://docs.info.apple.com/article.html?artnum=106214
Ort get Applejack...
http://www.versiontracker.com/dyn/moreinfo/macosx/19596
After installing, reboot holding down CMD+s, then when the prompt shows, type in...
applejack AUTO
Then let it do all 5 of it's things.
The 5 things it does are...
Correct any Disk problems.
Repair Permissions.
Clear out Cache Files.
Repair/check several plist files.
Dump the VM files for a fresh start.

New Kernel - stuck after unmounting file system

Hello,
I upgraded my kernel and I think that since then I'm having problems shuting down and rebooting. I get the screen where all the processes are being closed and when it comes to the "unmounting file system" it stucks.
I have a fairly strightforward system - ext3 for my linux partition and NTFS for my windows, both automaticly mounted, NTFS read only.
After I waited a few times I just have to manually shut down the computer. Not very healthy I believe.
If anyone encountered the problem or has any advice I'd welcome it.
Thank you,
Grey

i have the exact same problem, and it has been like this for a week i tought it was only me but surprises me that its not just me.
the thing is like this when u mount the ntfs filesystem if u dont read from the discs u can umount them but ir u read from them my machine freezes when it comes to the umount command !!
Im just a newbie in linux so i have no idea why this is but i have no problems at all with the reiserfs , ext3 mounts , only the ntfs is screwed up
kernel 2.6.12 , udev 062-1
when i installed from the cd i had no problems at all but , a week ago i formated all and did a ftp install , and i start having this problem.

File system check fails "FATAL"

Dear all,
after about three of years of running, one of my Xsan filesystems died. The fsm process stops running after about 2 minutes in running state. A filesystem check with cvfsck -w -v <Name> ends with:
Creating Daten allocation check file.
Stripe Group Daten ( 0) 0xe8def800 blocks.
Building Inode Index Database 91458560 ( 52%).
Fatal: rf_relblk write failed - Input/output error
Building Inode Index Database 91459584 ( 52%).
Fatal: Cannot insert inotab for [0x32a9e378800]! -No such file or directory
Fatal: Cannot build inode tracking tree - Input/output error.
I cannot see any misbehaviour of the hardware itself. RAID Admin is green everywhere.
The filesystem size is about 17 TB and the data is quite important. Is there any way to proceed without re-formatting?
Some more information I found in the log files:
[0923 16:26:42] 0xa000ed88 (debug) FSS 'Experiments' REGISTERED -> DYING, next e
vent in 60s
[0923 16:26:43] 0x1802e00 INFO Disk rescan found 10 disks
[0923 16:26:43] 0xa000ed88 INFO NSS: Active FSS 'Experiments[0]' at 192.168.100.
10:49275 (pid 354) - dropped.
[0923 16:26:45] 0x1801600 ERR Portmapper: FSS 'Experiments' (pid 354) exited on
signal 4
[0923 16:26:45] 0x1801600 ERR FSS 'Experiments' appears unstable (2 failures in
60 minutes or less), halting restarts
[0923 16:26:45] 0x1801600 (debug) FSS 'Experiments' DYING -> STOPPED (corefile l
imit exceeded)
Any hint is really appreciated.
Best regards,
Torsten

Thanks for the hint. Well, the cvfsck -j command succeeded rather quickly. But the -w afterwards fails again:
Super Block information.
FS Created On : Wed Aug 31 13:24:34 2005
Inode Version : '2.3'
File System Status : Clean
Allocated Inodes : 173699072
Free Inodes : 37814385
FL Blocks : 9309
Next Inode Chunk : 0x2c05d400
Windows Security Indx Inode : 0x4
Windows Security Data Inode : 0x5
Quota Database Inode : 0x6
ID Database Inode : 0xb
Client Write Opens Inode : 0x7
Creating Daten allocation check file.
Stripe Group Daten ( 0) 0xe8def800 blocks.
Building Inode Index Database 91363328 ( 52%).
Fatal: Cannot insert inotab for [0x8261a053f400]! -No such file or directory
Fatal: Cannot build inode tracking tree - Input/output error.
Is there anything else I can do?
Thanks,
Torsten

[SOLVED] Fresh install read only file system

I just did a fresh install of Arch this morning, and I have been trying to fix it most of the day. I was following the Beginner's Guide in the wiki as close as I could. (There were a couple items that didn't quite match up.) I only edited the files that it told me to, and then just minor edits. I checked out /etc/fstab during the process and noticed that none of my hard drives were present. I didn't think this was normal, so I opened another terminal and grabbed the UUIDs with ls -l /dev/disk/by-uuid/. I have two hard drives, but only sda1 (/) and sda2 (swap) showed up. (sdb1 is the entire second hard drive as /home.) Here is the default fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
/dev/fd0 /media/fl auto user,noauto 0 0
The example documentation indicated that the file should have lines similair to...
/dev/disk/by-uuid/6334340b-87f1-406e-a777-13210ba85887 / ext3 defaults,noatime,nodirtime 0 1
/dev/disk/by-uuid/5ffd6a40-6d72-4710-82af-ae894e557f89 swap swap defaults 0 0
/dev/disk/by-uuid/32935c6c-6b75-4039-6b69-21f8b805e8f8 /home ext3 defaults,noatime,nodirtime 0 2
...but then I found an example while searching around that showed the lines like this:
UUID=6334340b-87f1-406e-a777-13210ba85887 / ext3 defaults,noatime,nodirtime 0 1
UUID=5ffd6a40-6d72-4710-82af-ae894e557f89 swap swap defaults 0 0
UUID=32935c6c-6b75-4039-6b69-21f8b805e8f8 /home ext3 defaults,noatime,nodirtime 0 2
In the first scenario, everything boots like normal, but when I tried to do anything that required writing to disk, the operation failed with a message about the file system being read-only. (I was trying to edit some config files because I couldn't get online.) Mind you, I was working as root the whole time, because I hadn't even gotten to adding a user yet. The only way I could make changes was to boot a live cd, mount, edit, reboot. remember to remove the live cd, reboot again, repeat.
In the second version of fstab, the bootup process kept trying to check the disk for errors. When it was done it wanted to reboot. Then it tried to check again (presumably because it couldn't save the fact that it had already checked).
I am at a loss. I really wish to use Arch Linux. I've been baby-fed for quite a while on Ubuntu, but it always ran slow. Please somebody help me! I am happy to provide more information; just let me know what you need.
Last edited by ravinggenius (2008-07-05 18:33:22)

Thank you so much for pointing out that typo! Turns out that is what was wrong. Well plus two of uuids had one typo each....
Also from what I can tell it doesn't matter which format I use for the uuids in fstab. I will use the UUID=xxxxx... version unless somebody can tell me why I shouldn't.

[Solved] Canot format MicroSD. File system is read-only

I formatted it for my special needs some time ago using fdisk.
Don't remember the partition table, but there was 1 fat32 and 1 ext4 partition.
Now I want to format it fat32 clean, but I get the errors.
When I open GParted, it says
GParted wrote:/dev/sdb contains GPT signatures, indicating that it has a GPT table. However, it does not have a valid fake msdos partition table, as it should. Perhaps it was corrupted -- possibly by a program that doesn't understand GPT partition tables. Or perhaps you deleted the GPT table, and are now using an msdos partition table. Is this a GPT partition table?
If I click yes - it shows partitions, but creating new partition table fails, as it is read-only.
If I click no - it does not show up in the device list.
Here's a picture of the structure of the device.
What also strange, I remember making 1 GiB ext4, and rest fat32. But it shows the opposite.
So I tried formatting it with fdisk
$ fdisk /dev/sdb
o
n
w
fdisk: cannot write disk label: Bad file descriptor
I made sure they are unmounted
umount: /dev/sdb1: not mounted
umount: /dev/sdb2: not mounted
Then I checked the filesystems. The second one appears to be read-only
# fsck /dev/sdb1
fsck from util-linux 2.23.2
fsck.fat 3.0.22 (2013-07-19)
/dev/sdb1: 18 files, 96978/698280 clusters
# fsck /dev/sdb2
fsck from util-linux 2.23.2
e2fsck 1.42.8 (20-Jun-2013)
fsck.ext4: Read-only file system while trying to open /dev/sdb2
Disk write-protected; use the -n option to do a read-only
check of the device.
# fsck -n /dev/sdb2
fsck from util-linux 2.23.2
e2fsck 1.42.8 (20-Jun-2013)
/dev/sdb2: clean, 860/65664 files, 56633/262144 blocks
Tried the zero trick, but failed as well.
# dd if=/dev/zero of=/dev/sdb
dd: failed to open ‘/dev/sdb’: Read-only file system
# dd if=/dev/zero of=/dev/sdb2
dd: failed to open ‘/dev/sdb2’: Read-only file system
Tried to disable the write-protection
# hdparm -r0 /dev/sdb
/dev/sdb:
setting readonly to 0 (off)
readonly = 0 (off)
After that, fdisk still fails to format.
In Windows 8, it mounts only the fat32 part.
diskpart can't erase partition table as well.
Last edited by Doctor Drive (2013-10-09 08:28:13)

Finally I found the solution
MicroSD adapter has a "lock" feature.
When I inserted the adapter, the lock always triggered to locked state.
So I fixed it in unlocked state using the ducktape.
http://kb.sandisk.com/app/answers/detai … -or-locked

[SOLVED] Exaile doesn't start after system update

Hi,
After last system update Exaile won't start I've searched forum and web and can't find solution for that.
[lukasz@myhost ~]$ exaile
Traceback (most recent call last):
File "/usr/lib/exaile/exaile.py", line 32, in <module>
import gobject
ImportError: No module named gobject
As You can see it says something about gobject.
BTW. After update I also hav problems with catalyst from AUR, my Gnome wasn't starting so I had to replace it with opensource ATI drivers,
another problem is that everytime I startup gnome it's uing very small fonts, and I have to manually change it to one I had before.
Please help,
Regards,
Lukasz
Last edited by skraburski (2009-05-31 11:18:25)

Problem solved, had to reinstall pygobject. It looks like after last update many pacakges were corrupted and now Ia have to reinstall them, do You know any way to automatically reinstall all corrupted packages?
Regards,
Lukasz

[SOLVED] systemd service not starting

Hi,
Been using Arch for just over a week now moving from Ubuntu and loving it. Achieved so much more on Arch in this short time until this evening.
I am trying to run a shell script at startup. I added the service file under /etc/systemd/system/myapp.service
With the following content:
[Unit]
Description=Notification
[Service]
ExecStart=/usr/bin/myscript
[Install]
WantedBy=multi-user.target
As it is I can run "systemctl restart myapp.service" and the script execute flawlessly however on reboot it does nothing and I get this error when I run systemctl status myapp.service:
systemctl status myapp.service
myapp.service - Notification
Loaded: loaded (/etc/systemd/system/myapp.service; enabled)
Active: failed (Result: exit-code) since Thu 1970-01-01 10:00:08 EST; 14s ago
Process: 116 ExecStart=/usr/bin/myscript (code=exited, status=6)
Other info:
Script starts with #!/bin/sh
Script permissions 755
Tried adding After=network.target under unit.
Tried Type=oneshot and forking
O yes /var/log/messages.log | grep myapp
Sep 6 14:25:56 alarm systemd[1]: [/etc/systemd/system/myapp.service:1] Unknown section 'unit'. Ignoring.
Sep 6 14:25:56 alarm systemd[1]: [/etc/systemd/system/myapp.service:2] Assignment outside of section. Ignoring.
Jan 1 01:00:11 alarm systemd[1]: myapp.service: main process exited, code=exited, status=6/NOTCONFIGURED
Jan 1 01:00:11 alarm systemd[1]: Unit myapp.service entered failed state.
Jan 1 01:00:11 alarm [ 3.243318] systemd[1]: [/etc/systemd/system/myapp.service:1] Unknown section 'unit'. Ignoring.
Jan 1 01:00:11 alarm [ 3.243490] systemd[1]: [/etc/systemd/system/myapp.service:2] Assignment outside of section. Ignoring.
Only thing I dont get is the date difference? I have set the timezone correctly..
Any suggestions?
thanks
Last edited by blueteq (2013-09-10 10:01:11)

Reaching the network.target does not necessarily mean that an active connection has been reached. For example, if you use wicd or netctl-auto, it will report the stating of the service as successful after the daemon itself has started, but starting the daemon simply means that it is ready to start scanning for wireless networks and then connect.
If you want to be absolutely sure that there is a network connection before the service starts, you should use NetworkManager.service. That will also pull in the NetworkManager-wait-online.service which will not complete until a full connection has been reached. At that point the startup will have reached the network-online.target. So you should order the service after that instead. In reality, you should order it after that anyway, no matter what netowrk connection service you use, as that is a built in target to systemd.
Even though you have the RestartSec=35 and Restart=on-failure (which is a sane thing to do IMO), it is probably a good idea to order it After=netowrk-online.target anyway, as that will cause the service to start a bit later and at least attempt to order itself correctly. That way it will also ensure that the service is stopped before the network is taken down as well, hopefully ensuring a clean disconnect as well.

[SOLVED] systemd not alway starts dnsmasq and minidlna service

Hi!
After I've annoyed some of you (and hopefully helped others) with my threads on systemd I got systemd working. But; I still have one problem. Systemd seems to have trouble starting dnsmasq and minidlna.
dnsmasq.service loaded failed failed A lightweight DHCP and caching DNS server
[email protected] loaded active running Getty on tty1
httpd.service loaded active running Apache Web Server
logitechmediaserver.service loaded active running Logitech Media Server Daemon
lvm.service loaded active exited LVM activation
minidlna.service loaded failed failed minidlna server
Sometimes they do load, sometimes not. Is there a way to find out why a service could not be started?
btw
systemctl start minidlna dnsmasq
does start them perfectly
Last edited by theking2 (2012-12-13 18:50:35)

Yes, there is such a command systemctl status and it says
Dec 11 20:54:44 janus systemd[1]: Starting A lightweight DHCP and caching DNS server...
Dec 11 20:54:45 janus dnsmasq[308]: dnsmasq: syntax check OK.
Dec 11 20:54:45 janus dnsmasq[335]: dnsmasq: failed to create listening socket for 172.16.0.8: Cannot assign requested address
Dec 11 20:54:45 janus systemd[1]: dnsmasq.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Dec 11 20:54:45 janus systemd[1]: Failed to start A lightweight DHCP and caching DNS server.
Dec 11 20:54:45 janus systemd[1]: Unit dnsmasq.service entered failed state
and
minidlna.service - minidlna server
Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled)
Active: failed (Result: exit-code) since Tue, 2012-12-11 20:54:45 CET; 46s ago
Process: 303 ExecStart=/usr/sbin/minidlna -P /var/run/minidlna/minidlna.pid (code=exited, status=255)
CGroup: name=systemd:/system/minidlna.service

[Solved] systemd fails to start spawning /bin/plymouth

Hello all,
I currently can't get my system to boot up, systemd hangs and after a while enters emergency mode.
journalctl -xb
show the following error:
systemd[257]: Failed at step EXEC spwaning /bin/plymouth:
-- Subject: Process /bin/plymouth could not be executed
.. The process /bin/plymouth could not be executed and failed.
-- The error number returned while executing this process is 2.
I am not sure what to make of this, as far as I know plymouth is some splash screen utility which I have never installed. I also can't find any corresponding .service files. I also tried appending plymouth.enable=0 to the kernel command line, to no effect. Does anyone know this problem (since my hardware is currently in a rather shaky state I would not rule out some related error)?
Last edited by x2b (2013-09-11 17:55:32)

x2b wrote:I am not sure what to make of this, as far as I know plymouth is some splash screen utility which I have never installed.
Yes, that's plymouth.
I also can't find any corresponding .service files. I also tried appending plymouth.enable=0 to the kernel command line, to no effect. Does anyone know this problem (since my hardware is currently in a rather shaky state I would not rule out some related error)?
Might have something to do with https://bugs.archlinux.org/task/31031 so plymouth should not be the problem.
Edit: I just checked my journal and I could not find any plymouth related messages in there, but I remember seeing those before, too (must have been before february 20th, that's as far back as my journal goes). When did you do your last update?
Last edited by cookies (2013-09-11 13:58:43)

[SOLVED]systemd won't start my /etc/rc.local

I was trying to emulate rc.local behaviour with this:
/usr/lib/systemd/system/rc-local.service
[Unit]
Description=/etc/rc.local Compatibility
ConditionPathExists=/etc/rc.local
[Service]
Type=forking
ExecStart=/etc/rc.local start
TimeoutSec=0
StandardOutput=tty
RemainAfterExit=yes
SysVStartPriority=99
[Install]
WantedBy=multi-user.target
and my
/etc/rc-local
looks like this
modprobe -r samsung_laptop
But it's not working. When I execute sudo systemctl status rc-local.service I get
rc-local.service - /etc/rc.local Compatibility
Loaded: loaded (/usr/lib/systemd/system/rc-local.service; enabled)
Active: failed (Result: exit-code) since Fri 2013-03-29 17:54:16 CET; 5min ago
Process: 745 ExecStart=/etc/rc.local start (code=exited, status=203/EXEC)
Last edited by Neky (2013-03-29 18:31:39)

Why do you have "start" as an argument to /etc/rc.local?
Also, for what you are trying to achieve, why not simply blacklist the module in /etc/modrpobe.d? Then it would not be loaded under any circumstances. Also if this is out of fear of the UEFI bug, I believe that for this particular module, there has been a patch included in the latest kernels that protects this from happening by not allowing writes to the NVRAM if it is 50% full or more.

[solved] systemd services not starting at boot (or at all)

On my router, some systemd services fail to start at boot.
The services are :
adsl (pppoe connetction on the wan interface)
shorewall (funny again for a router)
logind (brings up only tty1, and not the others with a 'timeout' error)
adsl starts fine manually after booting up
the others don't work, I have to launch shorewall with the old sysvinit rc script (and it works)
I really don't know, what happened to logind...
Last edited by scar (2012-11-30 10:20:44)

cups: avahi client failed
adsl: timeout (ppp0 running on eth0, the service did not found eth0)
shorewall: did not work by the systemctl command, only with the old rc script
I'm not sure if there was an error with logind, but I've had only tty1, not all the others (I have not touched /etc/inittab)
since this was a very old install (but up to date), I've decided to reinstall the whole thing,
Everything works
(But reinstalling does not solve any problem, it erases the problems...)
Last edited by scar (2012-11-30 10:21:20)

[SOLVED] Systemd won't start netcfg

It works if I do netcfg up mynetwork.
If I do sudo systemctl start netcfg.service I get "Job for netcfg.service failed. See 'systemctl status netcfg.service' and 'journalctl -n' for details."
From systemctl status netcfg.service I get
netcfg.service - Netcfg multi-profile daemon
   Loaded: loaded (/usr/lib/systemd/system/netcfg.service; enabled)
   Active: failed (Result: exit-code) since Sun, 2012-11-25 14:22:54 GMT; 44s ago
   Process: 16081 ExecStart=/usr/bin/netcfg-daemon start (code=exited, status=1/FAILURE)
   CGroup: name=systemd:/system/netcfg.service
From journalctl -n I get
Showing user generated messages only. Users in the group 'adm' can see all messages. Pass -q to turn this notice off.
Last edited by acidic (2012-11-25 15:47:37)

https://bbs.archlinux.org/viewtopic.php?id=150076
https://bbs.archlinux.org/viewtopic.php?id=148079

[SOLVED] Systemd stuck at "Starting File system check"

Similar Messages

Maybe you are looking for