Re: Re: mdadm: raid not working after stop/reboot

From: Blagovest Bogoev (blagovest.bogoev_at_tumbleweed.com)
Date: 11/18/05

  • Next message: Andreas Rippl: "Re: Slow server response"
    Date: Fri, 18 Nov 2005 15:13:30 +0200
    To: debian-user@lists.debian.org
    
    

    On (29/06/05 08:25), Kristian Rink wrote:
    > Hi Mike;
    >
    > and, at first, thanks loads for your mail.
    >
    > michael@etalon.net schrieb:
    >
    > > I found it easier not use the mdadm.conf file at all. I simply deleted
    > > it.
    > > However, without it, your partitions and/or disks that are going to be
    > > used in your raid array must be fdisk'd to type "fd" or Linux Raid
    > > autodetect.
    > >
    > Yeah, I read about this and did this,all partitions to be used within
    > the array are type "FD". Even though this doesn't seem to change anything.
    >
    > > Then create your array, format it, mount it, set it in /etc/fstab and
    > > reboot.
    > > It should work. Perhaps give us some details of your /proc/mdstat or
    > > try hunting through dmesg to see if there any errors when the array is
    > > trying to be built upon a boot up.
    >
    > I'm hardly able to do any diagnostics on that since the information I
    > get is pretty limited. Basically, I created the array, xfs-formatted it,
    > put it into fstab and mounted it - worked well. Umounting, remounting
    > and everything worked as long as the array was running. After rebooting,
    > the array seemed gone. I don't get any useful error messages, just an
    > "XFS SB error" when trying to mount the array (which is not running at
    > this time), and when I try to start the array (mdadm -R /dev/md0), I
    > just get something like "/dev/md0 has no devices" (though the real
    > behaviour and message changes differing with the kernel version used).
    >

     

    Just recreate initrd.img (man mkinitrd) after all RAID puzzle is done, reboot and be happy

     

    --
    Blagovest Bogoev (blagovest.bogoev@tumbleweed.com
    QA Engineer
    Tumbleweed Communications (www.tumbleweed.com <http://www.tumbleweed.com/> )
    Sofia, Bulgaria

     


    "Tumbleweed E-mail Firewall <tumbleweed.com>" made the following
     annotations on 11/18/05 05:23:51
    ------------------------------------------------------------------------------
    This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
    ==============================================================================

    -- 
    To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: Andreas Rippl: "Re: Slow server response"

    Relevant Pages

    • Re: Asus P5QL Pro Nightmare
      ... should change is the setting of the SATA Hard disk. ... a row, but if I wait a few hours after shutting down, then I can reboot ... and as soon as I try to create the array with the ... You can speed up that reboot problem by discharging the power to ...
      (Ubuntu)
    • Re: Asus P5QL Pro Nightmare
      ... a row, but if I wait a few hours after shutting down, then I can reboot ... and as soon as I try to create the array with the ... raid array at all. ... You can speed up that reboot problem by discharging the power to ...
      (Ubuntu)
    • Re: mdadm: raid not working after stop/reboot
      ... >> reboot. ... Basically, I created the array, xfs-formatted it, ... I don't get any useful error messages, ... > behaviour and message changes differing with the kernel version used). ...
      (Debian-User)
    • Re: Asus P5QL Pro Nightmare
      ... a row, but if I wait a few hours after shutting down, then I can reboot ... and as soon as I try to create the array with the ... You can speed up that reboot problem by discharging the power to ... Most boot cd's will rebuild raid arrays. ...
      (Ubuntu)
    • Re: gvinum or vinum in 5.3-STABLE
      ... > The array works perfectly until reboot. ... Once the plexes are UP, issue a 'gvinum saveconfig'. ...
      (freebsd-stable)