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 have a system running fc10 and am setting up a software RAID array using mdadm. I have an array working in RAID 5 with 5 disks but after a reboot (or the devices are stopped in some other way) the array will not assemble with mdadm --assemble and with mdadm --auto-detect it builds it with 4 disks and a spare.
Could someone help me out?
Also when I use --examine on a device, it says there is no superblock and tells me nothing.
I did find one drive that was not raid autodetect (fd) and fixed that. I am trying a rebuild now but that will take a long time to check.
I also wonder, is there a way I may prevent my drives from getting new names whenever I swap some out? Having them get their device names at boot time is quite difficult when you have an array set up using a specific list of devices and perhaps you added a few drives or something.
Distribution: CentOS, RHEL, Solaris 10, AIX, HP-UX
Posts: 731
Rep:
Hi,
Code:
--incremental
will add a device to an existing array. So i think your commandline is wrong, because you try to add /dev/md0 which is an existing array. Normally you would add additional disks to an array eg. for replacement.
Do md arrays function like real RAID 5 (in my case)? Initially I was trying to test by building array, physically removing drive, and rebuilding... but after removal of drive I could still mount up? Twice. I think this is strange, it did some live rebuild, in 5 seconds, without asking? I don't really what's up.
And do you know what's going on with all my superblock errors? Whenever I try a command to modify or view array it tells me about how it can't read superblock. I can now assemble the array directly though.
For removal of a drive would I use:
mdadm --manage /dev/md0 --remove /dev/sdb1
Distribution: CentOS, RHEL, Solaris 10, AIX, HP-UX
Posts: 731
Rep:
Hi,
not sure if i all understand right
Sure you can mount your RAID-5 while one disk is gone. This is the purpose of RAID Yes md devices works like real RAID.
It's correct to remove a disk with --remove. Did you also have add a new disk or re-add an existing one? You can use --add to add a new disk or --re-add to add a disk previously removed.
The superblock errors occurs in case of incorrect usage. For example when you try to access the md-device istead of physical disk (in your --incremental for example you tried to access /dev/md0, but you have to use a physical devicename like /dev/sdb1).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.