Startup hangs at systemd-fsck [solved]

Here is a screenshot of where the machine hangs when starting (this is within VirtualBox, Win7 host and an Arch guest)--> http://i.imgur.com/4KPLmY8.png
Not sure how to troubleshoot this, the `Fallback initramfs` has the same issue.
Last edited by raj (2013-03-22 21:21:19)

Sorry, I should have stated this was not a new install. It was due to a vbox guest-utils update I got off -Syu a few days ago. Yesterday's update resolved the issue of Xorg not finding an available screen.
Case closed, thanks for the reply.

Similar Messages

[SOLVED] How to cancel systemd-fsck during reboot after power failure.

Hello
If power fails (or if I, for any reason, force a physical shutdown ) on my computer, it will display during boot :
systemd-fsck[171] : arch_data was not cleanly unmounted, check forced
And then hangs for a long time (10 minutes ) while checking arch_home partition, wich is a 1T ext4 partition.
then finish the boot.
Sometimes i want this behavior, but i may need to have my computer up and running as fast as possible, and i don't seem to be able to cancel this fsck.
Ctrl+C, or escape have no effect.
How to allow cancelation of system-fsck for this boot, postponing it for the next boot ?
my fstab :
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# UUID=cfdf8739-d512-4d99-9893-437a6a3c9bf4 LABEL=Arch root
/dev/sda12 / ext4 rw,relatime,data=ordered 0 2
# UUID=98b01aa3-0f7f-4777-a941-8e676a68adce LABEL=Arch boot
/dev/sda11 /boot ext2 rw,relatime 0 2
# UUID=8909c168-5f1e-4ae7-974c-3c681237af7a LABEL=Arch var
/dev/sda13 /var ext4 rw,relatime,data=ordered 0 2
# UUID=a13efc24-cf66-44d0-b26c-5bb5260627a0 LABEL=Arch tmp
/dev/sda14 /tmp ext4 rw,relatime,data=ordered 0 2
# UUID=779aeb69-9360-4df0-af84-da385b7117d1 LABEL=Arch home
/dev/sdb4 /home ext4 rw,relatime,data=ordered 0 2
/dev/sdb5 /home/glow/data ext4 rw,relatime,data=ordered 0 2
Last edited by GloW_on_dub (2013-12-07 16:00:06)

Maybe you can add a menu item to the grub boot menu so you can pick it from the menu instead of editing the grub line by hand?
I'm using syslinux, but I can have menu items that only differ in e.g. 'quiet' parameter:
APPEND root=/dev/sda3 rw init=/usr/lib/systemd/systemd quiet
APPEND root=/dev/sda3 rw init=/usr/lib/systemd/systemd
Everything else is the same.

[Solved -sorta] systemd-fsck []: fsck: /sbin/fsck.ext4: execute failed

Greetings.
I am getting the following on boot:
Starting Version 218
A password is required to access the MyStorage volume:
Enter passphrase for /dev/sda3
/dev/mapper/MyStorage-rootvol: clean, 210151/983040 files, 2284613/3932160 block
[ 78.084720] systemd-fsck [280]: fsck: /sbin/fsck.ext4: execute failed: Exec format error
[ 78.085215] systemd-fsck [287]: fsck: /sbin/fsck.ext2: execute failed: Exec format error
I then end up at a login prompt but if I try to login, I get “Login incorrect”. Sometimes Getty will stop and restart on tty1. Then I get returned to the login prompt.
This came about after upgrading with Pacman (which included “upgraded e2fsprogs (1.42.12-1 -> 1.42.12-2)”) a few days ago. Pacman completed successfully but on reboot the system froze forcing a hard reset.
I've booted to a USB and run fsck on the boot partition (the only ext2 partition). Ditto on the root and home volumes. All fine. I've also mounted all three and can access the data.
I would have thought it was something to do with the e2fs upgrade but it obviously scanned the root volume fine and I haven't been able to find any similar reports online.
I've searched online for ideas and I've also searched for logs which might give me some indication of what the cause is but at this point, I've reached my limits.
I'd just nuke the data and start again but I really want to understand what happened here.
Any thoughts on what caused this or suggestions on how to proceed?
Thank you.
Stephen
Last edited by FixedWing (2015-03-16 01:40:20)

