Arch Linux

hseara

Member

From: Tampere

Registered: 2010-03-24

Posts: 11

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 systemd-fsck@dev-md126p1.service -.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 systemd-fsck@dev-md126p1.service -.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)