This is true, however it's a temporary measure only, and I have backups.
Once the prices drop again, I'll buy another 1.5TB disk and convert back
to a RAID5.
On Tue, 2012-01-10 at 13:14 +0700, Pandu Poluan wrote:
>
> On Jan 10, 2012 8:48 AM, "Jeff Cranmer"
> wrote:
> >
> >
> > > >
> > > > Me too
On Jan 10, 2012 8:48 AM, "Jeff Cranmer" wrote:
>
>
> > >
> > > Me too.
> > >
> > > mdadm --detail /dev/md0 thinks that /dev/sdc1 is faulty.
> > > I'm not sure whether it's really faulty, or just that my setup for
RAID
> > > is screwed up.
> > >
> > > How do I get rid of an existing /dev/md0?
> >
>
> >
> > Me too.
> >
> > mdadm --detail /dev/md0 thinks that /dev/sdc1 is faulty.
> > I'm not sure whether it's really faulty, or just that my setup for RAID
> > is screwed up.
> >
> > How do I get rid of an existing /dev/md0?
>
> you stop it. Override the superblock with dd.. and lose all data
> >
> >
> >
> Success - I managed to get a raid1 device operating.
> I created the final filesystem by using mkfs.xfs -f /dev/md0, then
> waited for the rebuild to complete before rebooting the system.
>
> It appears to be created successfully. Now I'll try the same sequence
> with sdb and
On Sun, 2012-01-08 at 15:03 -0500, Jeff Cranmer wrote:
> On Sun, 2012-01-08 at 12:31 -0600, Paul Hartman wrote:
> > >
> > > What is going on here?
> >
> > (I didn't read this whole thread, sorry if I'm repeating someone else's
> > advice)
> >
> > kernel autodetection only works on old superblock
On Sun, 2012-01-08 at 12:31 -0600, Paul Hartman wrote:
> >
> > What is going on here?
>
> (I didn't read this whole thread, sorry if I'm repeating someone else's
> advice)
>
> kernel autodetection only works on old superblock version 0.90, you're
> using 1.2. Not a big deal, we use mdadm to do i
On 01/07/2012 11:20 AM, Jeff Cranmer wrote:
> On Sat, 2012-01-07 at 10:11 -0500, Jeff Cranmer wrote:
>
> What am I missing?
have you set the type to linux raid autodetect?
have you tried mdadm --assemble?
>>> mdadm --assemble /dev/md0 didn't make any difference.
>>
> >
> > How do I get rid of an existing /dev/md0?
>
> you stop it. Override the superblock with dd.. and lose all data on the disks.
>
>
> >
> > I'm thinking that I can try creating a RAID1 array using the two
> > allegedly good disks and see if I can make that work.
>
> yeah
>
> >
> > If t
Am Samstag, 7. Januar 2012, 13:27:04 schrieb Jeff Cranmer:
> > > I tried changing the type of each array element in fdisk to fd (linux
> > > raid autodetect.
> > >
> > > The array is still not being recognised at boot, with the same 'cannot
> > > read superblock' error.
> > >
> > > I also tried r
> >
> > I tried changing the type of each array element in fdisk to fd (linux
> > raid autodetect.
> >
> > The array is still not being recognised at boot, with the same 'cannot
> > read superblock' error.
> >
> > I also tried re-running mdadm --create /dev/md0 --level=5
> > --raid-devices=3 /d
Am Samstag, 7. Januar 2012, 12:20:08 schrieb Jeff Cranmer:
> On Sat, 2012-01-07 at 10:11 -0500, Jeff Cranmer wrote:
> > > > > What am I missing?
> > > >
> > > > have you set the type to linux raid autodetect?
> > > >
> > > > have you tried mdadm --assemble?
> > >
> > > mdadm --assemble /dev/md0
On Sat, 2012-01-07 at 10:11 -0500, Jeff Cranmer wrote:
> > > >
> > > > What am I missing?
> > >
> > > have you set the type to linux raid autodetect?
> > >
> > > have you tried mdadm --assemble?
> > >
> > mdadm --assemble /dev/md0 didn't make any difference.
> > Where do I set the type?
> >
>
> > >
> > > What am I missing?
> >
> > have you set the type to linux raid autodetect?
> >
> > have you tried mdadm --assemble?
> >
> mdadm --assemble /dev/md0 didn't make any difference.
> Where do I set the type?
>
after assembling,
results of cat/proc/mdstat
personalities : [linear] [raid
On Fri, 2012-01-06 at 13:36 +0100, Volker Armin Hemmann wrote:
> Am Donnerstag, 5. Januar 2012, 23:44:10 schrieb Jeff Cranmer:
> > On Fri, 2012-01-06 at 02:42 +0100, Volker Armin Hemmann wrote:
> > > in your case
> > >
> > > sfdisk -d /dev/sdb | sfdisk /dev/sdc
> > >
> > > of course ;)
> >
> > O
Am Donnerstag, 5. Januar 2012, 23:44:10 schrieb Jeff Cranmer:
> On Fri, 2012-01-06 at 02:42 +0100, Volker Armin Hemmann wrote:
> > in your case
> >
> > sfdisk -d /dev/sdb | sfdisk /dev/sdc
> >
> > of course ;)
>
> One of the disks had a GPT partition table which I was eventually able
> to get ri
On Fri, 2012-01-06 at 02:42 +0100, Volker Armin Hemmann wrote:
> in your case
>
> sfdisk -d /dev/sdb | sfdisk /dev/sdc
>
> of course ;)
>
One of the disks had a GPT partition table which I was eventually able
to get rid of with gdisk (emerge -av gptfdisk).
I'm close. I had a 2.7TiB RAID5
Am Donnerstag, 5. Januar 2012, 20:13:04 schrieb Jeff Cranmer:
> On Thu, 2012-01-05 at 11:22 +0100, Volker Armin Hemmann wrote:
> > Am Mittwoch, 4. Januar 2012, 22:45:45 schrieb Jeff Cranmer:
> > > On Thu, 2012-01-05 at 04:01 +0100, Volker Armin Hemmann wrote:
> > > > the short one:
> > > >
> > > >
Am Donnerstag, 5. Januar 2012, 20:13:04 schrieb Jeff Cranmer:
> On Thu, 2012-01-05 at 11:22 +0100, Volker Armin Hemmann wrote:
> > Am Mittwoch, 4. Januar 2012, 22:45:45 schrieb Jeff Cranmer:
> > > On Thu, 2012-01-05 at 04:01 +0100, Volker Armin Hemmann wrote:
> > > > the short one:
> > > >
> > > >
On Thu, 2012-01-05 at 11:22 +0100, Volker Armin Hemmann wrote:
> Am Mittwoch, 4. Januar 2012, 22:45:45 schrieb Jeff Cranmer:
> > On Thu, 2012-01-05 at 04:01 +0100, Volker Armin Hemmann wrote:
> > > the short one:
> > >
> > > partition one disk with (c)fdisk. Use sfdisk to transfer the partition
>
Am Mittwoch, 4. Januar 2012, 22:45:45 schrieb Jeff Cranmer:
> On Thu, 2012-01-05 at 04:01 +0100, Volker Armin Hemmann wrote:
> > the short one:
> >
> > partition one disk with (c)fdisk. Use sfdisk to transfer the partition
> > scheme to the other disks.
> >
> > run mdadm --create /dev/md0 level=w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05.01.2012 04:45, Jeff Cranmer wrote:
> On Thu, 2012-01-05 at 04:01 +0100, Volker Armin Hemmann wrote:
>
>> the short one:
>>
>> partition one disk with (c)fdisk. Use sfdisk to transfer the
>> partition scheme to the other disks.
>>
>> run mdadm
On Thu, 2012-01-05 at 04:01 +0100, Volker Armin Hemmann wrote:
> the short one:
>
> partition one disk with (c)fdisk. Use sfdisk to transfer the partition scheme
> to the other disks.
>
> run mdadm --create /dev/md0 level=whatever you want --raid-
> devices=thenumberofdevices /dev/sdXY /dev/sdZ
Am Mittwoch, 4. Januar 2012, 21:28:32 schrieb Jeff Cranmer:
> On Wed, 2012-01-04 at 14:39 +0100, Volker Armin Hemmann wrote:
> > Am Dienstag, 3. Januar 2012, 21:57:18 schrieb Jeff Cranmer:
> > > Hi all,
> > >
> > > I have recently built a new system, running Gentoo on a Sabertooth 990FX
> > > moth
On Wed, 2012-01-04 at 14:39 +0100, Volker Armin Hemmann wrote:
> Am Dienstag, 3. Januar 2012, 21:57:18 schrieb Jeff Cranmer:
> > Hi all,
> >
> > I have recently built a new system, running Gentoo on a Sabertooth 990FX
> > motherboard. The board has a raid controller on which I'm running a
> > 120
I was using a hardware-based 'fakeRAID'. It used to work on my old
OpenSuse install, but that broke and I installed gentoo instead. I
wasn't able to get that to work, and then the motherboard died, so I
built a new system and reused the 3-drive RAID5 array.
>
> While in the first case you see al
On Tue, 2012-01-03 at 22:21 -0600, Paul Hartman wrote:
> On 01/03/2012 08:57 PM, Jeff Cranmer wrote:
> > device-mapper: table: 253:0: raid45: unknown target type
>
> Maybe a dumb question, but is the raid45 module enabled in your kernel
> config?
>
genkernel --dmraid all
Not sure how to check tho
Am Dienstag, 3. Januar 2012, 21:57:18 schrieb Jeff Cranmer:
> Hi all,
>
> I have recently built a new system, running Gentoo on a Sabertooth 990FX
> motherboard. The board has a raid controller on which I'm running a
> 120GB solid state drive for the OS (Raid 0) and a set of three 1.5TB
> drives
On Wednesday 04 January 2012 11:57:18 Jeff Cranmer wrote:
> Hi all,
>
> I have recently built a new system, running Gentoo on a Sabertooth 990FX
> motherboard. The board has a raid controller on which I'm running a
> 120GB solid state drive for the OS (Raid 0) and a set of three 1.5TB
> drives wh
On 01/03/2012 08:57 PM, Jeff Cranmer wrote:
> device-mapper: table: 253:0: raid45: unknown target type
Maybe a dumb question, but is the raid45 module enabled in your kernel
config?
29 matches
Mail list logo