Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm getting superblock errors on one of the drives in my RAID 5 array.
There are 4 drives in the SATA array
So I tried to "heal" sdb (the affected drive) with e2fsck -b 8193 /dev/sdb and I even tried the other locations . After I did this it still gave me superblock errors after I tried to reassemble the arrary.
I have checked sdb for bad blocks with mkfs -c, no bad blocks (drives are under 6 months old.
the result of the mdadm assemble is :
ubuntu@ubuntu:~$ sudo mdadm --assemble /dev/sda /dev/sdb /dev/sdc /dev/sdd
mdadm: no recogniseable superblock on /dev/sdb
mdadm: /dev/sdb has no superblock - assembly aborted
I have formatted (fdisk) /dev/sdb hoping to create a superblock of some sort so that I can re-assemble the array but I still get "no superblock" error? Why is this if I create a filesystem on the drive? (I've done mkfs.ext3 /dev/sdb several times and I see the progress etc)
There is something wrong with your setup. It's strange that you're creating array with whole drives and not partitions.
I am using RAID 1 and never used RAID 5, but things should be quite similar. You should first start your array with survived disks and then try to add a new drive (/dev/sdb). But where is your sda drive? RAID 5 can't work if you lost 2 drives...
Superblock is created at the moment of RAID creation. It will be recreated when you add drive to array which is up and running.
lanart: I think you're right IIRC, you can't make array's out of physical
drives. I wonder if I'm not formatting with fdisk correctly , setting up the RAID flags on sdb? (sda seems fine btw, gparted seems to act bizzare on the 7.10 live disk I'm using to rescue the system).
juu801: I tried sudo mdadm --assemble /dev/md0 /dev/sda /dev/sdc /dev/sdd
no recogniseable superblock on /dev/sda
mdadm: /dev/sda has no superblock - assembly aborted