On Thu, Feb 5, 2009 at 11:22 PM, Lukasz Szybalski wrote:
> On Thu, Feb 5, 2009 at 12:45 PM, martin f krafft wrote:
>> also sprach Lukasz Szybalski [2009.02.05.0731 +0100]:
>>> Both drives are fairly new...Would the drive be defective since day1?
>>>
>>> Was the error log that I am getting now av
On Thu, Feb 5, 2009 at 12:45 PM, martin f krafft wrote:
> also sprach Lukasz Szybalski [2009.02.05.0731 +0100]:
>> Both drives are fairly new...Would the drive be defective since day1?
>>
>> Was the error log that I am getting now available in previous version
>> of the kernel?
>
> Yes.
>
> Eithe
also sprach Lukasz Szybalski [2009.02.05.0731 +0100]:
> Both drives are fairly new...Would the drive be defective since day1?
>
> Was the error log that I am getting now available in previous version
> of the kernel?
Yes.
Either the drives are faulty or the controller.
--
.''`. martin f. k
Both drives are fairly new...Would the drive be defective since day1?
Was the error log that I am getting now available in previous version
of the kernel?
Thanks,
Lucas
On Wed, Feb 4, 2009 at 3:12 AM, martin f krafft wrote:
> also sprach Lukasz Szybalski [2009.02.04.0655 +0100]:
>> 3. I then r
also sprach Lukasz Szybalski [2009.02.04.0655 +0100]:
> 3. I then readded my /dev/hda2 to /dev/md2 and a lot of errors
> started to appear in syslog...
[...]
> Feb 3 23:49:09 hplinux kernel: hdc: dma_intr: status=0x51 {
> DriveReady SeekComplete Error }
Looks like your /dev/hdc is dying. I h
On Sun, Jan 4, 2009 at 9:26 PM, Lukasz Szybalski wrote:
> On Sun, Jan 4, 2009 at 8:55 AM, Moritz Muehlenhoff wrote:
>> fOn Wed, Oct 17, 2007 at 04:16:39PM -0500, Lukasz Szybalski wrote:
>>> On 10/15/07, Neil Brown wrote:
>>> >
>>> > As you say, the devices are exactly the same size, thanks.
>>>
On Sun, Jan 4, 2009 at 8:55 AM, Moritz Muehlenhoff wrote:
> fOn Wed, Oct 17, 2007 at 04:16:39PM -0500, Lukasz Szybalski wrote:
>> On 10/15/07, Neil Brown wrote:
>> >
>> > As you say, the devices are exactly the same size, thanks.
>> >
>> > On Monday October 15, szybal...@gmail.com wrote:
>> > >
>
fOn Wed, Oct 17, 2007 at 04:16:39PM -0500, Lukasz Szybalski wrote:
> On 10/15/07, Neil Brown wrote:
> >
> > As you say, the devices are exactly the same size, thanks.
> >
> > On Monday October 15, szybal...@gmail.com wrote:
> > >
> > > how do I undo? mdadm /dev/md2 -f /dev/hda2
> > > So I could t
On 10/15/07, Neil Brown <[EMAIL PROTECTED]> wrote:
>
> As you say, the devices are exactly the same size, thanks.
>
> On Monday October 15, [EMAIL PROTECTED] wrote:
> >
> > how do I undo? mdadm /dev/md2 -f /dev/hda2
> > So I could try the sync in init 1
> > Lucas
>
> Well, you could:
> mdadm /de
also sprach Neil Brown <[EMAIL PROTECTED]> [2007.10.16.0043 +0100]:
> I was hoping for
>cat /proc/partitions
> and maybe even
>fdisk -l /dev/hda /dev/hdb
In the future, consider asking for
/usr/share/bug/mdadm/script 3>&1
which should have *all* the output you could ever want. :)
In
As you say, the devices are exactly the same size, thanks.
On Monday October 15, [EMAIL PROTECTED] wrote:
>
> how do I undo? mdadm /dev/md2 -f /dev/hda2
> So I could try the sync in init 1
> Lucas
Well, you could:
mdadm /dev/md2 -f /dev/hda2
mdadm /dev/md2 -r /dev/hda2
then when you are r
On Monday October 15, [EMAIL PROTECTED] wrote:
>
> seems as the size is the same?
"seems".
I was hoping for
cat /proc/partitions
and maybe even
fdisk -l /dev/hda /dev/hdb
I should have been more specific.
NeilBrown
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsu
On 10/15/07, Neil Brown <[EMAIL PROTECTED]> wrote:
> On Monday October 15, [EMAIL PROTECTED] wrote:
> >
> > seems as the size is the same?
>
> "seems".
> I was hoping for
>cat /proc/partitions
hplinux:/home/lucas# cat /proc/partitions
major minor #blocks name
3 0 312571224 hda
3
On 10/12/07, Neil Brown <[EMAIL PROTECTED]> wrote:
> On Friday October 12, [EMAIL PROTECTED] wrote:
> > yes I have.
> > Then I tried booting in knoppix to see if maybe there are hdd problems
> > so I run e2fsck on both drives to see if there are any issues.
> > reboot and it still does the same thi
On 10/12/07, Neil Brown <[EMAIL PROTECTED]> wrote:
> On Friday October 12, [EMAIL PROTECTED] wrote:
> > yes I have.
> > Then I tried booting in knoppix to see if maybe there are hdd problems
> > so I run e2fsck on both drives to see if there are any issues.
> > reboot and it still does the same thi
On Friday October 12, [EMAIL PROTECTED] wrote:
> yes I have.
> Then I tried booting in knoppix to see if maybe there are hdd problems
> so I run e2fsck on both drives to see if there are any issues.
> reboot and it still does the same thing.
Ok, it must be caused by some persistent state.
Could yo
On 10/11/07, Neil Brown <[EMAIL PROTECTED]> wrote:
> On Thursday October 11, [EMAIL PROTECTED] wrote:
> > Package: mdadm
> > Version: 2.5.6-9
> > Severity: normal
> >
> > Hello,
> > I am trying to setup raid1 on my pc.
> > I have 2 identical drives. 270+gb. each with 3 partitions.
> > 30gb hdb1 -
On Thursday October 11, [EMAIL PROTECTED] wrote:
> Package: mdadm
> Version: 2.5.6-9
> Severity: normal
>
> Hello,
> I am trying to setup raid1 on my pc.
> I have 2 identical drives. 270+gb. each with 3 partitions.
> 30gb hdb1 -> md0
> 250gb hdb2 ->md2
> 4gb swap hdb5 ->md4
>
> Initially my
Package: mdadm
Version: 2.5.6-9
Severity: normal
Hello,
I am trying to setup raid1 on my pc.
I have 2 identical drives. 270+gb. each with 3 partitions.
30gb hdb1 -> md0
250gb hdb2 ->md2
4gb swap hdb5 ->md4
Initially my raid had only one drive. I have added the second one with
mdadm --add /
19 matches
Mail list logo