New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
mdadm exited with status 127
Can anyone explain what does this error stands for? (Google does not have enough info).
Situation:
Centos6-64bit 4HD Software Raid Setup ( tried with both ext3 and ext4 system)
After installation, First Reboot, Error shows up during shut down. That is it. Any idea?
Comments
ext3 might work, is grub installed in md0 ?
I am not an expert in centos tho.
Edit, ah, didnt see you already booted fine.
M
@Maounique Ext3 and 4 tried both.
So, it boots, works fine and then at shutdown it throws that error ?
M
@Maounique Only during the initial Reboot ( first one after installation). No more error.
You are lucky, it looks like others have a frozen grub afterwards. Maybe related to where grub was installed, maybe because some drives temp names at install and then switch to final ones which breaks mdadm at shutdown. Long ago had a software raid in fedora and had another issue which might be related, but another error, and each shutdown. Dont remember much.
My 2c.
M
@Maounique Not sure. As it is only happening once and after that everything runs simply fine. And Never had such issue before ( Same configuration, portion and hardware)
Then I suspect it is because of target switching and some hard drive UUID or similar changing from temporary to final config while mdadm is still on.
M
Quick google churns up http://www.linuxquestions.org/questions/red-hat-31/error-mdadm-exited-with-status-127-a-855713/
And last post mentions a bug, https://bugzilla.redhat.com/show_bug.cgi?id=761584
And also here https://cn.forums.oracle.com/forums/thread.jspa?threadID=2203978&tstart=0&messageID=9512661
Seems to be multiple reports of this, You could try using a new mirror for the CentOS 6 or use a minor release of it.
@Jacob yes looks like something is wrong with anaconda. Will try with a new Disk.