Pages

Search

Software RAID-5 crash - Forums Linux

Software RAID-5 crash - Forums Linux

Software RAID-5 crash

Posted: 16 Sep 2004 06:36 AM PDT

Scott Odom wrote:

/ ...
 

1. If you don't have a backup of essential data, make one by any means
necessary.

2. Configure and mount the entire array as though is it being created for
the first time.

3. Test the array exhaustively.

4. Restore the backup data to the array.

I am absolutely amazed by the number of times we see this same situaiton
arise in posts here. Choosing a RAID array over a single drive can, and
often does, create a system that is much less reliable than one with only
one drive, for the reason that, if one of the RAID array drives fails, the
operator can't figure out what to do to get the array back up again.

This is why Charles Lindbergh chose a single-engine airplane for his
historic flight across the Atlantic in 1927. His argument was that few of
the multi-engine airplanes of the time could stay aloft with only one
engine, so a multi-engine airplane was ultimately less reliable than a
single-egine plane.

The argument can be made that the Lindbergh example has nothing whatever to
do with multi-drive RAID arrays, but that is only true if the operator
knows exactly what to do if a drive fails.

--
Paul Lutus
http://www.arachnoid.com

bprof on fedora core 2

Posted: 16 Sep 2004 04:12 AM PDT

On Thu, 16 Sep 2004 04:12:48 -0700, shane wrote:
 

You assumed wrong...... It's just a warning. Here a quick check;

rpm -qa --queryformat '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}.rpm\n'
compat-gcc

It's one long line with a space before the package name.

And by the way you could have installed both (assuming the two RPM's are
in the same location) by; rpm -ihv compat-gcc*.rpm bprof*.rpm

Read 'man rpm' and see why the switches 'h' and 'v' are nice.


--
Hi! I'm a .sig virus! Please copy me to your .sig! so I can spread
This E-mail is safe, no Microsoft products were used in creating me!

softraid, spare to active

Posted: 16 Sep 2004 02:03 AM PDT

Gerrit Polder <nl> wrote: 
 

And you are adverse to taking out one of the presently active mirror
components? The spare will dive right in to take over when you do.

 

I have exactly the same manual page as you. I would be careful to create
the array in degraded format with only one (or at least only known good)
component active, somewhat like


mdadm -A --force /dev/md0 --level=1 -n 1_more -x 1_less /dev/sda1 missing missing missing

(or use -C if -A will not allow change of -n and -x). Then put in the
"missing" components.

What was wrong with using mkraid?

 

Do you?
 


Peter

cannot boot from floppy

Posted: 15 Sep 2004 11:35 AM PDT

Christian Heinze <de> wrote: 

I'd also say that there LILO IS installed on the floppy.

Thy hitting the tab key on the boot prompt and see what happens.

ftp://ftp.slackware.com/pub/slackware/slackware/bootdisks/

has a variety of bootdisks, one of which should suit you.

Yours,
Laurenz Albe

Graphical terminal (n00b alert)

Posted: 15 Sep 2004 10:05 AM PDT

"Baho Utot" <org> wrote in
news:org:
 

So what? The OP does and he's asking the question.

--
- Mark ->
--

How to specify where to write MBR

Posted: 15 Sep 2004 08:31 AM PDT

Lew Pitcher wrote: 

that unfortunately doens't work. I did it and it did write to the MBR I
wnat, but the boot doesn't complete; at bootup it says

LI

and just hangs. I dug around and found out that's cos my /boot/boot.b is
in the wrong place.

my /etc/lilo.conf file:
prompt
timeout=50
default=fedora1
boot=/dev/hde
map=/boot/System.map
install=/boot/boot.b
#message=/boot/message
lba32

image=/boot/vmlinuz
label=fedora1
initrd=/boot/initrd-2.4.22-1.2115.nptl.img
read-only
append="hdb=ide-scsi root=/dev/hde7"


other=/dev/hde2
optional
label=DOS

HELP! Crashed system.

Posted: 15 Sep 2004 05:40 AM PDT

Ken Tew <wpic.upmc.edu> wrote in message news:<cia8gf$n76$srv.cis.pitt.edu>... 
[snip]
 

kde 1.x has not been maintained for ???? and is loaded with bugs, etc.
If a newer kde (eg., 3.2.3 available for RH8 and up) is not to your
liking, I would suggest you find a wm that you _do_ like and that is
_still_ maintained -- your life will be _much_ simpler.
 

The _entire_ install process _with_ new partitioning on this old PII
350 took about 45 minutes (somewhat stripped using customn install) --
the newer install programs are _much_ cleaner, quicker, and there is
_no_ reason to repartition your hard disks if you don't want to --
just reformat to your preferred fs (ext3?). BTW, it is _highly_
recommended to wipe a disk after a thorough hosing just to make sure
that no bit gremlins remain on disk -- running badblocks will do ;-)
 

Assume now you've learned the reason(s) why you should not go rolling
your own libc files until you fully understand the implications. The
last "official" errata update from RH was glibc-2.2.5-44.i686.rpm
(2003-11-13). Even RH8 and RH9 are at 2.3.2. And you didn't even
mention upgrading gcc :-( 2.3.3 doesn't show up till FC2.
 

Since you're using an X window manager -- kde -- you will find that
all those old configs are (all but) useless. Even XFree86 configs may
be problematic and newer distros get them pretty good at install
anyway.

Same may or may not apply to your app configs -- only you can tell.

Use a rescue cd of some sort (I've used http://www.sysresccd.org/ ) to
boot up and just try to write the data to cd from the command line if
necessary. Note that above cd can be loaded into memory then
unmounted, thus freeing the cd to be used to burn data to cd :-)
There are probably other similar cds.

Due to changes in distros, kernels (2.4.x or 2.6.x), threads (nptl
now), XFree86 vs X.org Foundation vs freedesktop.org -- well, you get
the picture: it's finally time to bite the bullet and do the new
install/upgrade thing ;-)

