[SOLVED] mdadm command not found?

Got a degraded array email when one 8TB drive in an eight drive RAID 5 array failed. Shut the server down to make certain I was replacing the correct drive (by serial number), found it, put it back in and booted the server, thinking, as has happened before, that the degraded array would mount and then I would replace the bad disk with a new one that was on-hand for this purpose.

Well, it didn't mount, and when I ssh'ed into the server to check things out with mdadm, I get the message "command not found." Just out of curiosity, wanted to see what would happen if I tried to (re-)install mdadm, but apt told me it was already the latest version. sudo'ed to root and did a find on the OS drive from the root for mdadm and sure enough, there is no mdadm binary on the drive.

No problem indicated with the SSD that is hosts the OS.

This is a real headscratcher to me.

Here is what the find (er) found:

root@OMV2:/# find . -name mdadm

./etc/default/mdadm

./etc/cron.d/mdadm

./etc/monit/conf-available/mdadm

./etc/init.d/mdadm

./etc/mdadm

./etc/logcheck/violations.d/mdadm

./etc/logcheck/ignore.d.server/mdadm

./run/mdadm

./var/www/openmediavault/js/omv/module/admin/storage/mdadm

./var/cache/salt/minion/roots/hash/base/omv/deploy/mdadm

./var/cache/salt/minion/files/base/omv/deploy/mdadm

./usr/sbin/mdadm

./usr/share/bug/mdadm

./usr/share/bash-completion/completions/mdadm

./usr/share/initramfs-tools/scripts/local-bottom/mdadm

./usr/share/initramfs-tools/scripts/local-block/mdadm

./usr/share/initramfs-tools/hooks/mdadm

./usr/share/doc/mdadm

./usr/share/mdadm

./srv/salt/omv/deploy/mdadm

Any ideas?

And the missing mdadm seems like the big problem here, but here is the mdadm.conf:

DEVICE partitions

# auto-create devices with Debian standard permissions

CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system

HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts

MAILADDR ******@**********.***

MAILFROM root

# definitions of existing MD arrays

ARRAY /dev/md127 metadata=1.2 spares=0 name=OMV2:OMV2 UUID=8de63887:374f9e49:4b351f6d:f1827845

Any input appreciated!

ARRGHH I just noticed the /usr/sbin, I guess that just isn't in the path (is that correct?)!

I'll try some instruction posted for previous users by rycoaaron and check back in if I need assistance later.

"which" returned nothing, I tried that before the "find"

Drive replaced, recovering.

Zitat von Zoki

which will check which binary would be run, if it is in your path.

If something is not in your path which will not find it.

Correct, that was the case here.