LinuxQuestions.org - Software RAID Failure?

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - Software RAID Failure? (https://www.linuxquestions.org/questions/linux-general-1/software-raid-failure-569126/)

Software RAID Failure?

Guys - I am not sure what happened here but I think I have a problem with RAID (software) on my home machine. I am using it fine now however during boot up, I see something scroll by in red however it is un-readable at 100 mph so I decided to check out some md stats on the box to see if something happened to a disk or RAID array I setup and I can't understand what I am looking at so perhaps you guys can help.

To make things as clear as possible, I have 2 identical drives on the machine both via S-ATA. The drives are 2x Western Digital 160GB disks and I am pretty sure they are both good but I am not sure.

Here is what I see:

Code:

tunafish:/home/cwilliams/Desktop# mdadm --detail /dev/md0

/dev/md0:

        Version : 00.90.03

  Creation Time : Fri Jun 22 21:20:43 2007

    Raid Level : raid1

    Array Size : 19534976 (18.63 GiB 20.00 GB)

  Used Dev Size : 19534976 (18.63 GiB 20.00 GB)

  Raid Devices : 2

  Total Devices : 1

Preferred Minor : 0

    Persistence : Superblock is persistent



    Update Time : Fri Jul 13 15:03:20 2007

          State : clean, degraded

 Active Devices : 1

Working Devices : 1

 Failed Devices : 0

  Spare Devices : 0



          UUID : 93f4ddb3:70d5783e:f47a10c4:9fe19ef3

        Events : 0.6582



    Number  Major  Minor  RaidDevice State

      0      8        3        0      active sync  /dev/sda3

      1      0        0        1      removed

As you can see there is a section that should match up below as /dev/sdb3 however it shows remove...:confused:

Then there is my 2nd RAID

Code:

tunafish:/home/cwilliams/Desktop# mdadm --detail /dev/md1

/dev/md1:

        Version : 00.90.03

  Creation Time : Fri Jun 22 21:20:49 2007

    Raid Level : raid1

    Array Size : 135275264 (129.01 GiB 138.52 GB)

  Used Dev Size : 135275264 (129.01 GiB 138.52 GB)

  Raid Devices : 2

  Total Devices : 1

Preferred Minor : 1

    Persistence : Superblock is persistent



    Update Time : Fri Jul 13 15:08:02 2007

          State : clean, degraded

 Active Devices : 1

Working Devices : 1

 Failed Devices : 0

  Spare Devices : 0



          UUID : c627213e:cbaed46d:6510c67a:3cf96311

        Events : 0.4564



    Number  Major  Minor  RaidDevice State

      0      8        4        0      active sync  /dev/sda4

      1      0        0        1      removed

Is one of my disks bad? What should I do? Should I place an identical spare in place of /dev/sdb and see if it starts to rebuild?

Both drives feel warm to touch as they are both getting power and I visible in the BIOS so I know it sees the drives but perhaps it has failed sectors on the disk, I don't know...

Code:

tunafish:/home/cwilliams/Desktop# cat /proc/mdstat

Personalities : [raid1]

md1 : active raid1 sda4[0]

      135275264 blocks [2/1] [U_]



md0 : active raid1 sda3[0]

      19534976 blocks [2/1] [U_]



unused devices: <none>

Suggestions or comments from data above?

Check /var/log/messages for errors. Before replacing, see if you can readd the drive:

mdadm /dev/md0 --re-add /dev/sdb3
mdadm /dev/md1 --re-add /dev/sdb4

This is all I found in /var/log/messages...

Can you make anything from this?

***********

Jul 11 21:22:42 tunafish kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Jul 11 21:22:42 tunafish kernel: md: bitmap version 4.39
Jul 11 21:22:42 tunafish kernel: md: raid1 personality registered for level 1
Jul 11 21:22:42 tunafish kernel: md: md0 stopped.
Jul 11 21:22:42 tunafish kernel: md: bind<sda3>
Jul 11 21:22:42 tunafish kernel: md: bind<sdb3>
Jul 11 21:22:42 tunafish kernel: md: kicking non-fresh sda3 from array!
Jul 11 21:22:42 tunafish kernel: md: unbind<sda3>
Jul 11 21:22:42 tunafish kernel: md: export_rdev(sda3)
Jul 11 21:22:42 tunafish kernel: raid1: raid set md0 active with 1 out of 2 mirrors
Jul 11 21:22:42 tunafish kernel: md: md1 stopped.
Jul 11 21:22:42 tunafish kernel: md: bind<sda4>
Jul 11 21:22:42 tunafish kernel: md: bind<sdb4>
Jul 11 21:22:42 tunafish kernel: md: kicking non-fresh sda4 from array!
Jul 11 21:22:42 tunafish kernel: md: unbind<sda4>
Jul 11 21:22:42 tunafish kernel: md: export_rdev(sda4)
Jul 11 21:22:42 tunafish kernel: raid1: raid set md1 active with 1 out of 2 mirrors
Jul 11 21:22:42 tunafish kernel: Attempting manual resume
Jul 11 21:22:42 tunafish kernel: EXT3-fs: INFO: recovery required on readonly filesystem.
Jul 11 21:22:42 tunafish kernel: EXT3-fs: write access will be enabled during recovery.
Jul 11 21:22:42 tunafish kernel: kjournald starting. Commit interval 5 seconds
Jul 11 21:22:42 tunafish kernel: EXT3-fs: recovery complete.
Jul 11 21:22:42 tunafish kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 11 21:22:42 tunafish kernel: ts: Compaq touchscreen protocol output
Jul 11 21:22:42 tunafish kernel: input: PC Speaker as /class/input/input3
Jul 11 21:22:42 tunafish kernel: Real Time Clock Driver v1.12ac
Jul 11 21:22:42 tunafish kernel: i2c_adapter i2c-0: nForce2 SMBus adapter at 0x1c00
Jul 11 21:22:42 tunafish kernel: i2c_adapter i2c-1: nForce2 SMBus adapter at 0x1c80
Jul 11 21:22:42 tunafish kernel: ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 20
Jul 11 21:22:42 tunafish kernel: ACPI: PCI Interrupt 0000:00:0f.1[B] -> Link [AAZA] -> GSI 20 (level, low) -> IRQ 90
Jul 11 21:22:42 tunafish kernel: hda_codec: Unknown model for AD1988, trying auto-probe from BIOS...
Jul 11 21:22:42 tunafish kernel: Adding 497972k swap on /dev/sda1. Priority:-1 extents:1 across:497972k
Jul 11 21:22:42 tunafish kernel: Adding 497972k swap on /dev/sdb1. Priority:-2 extents:1 across:497972k
Jul 11 21:22:42 tunafish kernel: EXT3 FS on md0, internal journal
Jul 11 21:22:42 tunafish kernel: loop: loaded (max 8 devices)
Jul 11 21:22:42 tunafish kernel: device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
Jul 11 21:22:42 tunafish kernel: kjournald starting. Commit interval 5 seconds
Jul 11 21:22:42 tunafish kernel: EXT3 FS on sda2, internal journal
Jul 11 21:22:42 tunafish kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 11 21:22:42 tunafish kernel: kjournald starting. Commit interval 5 seconds
Jul 11 21:22:42 tunafish kernel: EXT3 FS on md1, internal journal
Jul 11 21:22:42 tunafish kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 11 21:22:42 tunafish kernel: kjournald starting. Commit interval 5 seconds
Jul 11 21:22:42 tunafish kernel: EXT3 FS on sdb2, internal journal
Jul 11 21:22:42 tunafish kernel: EXT3-fs: mounted filesystem with ordered data mode.

The "md: kicking non-fresh sdxx from array!" message indicates that the array was not stopped gracefully previously (e.g., poweroff). You should be able to re-add the drives.