RAID5 array showing as degraded after motherboard replacement

RAID5 array showing as degraded after motherboard replacement

[James Lee]

[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]

Hi there,

I'm running a 5-drive software RAID5 array across two controllers.
The motherboard in that PC recently died - I sent the board back for
RMA.  When I refitted the motherboard, connected up all the drives,
and booted up I found that the array was being reported as degraded
(though all the data on it is intact).  I have 4 drives on the on
board controller and 1 drive on an XFX Revo 64 SATA controller card.
The drive which is being reported as not being in the array is the one
connected to the XFX controller.

The OS can see that drive fine, and "mdadm --examine" on that drive
shows that it is part of the array and that there are 5 active devices
in the array.  Doing "mdadm --examine" on one of the other four drives
shows that the array has 4 active drives and one failed.  "mdadm
--detail" for the array also shows 4 active and one failed.

Now I haven't lost any data here and I know I can just force a resync
of the array which is fine.  However I'm concerned about how this has
happened.  One worry is that the XFX SATA controller is doing
something funny to the drive.  I've noticed that it's BIOS has
defaulted to RAID0 mode (even though there's only one drive on it) - I
can't see how this would cause any particular problems here though.  I
guess it's possible that some data on the drive got corrupted when the
motherboard failed...

Any ideas what could cause mdadm to report as I've described above
(I've attached the output of these three commands)?  I'm running
Ubuntu Edgy, which is a 2.17.x kernel, and mdadm 2.4.1.  In case it's
relevant here, I created the array using EVMS...

Thanks,
James

[-- Attachment #2: mdadm_output.txt --]
[-- Type: text/plain, Size: 3346 bytes --]

james@james-server:~$ sudo mdadm --examine /dev/hde1
Password:
/dev/hde1:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 33d5338b:d2d6baf0:424498ad:47d05087
  Creation Time : Sun Jan 15 16:47:51 2006
     Raid Level : raid5
    Device Size : 312496128 (298.02 GiB 320.00 GB)
     Array Size : 1249984512 (1192.08 GiB 1279.98 GB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 0

    Update Time : Sat Nov  4 16:29:06 2006
          State : clean
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0
       Checksum : d628e17e - correct
         Events : 0.4232131

         Layout : left-asymmetric
     Chunk Size : 256K

      Number   Major   Minor   RaidDevice State
this     4     254        6        4      active sync

   0     0     254        2        0      active sync
   1     1     254        3        1      active sync
   2     2     254        4        2      active sync
   3     3     254        5        3      active sync
   4     4     254        6        4      active sync
james@james-server:~$ 
james@james-server:~$ 
james@james-server:~$ 
james@james-server:~$ sudo mdadm --examine /dev/sda1
/dev/sda1:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 33d5338b:d2d6baf0:424498ad:47d05087
  Creation Time : Sun Jan 15 16:47:51 2006
     Raid Level : raid5
    Device Size : 312496128 (298.02 GiB 320.00 GB)
     Array Size : 1249984512 (1192.08 GiB 1279.98 GB)
   Raid Devices : 5
  Total Devices : 4
Preferred Minor : 0

    Update Time : Sun Nov  5 11:56:29 2006
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 1
  Spare Devices : 0
       Checksum : d629ee25 - correct
         Events : 0.4232204

         Layout : left-asymmetric
     Chunk Size : 256K

      Number   Major   Minor   RaidDevice State
this     1       8        1        1      active sync   /dev/sda1

   0     0       8       17        0      active sync   /dev/sdb1
   1     1       8        1        1      active sync   /dev/sda1
   2     2       8       33        2      active sync   /dev/sdc1
   3     3       8       49        3      active sync   /dev/sdd1
   4     4       0        0        4      faulty removed
james@james-server:~$ 
james@james-server:~$ 
james@james-server:~$ 
james@james-server:~$ sudo mdadm --detail /dev/md0 
/dev/md0:
        Version : 00.90.03
  Creation Time : Sun Jan 15 16:47:51 2006
     Raid Level : raid5
     Array Size : 1249984512 (1192.08 GiB 1279.98 GB)
    Device Size : 312496128 (298.02 GiB 320.00 GB)
   Raid Devices : 5
  Total Devices : 4
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Sun Nov  5 11:56:29 2006
          State : clean, degraded
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-asymmetric
     Chunk Size : 256K

           UUID : 33d5338b:d2d6baf0:424498ad:47d05087
         Events : 0.4232204

    Number   Major   Minor   RaidDevice State
       0       8       17        0      active sync   /dev/sdb1
       1       8        1        1      active sync   /dev/sda1
       2       8       33        2      active sync   /dev/sdc1
       3       8       49        3      active sync   /dev/sdd1
       4       0        0        4      removed
james@james-server:~$ 

Re: RAID5 array showing as degraded after motherboard replacement

[dean gaudet]

On Sun, 5 Nov 2006, James Lee wrote:

> Hi there,
> 
> I'm running a 5-drive software RAID5 array across two controllers.
> The motherboard in that PC recently died - I sent the board back for
> RMA.  When I refitted the motherboard, connected up all the drives,
> and booted up I found that the array was being reported as degraded
> (though all the data on it is intact).  I have 4 drives on the on
> board controller and 1 drive on an XFX Revo 64 SATA controller card.
> The drive which is being reported as not being in the array is the one
> connected to the XFX controller.
> 
> The OS can see that drive fine, and "mdadm --examine" on that drive
> shows that it is part of the array and that there are 5 active devices
> in the array.  Doing "mdadm --examine" on one of the other four drives
> shows that the array has 4 active drives and one failed.  "mdadm
> --detail" for the array also shows 4 active and one failed.

that means the array was assembled without the 5th disk and is currently 
degraded.


> Now I haven't lost any data here and I know I can just force a resync
> of the array which is fine.  However I'm concerned about how this has
> happened.  One worry is that the XFX SATA controller is doing
> something funny to the drive.  I've noticed that it's BIOS has
> defaulted to RAID0 mode (even though there's only one drive on it) - I
> can't see how this would cause any particular problems here though.  I
> guess it's possible that some data on the drive got corrupted when the
> motherboard failed...

no it's more likely the devices were renamed or the 5th device didn't come 
up before the array was assembled.

it's possible that a different bios setting lead to the device using a 
different driver than is in your initrd... but i'm just guessing.

> Any ideas what could cause mdadm to report as I've described above
> (I've attached the output of these three commands)?  I'm running
> Ubuntu Edgy, which is a 2.17.x kernel, and mdadm 2.4.1.  In case it's
> relevant here, I created the array using EVMS...

i've never created an array with evms... but my guess is that it may have 
used "mapped" device names instead of the normal device names.  take a 
look at /proc/mdstat and see what devices are in the array and use those 
as a template to find the name of the missing device.  below i'll use 
/dev/sde1 as the example missing device and /dev/md0 as the example array.

first thing i'd try is something like this:

	mdadm /dev/md0 -a /dev/sde1

which hotadds the device into the array... which will start a resync.

when the resync is done (cat /proc/mdstat) do this.

	mdadm -Gb internal /dev/md0

which will add write-intent bitmaps to your device... which will avoid 
another long wait for a resync after the next reboot if the fix below 
doesn't help.

then do this:

	dpkg-reconfigure linux-image-`uname -r`

which will rebuild the initrd for your kernel ... and if it was a driver 
change this should include the new driver into the initrd.

then reboot and see if it comes up fine.  if it doesn't, you can repeat 
the "-a /dev/sde1" command above... the resync will be quick this time due 
to the bitmap... and we'll have to investigate further.

-dean

Re: RAID5 array showing as degraded after motherboard replacement

[James Lee]

[-- Attachment #1: Type: text/plain, Size: 5032 bytes --]

Thanks for the reply Dean.  I looked through dmesg output from the
boot up, to check whether this was just an ordering issue during the
system start up (since both evms and mdadm attempt to activate the
array, which could cause things to go wrong...).

Looking through the dmesg output though, it looks like the 'missing'
disk is being detected before the array is assembled, but that the
disk is throwing up errors.  I've attached the full output of dmesg;
grepping it for "hde" gives the following:

[17179574.084000]     ide2: BM-DMA at 0xd400-0xd407, BIOS settings:
hde:DMA, hdf:DMA
[17179574.380000] hde: NetCell SyncRAID(TM) SR5000 JBOD, ATA DISK drive
[17179575.312000] hde: max request size: 512KiB
[17179575.312000] hde: 625134827 sectors (320069 MB), CHS=38912/255/63, (U)DMA
[17179575.312000] hde: set_geometry_intr: status=0x51 { DriveReady
SeekComplete Error }
[17179575.312000] hde: set_geometry_intr: error=0x04 { DriveStatusError }
[17179575.312000] hde: cache flushes supported
[17179575.312000]  hde: hde1
[17179967.224000] md: bind<hde1>
[17179967.224000] md: kicking non-fresh hde1 from array!
[17179967.224000] md: unbind<hde1>
[17179967.224000] md: export_rdev(hde1)

Am I right in thinking this looks that drive is just bad (the two
set_geometry_intr errors, and the fact it gets kicked off the array by
mdadm)?  I'll run it through the Seagate diagnostics suite tomorrow to
see whether it's faulty or not...

James

On 05/11/06, dean gaudet <dean@arctic.org> wrote:
> On Sun, 5 Nov 2006, James Lee wrote:
>
> > Hi there,
> >
> > I'm running a 5-drive software RAID5 array across two controllers.
> > The motherboard in that PC recently died - I sent the board back for
> > RMA.  When I refitted the motherboard, connected up all the drives,
> > and booted up I found that the array was being reported as degraded
> > (though all the data on it is intact).  I have 4 drives on the on
> > board controller and 1 drive on an XFX Revo 64 SATA controller card.
> > The drive which is being reported as not being in the array is the one
> > connected to the XFX controller.
> >
> > The OS can see that drive fine, and "mdadm --examine" on that drive
> > shows that it is part of the array and that there are 5 active devices
> > in the array.  Doing "mdadm --examine" on one of the other four drives
> > shows that the array has 4 active drives and one failed.  "mdadm
> > --detail" for the array also shows 4 active and one failed.
>
> that means the array was assembled without the 5th disk and is currently
> degraded.
>
>
> > Now I haven't lost any data here and I know I can just force a resync
> > of the array which is fine.  However I'm concerned about how this has
> > happened.  One worry is that the XFX SATA controller is doing
> > something funny to the drive.  I've noticed that it's BIOS has
> > defaulted to RAID0 mode (even though there's only one drive on it) - I
> > can't see how this would cause any particular problems here though.  I
> > guess it's possible that some data on the drive got corrupted when the
> > motherboard failed...
>
> no it's more likely the devices were renamed or the 5th device didn't come
> up before the array was assembled.
>
> it's possible that a different bios setting lead to the device using a
> different driver than is in your initrd... but i'm just guessing.
>
> > Any ideas what could cause mdadm to report as I've described above
> > (I've attached the output of these three commands)?  I'm running
> > Ubuntu Edgy, which is a 2.17.x kernel, and mdadm 2.4.1.  In case it's
> > relevant here, I created the array using EVMS...
>
> i've never created an array with evms... but my guess is that it may have
> used "mapped" device names instead of the normal device names.  take a
> look at /proc/mdstat and see what devices are in the array and use those
> as a template to find the name of the missing device.  below i'll use
> /dev/sde1 as the example missing device and /dev/md0 as the example array.
>
> first thing i'd try is something like this:
>
>         mdadm /dev/md0 -a /dev/sde1
>
> which hotadds the device into the array... which will start a resync.
>
> when the resync is done (cat /proc/mdstat) do this.
>
>         mdadm -Gb internal /dev/md0
>
> which will add write-intent bitmaps to your device... which will avoid
> another long wait for a resync after the next reboot if the fix below
> doesn't help.
>
> then do this:
>
>         dpkg-reconfigure linux-image-`uname -r`
>
> which will rebuild the initrd for your kernel ... and if it was a driver
> change this should include the new driver into the initrd.
>
> then reboot and see if it comes up fine.  if it doesn't, you can repeat
> the "-a /dev/sde1" command above... the resync will be quick this time due
> to the bitmap... and we'll have to investigate further.
>
> -dean
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

[-- Attachment #2: dmesg.log --]
[-- Type: text/x-log, Size: 34267 bytes --]

[17179569.184000] Linux version 2.6.17-10-generic (root@vernadsky) (gcc version 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)) #2 SMP Fri Oct 13 18:45:35 UTC 2006 (Ubuntu 2.6.17-10.33-generic)
[17179569.184000] BIOS-provided physical RAM map:
[17179569.184000]  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[17179569.184000]  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[17179569.184000]  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[17179569.184000]  BIOS-e820: 0000000000100000 - 000000001f7f0000 (usable)
[17179569.184000]  BIOS-e820: 000000001f7f0000 - 000000001f7f3000 (ACPI NVS)
[17179569.184000]  BIOS-e820: 000000001f7f3000 - 000000001f800000 (ACPI data)
[17179569.184000]  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[17179569.184000]  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[17179569.184000] 0MB HIGHMEM available.
[17179569.184000] 503MB LOWMEM available.
[17179569.184000] found SMP MP-table at 000f3fd0
[17179569.184000] On node 0 totalpages: 129008
[17179569.184000]   DMA zone: 4096 pages, LIFO batch:0
[17179569.184000]   Normal zone: 124912 pages, LIFO batch:31
[17179569.184000] DMI 2.2 present.
[17179569.184000] ACPI: RSDP (v000 IntelR                                ) @ 0x000f7570
[17179569.184000] ACPI: RSDT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1f7f3040
[17179569.184000] ACPI: FADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1f7f30c0
[17179569.184000] ACPI: MCFG (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1f7f7480
[17179569.184000] ACPI: MADT (v001 IntelR AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1f7f73c0
[17179569.184000] ACPI: DSDT (v001 INTELR AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000
[17179569.184000] ACPI: PM-Timer IO Port: 0x408
[17179569.184000] ACPI: Local APIC address 0xfee00000
[17179569.184000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[17179569.184000] Processor #0 15:2 APIC version 20
[17179569.184000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled)
[17179569.184000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[17179569.184000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[17179569.184000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[17179569.184000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
[17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[17179569.184000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[17179569.184000] ACPI: IRQ0 used by override.
[17179569.184000] ACPI: IRQ2 used by override.
[17179569.184000] ACPI: IRQ9 used by override.
[17179569.184000] Enabling APIC mode:  Flat.  Using 1 I/O APICs
[17179569.184000] Using ACPI (MADT) for SMP configuration information
[17179569.184000] Allocating PCI resources starting at 20000000 (gap: 1f800000:c0800000)
[17179569.184000] Built 1 zonelists
[17179569.184000] Kernel command line: root=/dev/hda1 ro quiet splash
[17179569.184000] mapped APIC to ffffd000 (fee00000)
[17179569.184000] mapped IOAPIC to ffffc000 (fec00000)
[17179569.184000] Enabling fast FPU save and restore... done.
[17179569.184000] Enabling unmasked SIMD FPU exception support... done.
[17179569.184000] Initializing CPU#0
[17179569.184000] PID hash table entries: 2048 (order: 11, 8192 bytes)
[17179569.184000] Detected 2394.446 MHz processor.
[17179569.184000] Using pmtmr for high-res timesource
[17179569.184000] Console: colour VGA+ 80x25
[17179571.120000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[17179571.120000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[17179571.132000] Memory: 501096k/516032k available (1910k kernel code, 14368k reserved, 1070k data, 308k init, 0k highmem)
[17179571.132000] Checking if this processor honours the WP bit even in supervisor mode... Ok.
[17179571.212000] Calibrating delay using timer specific routine.. 4794.73 BogoMIPS (lpj=9589463)
[17179571.212000] Security Framework v1.0.0 initialized
[17179571.212000] SELinux:  Disabled at boot.
[17179571.212000] Mount-cache hash table entries: 512
[17179571.212000] CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000
[17179571.212000] CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000
[17179571.212000] CPU: Trace cache: 12K uops, L1 D cache: 8K
[17179571.212000] CPU: L2 cache: 512K
[17179571.212000] CPU: Hyper-Threading is disabled
[17179571.212000] CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080 00004400 00000000 00000000
[17179571.212000] Checking 'hlt' instruction... OK.
[17179571.228000] SMP alternatives: switching to UP code
[17179571.228000] Freeing SMP alternatives: 16k freed
[17179571.228000] checking if image is initramfs... it is
[17179571.808000] Freeing initrd memory: 6156k freed
[17179571.808000] ACPI: Core revision 20060707
[17179571.816000] ACPI: Looking for DSDT ... not found!
[17179571.824000] CPU0: Intel(R) Pentium(R) 4 CPU 2.40GHz stepping 09
[17179571.824000] Total of 1 processors activated (4794.73 BogoMIPS).
[17179571.824000] ENABLING IO-APIC IRQs
[17179571.824000] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
[17179571.968000] Brought up 1 CPUs
[17179571.968000] migration_cost=0
[17179571.968000] NET: Registered protocol family 16
[17179571.968000] EISA bus registered
[17179571.968000] ACPI: bus type pci registered
[17179571.968000] PCI: Using MMCONFIG
[17179571.968000] Setting up standard PCI resources
[17179571.992000] ACPI: Interpreter enabled
[17179571.992000] ACPI: Using IOAPIC for interrupt routing
[17179571.992000] ACPI: PCI Root Bridge [PCI0] (0000:00)
[17179571.992000] PCI: Probing PCI hardware (bus 00)
[17179571.992000] Boot video device is 0000:00:02.0
[17179571.992000] PCI quirk: region 0400-047f claimed by ICH6 ACPI/GPIO/TCO
[17179571.992000] PCI quirk: region 0480-04bf claimed by ICH6 GPIO
[17179571.992000] PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
[17179571.996000] PCI: Transparent bridge - 0000:00:1e.0
[17179571.996000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[17179572.004000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
[17179572.008000] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 9 10 11 *12 14 15)
[17179572.008000] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 7 9 10 11 12 14 15)
[17179572.008000] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 7 9 *10 11 12 14 15)
[17179572.008000] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12 14 15)
[17179572.008000] ACPI: PCI Interrupt Link [LNKE] (IRQs *3 4 5 7 9 10 11 12 14 15)
[17179572.008000] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
[17179572.012000] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
[17179572.012000] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 7 *9 10 11 12 14 15)
[17179572.012000] Linux Plug and Play Support v0.97 (c) Adam Belay
[17179572.012000] pnp: PnP ACPI init
[17179572.016000] pnp: PnP ACPI: found 13 devices
[17179572.016000] PnPBIOS: Disabled by ACPI PNP
[17179572.016000] PCI: Using ACPI for IRQ routing
[17179572.016000] PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
[17179572.016000] pnp: 00:09: ioport range 0x400-0x4bf could not be reserved
[17179572.016000] PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
[17179572.016000] PCI: Bridge: 0000:00:1e.0
[17179572.016000]   IO window: d000-dfff
[17179572.016000]   MEM window: d0000000-d00fffff
[17179572.016000]   PREFETCH window: 20000000-200fffff
[17179572.016000] PCI: Setting latency timer of device 0000:00:1e.0 to 64
[17179572.016000] NET: Registered protocol family 2
[17179572.044000] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[17179572.044000] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[17179572.044000] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[17179572.044000] TCP: Hash tables configured (established 16384 bind 8192)
[17179572.044000] TCP reno registered
[17179572.044000] audit: initializing netlink socket (disabled)
[17179572.044000] audit(1162727167.044:1): initialized
[17179572.044000] VFS: Disk quotas dquot_6.5.1
[17179572.044000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[17179572.044000] Initializing Cryptographic API
[17179572.044000] io scheduler noop registered
[17179572.044000] io scheduler anticipatory registered
[17179572.044000] io scheduler deadline registered
[17179572.044000] io scheduler cfq registered (default)
[17179572.044000] isapnp: Scanning for PnP cards...
[17179572.396000] isapnp: No Plug & Play device found
[17179572.424000] Real Time Clock Driver v1.12ac
[17179572.424000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
[17179572.424000] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[17179572.424000] 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[17179572.424000] mice: PS/2 mouse device common for all mice
[17179572.424000] RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
[17179572.424000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[17179572.424000] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[17179572.424000] PNP: No PS/2 controller found. Probing ports directly.
[17179572.428000] serio: i8042 AUX port at 0x60,0x64 irq 12
[17179572.428000] serio: i8042 KBD port at 0x60,0x64 irq 1
[17179572.428000] EISA: Probing bus 0 at eisa.0
[17179572.428000] EISA: Detected 0 cards.
[17179572.428000] TCP bic registered
[17179572.428000] NET: Registered protocol family 1
[17179572.428000] NET: Registered protocol family 8
[17179572.428000] NET: Registered protocol family 20
[17179572.428000] Using IPI No-Shortcut mode
[17179572.428000] ACPI: (supports S0 S1 S4 S5)
[17179572.428000] Freeing unused kernel memory: 308k freed
[17179573.572000] Capability LSM initialized
[17179573.608000] ACPI: Fan [FAN] (on)
[17179573.612000] ACPI Exception (acpi_processor-0693): AE_NOT_FOUND, Processor Device is not present [20060707]
[17179573.612000] ACPI: Getting cpuindex for acpiid 0x1
[17179573.616000] ACPI: Thermal Zone [THRM] (33 C)
[17179574.084000] Revolution: IDE controller at PCI slot 0000:01:02.0
[17179574.084000] ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 18 (level, low) -> IRQ 169
[17179574.084000] Revolution: chipset revision 0
[17179574.084000] Revolution: 100% native mode on irq 169
[17179574.084000] Revolution: simplex device: DMA forced
[17179574.084000]     ide2: BM-DMA at 0xd400-0xd407, BIOS settings: hde:DMA, hdf:DMA
[17179574.084000] Revolution: simplex device: DMA forced
[17179574.084000]     ide3: BM-DMA at 0xd408-0xd40f, BIOS settings: hdg:DMA, hdh:DMA
[17179574.084000] Probing IDE interface ide2...
[17179574.380000] hde: NetCell SyncRAID(TM) SR5000 JBOD, ATA DISK drive
[17179574.716000] ide2 at 0xd000-0xd007,0xd102 on irq 169
[17179574.720000] Probing IDE interface ide3...
[17179575.292000] ICH6: IDE controller at PCI slot 0000:00:1f.1
[17179575.292000] ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 169
[17179575.292000] ICH6: chipset revision 3
[17179575.292000] ICH6: not 100% native mode: will probe irqs later
[17179575.292000]     ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
[17179575.292000]     ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
[17179575.292000] Probing IDE interface ide0...
[17179575.312000] hde: max request size: 512KiB
[17179575.312000] hde: 625134827 sectors (320069 MB), CHS=38912/255/63, (U)DMA
[17179575.312000] hde: set_geometry_intr: status=0x51 { DriveReady SeekComplete Error }
[17179575.312000] hde: set_geometry_intr: error=0x04 { DriveStatusError }
[17179575.312000] ide: failed opcode was: 0xef
[17179575.312000] hde: cache flushes supported
[17179575.312000]  hde: hde1
[17179575.584000] hda: IC35L060AVV207-0, ATA DISK drive
[17179576.036000] hdb: _NEC DVD_RW ND-4570A, ATAPI CD/DVD-ROM drive
[17179576.096000] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[17179576.108000] hda: max request size: 512KiB
[17179576.108000] hda: 80418240 sectors (41174 MB) w/1821KiB Cache, CHS=16383/255/63, UDMA(33)
[17179576.108000] hda: cache flushes supported
[17179576.108000]  hda: hda1 hda2 < hda5 >
[17179576.140000] Probing IDE interface ide1...
[17179576.744000] hdb: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(33)
[17179576.744000] Uniform CD-ROM driver Revision: 3.20
[17179576.904000] SCSI subsystem initialized
[17179576.908000] libata version 1.20 loaded.
[17179576.912000] ata_piix 0000:00:1f.2: version 1.05
[17179576.912000] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 177
[17179576.912000] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[17179576.912000] ata1: SATA max UDMA/133 cmd 0xE900 ctl 0xEA02 bmdma 0xED00 irq 177
[17179576.912000] ata2: SATA max UDMA/133 cmd 0xEB00 ctl 0xEC02 bmdma 0xED08 irq 177
[17179577.084000] ata1: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3469 86:3c01 87:4003 88:203f
[17179577.084000] ata1: dev 0 ATA-6, max UDMA/100, 625142448 sectors: LBA48
[17179577.096000] ata1: dev 1 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3469 86:3c01 87:4003 88:203f
[17179577.096000] ata1: dev 1 ATA-6, max UDMA/100, 625142448 sectors: LBA48
[17179577.108000] ata1: dev 0 configured for UDMA/100
[17179577.120000] ata1: dev 1 configured for UDMA/100
[17179577.120000] scsi0 : ata_piix
[17179577.292000] ata2: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3469 86:3c01 87:4003 88:203f
[17179577.292000] ata2: dev 0 ATA-6, max UDMA/100, 625142448 sectors: LBA48
[17179577.304000] ata2: dev 1 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3469 86:3c01 87:4003 88:203f
[17179577.304000] ata2: dev 1 ATA-6, max UDMA/100, 625142448 sectors: LBA48
[17179577.316000] ata2: dev 0 configured for UDMA/100
[17179577.328000] ata2: dev 1 configured for UDMA/100
[17179577.328000] scsi1 : ata_piix
[17179577.328000]   Vendor: ATA       Model: WDC WD3200JD-00K  Rev: 08.0
[17179577.328000]   Type:   Direct-Access                      ANSI SCSI revision: 05
[17179577.328000]   Vendor: ATA       Model: WDC WD3200JD-22K  Rev: 08.0
[17179577.328000]   Type:   Direct-Access                      ANSI SCSI revision: 05
[17179577.328000]   Vendor: ATA       Model: WDC WD3200JD-00K  Rev: 08.0
[17179577.328000]   Type:   Direct-Access                      ANSI SCSI revision: 05
[17179577.328000]   Vendor: ATA       Model: WDC WD3200JD-00K  Rev: 08.0
[17179577.328000]   Type:   Direct-Access                      ANSI SCSI revision: 05
[17179577.348000] SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)
[17179577.348000] sda: Write Protect is off
[17179577.348000] sda: Mode Sense: 00 3a 00 00
[17179577.348000] SCSI device sda: drive cache: write back
[17179577.348000] SCSI device sda: 625142448 512-byte hdwr sectors (320073 MB)
[17179577.348000] sda: Write Protect is off
[17179577.348000] sda: Mode Sense: 00 3a 00 00
[17179577.348000] SCSI device sda: drive cache: write back
[17179577.348000]  sda: sda1
[17179577.360000] sd 0:0:0:0: Attached scsi disk sda
[17179577.364000] SCSI device sdb: 625142448 512-byte hdwr sectors (320073 MB)
[17179577.368000] sdb: Write Protect is off
[17179577.368000] sdb: Mode Sense: 00 3a 00 00
[17179577.372000] SCSI device sdb: drive cache: write back
[17179577.376000] SCSI device sdb: 625142448 512-byte hdwr sectors (320073 MB)
[17179577.376000] sdb: Write Protect is off
[17179577.376000] sdb: Mode Sense: 00 3a 00 00
[17179577.376000] SCSI device sdb: drive cache: write back
[17179577.376000]  sdb: sdb1
[17179577.396000] sd 0:0:1:0: Attached scsi disk sdb
[17179577.400000] SCSI device sdc: 625142448 512-byte hdwr sectors (320073 MB)
[17179577.400000] sdc: Write Protect is off
[17179577.400000] sdc: Mode Sense: 00 3a 00 00
[17179577.400000] SCSI device sdc: drive cache: write back
[17179577.400000] SCSI device sdc: 625142448 512-byte hdwr sectors (320073 MB)
[17179577.400000] sdc: Write Protect is off
[17179577.400000] sdc: Mode Sense: 00 3a 00 00
[17179577.400000] SCSI device sdc: drive cache: write back
[17179577.400000]  sdc: sdc1
[17179577.416000] sd 1:0:0:0: Attached scsi disk sdc
[17179577.420000] SCSI device sdd: 625142448 512-byte hdwr sectors (320073 MB)
[17179577.420000] sdd: Write Protect is off
[17179577.420000] sdd: Mode Sense: 00 3a 00 00
[17179577.424000] SCSI device sdd: drive cache: write back
[17179577.428000] SCSI device sdd: 625142448 512-byte hdwr sectors (320073 MB)
[17179577.428000] sdd: Write Protect is off
[17179577.428000] sdd: Mode Sense: 00 3a 00 00
[17179577.432000] SCSI device sdd: drive cache: write back
[17179577.432000]  sdd: sdd1
[17179577.448000] sd 1:0:1:0: Attached scsi disk sdd
[17179577.680000] Probing IDE interface ide1...
[17179577.708000] usbcore: registered new driver usbfs
[17179577.708000] usbcore: registered new driver hub
[17179577.708000] USB Universal Host Controller Interface driver v3.0
[17179577.708000] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 185
[17179577.708000] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[17179577.708000] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[17179577.708000] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
[17179577.708000] uhci_hcd 0000:00:1d.0: irq 185, io base 0x0000e000
[17179577.708000] usb usb1: configuration #1 chosen from 1 choice
[17179577.708000] hub 1-0:1.0: USB hub found
[17179577.708000] hub 1-0:1.0: 2 ports detected
[17179577.772000] ieee1394: Initialized config rom entry `ip1394'
[17179577.816000] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 177
[17179577.816000] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[17179577.816000] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[17179577.816000] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
[17179577.816000] uhci_hcd 0000:00:1d.1: irq 177, io base 0x0000e100
[17179577.816000] usb usb2: configuration #1 chosen from 1 choice
[17179577.816000] hub 2-0:1.0: USB hub found
[17179577.816000] hub 2-0:1.0: 2 ports detected
[17179577.924000] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 169
[17179577.924000] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[17179577.924000] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[17179577.924000] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
[17179577.924000] uhci_hcd 0000:00:1d.2: irq 169, io base 0x0000e200
[17179577.924000] usb usb3: configuration #1 chosen from 1 choice
[17179577.924000] hub 3-0:1.0: USB hub found
[17179577.924000] hub 3-0:1.0: 2 ports detected
[17179578.032000] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 193
[17179578.032000] PCI: Setting latency timer of device 0000:00:1d.3 to 64
[17179578.032000] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[17179578.032000] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
[17179578.032000] uhci_hcd 0000:00:1d.3: irq 193, io base 0x0000e300
[17179578.032000] usb usb4: configuration #1 chosen from 1 choice
[17179578.032000] hub 4-0:1.0: USB hub found
[17179578.032000] hub 4-0:1.0: 2 ports detected
[17179578.152000] ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 185
[17179578.152000] PCI: Setting latency timer of device 0000:00:1d.7 to 64
[17179578.152000] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[17179578.152000] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
[17179578.152000] PCI: cache line size of 128 is not supported by device 0000:00:1d.7
[17179578.152000] ehci_hcd 0000:00:1d.7: irq 185, io mem 0xd01c0000
[17179578.156000] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[17179578.156000] usb usb5: configuration #1 chosen from 1 choice
[17179578.156000] hub 5-0:1.0: USB hub found
[17179578.156000] hub 5-0:1.0: 8 ports detected
[17179578.264000] ACPI: PCI Interrupt 0000:01:0a.0[A] -> GSI 20 (level, low) -> IRQ 201
[17179578.264000] PCI: Via IRQ fixup for 0000:01:0a.0, from 3 to 9
[17179578.312000] Probing IDE interface ide3...
[17179578.324000] ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[201]  MMIO=[d0012000-d00127ff]  Max Packet=[2048]  IR/IT contexts=[4/8]
[17179578.684000] usb 5-6: new high speed USB device using ehci_hcd and address 2
[17179578.932000] raid5: automatically using best checksumming function: pIII_sse
[17179578.952000]    pIII_sse  :  3129.000 MB/sec
[17179578.952000] raid5: using function: pIII_sse (3129.000 MB/sec)
[17179578.952000] md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
[17179578.952000] md: bitmap version 4.39
[17179578.956000] md: raid5 personality registered for level 5
[17179578.956000] md: raid4 personality registered for level 4
[17179578.996000] usb 5-6: configuration #1 chosen from 1 choice
[17179579.608000] ieee1394: Host added: ID:BUS[0-00:1023]  GUID[001106012e09b2f9]
[17179579.640000] usb 4-1: new full speed USB device using uhci_hcd and address 2
[17179579.824000] usb 4-1: configuration #1 chosen from 1 choice
[17179579.824000] hub 4-1:1.0: USB hub found
[17179579.828000] hub 4-1:1.0: 4 ports detected
[17179580.168000] usb 4-1.1: new low speed USB device using uhci_hcd and address 3
[17179580.320000] usb 4-1.1: configuration #1 chosen from 1 choice
[17179580.548000] usb 4-1.2: new low speed USB device using uhci_hcd and address 4
[17179580.700000] usb 4-1.2: configuration #1 chosen from 1 choice
[17179580.928000] usb 4-1.3: new full speed USB device using uhci_hcd and address 5
[17179581.076000] usb 4-1.3: configuration #1 chosen from 1 choice
[17179581.080000] usbcore: registered new driver hiddev
[17179581.100000] input: CHESEN USB Keyboard as /class/input/input0
[17179581.100000] input: USB HID v1.10 Keyboard [CHESEN USB Keyboard] on usb-0000:00:1d.3-1.1
[17179581.132000] input: CHESEN USB Keyboard as /class/input/input1
[17179581.132000] input: USB HID v1.10 Device [CHESEN USB Keyboard] on usb-0000:00:1d.3-1.1
[17179581.148000] input: Logitech USB-PS/2 Optical Mouse as /class/input/input2
[17179581.148000] input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.3-1.2
[17179581.148000] usbcore: registered new driver usbhid
[17179581.148000] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[17179581.148000] usbcore: registered new driver libusual
[17179581.184000] Initializing USB Mass Storage driver...
[17179581.184000] scsi2 : SCSI emulation for USB Mass Storage devices
[17179581.184000] usb-storage: device found at 5
[17179581.184000] usb-storage: waiting for device to settle before scanning
[17179581.184000] usbcore: registered new driver usb-storage
[17179581.184000] USB Mass Storage support registered.
[17179586.188000] usb-storage: device scan complete
[17179586.192000]   Vendor: Generic   Model: USB SD Reader     Rev: 1.00
[17179586.192000]   Type:   Direct-Access                      ANSI SCSI revision: 00
[17179586.192000]   Vendor: Generic   Model: USB CF Reader     Rev: 1.01
[17179586.192000]   Type:   Direct-Access                      ANSI SCSI revision: 00
[17179586.196000]   Vendor: Generic   Model: USB SM Reader     Rev: 1.02
[17179586.196000]   Type:   Direct-Access                      ANSI SCSI revision: 00
[17179586.200000]   Vendor: Generic   Model: USB MS Reader     Rev: 1.03
[17179586.200000]   Type:   Direct-Access                      ANSI SCSI revision: 00
[17179586.256000] sd 2:0:0:0: Attached scsi removable disk sde
[17179586.308000] sd 2:0:0:1: Attached scsi removable disk sdf
[17179586.364000] sd 2:0:0:2: Attached scsi removable disk sdg
[17179586.420000] sd 2:0:0:3: Attached scsi removable disk sdh
[17179967.220000] md: md0 stopped.
[17179967.224000] md: bind<sda1>
[17179967.224000] md: bind<sdc1>
[17179967.224000] md: bind<sdd1>
[17179967.224000] md: bind<hde1>
[17179967.224000] md: bind<sdb1>
[17179967.224000] md: kicking non-fresh hde1 from array!
[17179967.224000] md: unbind<hde1>
[17179967.224000] md: export_rdev(hde1)
[17179967.232000] raid5: device sdb1 operational as raid disk 0
[17179967.232000] raid5: device sdd1 operational as raid disk 3
[17179967.232000] raid5: device sdc1 operational as raid disk 2
[17179967.232000] raid5: device sda1 operational as raid disk 1
[17179967.232000] raid5: allocated 5245kB for md0
[17179967.232000] raid5: raid level 5 set md0 active with 4 out of 5 devices, algorithm 0
[17179967.232000] RAID5 conf printout:
[17179967.232000]  --- rd:5 wd:4 fd:1
[17179967.232000]  disk 0, o:1, dev:sdb1
[17179967.232000]  disk 1, o:1, dev:sda1
[17179967.232000]  disk 2, o:1, dev:sdc1
[17179967.232000]  disk 3, o:1, dev:sdd1
[17179967.248000] md: md1 stopped.
[17179967.252000] md: bind<hda>
[17179967.548000] Attempting manual resume
[17179967.580000] kjournald starting.  Commit interval 5 seconds
[17179967.580000] EXT3-fs: mounted filesystem with ordered data mode.
[17179977.384000] Linux agpgart interface v0.101 (c) Dave Jones
[17179977.388000] agpgart: Detected an Intel 915G Chipset.
[17179977.388000] agpgart: Detected 7932K stolen memory.
[17179977.408000] agpgart: AGP aperture is 256M @ 0xc0000000
[17179977.976000] Linux video capture interface: v1.00
[17179978.484000] Floppy drive(s): fd0 is 1.44M
[17179978.496000] 8139too Fast Ethernet driver 0.9.27
[17179978.496000] ACPI: PCI Interrupt 0000:01:09.0[A] -> GSI 19 (level, low) -> IRQ 177
[17179978.500000] eth0: RealTek RTL8139 at 0xe023c000, 00:01:2e:02:ba:94, IRQ 177
[17179978.500000] eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
[17179978.508000] 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
[17179978.560000] FDC 0 is a post-1991 82077
[17179978.584000] input: PC Speaker as /class/input/input3
[17179978.616000] saa7130/34: v4l2 driver version 0.2.14 loaded
[17179978.616000] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 193
[17179978.616000] saa7130[0]: found at 0000:01:00.0, rev: 1, irq: 193, latency: 32, mmio: 0xd0013000
[17179978.616000] saa7130[0]: subsystem: 185b:c901, board: Compro Videomate DVB-T200 [card=71,autodetected]
[17179978.616000] saa7130[0]: board init: gpio is 843f00
[17179978.616000] input: saa7134 IR (Compro Videomate DV as /class/input/input4
[17179978.664000] parport: PnPBIOS parport detected.
[17179978.664000] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[17179978.752000] saa7130[0]: i2c eeprom 00: 5b 18 01 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
[17179978.752000] saa7130[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff
[17179978.752000] saa7130[0]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 88 ff ff ff ff
[17179978.752000] saa7130[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179978.752000] saa7130[0]: i2c eeprom 40: ff d0 00 c2 86 10 ff ff ff ff ff ff ff ff ff ff
[17179978.752000] saa7130[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb
[17179978.752000] saa7130[0]: i2c eeprom 60: 30 26 ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179978.752000] saa7130[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179978.752000] saa7130[0]: registered device video0 [v4l2]
[17179978.752000] saa7130[0]: registered device vbi0
[17179978.752000] ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 17 (level, low) -> IRQ 209
[17179978.752000] saa7130[1]: found at 0000:01:01.0, rev: 1, irq: 209, latency: 32, mmio: 0xd0010000
[17179978.752000] saa7130[1]: subsystem: 185b:c901, board: Compro Videomate DVB-T200 [card=71,autodetected]
[17179978.752000] saa7130[1]: board init: gpio is 843f00
[17179978.752000] input: saa7134 IR (Compro Videomate DV as /class/input/input5
[17179978.892000] saa7130[1]: i2c eeprom 00: 5b 18 01 c9 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
[17179978.892000] saa7130[1]: i2c eeprom 10: 00 ff 86 0f ff 20 ff ff ff ff ff ff ff ff ff ff
[17179978.892000] saa7130[1]: i2c eeprom 20: 01 40 01 03 03 ff 03 01 08 ff 00 88 ff ff ff ff
[17179978.892000] saa7130[1]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179978.892000] saa7130[1]: i2c eeprom 40: ff d0 00 c2 86 10 ff ff ff ff ff ff ff ff ff ff
[17179978.892000] saa7130[1]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff cb
[17179978.892000] saa7130[1]: i2c eeprom 60: 30 26 ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179978.892000] saa7130[1]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[17179978.892000] saa7130[1]: registered device video1 [v4l2]
[17179978.892000] saa7130[1]: registered device vbi1
[17179978.968000] ts: Compaq touchscreen protocol output
[17179979.180000] ACPI: PCI Interrupt 0000:00:1e.2[A] -> GSI 17 (level, low) -> IRQ 209
[17179979.180000] PCI: Setting latency timer of device 0000:00:1e.2 to 64
[17179979.484000] saa7134 ALSA driver for DMA sound loaded
[17179979.484000] saa7130[0]/alsa: saa7130[0] at 0xd0013000 irq 193 registered as card -1
[17179979.484000] saa7130[1]/alsa: saa7130[1] at 0xd0010000 irq 209 registered as card -1
[17179979.496000] intel8x0_measure_ac97_clock: measured 54727 usecs
[17179979.496000] intel8x0: clocking to 48000
[17179979.560000] sd 0:0:0:0: Attached scsi generic sg0 type 0
[17179979.560000] sd 0:0:1:0: Attached scsi generic sg1 type 0
[17179979.560000] sd 1:0:0:0: Attached scsi generic sg2 type 0
[17179979.560000] sd 1:0:1:0: Attached scsi generic sg3 type 0
[17179979.560000] sd 2:0:0:0: Attached scsi generic sg4 type 0
[17179979.560000] sd 2:0:0:1: Attached scsi generic sg5 type 0
[17179979.560000] sd 2:0:0:2: Attached scsi generic sg6 type 0
[17179979.560000] sd 2:0:0:3: Attached scsi generic sg7 type 0
[17179979.680000] eth1: link down
[17179979.808000] hw_random hardware driver 1.0.0 loaded
[17179980.144000] lp0: using parport0 (interrupt-driven).
[17179980.160000] ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
[17179980.160000] ieee1394: sbp2: Try serialize_io=0 for better performance
[17179980.192000] Adding 1477940k swap on /dev/disk/by-uuid/6e10a8b4-b78a-41df-9f3f-316832934505.  Priority:-1 extents:1 across:1477940k
[17179980.252000] EXT3 FS on hda1, internal journal
[17179980.504000] device-mapper: 4.6.0-ioctl (2006-02-17) initialised: dm-devel@redhat.com
[17179980.808000] NET: Registered protocol family 17
[17179980.872000] device-mapper: dm-linear: Device lookup failed
[17179980.872000] device-mapper: error adding target to table
[17179980.872000] device-mapper: dm-linear: Device lookup failed
[17179980.872000] device-mapper: error adding target to table
[17179980.884000] device-mapper: dm-linear: Device lookup failed
[17179980.884000] device-mapper: error adding target to table
[17179980.884000] device-mapper: dm-linear: Device lookup failed
[17179980.884000] device-mapper: error adding target to table
[17179980.888000] device-mapper: dm-linear: Device lookup failed
[17179980.888000] device-mapper: error adding target to table
[17179980.888000] device-mapper: dm-linear: Device lookup failed
[17179980.888000] device-mapper: error adding target to table
[17179980.892000] device-mapper: dm-linear: Device lookup failed
[17179980.892000] device-mapper: error adding target to table
[17179980.892000] device-mapper: dm-linear: Device lookup failed
[17179980.892000] device-mapper: error adding target to table
[17179981.076000] kjournald starting.  Commit interval 5 seconds
[17179981.120000] EXT3 FS on dm-5, internal journal
[17179981.120000] EXT3-fs: mounted filesystem with ordered data mode.
[17179983.720000] ndiswrapper version 1.22 loaded (preempt=no,smp=yes)
[17179983.880000] usb 5-6: reset high speed USB device using ehci_hcd and address 2
[17179984.088000] ndiswrapper: driver rt73 (Belkin,08/02/2005, 1.00.00.0000) loaded
[17179984.916000] wlan0: vendor: 'IEEE 802.11g Wireless Card.'
[17179984.916000] wlan0: ethernet device 00:11:50:c1:bf:87 using NDIS driver rt73, 050D:705A.F.conf
[17179984.916000] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
[17179984.916000] usbcore: registered new driver ndiswrapper
[17179999.824000] NET: Registered protocol family 10
[17179999.824000] lo: Disabled Privacy Extensions
[17179999.824000] ADDRCONF(NETDEV_UP): eth1: link is not ready
[17179999.824000] IPv6 over IPv4 tunneling driver
[17180001.068000] ACPI: Power Button (FF) [PWRF]
[17180001.068000] ACPI: Power Button (CM) [PWRB]
[17180001.196000] ibm_acpi: ec object not found
[17180001.228000] pcc_acpi: loading...
[17180003.004000] [drm] Initialized drm 1.0.1 20051102
[17180003.008000] ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 193
[17180003.012000] [drm] Initialized i915 1.5.0 20060119 on minor 0
[17180004.076000] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
[17180004.076000] apm: overridden by ACPI.
[17180009.996000] wlan0: no IPv6 routers present
[17180010.028000] Bluetooth: Core ver 2.8
[17180010.028000] NET: Registered protocol family 31
[17180010.028000] Bluetooth: HCI device and connection manager initialized
[17180010.028000] Bluetooth: HCI socket layer initialized
[17180010.044000] Bluetooth: L2CAP ver 2.8
[17180010.044000] Bluetooth: L2CAP socket layer initialized
[17180010.144000] Bluetooth: RFCOMM socket layer initialized
[17180010.144000] Bluetooth: RFCOMM TTY layer initialized
[17180010.144000] Bluetooth: RFCOMM ver 1.7
[17184354.040000] device-mapper: dm-linear: Device lookup failed
[17184354.040000] device-mapper: error adding target to table
[17184354.044000] device-mapper: dm-linear: Device lookup failed
[17184354.044000] device-mapper: error adding target to table
[17184354.044000] device-mapper: dm-linear: Device lookup failed
[17184354.048000] device-mapper: error adding target to table
[17184354.048000] device-mapper: dm-linear: Device lookup failed
[17184354.048000] device-mapper: error adding target to table
[17184354.052000] device-mapper: dm-linear: Device lookup failed
[17184354.052000] device-mapper: error adding target to table
[17184354.052000] device-mapper: dm-linear: Device lookup failed
[17184354.056000] device-mapper: error adding target to table
[17184354.056000] device-mapper: dm-linear: Device lookup failed
[17184354.056000] device-mapper: error adding target to table
[17184354.060000] device-mapper: dm-linear: Device lookup failed
[17184354.060000] device-mapper: error adding target to table
[17199922.424000] usb 4-1.2: USB disconnect, address 4

Re: RAID5 array showing as degraded after motherboard replacement

[dean gaudet]

On Mon, 6 Nov 2006, James Lee wrote:

> Thanks for the reply Dean.  I looked through dmesg output from the
> boot up, to check whether this was just an ordering issue during the
> system start up (since both evms and mdadm attempt to activate the
> array, which could cause things to go wrong...).
> 
> Looking through the dmesg output though, it looks like the 'missing'
> disk is being detected before the array is assembled, but that the
> disk is throwing up errors.  I've attached the full output of dmesg;
> grepping it for "hde" gives the following:
> 
> [17179574.084000]     ide2: BM-DMA at 0xd400-0xd407, BIOS settings:
> hde:DMA, hdf:DMA
> [17179574.380000] hde: NetCell SyncRAID(TM) SR5000 JBOD, ATA DISK drive
> [17179575.312000] hde: max request size: 512KiB
> [17179575.312000] hde: 625134827 sectors (320069 MB), CHS=38912/255/63, (U)DMA
> [17179575.312000] hde: set_geometry_intr: status=0x51 { DriveReady
> SeekComplete Error }
> [17179575.312000] hde: set_geometry_intr: error=0x04 { DriveStatusError }
> [17179575.312000] hde: cache flushes supported

is it possible that the "NetCell SyncRAID" implementation is stealing some 
of the sectors (even though it's marked JBOD)?  anyhow it could be the 
disk is bad, but i'd still be tempted to see if the problem stays with the 
controller if you swap the disk with another in the array.

-dean

Re: RAID5 array showing as degraded after motherboard replacement

[James Lee]

On 06/11/06, dean gaudet <dean@arctic.org> wrote:
>
>
> On Mon, 6 Nov 2006, James Lee wrote:
>
> > Thanks for the reply Dean.  I looked through dmesg output from the
> > boot up, to check whether this was just an ordering issue during the
> > system start up (since both evms and mdadm attempt to activate the
> > array, which could cause things to go wrong...).
> >
> > Looking through the dmesg output though, it looks like the 'missing'
> > disk is being detected before the array is assembled, but that the
> > disk is throwing up errors.  I've attached the full output of dmesg;
> > grepping it for "hde" gives the following:
> >
> > [17179574.084000]     ide2: BM-DMA at 0xd400-0xd407, BIOS settings:
> > hde:DMA, hdf:DMA
> > [17179574.380000] hde: NetCell SyncRAID(TM) SR5000 JBOD, ATA DISK drive
> > [17179575.312000] hde: max request size: 512KiB
> > [17179575.312000] hde: 625134827 sectors (320069 MB), CHS=38912/255/63, (U)DMA
> > [17179575.312000] hde: set_geometry_intr: status=0x51 { DriveReady
> > SeekComplete Error }
> > [17179575.312000] hde: set_geometry_intr: error=0x04 { DriveStatusError }
> > [17179575.312000] hde: cache flushes supported
>
> is it possible that the "NetCell SyncRAID" implementation is stealing some
> of the sectors (even though it's marked JBOD)?  anyhow it could be the
> disk is bad, but i'd still be tempted to see if the problem stays with the
> controller if you swap the disk with another in the array.
>
> -dean
>

Looks like you might be right.  I removed one of the other drives from
the onboard controller, and moved the 'faulty' drive from the NetCell
controller to the onboard one.  Booted up up the machine, and the
drive is still not added to the array correctly (so the array now
fails to assemble, as there's only 3 out of 5 drives).  I've run the
Seagate diagnostics tools over the drive and they report successful
when it's connected to the onboard controller and unsuccessful when
it's connected to the NetCell controller (this may be a test tool
issue though).

I guess this indicates that either:
1) The NetCell controller is faulty and just not reading/writing data properly.
2) The NetCell controller's RAID implementation has somehow not been
transparent to the OS and has overwritten/modified md's superblocks.
3) EVMS somehow messed the config up on that drive when trying to
reassemble the array after the first time the controller came up.

I'll test for 1) by attaching another drive (not one of the ones in
the array!) to the NetCell contoller and seeing if it passed
diagnostics tests.  3) seems pretty unlikely.

I bought the NetCell card mainly for its Linux compatibility - do they
have known issues with mdadm?

Thanks,
James

Re: RAID5 array showing as degraded after motherboard replacement

[Bill Davidsen]

James Lee wrote:

> Hi there,
>
> I'm running a 5-drive software RAID5 array across two controllers.
> The motherboard in that PC recently died - I sent the board back for
> RMA.  When I refitted the motherboard, connected up all the drives,
> and booted up I found that the array was being reported as degraded
> (though all the data on it is intact).  I have 4 drives on the on
> board controller and 1 drive on an XFX Revo 64 SATA controller card.
> The drive which is being reported as not being in the array is the one
> connected to the XFX controller.
>
> The OS can see that drive fine, and "mdadm --examine" on that drive
> shows that it is part of the array and that there are 5 active devices
> in the array.  Doing "mdadm --examine" on one of the other four drives
> shows that the array has 4 active drives and one failed.  "mdadm
> --detail" for the array also shows 4 active and one failed.
>
> Now I haven't lost any data here and I know I can just force a resync
> of the array which is fine.  However I'm concerned about how this has
> happened.  One worry is that the XFX SATA controller is doing
> something funny to the drive.  I've noticed that it's BIOS has
> defaulted to RAID0 mode (even though there's only one drive on it) - I
> can't see how this would cause any particular problems here though.  I
> guess it's possible that some data on the drive got corrupted when the
> motherboard failed... 

I notice in your later post that the driver thinks this is a JBOD setup, 
can you either tell the controller to JBOD or force the driver to 
consider this a RAID0 single disk setup? I don't know what RAID0 on one 
drive means, but I suspect that having the controller in the mode you 
want is desirable. That might have been changed in the hardware failure.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979

Re: RAID5 array showing as degraded after motherboard replacement

[James Lee]

On 08/11/06, James Lee <james.lee@cantab.net> wrote:
> On 07/11/06, James Lee <james.lee@cantab.net> wrote:
> > On 06/11/06, dean gaudet <dean@arctic.org> wrote:
> > >
> > >
> > > On Mon, 6 Nov 2006, James Lee wrote:
> > >
> > > > Thanks for the reply Dean.  I looked through dmesg output from the
> > > > boot up, to check whether this was just an ordering issue during the
> > > > system start up (since both evms and mdadm attempt to activate the
> > > > array, which could cause things to go wrong...).
> > > >
> > > > Looking through the dmesg output though, it looks like the 'missing'
> > > > disk is being detected before the array is assembled, but that the
> > > > disk is throwing up errors.  I've attached the full output of dmesg;
> > > > grepping it for "hde" gives the following:
> > > >
> > > > [17179574.084000]     ide2: BM-DMA at 0xd400-0xd407, BIOS settings:
> > > > hde:DMA, hdf:DMA
> > > > [17179574.380000] hde: NetCell SyncRAID(TM) SR5000 JBOD, ATA DISK drive
> > > > [17179575.312000] hde: max request size: 512KiB
> > > > [17179575.312000] hde: 625134827 sectors (320069 MB), CHS=38912/255/63, (U)DMA
> > > > [17179575.312000] hde: set_geometry_intr: status=0x51 { DriveReady
> > > > SeekComplete Error }
> > > > [17179575.312000] hde: set_geometry_intr: error=0x04 { DriveStatusError }
> > > > [17179575.312000] hde: cache flushes supported
> > >
> > > is it possible that the "NetCell SyncRAID" implementation is stealing some
> > > of the sectors (even though it's marked JBOD)?  anyhow it could be the
> > > disk is bad, but i'd still be tempted to see if the problem stays with the
> > > controller if you swap the disk with another in the array.
> > >
> > > -dean
> > >
> >
> > Looks like you might be right.  I removed one of the other drives from
> > the onboard controller, and moved the 'faulty' drive from the NetCell
> > controller to the onboard one.  Booted up up the machine, and the
> > drive is still not added to the array correctly (so the array now
> > fails to assemble, as there's only 3 out of 5 drives).  I've run the
> > Seagate diagnostics tools over the drive and they report successful
> > when it's connected to the onboard controller and unsuccessful when
> > it's connected to the NetCell controller (this may be a test tool
> > issue though).
> >
> > I guess this indicates that either:
> > 1) The NetCell controller is faulty and just not reading/writing data properly.
> > 2) The NetCell controller's RAID implementation has somehow not been
> > transparent to the OS and has overwritten/modified md's superblocks.
> > 3) EVMS somehow messed the config up on that drive when trying to
> > reassemble the array after the first time the controller came up.
> >
> > I'll test for 1) by attaching another drive (not one of the ones in
> > the array!) to the NetCell contoller and seeing if it passed
> > diagnostics tests.  3) seems pretty unlikely.
> >
> > I bought the NetCell card mainly for its Linux compatibility - do they
> > have known issues with mdadm?
> >
> > Thanks,
> > James
> >
>
> Well I'm still a little unsure what might have happened here.  I've
> reconnected the 'bad' drive to the NetCell controller, and run
> badblocks over that device.  It isn't reporting any bad blocks at all,
> which I guess pretty much indicates that neither the hard drive nor
> the controller are faulty right?
>
> However I'm still seeing the error messages in my dmesg (the ones I
> posted earlier), and they suggest that there is some kind of hardware
> fault (based on a quick Google of the error codes).  So I'm a little
> confused.
>
> If the hard-drive and controller are not faulty, then how can I go
> about figuring out whether the drive got messed up by the controller
> going and overwriting some data due to it's internal RAIDing (which
> would seem unlikely - I'd assume this would have been reported and
> fixed as it would not just be a Linux problem)?  I guess the other
> possibility is that in the process of the motherboard dying, some data
> on the drive corrupted - does this seem at all plausible?
>
> Basically I'm just not sure how to move forward in a way that I can
> feel confident that this won't happen again (possibly in a more
> serious way that means losing all the data on the array).  Would
> dumping the sectors at the start of the drive help at all to figure
> out what's going on?
>

[Sorry for the double mail - forgot to CC the list]

Re: RAID5 array showing as degraded after motherboard replacement

[dean gaudet]

On Wed, 8 Nov 2006, James Lee wrote:

> > However I'm still seeing the error messages in my dmesg (the ones I
> > posted earlier), and they suggest that there is some kind of hardware
> > fault (based on a quick Google of the error codes).  So I'm a little
> > confused.

the fact that the error is in a geometry command really makes me wonder...

did you compare the number of blocks on the device vs. what seems to be 
available when it's on the weird raid card?

-dean