Re: [gentoo-amd64] SATA mdraid woes

[Thomas Rösner]

Peter Humphrey wrote:

A few weeks ago I had a hardware problem, and the upshot is that I now have
a new motherboard, a SuperMicro H8DCE. I now can't boot my Gentoo system.

[...]
All I can think of is that I've made an error in creating the RAID-1 arrays,
but can anyone point me to what that might be?
  


Did you create the partitions with type "Linux RAID Autodetect"?

Regards,
   T.
--
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] SATA mdraid woes

[Boyd Stephen Smith Jr.]

On Thursday 28 December 2006 12:06, "Peter Humphrey" <[EMAIL PROTECTED]> 
wrote about '[gentoo-amd64] SATA mdraid woes':
> Then I'm invited to specify another device, or enter a shell. I use the
> shell to say "ls -l /dev/md2", which shows the block device I expect to
> see, but "cat /dev/md2" returns an empty result. If I do that from the
> installation CD I get a dump of the contents of the md disk, so it seems
> that the node exists but it isn't connected to the array /dev/md2.

I have the same symptoms on my RAID 0, although I have a slightly different 
setup.  I am able to boot because although the RAID 0 is a pv in my single 
vg LVM setup, all the data for my root lv is on other disks, but I haven't 
been able to boot unattended for many months now.

Anyway, I have two suggestions for you.  First, use your favorite fdisk 
tool to confirm all your RAID partitions are set to be RAID autodetect; 
some initrds and particularly the kernel code for RAID detection is very 
picky about this.  [Unfortunately, this is not possible for me, since I 
put whole disks into the RAID array; not partitions.]

If that fails to fix the problem, you might create your own 
initrd/initramfs that includes the full mdadm tool and your mdadm.conf, 
because genkernel (and indeed all "mkinitrd"s I've run under Gentoo) just 
doesn't seem to be able to handle all RAID correctly -- in particular my 
setup has never worked, independent of the options I provide the script.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh


pgppYTkrXU9OR.pgp
Description: PGP signature

Re: [gentoo-amd64] SATA mdraid woes

[Antoine Martin]

On Thu, 2006-12-28 at 18:06 +, Peter Humphrey wrote:
> A few weeks ago I had a hardware problem, and the upshot is that I now have
> a new motherboard, a SuperMicro H8DCE. I now can't boot my Gentoo system.
I had a similar problem resulting from a similar upgrade.
It was because of the order of the drives, which was different in the
BIOS (as seen by grub) and the Linux kernel.
mdadm should not care and it should be able to re-assemble the array no
matter what the partitions are named (sdc|d instead of sda|b in my case)
Some of the arrays were out of sync (I had mounted one of the raid-1
partitions separately for making a backup, etc) - booting using knoppix
(or using a simple recovery ramdisk) allowed me to re-assemble them.
Reboot, done.
It can be useful to keep a ~200MB partition to install something small
like Slackware/Busybox for emergencies, this would allow you to boot on
a single drive and see what the kernel and mdadm tools make of your
array.
Hope this helps!

Antoine

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] SATA mdraid woes

[Peter Humphrey]

A few weeks ago I had a hardware problem, and the upshot is that I now have
a new motherboard, a SuperMicro H8DCE. I now can't boot my Gentoo system.

This box has two IDE drives on the primary IDE channel (and two optical
drives on the secondary), and I have two small ext2 partitions on /dev/hda1
to boot Linux. Windows lives in hda3, and I'm using it now to write Webmail.
Grub lives in /dev/hda1, pointed to by BootMagic in the MBR. Hdb is mostly
to keep backups of other things, being 200 GB.

Gentoo lives on two SATA drives, which the BIOS shows me as ide3 master and
ide4 master. I have a small boot partition on each of them, rarely used,
then the rest is given over to several RAID-1 partitions. E.g. the root
partition is on /dev/md2, which is assembled from /dev/sd[ab]5.

When I first got the box back I tried booting with no changes. Blank screen
and no keyboard as soon as I hit the default choice in the grub screen. That
was ok as several hardware changes have occurred. So I compiled a new kernel
to use the new graphics card (PCI Express instead of AGP) and motherboard
chipset (nForce Pro 2200/2050 instead of VIA) and network card (forcedeth
instead of tg3). Still the same, so I backed up all the data, deleted the md
and sd partitions and recreated them all afresh, then restored all the
backed-up data.

Now I get a can't-find-root error. I've experimented with lots of kernel
parameters, both when compiling and on the command line, but I can't get the
system to boot. Here's a selection of diagnostics, which I hope I've
transcribed aright:

--
ACPI: PCI Interrupt Link [LTID] enabled at IRQ22
ata1: SATA max UDMA/133 cmd 0xC800 ctl 0xC402 bmdma 0xB800 irq22
ata1: SATA max UDMA/133 cmd 0xC800 ctl 0xBC02 bmdma 0xB800 irq22
[that's the ordinary IDE subsystem]
...
scsi2: sata_nv
[so the nForce SATA functionality is compiled in ok]
ata1: SATA link up 1.5Gbps (SStatus 113 SControl 300)
ata1.00: ATA-7, max UDMA/133, 398297088 sectors: LBA48 NCQ (depth 0/32)
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/133
scsi3: sata_nv
ata2: SATA link up 1.5Gbps (SStatus 113 SControl 300)
ata2.00: ATA-7, max UDMA/133, 398297088 sectors: LBA48 NCQ (depth 0/32)
ata2.00: ata2: dev 0 multi count 16
ata2.00: configured for UDMA/133
scsi 2:0:0:0 Direct-Access ATA Maxtor 6L200M0 BANC PQ: ANSI: 5
scsi 3:0:0:0 Direct-Access ATA Maxtor 6L200M0 BANC PQ: ANSI: 5
[that's the two SATA drives]
ACPI: PCI Interrupt Link [LTIE] enabled at IRQ 21
ACPI: PCI Interrupt :00:08.0[A] -> Link [LTIE] -> GSI 21 (level, low) ->
IRQ21
...
(ata3 to ata8 links down)
...
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
[so I've got mdraid compiled in]
...
Activating mdev
Detected real_root as a md device. Setting up the device node
Determining root device...
Mounting root...
...
The root block device is unspecified or not detected.
--
[end of transcript]
Then I'm invited to specify another device, or enter a shell. I use the
shell to say "ls -l /dev/md2", which shows the block device I expect to see,
but "cat /dev/md2" returns an empty result. If I do that from the
installation CD I get a dump of the contents of the md disk, so it seems
that the node exists but it isn't connected to the array /dev/md2.

All I can think of is that I've made an error in creating the RAID-1 arrays,
but can anyone point me to what that might be?

--
Rgds
Peter.



Message sent using UebiMiau 2.7.2

-- 
gentoo-amd64@gentoo.org mailing list