x86_64 x86_64
x86_64 GNU/Linux
-([EMAIL PROTECTED])-(/)- #
Thanks,
David M. Strang
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
/Patrick wrote:
pretty sure smartctl -d ata -a /dev/sdwhatever will tell you the
serial number. (Hopefully the kernel is new enough that it supports
SATA/smart, otherwise you need a kernel patch which won't be any
better...)
Yep... 2.6.15 or better... I need the magical patch =\.
Any other
proceed any further... what are my options? Do I have any options?
I could run a fsck... but I held off fearing it could just make things
worse.
Thanks,
David M. Strang
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More
.
Any suggestions? I don't have any 'non-raid' bootable devices.
-- David M. Strang
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
hasn't started.
Help!
-- David M. Strang
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
!)
Is that feasible with an initrd? Since I'm not intending to have any
standard partitions.
-- David M. Strang
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sunday 27 November 2005 16:18:23, Raphaël Rigo wrote
Hi,
here is a patch that fixes the problem described by David M. Stra.
The problem is that the array is first initialized with SET_ARRAY_INFO
without
any specific parameter and the md driver uses the 0.90 behaviour by
default.
So we
rather
learn (use) it.
-- David M. Strang
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
EVMS in the past... I was trying to grow my raid5. It
looks like it would have done the job, except it was going to take a week...
I opted to go the backup, recreate, and restore route.
-- David M. Strang
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body
PROTECTED])-(~)- # mdadm -Q /dev/sdb1
/dev/sdb1: is not an md array
/dev/sdb1: device 1 in 2 device unknown raid1 array. Use mdadm --examine
for more detail.
I'm really confused; mdadm seems to recognize it and load it fine... why
can't I get the kernel to load it?
-- David M. Strang
On Saturday 26 November 2005 12:16:14, Guillaume Filion wrote:
Le 05-11-26, à 11:18, David M. Strang a écrit :
md: invalid raid superblock magic on sdb1
Did you include the md and raid1 modules in mkinirtd.conf?
I'll admit that while I have my root on a raid1 device, I'm a bit confused
On Saturday 26 November 2005 11:14:46, David M. Strang wrote:
sdb1 is a 400GB partition -- it is type FD.
Disk /dev/sdb: 400.0 GB, 400088457216 bytes
2 heads, 4 sectors/track, 97677846 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Device Boot Start End Blocks Id
On Saturday 26 November 2005 14:03:35, David M. Strang wrote:
On Saturday 26 November 2005 11:14:46, David M. Strang wrote:
sdb1 is a 400GB partition -- it is type FD.
Disk /dev/sdb: 400.0 GB, 400088457216 bytes
2 heads, 4 sectors/track, 97677846 cylinders
Units = cylinders of 8 * 512
NeilBrown wrote:
Hmm.. obviously hot-add isn't enough to trigger the rebuild in that
kernel.
I can attest to this; as I workaround I've been using:
mdadm --readonly /dev/mdX
mdadm --readwrite /dev/mdX
That will trigger a rebuild.
-- David
-
To unsubscribe from this list: send the line
Mr. James W. Laferriere wrote:
Hello David , Thank you for the idea . But ...
[EMAIL PROTECTED]:~ # mdadm --readonly /dev/md_d0
mdadm: failed to set readonly for /dev/md_d0: Device or resource busy
James --
umount /dev/md_d0 first; you can remount it right after you re-enable
writes.
Farkas Levente wrote:
this is mdadm 1.12, just another site note there is no rpm for version
2.0:-(
No. I seem to remember some odd compile issue with making the RPM
and thinking I don't care. Maybe I should care a bit more
would be useful.
Not trying to be rude; but the install
Neil Brown wrote:
On Friday September 2, [EMAIL PROTECTED] wrote:
Neil Brown wrote:
On Friday September 2, [EMAIL PROTECTED] wrote:
Can you run that with '-v' for me?
mdadm: looking for devices for /dev/md0
mdadm: /dev/sda is identified as a member of /dev/md0, slot 0.
Neil Brown wrote:
On Friday September 2, [EMAIL PROTECTED] wrote:
Neil Brown wrote:
On Friday September 2, [EMAIL PROTECTED] wrote:
Does this mean I'm going to loose all my data?
No.
At least, you shouldn't, and doing the --create won't make anything
worse.
So do the
This is somewhat of a crosspost from my thread yesterday; but I think it
deserves it's own thread atm. Some time ago, I had a device fail -- with the
help of Neil, Tyler others on the mailing list; a few patches to mdadm --
I was able to recover. Using mdadm --remove mdadm --add, I was able
; and see what happens.
-- David M. Strang
- Original Message -
From: Forrest Taylor
To: David M. Strang
Cc: Linux RAID
Sent: Wednesday, August 31, 2005 3:28 PM
Subject: Re: raid5: Disk failure on sdm, disabling device
On Wed, 2005-08-31 at 13:26, David M. Strang wrote:
Okay, my
. Strang
Cc: linux-raid@vger.kernel.org
Sent: Wednesday, August 31, 2005 3:29 PM
Subject: Re: raid5: Disk failure on sdm, disabling device
David M. Strang wrote:
Okay, my array is degraded -- and the device /dev/sdm is disabled.
Short of a reboot, is there a way to re-enable the device? It's already
-- David M. Strang
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 2005-08-31 at 14:45, David M. Strang wrote:
On Wed, 2005-08-31 at 14:39, Forrest Taylor wrote:
If you are running 2.4 kernel, did you try running rescan-scsi-bus.sh
(http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh)?
uname -ar
Linux abyss 2.6.11.12 #2 SMP Thu Jul 21 07:49:40 UTC
On Wed, 2005-08-31 at 14:55, Forrest Taylor wrote:
On Wed, 2005-08-31 at 14:45, David M. Strang wrote:
On Wed, 2005-08-31 at 14:39, Forrest Taylor wrote:
If you are running 2.4 kernel, did you try running rescan-scsi-bus.sh
(http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh)?
uname -ar
Is there something a little deeper to this error message?
Aug 31 04:48:15 abyss kernel: scsi2 (12:0): rejecting I/O to offline
device
Aug 31 04:48:15 abyss kernel: raid5: Disk failure on sdm, disabling
device.
This error would make me think that the disk is bad. Have you tested
the disk, or
EMVS supports this --
http://evms.sourceforge.net
However, in my experience -- it's really slow; and it was faster for me to
backup the data to tape; recreate the raid and restore.
It may be faster now; that was under release v2.5.1
David M. Strang
- Original Message -
From
160 26 active sync
/dev/scsi/host2/bus0/target26/lun0/disc
Is it supposed to stay with number 26 as removed forever? Does number 28
ever jump back up to that spot? I shouldn't have to hotadd and allow it to
resync everytime I re-assemble the raid should I?
-- David M. Strang
-0
superblocks.
Jul 17 20:22:05 abyss kernel: md0: HOT_ADD may only be used with version-0
superblocks.
Still no go with -a or -add.
-- David M. Strang
- Original Message -
From: Tyler
To: David M. Strang
Cc: Neil Brown ; linux-raid@vger.kernel.org
Sent: Sunday, July 17, 2005 8:05
.
Breakpoint 1, Manage_subdevs (devname=0xbfe75e5f /dev/md0, fd=7,
devlist=0x8067018) at Manage.c:174
174 void *dsuper = NULL;
(gdb) c
Continuing.
mdadm: hot add failed for /dev/sdaa: Invalid argument
Program exited with code 01.
(gdb)
-- David M. Strang
- Original Message
return 1;
(gdb) n
307 }
(gdb) n
main (argc=5, argv=0xbfe0cb14) at mdadm.c:810
810 if (!rv readonly 0)
(gdb) n
812 if (!rv runstop)
(gdb) n
1072exit(rv);
(gdb) n
Program exited with code 01.
-- David M. Strang
= -1208577344, state
= -1208582100, active_disks = -1208448832, working_disks = -1079477752,
failed_disks = -1209047199, spare_disks = 5,
layout = -1079477052, chunk_size = 134623392}
-- David M. Strang
- Original Message -
From: David M. Strang
To: unlisted-recipients: ; no To-header on input
,
degraded.
What do I do next? What I wanted to do was to put /dev/sdaa back in as
device 26, but now it's device 28 - and flagged as spare. How do I make it
active in the array again?
-- David M. Strang
- Original Message -
From: Neil Brown
To: David M. Strang
Cc: linux-raid
. Strang
- Original Message -
From: Neil Brown
To: David M. Strang
Cc: linux-raid@vger.kernel.org
Sent: Sunday, July 17, 2005 10:15 PM
Subject: Re: Raid5 Failure
On Sunday July 17, [EMAIL PROTECTED] wrote:
Neil --
That worked, the device has been added to the array. Now, I think the next
are all marked clean;
while sdn-sdab are marked active.
What can I do to resolve this issue? Any assistance would be greatly
appreciated.
-- David M. Strang
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info
sync /dev/evms/.nodes/sdz
26 65 160 26 active sync /dev/evms/.nodes/sdaa
27 65 176 27 active sync /dev/evms/.nodes/sdab
-- David M. Strang
- Original Message -
From: Neil Brown
To: David M. Strang
Cc: linux-raid@vger.kernel.org
Sent
35 matches
Mail list logo
