>
>
> You create the partitions in the installer, setting the partition use to
> 'raid'. You then select configure raid, and setup all your raid devices.
> Then when you return to the partition tool you will see the new raid
> md devices, which you then set to 'use as LVM volume', then you go to
>
On Wed, Mar 11, 2009 at 09:53:14AM +0100, Francesco Pietra wrote:
> To my dismay, I tried (repeatedly) unsuccessfully to implement the
> scheme below on old Tyan S2895 with two dual-opteron and two new
> Maxtor 250GB, before moving to the new machine. With the recent amd
> installer, I tried to set
On Fri, Mar 13, 2009 at 11:45:37AM +0100, Goswin von Brederlow wrote:
> Alex Samad writes:
>
> > On Wed, Mar 11, 2009 at 11:02:31AM +0100, Goswin von Brederlow wrote:
> >> Alex Samad writes:
> >>
> >> > On Wed, Mar 11, 2009 at 09:53:14AM +0100, Francesco Pietra wrote:
[snip]
> > I would still
Alex Samad writes:
> On Wed, Mar 11, 2009 at 11:02:31AM +0100, Goswin von Brederlow wrote:
>> Alex Samad writes:
>>
>> > On Wed, Mar 11, 2009 at 09:53:14AM +0100, Francesco Pietra wrote:
>> >> To my dismay, I tried (repeatedly) unsuccessfully to implement the
>> >> scheme below on old Tyan S289
On Wed, Mar 11, 2009 at 11:02:31AM +0100, Goswin von Brederlow wrote:
> Alex Samad writes:
>
> > On Wed, Mar 11, 2009 at 09:53:14AM +0100, Francesco Pietra wrote:
> >> To my dismay, I tried (repeatedly) unsuccessfully to implement the
> >> scheme below on old Tyan S2895 with two dual-opteron and
Alex Samad writes:
> On Wed, Mar 11, 2009 at 09:53:14AM +0100, Francesco Pietra wrote:
>> To my dismay, I tried (repeatedly) unsuccessfully to implement the
>> scheme below on old Tyan S2895 with two dual-opteron and two new
>> Maxtor 250GB, before moving to the new machine. With the recent amd
>
On Wed, Mar 11, 2009 at 09:53:14AM +0100, Francesco Pietra wrote:
> To my dismay, I tried (repeatedly) unsuccessfully to implement the
> scheme below on old Tyan S2895 with two dual-opteron and two new
> Maxtor 250GB, before moving to the new machine. With the recent amd
> installer, I tried to set
To my dismay, I tried (repeatedly) unsuccessfully to implement the
scheme below on old Tyan S2895 with two dual-opteron and two new
Maxtor 250GB, before moving to the new machine. With the recent amd
installer, I tried to set up (manually) the two partitions on both
disks to set up raid1.
First, I
lsore...@csclub.uwaterloo.ca (Lennart Sorensen) writes:
> On Tue, Mar 03, 2009 at 10:59:50PM +0100, Francesco Pietra wrote:
>> I understand that the double recommendation is fine. Though, I am
>> pressed by answering the referees about a submitted paper as they
>> requested additional computation.
On Tue, Mar 03, 2009 at 10:59:50PM +0100, Francesco Pietra wrote:
> I understand that the double recommendation is fine. Though, I am
> pressed by answering the referees about a submitted paper as they
> requested additional computation. That was going on until the host
> suspended access to sda. A
On Tue, Mar 3, 2009 at 9:52 PM, Alex Samad wrote:
> On Tue, Mar 03, 2009 at 12:26:27PM +0100, Goswin von Brederlow wrote:
>> Francesco Pietra writes:
> [snip]
>
>>
>> That is a lot of raids. Have you ever thought about using LVM? The
>> different raid1 will mess up each others assumption about th
On Tue, Mar 03, 2009 at 12:26:27PM +0100, Goswin von Brederlow wrote:
> Francesco Pietra writes:
[snip]
>
> That is a lot of raids. Have you ever thought about using LVM? The
> different raid1 will mess up each others assumption about the head
> positioning of the component devices. On read the
2:36.600 READ DMA
> c8 00 08 37 9d 9b 4c 00 00:52:36.600 READ DMA
>
> SMART Self-test log structure revision number 1
> No self-tests have been logged. [To run self-tests, use: smartctl -t]
> ===
>
> I.e., I am still uncertain if sda has to be replaced with a new disk,
> or the errors reported were temporary and have been remo
Re: raid1 issue, somewhat related to recent "debian on big machines"
To: Ron Johnson
On Tue, Mar 3, 2009 at 10:08 AM, Ron Johnson wrote:
> On 03/03/2009 02:53 AM, Francesco Pietra wrote:
>>
>> lupus in fabula as a follow up of my short intervention on raid1 with
>> m
Francesco Pietra writes:
The important bit is:
> Disk failure on sda1, disabling device
So one of your disks failed. The kernel marked it as such and
continious on the other disk alone. This is invisible to the
application (apart from the short hickup) and no data is corrupted or
lost. That is
On 03/03/2009 02:53 AM, Francesco Pietra wrote:
lupus in fabula as a follow up of my short intervention on raid1 with
my machine to the thread "Debian on big systems".
System: supermicro H8QC8 m.board, two WD Raptor SATA 150GB, Debian
amd64 lenny, raid1
While running an electronic molecular cal
lupus in fabula as a follow up of my short intervention on raid1 with
my machine to the thread "Debian on big systems".
System: supermicro H8QC8 m.board, two WD Raptor SATA 150GB, Debian
amd64 lenny, raid1
While running an electronic molecular calculation - estimated to four
days time - I noticed
17 matches
Mail list logo