Head_on_a_Stick wrote:
https://wiki.archlinux.org/index.php/Pa … ond_repair
However, it may be simplest to just re-install in your case -- it depends whether you want to use the troubleshooting & repairing as a learning process or if you just want your system up & running again ASAP...
All fixed and working just like nothing happened.
I did use the advice at the referred link plus a few others on archlinux.org and elsewhere. Yes, an absolutely wonderful learning experience!
I manually reinstalled e2fsprogs. That got Pacman working again and I was able to boot into the system. Then I used Pacman to reinstall e2fsprogs properly plus the other seven packages which were also installed during the same Pacman session despite their being corrupted.
What I really don't get is how Pacman could accept a package with 0 bytes and install it? How could such a package possible pass the security check? When I reinstalled the packages, Pacman of course refused to install the corrupt packages in the cache and deleted them. So why didn't that happen initially? I can only think that a corrupt file in that process terminated prematurely and that Pacman wasn't robust enough to detect this so simply continued on, now skipping the scans and installing the corrupt packages. So just to be sure it wasn't a corrupt file in Pacman itself, I also forced a reinstall of that package as well. I've upgraded packages since without issue so I have to assume that whatever the issue was is now gone.
Anyway, thanx for the help!
Stephen

[SOLVED] systemd-fsck does checks on every boot

How do I say it to check only after crashes (bad unmounts and so on..) and just mount without checks otherwise?
I use the classic /etc/fstab layout:
/dev/drive/root / ext4 rw,relatime 0 1
/dev/drive/boot /boot ext4 rw,relatime,noexec 0 2
/dev/drive/swap none swap defaults 0 0
/dev/drive/var /var ext4 rw,relatime,nodev,noexec,nosuid 0 2
/dev/drive/home /home ext4 rw,relatime 0 2
Here is some info from systemd's journal:
дек. 08 22:43:20 localhost systemd[1]: Found device /dev/drive/var.
дек. 08 22:43:21 localhost systemd-fsck[124]: /dev/mapper/drive-root: clean, 56204/2621440 files, 523339/10485760 blocks
дек. 08 22:43:21 localhost systemd[1]: Started File System Check on Root Device.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/var...
дек. 08 22:43:21 localhost systemd[1]: Starting Remount Root and Kernel File Systems...
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/swap.
дек. 08 22:43:21 localhost systemd[1]: Activating swap /dev/drive/swap...
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/boot.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/boot...
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/home.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/home...
дек. 08 22:43:21 localhost systemd-fsck[252]: /dev/mapper/drive-var: clean, 2007/262144 files, 463082/1048576 blocks
дек. 08 22:43:22 localhost systemd[1]: Started Remount Root and Kernel File Systems.
дек. 08 22:43:22 localhost systemd[1]: Starting Local File Systems (Pre).
дек. 08 22:43:22 localhost systemd[1]: Reached target Local File Systems (Pre).
дек. 08 22:43:22 localhost systemd[1]: Mounting /var...
дек. 08 22:43:22 localhost systemd-fsck[257]: /dev/mapper/drive-boot: clean, 313/65536 files, 33914/262144 blocks
дек. 08 22:43:22 localhost systemd[1]: Mounted /var.
дек. 08 22:43:22 localhost systemd-fsck[262]: /dev/mapper/drive-home: clean, 5080/16375808 files, 2332630/65492992 blocks
дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/boot.
дек. 08 22:43:22 localhost systemd[1]: Mounting /boot...
дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/home.
дек. 08 22:43:22 localhost systemd[1]: Mounting /home...
дек. 08 22:43:22 localhost systemd[1]: Mounted /boot.
дек. 08 22:43:23 localhost systemd[1]: Mounted /home.
дек. 08 22:43:23 localhost systemd[1]: Starting Local File Systems.
дек. 08 22:43:23 localhost systemd[1]: Reached target Local File Systems.
These filesystem checks seem to add huge delay to boot time. But I don't want this delay!
Last edited by eruditorum (2012-12-10 19:26:54)

