Page 1 of 5 123 ... LastLast
Results 1 to 10 of 49

Thread: Raid array does not auto start/auto mount

  1. #1
    Join Date
    May 2010
    Beans
    35

    Raid array does not auto start/auto mount

    Hey all
    Ive searched high and low for a solution to this problem but havent been able to solve it so I though i'd post here.

    On boot I get a screen stating 'the disk for/mnt/md0 is not ready yet or not present. Continue to wait; or Press S to skip mount or M for manual recover'. If i press M and try 'mount -a' it states that 'special device /dev/md0 does not exist'. If I try 'mdadm --assemble --scan' it states 'no devices found for /dev/md0'. If I skip the mounting of the array, and start the array then mount it through palimpset everything mounts as should be (devices in array and mount location).

    Some information:

    server@server:~$ sudo mdadm -D -s
    ARRAY /dev/md0 level=raid5 num-devices=4 metadata=01.02 name=:raid5 UUID=02bcfe3b:44fc949f:f5f7e481:a421a2c0

    /etc/mdadm/mdadm.conf

    # mdadm.conf
    #
    # Please refer to mdadm.conf(5) for information about this file.
    #

    # by default, scan all partitions (/proc/partitions) for MD superblocks.
    # alternatively, specify devices to scan, using wildcards if desired.
    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 server

    # definitions of existing MD arrays
    ARRAY /dev/md0 level=raid5 metadata=1.2 num-devices=4 UUID=02bcfe3b:44fc949f:f5f7e481:a421a2c0 name=md0

    # This file was auto-generated on Sat, 01 May 2010 18:15:04 +1000
    # by mkconf $Id$

    /etc/fstab

    # /etc/fstab: static file system information.
    #
    # Use 'blkid -o value -s UUID' to print the universally unique identifier
    # for a device; this may be used with UUID= as a more robust way to name
    # devices that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc nodev,noexec,nosuid 0 0
    # / was on /dev/sda1 during installation
    UUID=906694f9-9425-4ae3-88cc-bd9f4161846b / ext4 errors=remount-ro 0 1
    # swap was on /dev/sda5 during installation
    UUID=01cb5d34-e4ac-4329-95c1-e9396a414a28 none swap sw 0 0
    #mdadm array
    /dev/md0 /mnt/md0 auto defaults 0 0

    I have tried editing the mdadm.conf using this thread,but the problem still persists.

    Any suggestions?

    EDIT: Im running ubuntu 10.04 with all updates installed.
    Last edited by teeedubb; May 1st, 2010 at 12:22 PM. Reason: Added info

  2. #2
    Join Date
    Apr 2010
    Beans
    327

    Re: Raid array does not auto start/auto mount

    Hi from 10.04 land!

    Im not going to be alot of help but I have run into the same problem. In order for me to mount my raid I have to manually do it.

    sudo mount -t ext3 /dev/md0 /mnt/raid

    My fstab entry does not work and gives me the following error:

    sandy@sandy-desktop:/etc$ sudo mount /dev/md0
    mount: wrong fs type, bad option, bad superblock on /dev/md0,
    missing codepage or helper program, or other error
    In some cases useful info is found in syslog - try
    dmesg | tail or so
    Manually mounting the raid works fine. But not thru fstab for some reason. Hopefully they can fix this soon. Its not pretty to manually have to mount the raid.

    More info:
    sandy@sandy-desktop:/etc$ sudo mdadm -D /dev/md0
    /dev/md0:
    Version : 00.90
    Creation Time : Fri Apr 30 13:28:30 2010
    Raid Level : raid5
    Array Size : 1953519872 (1863.02 GiB 2000.40 GB)
    Used Dev Size : 976759936 (931.51 GiB 1000.20 GB)
    Raid Devices : 3
    Total Devices : 3
    Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Sat May 1 10:16:39 2010
    State : clean
    Active Devices : 3
    Working Devices : 3
    Failed Devices : 0
    Spare Devices : 0

    Layout : left-symmetric
    Chunk Size : 64K

    UUID : f00cb7c7:325e1ad0:e1af99e9:92c82b1d
    Events : 0.55

    Number Major Minor RaidDevice State
    0 8 17 0 active sync /dev/sdb1
    1 8 33 1 active sync /dev/sdc1
    2 8 49 2 active sync /dev/sdd1
    coffee

  3. #3
    Join Date
    May 2010
    Beans
    35

    Re: Raid array does not auto start/auto mount

    coffee412: So is your raid array being started automatically? Is the only problem that you have is that its not being mounted? Mine isnt being started during boot, so Im not sure if its a fstab or mdadm.conf issue, though both seem to be correct.

  4. #4
    Join Date
    May 2010
    Beans
    35

    Re: Raid array does not auto start/auto mount

    I have posted a bug report as the same is happening on another machine with a raid array, although its a raid 0 array. As I posted in the bug report, I noticed this during the installation of mdadm on the new machine:

    Setting up mdadm (2.6.7.1-1ubuntu15) ...
    Generating array device nodes... /var/lib/dpkg/info/mdadm.postinst: 170: /dev/MAKEDEV: not found
    failed.
    Generating mdadm.conf... done.
    Removing any system startup links for /etc/init.d/mdadm-raid ...
    Could this have something to do with the array not starting?
    Here is the complete transcript of the install:


    The following NEW packages will be installed:
    mdadm postfix
    0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
    Need to get 1,642kB of archives.
    After this operation, 4,248kB of additional disk space will be used.
    Do you want to continue [Y/n]? y
    Get:1 http://archive.ubuntu.com/ubuntu/ lucid/main mdadm 2.6.7.1-1ubuntu15 [239kB]
    Get:2 http://archive.ubuntu.com/ubuntu/ lucid/main postfix 2.7.0-1 [1,403kB]
    Fetched 1,642kB in 8s (200kB/s)
    Preconfiguring packages ...
    Selecting previously deselected package mdadm.
    (Reading database ... 149165 files and directories currently installed.)
    Unpacking mdadm (from .../mdadm_2.6.7.1-1ubuntu15_amd64.deb) ...
    Selecting previously deselected package postfix.
    Unpacking postfix (from .../postfix_2.7.0-1_amd64.deb) ...
    Processing triggers for ureadahead ...
    Processing triggers for doc-base ...
    Processing 26 changed 1 added doc-base file(s)...
    Registering documents with scrollkeeper...
    Processing triggers for man-db ...
    Processing triggers for ufw ...
    Setting up mdadm (2.6.7.1-1ubuntu15) ...
    Generating array device nodes... /var/lib/dpkg/info/mdadm.postinst: 170: /dev/MAKEDEV: not found
    failed.
    Generating mdadm.conf... done.
    Removing any system startup links for /etc/init.d/mdadm-raid ...
    update-initramfs is disabled since running on read-only media
    update-rc.d: warning: mdadm start runlevel arguments (2 3 4 5) do not match LSB Default-Start values (S)
    update-rc.d: warning: mdadm stop runlevel arguments (0 1 6) do not match LSB Default-Stop values (0 6)
    * Starting MD monitoring service mdadm --monitor [ OK ]
    Setting up postfix (2.7.0-1) ...
    Adding group `postfix' (GID 123) ...
    Done.
    Adding system user `postfix' (UID 115) ...
    Adding new user `postfix' (UID 115) with group `postfix' ...
    Not creating home directory `/var/spool/postfix'.
    Creating /etc/postfix/dynamicmaps.cf
    Adding tcp map entry to /etc/postfix/dynamicmaps.cf
    Adding group `postdrop' (GID 124) ...
    Done.
    setting myhostname: ubuntu
    setting alias maps
    setting alias database
    mailname is not a fully qualified domain name. Not changing /etc/mailname.
    setting destinations: ubuntu, localhost.localdomain, , localhost
    setting relayhost:
    setting mynetworks: 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
    setting mailbox_size_limit: 0
    setting recipient_delimiter: +
    setting inet_interfaces: all
    /etc/aliases does not exist, creating it.
    WARNING: /etc/aliases exists, but does not have a root alias.
    Postfix is now set up with a default configuration. If you need to make
    changes, edit
    /etc/postfix/main.cf (and others) as needed. To view Postfix configuration
    values, see postconf(1).
    After modifying main.cf, be sure to run '/etc/init.d/postfix reload'.
    Running newaliases
    * Stopping Postfix Mail Transport Agent postfix [ OK ]
    * Starting Postfix Mail Transport Agent postfix [ OK ]
    Processing triggers for libc-bin ...
    ldconfig deferred processing now taking place
    ubuntu@ubuntu:~$

  5. #5
    Join Date
    May 2010
    Beans
    35

    Re: Raid array does not auto start/auto mount

    Any ideas?

  6. #6
    Join Date
    Jun 2006
    Beans
    26

    Re: Raid array does not auto start/auto mount

    same issue here with my raid 0 array. I'm suspecting it is an issue with the 10.04 upgrade(as it happened right after i did the upgrade and rebooted).
    Double checked my fstab and mdadm.conf and both seem fine yet for some reason when i reboot ubuntu server it says unable to mount and waits for me to press s to continue or another key to drop to shell.

    When i run mdadm --assemble --scan creates the /dev/md0 device and when i run mount /dev/md0 /mnt/raid it all mounts as it should.
    just not at bootup like normal.

    Just tried apt-get remove mdadm and then apt-get install mdadm,..didn't fix it...
    Last edited by frente69; May 12th, 2010 at 10:41 AM.

  7. #7
    Join Date
    Nov 2009
    Beans
    Hidden!
    Distro
    Kubuntu 10.10 Maverick Meerkat

    Re: Raid array does not auto start/auto mount

    Did any of you try pasting the complete string output of the following command that starts with the word "ARRAY" into mdadm.conf:
    sudo mdadm -D -s
    or
    sudo mdadm --detail --scan

    I noticed a slightly different name and metadata superblock information in mdadm.conf. Not sure on whether that info is required given the UUID. But try keeping things simple.

  8. #8
    Join Date
    Apr 2009
    Beans
    4

    Re: Raid array does not auto start/auto mount

    Quote Originally Posted by frente69 View Post
    same issue here with my raid 0 array. I'm suspecting it is an issue with the 10.04 upgrade(as it happened right after i did the upgrade and rebooted).
    Double checked my fstab and mdadm.conf and both seem fine yet for some reason when i reboot ubuntu server it says unable to mount and waits for me to press s to continue or another key to drop to shell.

    When i run mdadm --assemble --scan creates the /dev/md0 device and when i run mount /dev/md0 /mnt/raid it all mounts as it should.
    just not at bootup like normal.

    Just tried apt-get remove mdadm and then apt-get install mdadm,..didn't fix it...
    --
    I think this seems a different issue to the original post maybe? BUT I had similar issues because my /etc/mdadm/mdadm.conf file was still there...

    Did you try to delete the file: sudo rm /etc/mdadm/mdadm.conf

    then run: sudo dpkg-reconfigure mdadm (no need to uninstall/reinstall)

    It should re-create /etc/mdadm/mdadm.conf

    AND should spew some messages about running update-initramfs (I don't know but it seem to use the content of mdadm.conf when building the initrd.img - can anyone confirm?)

    I also found I had problems with using UUIDs in the mdadm.conf - it grabbed the device for the raid instead of the partition, so for me what finally worked is setting the content of mdadm.conf to:

    ARRAY /dev/md0 devices=/dev/sdb1,/dev/sdc1,/dev/sdd1,/dev/sde1
    the same devices as I used for the create (instead of UUIDs)

    THEN again ran: sudo dpkg-reconfigure mdadm
    (this time because you have a valid /etc/mdadm/mdadm.conf - it does NOT get recreated, but the settings seem to be used for the initrd.img).

    Now everything's coming up Millhouse for me..

    Hope this helped someone - and if anyone can explain why mdadm grabs the device instead of the partition (when using UUIDs), I'd appreciate it!

    Cheers,
    ObM.

  9. #9
    Join Date
    Apr 2009
    Beans
    31

    Re: Raid array does not auto start/auto mount

    Its not working for me.
    I've deleted the mdadm.conf recreated with dpkg-reconfigure, and I've replaced the UUIDs with device names.

    On reboot the array shows as: "not running - partially assembled".

    Stopping and starting it in the gui works fine, and no disks are showing as having any problems.

    Any ideas?

  10. #10
    Join Date
    Apr 2009
    Beans
    31

    Re: Raid array does not auto start/auto mount

    As an aside I have two machines using RAID:

    One is a raid 5 machine (array originally created under gentoo).
    This one works fine. The machine is running 10.04. (metadata 0.9)

    The other machine is raid 1, it was freshly created on the previous (i forget?) ubuntu but was then upgraded to 10.04. This is the one that fails to assemble on boot. (metadata 1.2).

    I noticed problems started almost immediately after upgrading to 10.04.
    Last edited by HRH_H_Crab; June 7th, 2010 at 06:50 PM.

Page 1 of 5 123 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •