[ale] update on my RAID problems from yesterday.

John Cole JohnC at LGEFCU.org
Tue Feb 10 11:36:26 EST 2004


Well, I did do that partition change for /dev/hdf1.

Now I did the following.  (I removed the /var/logs line from /etc/fstab so
that I could boot up onto the network),

[root at CATCH1 root]#  mdadm --assemble --verbose -s
mdadm: looking for devices for /dev/md1
mdadm: /dev/hde1 is identified as a member of /dev/md1, slot 0.
mdadm: no RAID superblock on /dev/hdf1
mdadm: /dev/hdf1 has no superblock - assembly aborted

   Device Boot Start     End   #cyls   #blocks   Id  System
/dev/hde1   *      0+ 116357  116358- 58644400+  83  Linux
/dev/hdf1   *      0+ 116357  116358- 58644400+  fd  Linux raid autodetect

Here is the output of some other commands:

[root at CATCH1 root]# mdadm --assemble -U summaries /dev/md1
mdadm: /dev/hdf1 has no superblock - assembly aborted

[root at CATCH1 root]# mdadm --assemble -s /dev/md1
mdadm: /dev/hdf1 has no superblock - assembly aborted

Lost in RAID world :)
Disclaimer: The information contained in this email is proprietary and
confidential.  It is intended solely for the use of the person identified
and intended as the recipient. This document is forwarded to you in such a
form (E-mail) that LGEFCU cannot guarantee the completeness and/or
correctness of its contents and information. If you have received this
E-mail message in error, please notify us immediately. Please also delete
this document from your computer. This document may not be reproduced,
copied, distributed, published, modified, or furnished to third parties,
without the prior written consent of LGEFCU. LGEFCU specifically disclaims
any responsibility or liability for any personal information or opinions of
the author expressed in this email.

More information about the Ale mailing list