falconindy wrote:These are the same checks that have always occurred.
But I want to remove them!
falconindy wrote:Notice that /home is mounted within the same second timestamp that it's fsck'd. Same goes for /boot, and /var is probably under a second as well. If you're seeing delays, go look elsewhere.
I think filesystem checks add delays (about one second for each logical volume or so), also as you know systemd is doing everything in parallel it can at the given moment of time, for example I can say you that water has already boiled, while it is still going to boil but you don't know it:
дек. 08 22:43:19 localhost systemd[1]: Starting File System Check on Root Device...
дек. 08 22:43:21 localhost systemd-fsck[124]: /dev/mapper/drive-root: clean, 56204/2621440 files, 523339/10485760 blocks
дек. 08 22:43:21 localhost systemd[1]: Started File System Check on Root Device.
дек. 08 22:43:21 localhost systemd[1]: Starting Remount Root and Kernel File Systems...
/var:
дек. 08 22:43:20 localhost systemd[1]: Found device /dev/drive/var.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/var...
дек. 08 22:43:21 localhost systemd-fsck[252]: /dev/mapper/drive-var: clean, 2007/262144 files, 463082/1048576 blocks
дек. 08 22:43:21 localhost systemd[1]: Started File System Check on /dev/drive/var.
дек. 08 22:43:22 localhost systemd[1]: Mounting /var...
дек. 08 22:43:22 localhost systemd[1]: Mounted /var.
/boot:
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/boot.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/boot...
дек. 08 22:43:22 localhost systemd-fsck[257]: /dev/mapper/drive-boot: clean, 313/65536 files, 33914/262144 blocks
дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/boot.
дек. 08 22:43:22 localhost systemd[1]: Mounting /boot...
дек. 08 22:43:22 localhost systemd[1]: Mounted /boot.
/home:
дек. 08 22:43:21 localhost systemd[1]: Found device /dev/drive/home.
дек. 08 22:43:21 localhost systemd[1]: Starting File System Check on /dev/drive/home...
дек. 08 22:43:22 localhost systemd-fsck[262]: /dev/mapper/drive-home: clean, 5080/16375808 files, 2332630/65492992 blocks
дек. 08 22:43:22 localhost systemd[1]: Started File System Check on /dev/drive/home.
дек. 08 22:43:22 localhost systemd[1]: Mounting /home...
дек. 08 22:43:23 localhost systemd[1]: Mounted /home.
Last edited by eruditorum (2012-12-09 13:20:15)

Boot is taking forever (systemd-fsck?)

Im sorry for the bad topic.
When I boot Arch it stops and shows me this message for about 5 minutes or so (It feels like forever):
/dev/sda1: clean, 113567/640848 files, 662474/2561272 blocks
[ 1.582745] kvm: disabled by bios
systemd-fsck[242]: /dev/sda2: clean, 90976/640848 files, 505908/2558464 blocks
I dual boot with Windows and I reboot my computer on a daily basis (Im a gamer) so its driving me crazy.
I have googled it and read a bunch of topics for the past three days now.. Whats wrong?

Hund wrote:
Bah.. Whats up with the systemd thingy anyway? Whats the benefits with it? So far Ive just seen a bunch of bugs. Arch used to work flawless for me, but ever since the switch to systemd it all went south. Boot hangs, shutdown hangs, no network at boot and autmounting my Samba share doesnt work.. Yay!
Edit: Atleast I solved the network at boot a few days ago. But I have no idea how I did it tbh.. Arch used to be so simple! But now with this systemd piece of shit? Its a mess.
The experience of most people is that sysytemd has introduced benefits; most of the issues that you are describing are probably fixable by some simple configuration changes.
In any event, we have grown rather tired of the petulant "systemd is a piece of shit"-type rants that a minority feel compelled to vent; please don't bother. If you don't like it, install something else.
FWIW: anyone who starts a sentence about a rolling release with a fond nostalgia for the past is clearly deluding themselves; change is at the core of Arch, deal with it.

Power mac G4 - Startup hangs at gray screen

