Re: degraded array - former device is unavailable

From: Philip Ross (psr_at_warwickcompsoc.co.uk)
Date: 06/28/05

  • Next message: Bob Proulx: "Re: [Re-asking] Group limitation of 32 in Sarge with kernel 2.6" 
    To: debian-user@lists.debian.org
Date: Tue, 28 Jun 2005 15:57:06 +0100

    David Svejda wrote:
    > I've problem with software RAID 1. I've installed Debian 3.1 and
    > everything went ok.The machine was running for few days, then it was
    > halted due to power supply failure.
    >
    > Then, after reboot, there is an error on md0 device as seen in
    > /var/log/dmesg:
    >
    > md0: former device ide/host0/bus0/target1/lun0/part1 is unavailable,
    > removing from array!

    Have you managed to resolve this issue?

    I'm getting exactly the same problem after upgrading a test system from
    Woody to Sarge. Every time I reboot the md raid1 root device is failing
    to come up with both mirrors (see dmesg output below). When I add the
    missing mirror manually using mdadm everything works fine up until the
    next reboot.

    Both partitions are set as Linux raid autodetect.

    Other raid1 md devices on the machine (mounted on /home and /boot) start
    up without any problems.

    I've created a new /etc/mdadm/mdadm.conf file as per the instructions in
    the Sarge release notes
    (http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html#s-mdadm)

    I'm only seeing the problems with the 2.4.27-2-686 kernel from Sarge. If
    I drop back to Woody's 2.4.18-1-686 kernel, everything works fine.

    Does anyone have any ideas as to what is going on here?

    Please CC me on any replies as I'm not currently subscribed to the list.

    Thanks,

    Phil

    PIIX4: IDE controller at PCI slot 00:07.1
    PIIX4: chipset revision 1
    PIIX4: not 100% native mode: will probe irqs later
         ide0: BM-DMA at 0x1410-0x1417, BIOS settings: hda:DMA, hdb:pio
         ide1: BM-DMA at 0x1418-0x141f, BIOS settings: hdc:DMA, hdd:DMA
    hda: VMware Virtual IDE Hard Drive, ATA DISK drive
    blk: queue c883ecc0, I/O limit 4095Mb (mask 0xffffffff)
    hdc: VMware Virtual IDE Hard Drive, ATA DISK drive
    hdd: VMware Virtual IDE CDROM Drive, ATAPI CD/DVD-ROM drive
    blk: queue c883f114, I/O limit 4095Mb (mask 0xffffffff)
    ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
    ide1 at 0x170-0x177,0x376 on irq 15
    hda: attached ide-disk driver.
    hda: 8388608 sectors (4295 MB) w/32KiB Cache, CHS=8322/16/63, UDMA(33)
    hdc: attached ide-disk driver.
    hdc: 13631488 sectors (6979 MB) w/32KiB Cache, CHS=13523/16/63, UDMA(33)
    Partition check:
      /dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 >
      /dev/ide/host0/bus1/target0/lun0: p1 p2 < p5 p6 p7 p8 >
      [events: 00000045]
    md: bind<ide/host0/bus0/target0/lun0/part5,1>
    md: ide/host0/bus0/target0/lun0/part5's event counter: 00000045
    md5: former device ide/host0/bus1/target0/lun0/part5 is unavailable,
    removing from array!
    md: RAID level 1 does not need chunksize! Continuing anyway.
    md5: max total readahead window set to 124k
    md5: 1 data-disks, max readahead per data-disk: 124k
    raid1: device ide/host0/bus0/target0/lun0/part5 operational as mirror 0
    raid1: md5, not all disks are operational -- trying to recover array
    raid1: raid set md5 active with 1 out of 2 mirrors
    md: updating md5 RAID superblock on device
    md: ide/host0/bus0/target0/lun0/part5 [events: 00000046]<6>(write)
    ide/host0/bus0/target0/lun0/part5's sb offset: 2929600
    md: recovery thread got woken up ...
    md5: no spare disk to reconstruct array! -- continuing in degraded mode
    md: recovery thread finished ...
    Journalled Block Device driver loaded
    kjournald starting. Commit interval 5 seconds
    EXT3-fs: mounted filesystem with ordered data mode.
    Adding Swap: 97736k swap-space (priority -1)
    Adding Swap: 97740k swap-space (priority -2)
    EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,5), internal journal
    Real Time Clock Driver v1.10f
    pcnet32.c:v1.30c 05.25.2004 tsbogend@alpha.franken.de
    pcnet32: PCnet/PCI II 79C970A at 0x1080, 00 0c 29 69 18 b2 assigned IRQ 18.
    eth0: registered as PCnet/PCI II 79C970A
    pcnet32: 1 cards_found.
    device-mapper: 4.1.1-ioctl (2004-04-07) initialised: dm-devel@redhat.com
      [events: 00000039]
    md: bind<ide/host0/bus1/target0/lun0/part1,1>
      [events: 00000039]
    md: bind<ide/host0/bus0/target0/lun0/part1,2>
    md: ide/host0/bus0/target0/lun0/part1's event counter: 00000039
    md: ide/host0/bus1/target0/lun0/part1's event counter: 00000039
    md: RAID level 1 does not need chunksize! Continuing anyway.
    md1: max total readahead window set to 124k
    md1: 1 data-disks, max readahead per data-disk: 124k
    raid1: device ide/host0/bus0/target0/lun0/part1 operational as mirror 0
    raid1: device ide/host0/bus1/target0/lun0/part1 operational as mirror 1
    raid1: raid set md1 active with 2 out of 2 mirrors
    md: updating md1 RAID superblock on device
    md: ide/host0/bus0/target0/lun0/part1 [events: 0000003a]<6>(write)
    ide/host0/bus0/target0/lun0/part1's sb offset: 97664
    md: ide/host0/bus1/target0/lun0/part1 [events: 0000003a]<6>(write)
    ide/host0/bus1/target0/lun0/part1's sb offset: 97664
      [events: 00000039]
    md: bind<ide/host0/bus1/target0/lun0/part7,1>
      [events: 00000039]
    md: bind<ide/host0/bus0/target0/lun0/part7,2>
    md: ide/host0/bus0/target0/lun0/part7's event counter: 00000039
    md: ide/host0/bus1/target0/lun0/part7's event counter: 00000039
    md: RAID level 1 does not need chunksize! Continuing anyway.
    md7: max total readahead window set to 124k
    md7: 1 data-disks, max readahead per data-disk: 124k
    raid1: device ide/host0/bus0/target0/lun0/part7 operational as mirror 0
    raid1: device ide/host0/bus1/target0/lun0/part7 operational as mirror 1
    raid1: raid set md7 active with 2 out of 2 mirrors
    md: updating md7 RAID superblock on device
    md: ide/host0/bus0/target0/lun0/part7 [events: 0000003a]<6>(write)
    ide/host0/bus0/target0/lun0/part7's sb offset: 1068864
    md: ide/host0/bus1/target0/lun0/part7 [events: 0000003a]<6>(write)
    ide/host0/bus1/target0/lun0/part7's sb offset: 1068864
    kjournald starting. Commit interval 5 seconds
    EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,1), internal journal
    EXT3-fs: mounted filesystem with ordered data mode.
    kjournald starting. Commit interval 5 seconds
    EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,7), internal journal
    EXT3-fs: mounted filesystem with ordered data mode.

    # fdisk /dev/hda

    The number of cylinders for this disk is set to 8322.
    There is nothing wrong with that, but this is larger than 1024,
    and could in certain setups cause problems with:
    1) software that runs at boot time (e.g., old versions of LILO)
    2) booting and partitioning software from other OSs
        (e.g., DOS FDISK, OS/2 FDISK)

    Command (m for help): p

    Disk /dev/hda: 4294 MB, 4294967296 bytes
    16 heads, 63 sectors/track, 8322 cylinders
    Units = cylinders of 1008 * 512 = 516096 bytes

        Device Boot Start End Blocks Id System
    /dev/hda1 1 194 97744+ fd Linux raid
    autodetect
    /dev/hda2 195 8322 4096512 5 Extended
    /dev/hda5 195 6007 2929720+ fd Linux raid
    autodetect
    /dev/hda6 6008 6201 97744+ 82 Linux swap / Solaris
    /dev/hda7 6202 8322 1068952+ fd Linux raid
    autodetect

    Command (m for help): q

    # fdisk /dev/hdc

    The number of cylinders for this disk is set to 13523.
    There is nothing wrong with that, but this is larger than 1024,
    and could in certain setups cause problems with:
    1) software that runs at boot time (e.g., old versions of LILO)
    2) booting and partitioning software from other OSs
        (e.g., DOS FDISK, OS/2 FDISK)

    Command (m for help): p

    Disk /dev/hdc: 6979 MB, 6979321856 bytes
    16 heads, 63 sectors/track, 13523 cylinders
    Units = cylinders of 1008 * 512 = 516096 bytes

        Device Boot Start End Blocks Id System
    /dev/hdc1 1 194 97744+ fd Linux raid
    autodetect
    /dev/hdc2 195 13523 6717816 5 Extended
    /dev/hdc5 195 6007 2929720+ fd Linux raid
    autodetect
    /dev/hdc6 6008 6201 97744+ 82 Linux swap / Solaris
    /dev/hdc7 6202 8322 1068952+ fd Linux raid
    autodetect
    /dev/hdc8 8323 13523 2621272+ 83 Linux

    Command (m for help): q 

    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Bob Proulx: "Re: [Re-asking] Group limitation of 32 in Sarge with kernel 2.6"

    Relevant Pages

    • Re: Problem with Raid Array persistence across reboots.
      ... I recently set up a Sarge box, with raid and LVM. ... 0000:00:00.0 Host bridge: Intel Corp. Server Memory Controller Hub ... Install base system: ...
      (Debian-User)
    • SW Raid - rebuilding array ?
      ... It booted up ok after the OS install and the raid looked good. ... md0: 1 data-disks, ... raid1: device hda1 operational as mirror 0 ... md2: max total readahead window set to 124k ...
      (comp.os.linux.hardware)
    • Re: Possible to delete RAID metadata from hard drives?
      ... You can mount the disks individually by first breaking ... Depending on the version of the RAID tools ... The next autodetect will assemble the ... Linux parition). ...
      (comp.sys.ibm.pc.hardware.storage)