And after installing from iso's (?) get familiar with apt/synaptic if
not so already.

hth,
prg
email above disabled

partition magic stops working after installing linux

Posted: 15 Sep 2004 05:01 AM PDT

On 2004-09-15, John Karuski <com> wrote:
 

Windows will only assign drive letter to partition type it recognizes;
e.g. FAT, NTFS. This is actually a Good Thing, because if Windows thinks
it should be able to read the linux partitions, it will pitch a fit until
you either 1) reformat the partitions to a type Windows can recognize, or
2) edit the partition table so that Windows doesn't think it should access
them.
 

This isn't really a solution, but have you considered using a different
tool to handle partitioning? GNUPartEd works well with both Windows and
linux filesystems and with QTPartEd as the GUI actually looks and feels a
great deal like Partition Magic.

You might want to try the "System Rescue CD" (http://www.sysresccd.org/)
for a self-contained, bootable CD with these and other useful tools.

--

-John (dhs.org)

Lisa daemon...

Posted: 14 Sep 2004 03:23 PM PDT

On Wed, 15 Sep 2004 17:37:01 +0200, Jose Maria Lopez Hernandez
<com> wrote:
 

Thanks for that but there is no chkconfig in there or revealed on a search
from /ect/ in all subdirectories.



--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

Dual boot Linux-Win98, LILO problem

Posted: 14 Sep 2004 02:21 PM PDT

On Wed, 15 Sep 2004 12:09:43 +0200, Eric Moors <land> wrote:
 

Versions of LILO since 22.5 (out now for over a year) have a simpler, and more
general syntax:

boot-as = 0x80

This is now the preferred syntax, as the BIOS device codes of disks are
determined by the LILO boot loader dynamically (at boot-time), and the
appropriate drive mapping is installed if necessary.

As long as the disk configuration is static, the older "map-drive" syntax may
be used. "map-drive" will be retained in future releases of LILO for backward
compatibility.

--John
 

Windows won't start after partition resize

Posted: 14 Sep 2004 12:59 PM PDT

Harry George <com> writes:
 

1. From http://homepage.ntlworld.com/allcam/hddformat.html

For Windows 2000 and XP user, it is a little bit complicated, you have
to choose according to your situation:

1. If all your computers have Windows 200 or XP, NTFS is certainly
the choice;

2. If you wish to have two or more operation system on the same
computer, such as Windows 98 in one partition and Windows XP in
another partition; you'd better choose FAT32, otherwise you can not
access the Windows 98 partition when you are running Windows XP, or
access the Windows XP partition when you are running Windows 98.

3. For those people who use portable hard drive or external hard
drive:

3.1 If all your computers are in NTFS format, choose NTFS
for your portable hard drive;

3.2 If your computer have both Window 98 and Windows XP, and
the system hard drive ( where the Windows 98 and XP are
installed) should be FAT32, and the portable hard drive
should also be FAT32;

3.3 In situation of 3.2, if you are not going to use the
portable hard drive under Windows 98, you may well choose
NTFS, as this will allow you to use a 250GB hard drive
under one drive letter (such as F:)


2. From "man mkfs.msdos"

DOS 6.x WARNING
The DOS 6.x FORMAT command looks for some information
in the first sector of the data area of the partition, and
treats this information as more reliable than the information
in the partition table. DOS FORMAT expects DOS FDISK to clear
the first 512 bytes of the data area of a partition whenever a
size change occurs. DOS FORMAT will look at this extra
information even if the /U flag is given -- we consider this a
bug in DOS FORMAT and DOS FDISK.

The bottom line is that if you use cfdisk or fdisk to change
the size of a DOS partition table entry, then you must also use
dd to zero the first 512 bytes of that partition before using
DOS FORMAT to format the partition. For example, if you were
using cfdisk to make a DOS partition table entry for /dev/hda1,
then (after exiting fdisk or cfdisk and rebooting Linux so that
the partition table information is valid) you would use the
command "dd if=/dev/zero of=/dev/hda1 bs=512 count=1" to zero
the first 512 bytes of the partition.

BE EXTREMELY CAREFUL if you use the dd command, since a small
typo can make all of the data on your disk useless.

For best results, you should always use an OS-specific
partition table program. For example, you should make DOS
partitions with the DOS FDISK program and Linux partitions with
the Linux fdisk or Linux cfdisk program.


--
com
6-6M21 BCA CompArch Design Engineering
Phone: (425) 342-0007

problem installing gparted

Posted: 14 Sep 2004 08:13 AM PDT

Bjarke Thor Iversen wrote: 

You need the gtkmm-2.4 or greater version package installed
in your system, otherwise the configure command won't create
the Makefile and make install doesn't work.


--

Jose Maria Lopez Hernandez
Director Tecnico de bgSEC
com
bgSEC Seguridad y Consultoria de Sistemas Informaticos
http://www.bgsec.com
ESPAÑA

The only people for me are the mad ones -- the ones who are mad to live,
mad to talk, mad to be saved, desirous of everything at the same time,
the ones who never yawn or say a commonplace thing, but burn, burn, burn
like fabulous yellow Roman candles.
-- Jack Kerouac, "On the Road"

Package Managment

Posted: 13 Sep 2004 02:23 PM PDT

Thx. :)


"Nico Kadel-Garcia" <net> wrote in message
news:com... 
Server