Hello all,
I have a Power mac G4 - mirrored drive door model. 512mb of RAM; 833mghz - about 50+ gigabytes of storage remaining.
I recently starting using this mac again, here is what happened:
Power mac G4 was running 10.2.1 - had never been updated; it also was capable of running classic os9 (even though I never used it)
Started using machine again a few weeks ago; let "software update" install 10.2.8 update - everything worked fine
Put computer into target disk mode to transfer files to my new macbook pro (13") - using firewire connection
While trying to connect (migration assistant) - window froze will calculating the amount of space that the "user" on the power mac totalled - power mac appeared to be frozen
Did a hard reset / power down of the power mac G4
Upon restart, power mac G4 goes through all start up functions up to gray screen with apple logo (with spinning wheel) and then goes to a darker gray screen (without the logo) and spinning wheel
Dark gray screen with spinning wheel hangs indefinitely - I've let it stay there for hours on end hoping it will resolve but it doesn't
Here's what I have done so far:
Placed power mac G4 into target disk mode again in conjunction with macbook proI can see all the files on the power mac G4 (and have already copied them to the macbook pro) - so I don't think the hard drive is damaged
Disconnected all non-apple peripheral devices - only had a card installed in the back - but took that out - issue persisted (did not replace card in back)
Removed one non-apple RAM stick - issue persisted
Replaced non-apple RAM stick and removed apple RAM stick - issue persisted
Reset PRAM
Started computer in single-user modeused fsck and tried to have system check/fix issue; no matter how many times I re-run the command to repair it never comes back with a message saying no issues found - instead it keeps returning with a message saying that the issue was repaired "system modified"
Started computer in verbose modestartup seems to hang when this appears:
"/System/Library/CoreServices/loginwindow.app/Contents/MacOs/loginwindow: (ipc/send) invalid destination""LayState: cannot map display interlocks."
"/System/Library/CoreServices/loginwindow.app/Contents/MacOs/loginwindow: kCGErrorFailure: CGSNewConnection""Cannot connect to server"
"/System/Library/CoreServices/loginwindow.app/Contents/MacOs/loginwindow: kCGErrorInvalidConnection""Connection called with invalid connection"
Tried re-installing with system discsThe only discs I received with the power mac G4 when I purchased are orange and say "SSW version 8.6" on it" ("iMac Software Restore" and "iMac Software Install")
Computer does not respond when holding down "C" key at startup with either disc in the drive
When holding down "option" key at startup, the computer shows the bootable choices as ONLY the internal HD - not either of the CDs I mentioned above; I wonder if it no longer recognizes the original CDs because I updated to 10.2.8 from 10.2.1 before the issue?I also have an install disc for OS X 10.4.7 - for a friend's iMac (G5)
When holding down "C" key at startup with the OS X 10.4.7 in the drive I get a kernel panic
When holding down "option" key at startup, the computer shows the bootable choices as the OS X 10.4.7 in the drive AND the internal HD
When I choose the OS X 10.4.7 in the drive I get a kernel panic
When I choose the internal HD the startup hangs at the gray screen I mentioned above
At this point, I don't know what else to do. I believe the computer is still good because I can see everything on it when I put it into target disk mode; it just refuses to make it through the startup/login process. I have read discussion threads that suggest re-installing the OS using another computer - but I don't know how to do that. I also wondered if there was a way to tell the computer to re-install the software using the original CDs - but from the command line (in single-user mode)?
Someone - PLEASE HELP!

Sorry, SU Single User Mode, OF Open Firmware as these 2 where mentioned before.
As a test, let's try disconnecting the HD & see if it booys to any mode without it attached.
It could be the User's files or login messed up, if you want to try something a little more desperate...
Reset OS X Password Without an OS X CD...
http://theappleblog.com/2008/06/22/reset-os-x-password-without-an-os-x-cd/
It'll boot like a newly setup Mac, but all your stuff should still be there once filling out the stuff.
Except you could just use Target mode and move or rename that file.

Systemd-fsck complains that my hardware raid is in use and fail init

Hi all,
I have a hardware raid of two sdd drives. It seems to be properly recongnized everywhere and I can mount it manually and use it without any problem. The issue is that when I add it to the /etc/fstab My system do not start anymore cleanly.
I get the following error( part of the journalctl messages) :
Jan 12 17:16:21 biophys02.phys.tut.fi systemd[1]: Found device /dev/md126p1.
Jan 12 17:16:21 biophys02.phys.tut.fi systemd[1]: Starting File System Check on /dev/md126p1...
Jan 12 17:16:21 biophys02.phys.tut.fi systemd-fsck[523]: /dev/md126p1 is in use. <--------------------- THIS ERROR
Jan 12 17:16:21 biophys02.phys.tut.fi systemd-fsck[523]: e2fsck: Cannot continue, aborting.<----------- THIS ERROR
Jan 12 17:16:21 biophys02.phys.tut.fi systemd-fsck[523]: fsck failed with error code 8.
Jan 12 17:16:21 biophys02.phys.tut.fi systemd-fsck[523]: Ignoring error.
Jan 12 17:16:22 biophys02.phys.tut.fi systemd[1]: Started File System Check on /dev/md126p1.
Jan 12 17:16:22 biophys02.phys.tut.fi systemd[1]: Mounting /home1...
Jan 12 17:16:22 biophys02.phys.tut.fi mount[530]: mount: /dev/md126p1 is already mounted or /home1 busy
Jan 12 17:16:22 biophys02.phys.tut.fi systemd[1]: home1.mount mount process exited, code=exited status=32
Jan 12 17:16:22 biophys02.phys.tut.fi systemd[1]: Failed to mount /home1.
Jan 12 17:16:22 biophys02.phys.tut.fi systemd[1]: Dependency failed for Local File Systems.
Does anybody undersand what is going on. Who is mounting the /dev/md126p1 previous the systemd-fsck. This is my /etc/fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda1
UUID=4d9f4374-fe4e-4606-8ee9-53bc410b74b9 / ext4 rw,relatime,data=ordered 0 1
#home raid 0
/dev/md126p1 /home1 ext4 rw,relatime,data=ordered 0 1
The issue is that after the error I'm droped to the emergency mode console and just pressing cantrol+D to continues boots the system and the mount point seems okay. This is the output of 'system show home1.mount':
Id=home1.mount
Names=home1.mount
Requires=systemd-journald.socket [email protected] -.mount
Wants=local-fs-pre.target
BindsTo=dev-md126p1.device
RequiredBy=local-fs.target
WantedBy=dev-md126p1.device
Conflicts=umount.target
Before=umount.target local-fs.target
After=local-fs-pre.target systemd-journald.socket dev-md126p1.device [email protected] -.mount
Description=/home1
LoadState=loaded
ActiveState=active
SubState=mounted
FragmentPath=/run/systemd/generator/home1.mount
SourcePath=/etc/fstab
InactiveExitTimestamp=Sat, 2013-01-12 17:18:27 EET
InactiveExitTimestampMonotonic=130570087
ActiveEnterTimestamp=Sat, 2013-01-12 17:18:27 EET
ActiveEnterTimestampMonotonic=130631572
ActiveExitTimestampMonotonic=0
InactiveEnterTimestamp=Sat, 2013-01-12 17:16:22 EET
InactiveEnterTimestampMonotonic=4976341
CanStart=yes
CanStop=yes
CanReload=yes
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=no
OnFailureIsolate=no
IgnoreOnIsolate=yes
IgnoreOnSnapshot=no
DefaultControlGroup=name=systemd:/system/home1.mount
ControlGroup=cpu:/system/home1.mount name=systemd:/system/home1.mount
NeedDaemonReload=no
JobTimeoutUSec=0
ConditionTimestamp=Sat, 2013-01-12 17:18:27 EET
ConditionTimestampMonotonic=130543582
ConditionResult=yes
Where=/home1
What=/dev/md126p1
Options=rw,relatime,rw,stripe=64,data=ordered
Type=ext4
TimeoutUSec=1min 30s
ExecMount={ path=/bin/mount ; argv[]=/bin/mount /dev/md126p1 /home1 -t ext4 -o rw,relatime,data=ordered ; ignore_errors=no ; start_time=[Sat, 2013-01-12 17:18:27 EET] ; stop_time=[Sat, 2013-
ControlPID=0
DirectoryMode=0755
Result=success
UMask=0022
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=4096
LimitAS=18446744073709551615
LimitNPROC=1031306
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=1031306
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
SameProcessGroup=yes
ControlGroupModify=no
ControlGroupPersistent=no
IgnoreSIGPIPE=yes
NoNewPrivileges=no
KillMode=control-group
KillSignal=15
SendSIGKILL=yes
Last edited by hseara (2013-01-13 19:31:00)

Hi Hatter, I'm a little confused about your statement not to use raid right now. I'm new to the Mac, awaiting the imminent delivery of my first Mac Pro Quad core with 1tb RAID10 setup. As far as I know, it's software raid, not the raid card (pricey!). My past understanding about raid10 on any system is that it offers you the best combination for speed and safety (backups) since the drives are a striped and mirrored, one drive dies, quick replacement and you're up and running a ton quicker than if you had gone RAID5 (20 mins writes per 5G data?)Or were you suggesting not to do raid with the raid card..?
I do plan to use an external drive for archival backups of settings, setups etc, because as we all know, if the best fool proof plans can be kicked in the knees by Murhpy.
My rig is destined to be my video editing machine so the combo of Quad core, 4G+ memory and Raid10 should make this quite the machine.. but I'm curious why you wouldn't suggest raid..
And if you could explain this one: I see in the forums a lot of people are running Bootcamp Parralels(sp) which I assume is what you use to run mulitple OS on your Mac systems so that you can run MacOS and Windblows on the same machine.. but why is everyone leaning towards Vista when thems of us on Windblows are trying to avoid it like the plague? I've already dumped Vista from two PCs and installed XP for a quicker less bloated PC. Is vista the only MSOS that will co-exist with Mac systems? Just curious..
Thanks in advance.. Good Holidays

Systemd-fsck output

Hallo,
i have some questions about systemd-fsck output shown in the console during the system boot. it looks like this:
/dev/mapper/vg-root: clean, 82501/1310720 files, 647916/5242880 blocks
systemd-fsck[234]: /dev/sda2: clean, 337/64000 files, 88881/256000 blocks
systemd-fsck[233]: /dev/mapper/vg-home: clean, 30217/5283840 files, 961660/21116928 blocks
systemd-fsck[232]: /dev/mapper/vg-var: clean, 19485/851968 files, 846527/3407872 blocks
systemd-fsck[238]: fsck.fat 3.0.20 (12 Jun 2013)
systemd-fsck[238]: /dev/sda1: 251 files, 3820/403266 clusters
is it actually running any test?
assuming the above shown output means something like "ok" or "there is no problem", i then want to hide it, so i created a file /etc/systemd/system/[email protected]/custom.conf with the content:
# dont show systemd-fsck results in the console, if everything is ok
[Service]
StandardOutput=journal
StandardError=journal+console
this seems to work pretty nice, but there is one line remaining in the console, the very first one about the root partition. it seems somewhat different to the other lines, in that it misses the prefix systemd-fsck and it can't be found by journalctl
how could i hide this first line?
Is it right, that in case systemd-fsck detects any file system error it still would output these on the console because of the setting StandardError=journal+console?

When you remove the fsck hook from the initramfs, you aren't hiding the output. Rather the test is not being run. Personally, I think that not running an important check on the integrity of your file systems simply to hide a few lines of output on the console reflects rather weird priorities but obviously that's up to you.
For whatever it is worth, I have had cases in which stuff has gone wrong and fsck has identified the need to look at the file system journal. In every single case, the automated routine has examined, repaired and mounted the file system correctly. It has never prevented booting and I have seen almost no file system corruption with the exception of something on a fat 32 system which is obviously not journalled. Given that my system was for a while routinely shutting off in the dirtiest way possible, I think this reflects the robustness of both the file system and the associated maintenance tools like fsck and I would put up with a great deal more than a few lines of text on the console in exchange for this sort of security. My data is the most important thing on the computer and I will use whatever means are reasonably available to me to protect it.
Of course, if nothing like this has (yet) happened to you, you may not (yet) appreciate the system's robustness. But sooner or later, you almost certainly will. (Unless your data is unimportant to you, of course. That would be different.)

27" iMac startup hangs freezes

I have a 27" iMac and am having trouble starting up. I get the startup chime but the startup hangs or freezes and the iMac tries to restart again after a little while.
So I tried starting up from a Techtools CD in the external drive (there is no internal CD drive on the iMac). Unfortunately the iMac would not start from the CD and the CD is now stuck in the external drive. I was able to eject the CD by holding down the mouse button or trackpad while restarting. I tried starting up from an OS X 10.6.3 install DVD but it didn't seem to read it while holding down the C key at startup.
I tried a PRAM zap (holding down the Option + Cmd + P + R keys for two or three chimes) but the startup still hangs freezes.
I tried starting up holding down Cmd + S to boot Unix but I don't really know Unix so only entered exit.
I tried starting up holding down Cmd + R which I think is the recovery system but the startup still got stuck.
Holding down the Shift key while starting up brings up the "safe mode" and a grey bar which didn't fill before it disappeared and the startup froze.
Holding down the Option key while starting up brought up the hard drive to select as the startup disk but startup still hung.
Any ideas or help would be much appreciated.
Thanks

Thanks for getting back to me quickly.
I get the startup chime when the iMac starts up, the little daisy goes around a few times but then gets stuck. The iMac will shut itself down and continue to try to restart.
Holding down Shift during startup brings up the safe mode grey bar on the bottom of the screen but this fills only to about one-third before the startup freezes.
I tried starting up holding down the C key with a OS X 10.6.4 (Snow Leopard) install DVD in an external CD/DVD drive but just as you said, it would not boot from that.
I tried holding down the D key at startup to perform the Apple Hardware Test. Even the extended test did not detect any hardware problems.
Holding Cmd + R during startup would not start the recovery mode for me. However, holding Option down at startup did give me the choice of the Recovery 10.8.2 partition. Unfortunately, this froze as it was starting up too.
So I tried your suggestion of holding down Opt + Cmd + R to boot from Apple's remote servers. This started up but even then froze too.
I think you might be right that it could be a logic board problem. So I will take it in for repair.
Thanks Ralph, I much appreciate your help with this.

Arch boot stops on systemd-fsck

Today I upgraded my packages then I replaced catalyst package with catalyst-total after reboot the booting process stops on this line
Systemd-fsck[362]: /dev/sda5: clean etc
The sda5 is my home drive the boot stops after this line
I pressed alt+f2 to switch in CLI mode then I removed catalyst-total and installed catalyst but the booting process still stops Even when I run startx in CLI mode it gives
Unable to connect x server
The xorg log file error is
DRM report mode setting isn't supported
Unload module radeon
Devices detected but none match those in config file

Not using catalyst myself, so I'm not sure about this. But to me it looks like a conflict w/ either the radeon module or KMS. The wiki has information about this: https://wiki.archlinux.org/index.php/AM … le_at_boot
See "disable KMS" and "blacklist radeon", have you done these? Edit: Maybe recheck...
Regards
Edit2: Also maybe check whether something else is failing, either remove "quiet" from kernel parameters or check via systemctl (see systemd wiki for more information).
Last edited by rebootl (2014-05-19 22:41:15)

Systemd-fsck Message, but alt-ctrl F2 login works

When I start archlnux I receive the message
systemd-fsck fsck.btrfs not found
error 2 while executing fsck.btrfs for /dev/sda7
The screen remains at this message
However using alt-ctrl F2 I can login without any problems.

Ah, so you use btrfs as file system for /dev/sda7 ? Well I never tried that before, seems to be rather new. Did you read the Btrfs page in the ArchWiki? My guess would be,that the fsck tool for this file system is containend in btrfs-progs .

IWork '09 startup hang...proxy issue?

iWork hangs at startup anytime that I launch the applications when I'm behind a firewall. I can reproduce this problem very easily by successfully starting up the application on home home network and encountering problems anytime I launch the applications under a VPN connection or at the office.
Is iWork trying to check in with iwork.com at launch? If so, is there any way to disable this behavior or transparently handle the proxy issue without my having to edit preferences every time I switch network settings?
Thanks for reading this!
-Jamie

I was able to eliminate the iWork '09 startup hang by properly configuring my global HTTP proxy. I ran "netstat -an" from the console during the hang and found that iWork was attempting to connect to one of the iWork.com servers at startup.
Here's what I saw:
hostname:~ username$ netstat -an
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp4 0 0 192.168.0.194.52595 17.250.248.128.80 SYN_SENT
tcp4 0 0 192.168.0.194.52594 17.250.248.105.443 SYN_SENT

Systemd-fsck boot message

systemd-fsck show message when boot evertime. What does meaning? And how to hidding them.
systemd-fsck[145]: /dev/sda4: clean, 112977/9296096 files, 185427/21217024 blocks
systemd-fsck[151]: /dev/sda1: clean, 345/26104 files, 34083/104388 blocks (check after next mount)
edit:
Sorry, I loss something. Full message is:
/dev/sda3: clean, 131838/991232 files, 1193255/3933482 blocks
systemd-fsck[145]: /dev/sda4: clean, 2977/296096 files, 85427/1217024 blocks
systemd-fsck[151]: /dev/sda1: clean, 345/26104 files, 34083/104388 blocks (check after next mount)
my lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 20G 0 disk
├─sda1 8:1 0 102M 0 part /boot
├─sda2 8:2 0 258.9M 0 part [SWAP]
├─sda3 8:3 0 15G 0 part /
└─sda4 8:4 0 4.7G 0 part /home
Last edited by eshizhan (2012-10-22 04:52:13)

fsck stands for "file system check" [1]. systemd will check all of your filesystems every time you boot [2].
systemd-fsck[145]: /dev/sda4: clean, 2977/296096 files, 85427/1217024 blocks
systemd-fsck[151]: /dev/sda1: clean, 345/26104 files, 34083/104388 blocks (check after next mount)
These messages mean that there are no problems with your filesystems and they are "clean". If there ever was a problem with any of your filesystems, these messages are how fsck will let you know so I don't think you want to hide them.
[1] https://wiki.archlinux.org/index.php/Fsck
[2] https://wiki.archlinux.org/index.php/Systemd#Automount

Systemd + fsck -- default timeout is not enough

systemd-fsck tries for check my ~ 1 TB ext3 partition, but it fails: machine gets turned off because the check seems to reach some systemd timeouts (despite 15 minutes seems reasonable long for it at first):
-- Reboot --
Dec 09 19:08:52 hostname systemd-journal[169]: Journal stopped
Dec 09 19:08:52 hostname systemd[1]: Shutting down.
Dec 09 19:08:52 hostname systemd[1]: Forcibly powering off as result of failure.
Dec 09 19:08:52 hostname systemd[1]: Dependency failed for Network Manager.
Dec 09 19:08:52 hostname systemd[1]: Dependency failed for A lightweight DHCP and caching DNS server.
Dec 09 19:08:52 hostname systemd[1]: Dependency failed for Login Service.
Dec 09 19:08:52 hostname systemd[1]: Dependency failed for Graphical Interface.
Dec 09 19:08:52 hostname systemd[1]: Dependency failed for Multi-User System.
Dec 09 19:08:52 hostname systemd[1]: Dependency failed for GNOME Display Manager.
Dec 09 19:08:52 hostname systemd[1]: Dependency failed for D-Bus System Message Bus.
Dec 09 19:08:52 hostname systemd[1]: Dependency failed for Permit User Sessions.
Dec 09 19:08:52 hostname systemd[1]: Timed out starting Basic System.
Dec 09 19:08:52 hostname systemd[1]: Job basic.target/start timed out.
Dec 09 18:53:53 hostname systemd-fsck[300]: /dev/sdb5 has been mounted 24 times without being checked, check forced.
I failed to google it or find in man pages how to change timeout for basic.target/start -- increasing it looks valid in this particular case. Does anyone know how to do that or has another idea how to get fs checked on boot?

being hit by the same issue, does this help?
[root@olivia ~]# systemctl show basic.target | grep Path
FragmentPath=/usr/lib/systemd/system/basic.target
[root@olivia ~]# vi /usr/lib/systemd/system/basic.target
# change 15min to 35min, save and exit
[root@olivia ~]# systemctl daemon-reload

Startup hangs at "Waiting for Internet Services"

I have a Quicksilver 800 and after a power outage when I tried to restart my Mac the startup hangs at "Waiting for Internet Services" and will not get to the login window. I ran a disk repair, permissions repair, and ran Disk Warrior with no luck. I'd appreciate any help you can give.

William, welcome to Apple Discussions.
Will it boot from your system CD?
Is the Startup Disk set to start from your HD or a Network?
Many times after a power failure, the Mac won't startup & you have to do a PMU reset. See Mac PRAM, NVRAM, CUDA/PMU & Battery Tutorial
 Cheers, Tom

Startup hangs at systemd-fsck [solved]

Similar Messages

Maybe you are looking for