Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I can't seem to figure out how to autostart my RAID 5 on bootup. (I'm using Debian 6.0)
I've tried a few things, but I'm worried that tinkering too much would make me loose my data. The raid has to be started manually (within Gnome) after every reboot.
enhed opstart start slut blokke id system
/dev/sdd1 * 1 6996 56190976 83 linux
/dev/sdd2 6996 7298 2421761 5 udvidet
/dev/sdd5 6996 7298 2421760 82 linux swap / solaris
3 mdadm --detail
Quote:
# mdadm --detail
mdadm: Only give one device per array line: /dev/md0 and raid
mdadm: Only give one device per array line: /dev/md0 and array
mdadm: No devices given.
# cat /etc/fstab
# /etc/fstab: Static file system information.
#
# use 'blkid' 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 defaults 0 0
# / was on /dev/sda1 during installation
uuid=473eb1c4-f7c2-4270-ba64-c70d66d778bc / ext3 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
uuid=9e4c8ca5-ddf0-4d24-bdac-a99f6b39614b none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/md0 /jadda ext4 defaults 0 0
# rw,nosuid,nodev 0 0
Did you run these commands when your RAID was up? For mdadm --detail you have to mention the device as well as follows:
mdadm --detail /dev/md0
I do not see any out for cat /proc/mdstat which makes me think that you ran the commands when RAID was not up.
It would be good if you could paste the output of mdadm.conf file as well. And you did not mention what are the things that you already tried. Just want to know so that we do not suggest what you already tried.
Perhaps the content of mdadm.conf is of interest as well?
C
Quote:
REATE 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 root
# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 UUID=8a0a4f78:8c878d94:7063b77d:d9bcbf92 name=:New RAID Array
# This file was auto-generated on Tue, 07 Feb 2012 18:16:27 +0100
# by mkconf 3.1.4-1+8efb9d1+squeeze1
---------- Post added 02-18-12 at 10:12 PM ----------
Perhaps the content of mdadm.conf is of interest as well?
C
Quote:
REATE 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 root
# definitions of existing MD arrays
ARRAY /dev/md0 metadata=1.2 UUID=8a0a4f78:8c878d94:7063b77d:d9bcbf92 name=:New RAID Array
# This file was auto-generated on Tue, 07 Feb 2012 18:16:27 +0100
# by mkconf 3.1.4-1+8efb9d1+squeeze1
Note: Make sure that you take a backup of existing mdadm.conf file. Make sure that you use double redirector >>. If you will use single then you will loose the existing stuff in that file.
I've been trying some changes to the mdadm.conf, enableing/disableing services related to mdadm and a whole lot of rebooting to see if i were going somewhere..
Thought it had to be down; here are mdadm --detail while up-and-running
Quote:
# mdadm --detail /dev/md0
mdadm: only give one device per ARRAY line: /dev/md0 and RAID
mdadm: only give one device per ARRAY line: /dev/md0 and Array
/dev/md0:
Version : 1.2
Creation Time : Sun Oct 30 17:34:28 2011
Raid Level : raid5
Array Size : 3907020800 (3726.03 GiB 4000.79 GB)
Used Dev Size : 1953510400 (1863.01 GiB 2000.39 GB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Sat Feb 18 21:35:04 2012
State : active
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
and comment out following line (put a # sign before it):
Code:
/dev/md0 /jadda ext4 defaults 0 0
Reboot the system.
Another thing that I noticed about your RAID is the name. Did you give it a name New Raid Array because I have seen people using giving one word name to their RAID array.
If the above does not work then we can think of putting a script to run at boot time to automatically mount it using the command.
Make sure that you take a backup of existing /etc/fstab before making any modifications. It is better to be safe then sorry ;-)
The name was the default suggestion; I would have given it another name with just one word.. :-)
Anyway; after reboot, the raid is still not up and running..
Thing that I am trying to figure out is how the RAID is getting started via Gnome. In short which command it is executing in the backend. And how it is identifying the RAID when system is unable to at the time of boot.
Another thing that you could try is putting the uuid in the following format in /etc/fstab:
# mdadm /dev/md0 --assemble -u 8a0a4f78-8c87-8d94-7063-b77dd9bcbf92
mdadm: only give one device per ARRAY line: /dev/md0 and RAID
mdadm: only give one device per ARRAY line: /dev/md0 and Array
mdadm: /dev/md0 has been started with 3 drives.
..exept for the two lines of "only give... ", wich i strongly assume has to do with the naming..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.