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 .

Similar Messages

Alt-Ctrl-C not working, InDesign CS3, Windows

Hello,
We are currently running Adobe Design Premium CS3 and are having a hard time getting the keyboard shortcut Alt-Ctrl-C to work in InDesign.
I do have the ATI Catalyst control center application running at startup on my Windows Vista PC, however even though I have disabled hot-keys within this application Alt-Ctrl-C still fails in InDesign.
Just in case the ATI application was still intercepting the key press event I tried both changing the hotkey that ATI responds to and closing the application all together. Still InDesign refuses to accept Alt-Ctrl-C
Any ideas?

The solution is to STOP ATI Catalyst from starting up in the startup menu when booting XP.
I had the same problem and it was ATI Catalyst that was the offender. It has a built-in shortcut key of CTRL + ALT + C that is set to open the program and it overrides the one in InDesign.
People have tried to disable the shortcut keys in Catalyst, but in all honesty, you just do not need the thing open until you actually want to use it. It is sitting there are a memory hog.
I solved the problem by going into the Start Menu of XP and taking it right out of there so it doesn't start up at all. This then leaves ID free to use the shortcut of CTRL + ALT + C.
You can also go to the START button, then RUN, then type in MSCONFIG, and select the last tab on the right: Startup. Then disable the ATI Catalyst check box. Close out of everything and do a reboot of your system.
Hope this helps those with the problem.

Ipod touch won't start up beyond apple on screen, just keeps flashing. Tried restoring but I continually get error messages but none of the solutions work. Help?

My Ipod touch stays on the start up screen with the apple and just blinks. I have tried all suggested
resolutions but none work. I have tried to restore it but continually get error code 1611 or 9. I have
tried all of those solution to no avail. Any other suggestions?

If you tried all the suggestions of:
http://support.apple.com/kb/TS3694
You likely have a hardware problem since the article says a possible cause of the 1611 error is a hardware problem. I would make an appointment at the Genius Bar of an Apple store.

[SOLVED] Ctrl-Alt-F1 does not work from KDM login screen

I have some weird problems with switching to the virtual console from the graphical GUI.
rc.conf: KEYMAP=hu
Unless I define hungarian keyboard in KDE4 also, I cannot switch to vc/1 with Ctrl-Alt-F1. When the keyboard is defined in KDE4, i can switch.
But in the KDM login screen, I am unable to switch and there is no option to set the keyboard.
Any ideas please?
Last edited by SanskritFritz (2009-02-28 19:08:24)

Option "XkbLayout" "en"
Hey, you got the point, this was the solution! Setting the option to "hu" solved my problem! Thank you!

Help needed, M getting this message sandbox environment error no test user account, when downloading any application from iTunes, friend told me to sign out and sign in iTunes it might solve the problem but instead I cannot login I to my itune account.

Help needed,
I am getting this message sandbox environment error no test user account, when downloading any application from iTunes, friend told me to sign out and sign in iTunes it might solve the problem , and i triyed it but still I cannot login I to my itune account. Same message keeping. Popping up, this problem started supricly today.

Take a look at the instructions here.
http://www.technogal.net/2012/03/this-is-not-test-user-account-please.html

I AM A CREATIVE CLOUD MEMBER FOR SOMETIME BUT NOW WHEN I LOGIN WITH THE CORRECT PASSWORD I STILL GET SIGNED OUT MESSAGE AND THEN WHEN TRIED THE SOLUTION GIVEN BY HELP THAT IS TO DELETE OPM.DB FILE OR SECOND SOLUTION INSTALL A FRESH CREATIVE CLOUD FOR DESK

I AM A CREATIVE CLOUD MEMBER FOR SOMETIME BUT NOW WHEN I LOGIN WITH THE CORRECT PASSWORD I STILL GET SIGNED OUT MESSAGE AND THEN WHEN TRIED THE SOLUTION GIVEN BY HELP THAT IS TO DELETE OPM.DB FILE OR SECOND SOLUTION INSTALL A FRESH CREATIVE CLOUD FOR DESKTOP APP OR EVEN SOLUTION OF RUN OF IMSLIBREPLACER IM STIILL NOT ABLE TO LOGIN TO MY CREATIVE CLOUD FOR DEKTOP APP . PLEASE HELP ME AS I NEED TO GET IN AND EXPLORE MORE OF MY DOWNLOADED S/W
I HAVE TRIED ALL POSSIBLE SOLUTION BUT AM AMAZED HOW THIS IS HAPPENING TO ME.
PLEASE PLEASE HELP ME .Creative Cloud Connection

Hi Alfred,
I would like to know the exact error message when you sign in, in the meanwhile please try the following steps assuming its Windows, let me know if its a MAC:
1) Go to Start button>> Control panel>> Uninstall a program.
2) Check if you see Browser safeguard there, if yes then uninstall it.
3) Open Internet explorer>> Tools>> Internet options>> Connections>> Lan Settings>> and it should be like this.
-Ankit

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

Hi..i am trying to login i message but i cant access ,it thing i forgot my password number, please i need help,how i can reset new password number. please i need help.

hi..i am trying to login i message but i cant access ,it thing i forgot my password number, please i need help,how i can reset new password number. please i need help.

Go here.
Good luck,
Clinton

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

Macbook Pro not shutting down using "cmd alt ctrl eject"

Usually, the keyboard shortcut "cmd alt ctrl eject" worked as expected, shutting down my Macbook Pro 2010 (running latest Mountain Lion) instantly.
Now, recently, it started to behave differently: It will now not shut down, but (very shortly - almost not readable) display the error message "You shut down your computer because of a problem" and then go to the login screen. Typing in the password will lead back to the desktop - no shutting down. Otherwise, through the menu or power button, shutting down still works.
I have browsed the forum for this case, but could only find few other (mostly unsolved) issues that sounded similar (issues on start up etc), but didn't really match my specific issue.
Did anybody experience a similar issue and/or has an idea for a solution?
btw I have recently installed a new SSD drive and installed Mountain Lion freshly. After the install, the keyboard shortcut worked fine, until it stopped working...
Thanks, Ralf.

After playing around some more, I think I have found the source of the issue.
It seems that a background process from a ColorMunki calibration tool kept the Mac from shutting down properly. The calibration SW had placed a little icon in the top bar. After exiting from that program, the keyboard command is now again working.
So, might be that other similar cases are also related to processes / programs still running in the background, without being visible as such in the dock...

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

[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

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)

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.

Hotkeys Alt+Ctrl+F1 - Alt+Ctrl+F5 - which pre-install application intercepts them

I used to use keys combination from Alt+Ctrl+F1 to Alt+Ctrl+F5 as hotkeys for certain application. But in my new Lenovo ThinkPad w530 with Windows 7 x64 I can not do it, as it seems, that some pre-installed software has registered these combination for itself. When I press them, absolutely nothing happens, but if I try to assign these combinations in my app, i get the error message, that they are already registered for some other application.
I've checked twice all installed applications, starting from Window 7 itself. Seems, that none of them uses these keys.
Well, I've tried than to stop virtually any software, incuding resident utilities, but this hotkyes are still busy
Is there any ideas, which piece of software pre-installed by Lenovo might reserve these combination for itself?
Or is there any way to detect, which application intercepts handling this keys?
Thanks in advance!

So what? Whether nobody has the same issue with occupied hotkeys or has no time to answer?
I suppose, that the problem is somehow connected to the package Intel Management and Security Status, which is pre-installed by Lenovo. But i could not find any option to change these default hotkeys or disable them at all.

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

Similar Messages

Maybe you are looking for