`mount -a` command is not works for mdadm RAIDs

Dave Chiluk chiluk at gmail.com
Wed Sep 13 05:05:01 UTC 2017


Please direct questions like this to https://ubuntuforums.org/,
https://askubuntu.com/, or one of the other support resources like
https://help.ubuntu.com/community/OtherResources.  This is not a support
mailing list.

That being said, you need to make sure that your mdadm raid is listed in
/etc/fstab, and that it has the auto option.  If that doesn't work please
direct your question to one of the above resources.

Thank you,
Dave Chiluk

On Sun, Sep 10, 2017 at 8:52 AM, hibi <hibi.sasahara at gmail.com> wrote:

> Hello.
>
> I trying Ubuntu17.10 amd64 from 16.04.
> I use mdadm raid array (two array of raid0, raid1).
>
> My problem is `mount -a` command is not works for mdadm RAIDs.
> This is issue? or new technical specification?
>
>
>
> I setting to "/etc/fstab".
> ```
> UUID=3b1ea9cc-4969-443f-b1f5-XXXX /home/ME/raid0 ext4 noatime     0 2
> ```
>
> and mount -a command option is not work.(not mounted)
> `sudo mount -a`
>
> but, this command is work!
> ` sudo mount --uuid 3b1ea9cc-4969-443f-b1f5-XXXX /home/ME/raid0 `
>
> I check "/var/log/syslog".
> but nothing error message.
>
>
>
> I know issue of mdadm RAID array is not mounted when boot.
>
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1020032
> and others.
> https://bugs.launchpad.net/ubuntu/?field.searchtext=fstab+
> mdadm&search=Search&field.status%3Alist=NEW&field.status
> %3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPL
> ETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.
> status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=
> FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.
> omit_dupes=on&field.has_patch=&field.has_no_package=
>
>
>
> What should I try?
>
> Thanks.
>
> --
> Ubuntu-bugsquad mailing list
> Ubuntu-bugsquad at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20170913/712674cb/attachment.html>


More information about the Ubuntu-bugsquad mailing list