also sprach martin f krafft <[EMAIL PROTECTED]> [2007.09.30.1234 +0100]:
> Oh well, I think this is an amd64-specific problem. Daniel, are you
> around today to debug this? Or anyone else with amd64? I don't have
> an amd64 machine around to test this for another three weeks, so I'd
> really apprec
Neil Brown wrote:
> Reshape won't restart while the array is auto-read-only.
> You can start it simply by mounting the filesystem, or with
> mdadm /dev/md0 --readwrite
>
Neil,
Thank you very much for your prompt response. I would have never figured
it out myself, with my incorrect assumption
On Tue, Dec 19, 2006 at 10:47:29PM -0500, Bill Davidsen wrote:
> Louis-David Mitterrand wrote:
> >On Thu, Nov 09, 2006 at 03:27:31PM +0100, Louis-David Mitterrand wrote:
> >
> >>I forgot to add that to help us solve this we are ready to hire a paid
> >>consultant please contact me by mail or pho
Louis-David Mitterrand wrote:
On Thu, Nov 09, 2006 at 03:27:31PM +0100, Louis-David Mitterrand wrote:
I forgot to add that to help us solve this we are ready to hire a paid
consultant please contact me by mail or phone at +33.1.46.47.21.30
Update: we eventually succeded in reassembling
On Thu, Nov 09, 2006 at 03:27:31PM +0100, Louis-David Mitterrand wrote:
> I forgot to add that to help us solve this we are ready to hire a paid
> consultant please contact me by mail or phone at +33.1.46.47.21.30
Update: we eventually succeded in reassembling the partition, with two
missing dis
Bobby S wrote:
>
> Hello, I had a software raid 5 array of 4 disks drop two last night and
> was curious of what help I may find.
>
> I have 4 250GB maxtor drives in software raid 5 array and I seem to get
> the dma_timer_expiry error comming up every few weeks and I was curious as
> to how I m
Array is online, degraded for the moment but I can access the file systems for
backups.
I passed -A --force to mdadm, seems that did the trick.
What puzzles me still is that I had a degraded array for the third time now
and never could tell why it happened in the first place.
This time the mac
Molle Bestefich gmail.com> writes:
> My best guess is that it's OK and you won't loose data if you run
> --zero-superblock on /dev/sd[abcd] and then create an array on
> /dev/sd[abcd]1, but I do find it odd that it suddenly can't find
> superblocks on /dev/sd[abcd]1.
OK, I tried several things a
Neil
Well I did warn you that I was an idiot... :-) I have been attempting to
work out exactly what I did and what happened. All I have learned is
that I need to keep better notes
Yes, the 21 mounts is a fsck, nothing to do with raid. However it is
still noteworthy that this took several hours t
On 24 May 2006, Florian Dazinger uttered the following:
> Neil Brown wrote:
>> Presumably you have a 'DEVICE' line in mdadm.conf too? What is it.
>> My first guess is that it isn't listing /dev/sdd? somehow.
>> Otherwise, can you add a '-v' to the mdadm command that assembles the
>> array, and cap
Neil Brown wrote:
Presumably you have a 'DEVICE' line in mdadm.conf too? What is it.
My first guess is that it isn't listing /dev/sdd? somehow.
Otherwise, can you add a '-v' to the mdadm command that assembles the
array, and capture the output. That might be helpful.
NeilBrown
stupid me! I h
Mystery solved: had to probe another module.
Wait, wait, I can defend myself :)
What led me to believe the controller was autoprobed during boot is that mdadm
complained about *sdd*, but not about sd[abc], hence I assumed [abc] were all
fine.
Plus, I didn't have to probe the module man
Thanks for all the help. I am now up and running again and have been
stable for over a day. I will now install my new drive and add it to
give me an array of three drives.
I'll also learn more about Raid, mdadm and smartd so that I am better
prepared next time.
Thanks again
Nigel
Neil Brown wrot
On Tue, 6 Dec 2005, Michael Stumpf wrote:
Sure it's a FAQ. It's probably even documented. And, I know it, but it
still surprised me. Such is life:
2/3 sticks of perfectly good ECC ram in an old server class p3 board
apparently have gone bad. Result? Random lockups/reboots with nothing in
Sure it's a FAQ. It's probably even documented. And, I know it, but it
still surprised me. Such is life:
2/3 sticks of perfectly good ECC ram in an old server class p3 board
apparently have gone bad. Result? Random lockups/reboots with nothing
in the system logs to even lend a clue.
Mem
Hi all,
I finally solved my problem by booting with knoppix and recreating the
raid from scratch.
From memory, the process might have looked like that:
boot with knoppix as single user
mdadm --zero-superblock /dev/hdg2
mdadm --zero-superblock /dev/hdg
mdadm --zero-superblock /dev/hdc2
mdadm
On Sun, 7 Aug 2005, Trevor Cordes wrote:
> Any array that is a superset of other arrays (a multilevel array) must
> set to non-autodetect. Use fdisk to change the parition type to 83
> (standard linux), NOT "fd" (linux raid autodetect).
you know i'd be worried setting it to 0x83 will cause troub
How to have raid-based subcomponents autorun before a superset raid array
(ie: RAID6+0 or RAID1+0/RAID10) in a multilevel/multilayer array setup:
(It would be nice if the autodetect during boot would be intelligent
about starting subarrays first, but it currently is not. It would not
be that hard
n I created a RAID1 of this disks and tried the test again... Same
| error!
|
| Maybe it's an problem with ext3 running on RAID1, but it's worked under
| 2.4.25!
Hi everybody!
I finally solved my problem. After some more test, I was finally able to
reproduce the
problem under Linux 2.4 to
On June 1, Neil Brown e-mailed me in response to the file output he asked me for:
>mdstat:
> Personalities : [3 raid1]
> read_ahead not set
> md0 : inactive
> md1 : inactive
> md2 : inactive
> md3 : inactive
> This indicates that you haven't patched your kernel with the "raid
>
Hello Neil,
thank you for your help - devfs=nomount fixed my problem.
with regards,
Oliver
> On Sunday January 7, [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > on my machine (x86) I've debian2.2r2 with kernel 2.2.16 + raidtools 0.9
> > running. No problems. Yesterday I installed kern 2.4.0 with the
21 matches
Mail list logo
