Re: my first raid disaster on reboot :o( update
hi ya ken
On Thu, 8 Sep 2005, Ken Walker wrote:
== which is it ..
- raid1 or raid0 .. big difference betweenthe two
> /dev/md7 using /dev/hda,/dev/hdc
> /dev/md8 using /dev/hab,/dev/hdd
the whole disk or /dev/hda1 and /dev/hdc1 ??
- its a good choice for /dev/hdcxx and /dev/hdcxx
but it'd be better for hda+hdd and hdb+hdc
> mdadm -C /dev/md7 -l1 -n2 /dev/hda /dev/hdc
why ??
> I checked with Fdisk that they were all set as FD.
good
> And on reboot only md0 would mount.
and what is /dev/md0 ???
- its not defined above
> So i copied the original mdadm.conf back and rebooted, and all the raids
> apart from md7 and md8 started.
presumably you have /dev/md0, /dev/md1, .. etc.. etc
copying mdadm.conf files is not a good idea unless
its all configured the same way ...
> The system booted up properly this time but again without md7 or md8, it did
> its corrupt superblock or ext2 file system complaints.
:-)
moving files around and/o incorrect mdadm commands
> DEVICE /dev/sdb1 /dev/sdc1
> ARRAY /dev/md0 level=raid0 num-devices=2
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
raid0 means 2-small-disk is combined to look like 1 big-disk
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
- ie, there is no redundancy
> ARRAY /dev/md0 level=raid0 num-devices=2
> UUID=410a299e:4cdd535e:169d3df4:48b7144a
> DEVICE /dev/sdb1 /dev/sdc1
>
> Which way round should it be?
if you're referring to the order of array, uuid and device, it shouldn't
matter unless things changed that it is order sensitive
> I have also read that a mdadm.conf file isn't really needed, but can be
> helpful, if i hide me mdadm.conf file will the system boot with md7 and md8.
i'd say you have some undefined ( unknown ) /dev/md devices
> I do have those two raids in my fstab file at the end as
>
> /dev/md7 /Cad100 ext3 defaults 0 2
> /dev/md8 /Cad200 ext3 defaults 0 2
and where is / /tmp and /var etc defined
the system should boot with /dev/md7 and /dev/md8 commented out,
otherwise you ahve system problems ... in additiona to corrupted raid
devices
> The SCSI is split up into / /usr /var /swap /tmp and /home, each set as
> a raid1.
goood
but here you said raid1 ... the previous config files you showed referred
to raid0
> The IDE's are set up as raid1 on the ide channels, such that hda is mirrored
> with hdc and hdb is mirrored with hdd.
its a good start .. but it will nto guarantee that you cn boot,
because you do NOT have a master disk on the 2nd raid pair
( some bios' is picky )
> I had to move the system today so powered down with shutdown -h now.
good
> On reboot i just get / mounted ( i think ) and everything else says mdx
> corrupt superblock or such and not a valid ext2 fs.
corrupt superblock means your eitehr your fs is corrupt or your raid
is broken ( not really working raid )
> all the mirrors were set us as ext3 and when it was up and running
> /proc/mdstat said all was well.
what is its output ??
c ya
alvin
Reply to: