Koozali.org formerly Contribs.org

Raid disk failure - cannot get same size disk

Offline tlicht

  • **
  • 56
  • Imagination is more important than knowledge.
Raid disk failure - cannot get same size disk
« on: February 02, 2008, 07:28:07 PM »
Hi,
The server (SME 6,5) sent the following alert:
Code: [Select]
Feb  1 15:53:39 hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Feb  1 15:53:39 hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=2639328, high=0, low=2639328, sector=20728
Feb  1 15:53:39 end_request: I/O error, dev 03:43 (hdb), sector 20728
Feb  1 15:53:39 raid1: Disk failure on hdb3, disabling device. 
Feb  1 15:53:39 raid1: hdb3: rescheduling block 20728
Feb  1 15:53:39 md1: no spare disk to reconstruct array! -- continuing in degraded mode
Feb  1 15:53:39 md: (skipping faulty hdb3 )
Feb  1 15:53:39 raid1: hda3: redirecting sector 20728 to another mirror
Feb  1 15:53:39 hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Feb  1 15:53:39 hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=2639328, high=0, low=2639328, sector=20728
Feb  1 15:53:39 end_request: I/O error, dev 03:43 (hdb), sector 20728
Feb  1 15:53:39 raid1: Disk failure on hdb3, disabling device. 
Feb  1 15:53:39 raid1: hdb3: rescheduling block 20728
Feb  1 15:53:39 md1: no spare disk to reconstruct array! -- continuing in degraded mode
Feb  1 15:53:39 md: (skipping faulty hdb3 )
Feb  1 15:53:39 raid1: hda3: redirecting sector 20728 to another mirror

I restarted it today and saw the following in the startup log:
Code: [Select]
Feb 2 13:11:23 lflsrvr kernel: md: considering hda3 ...
Feb 2 13:11:23 lflsrvr kernel: md: adding hda3 ...
Feb 2 13:11:23 lflsrvr kernel: md: adding hdb3 ...
Feb 2 13:11:23 lflsrvr kernel: md: created mdl
Feb 2 13:11:23 lflsrvr kernel: md: bind<hdb3,1>
Feb 2 13:11:23 lflsrvr kernel: md: bind<hda3,2>
Feb 2 13:11:23 lflsrvr kernel: md: running: <hda3><hdb3>
Feb 2 13:11:23 lflsrvr kernel: md: hda3's event counter: 00000033
Feb 2 13:11:23 lflsrvr kernel: md: hdb3's event counter: 00000031
Feb 2 13:11:23 lflsrvr kernel: md: superblock update time inconsistency -using the most recent one
Feb 2 13:11:23 lflsrvr kernel: md: freshest: hda3
Feb 2 13:11:23 lflsrvr kernel: md: kicking non-fresh hdb3 from array!
Feb 2 13:11:23 lflsrvr kernel: md: unbind<hdb3,1>
Feb 2 13:11:23 lflsrvr kernel: md: export_rdev(hdb3)
Feb 2 13:11:23 lflsrvr kernel: mdl: removing former faulty hdb3!
Feb 2 13:11:23 lflsrvr kernel: md: RAID level 1 does not need chunksize! Continuing anyway.
Feb 2 13:11:23 lflsrvr kernel: mdl: max total readahead window set to 124k
Feb 2 13:11:23 lflsrvr kernel: mdl: 1 data-disks, max readahead per data-disk: 124k
Feb 2 13:11:23 lflsrvr kernel: raidl: device hda3 operational as mirror 0
Feb 2 13:11:23 lflsrvr kernel: raidl: mdl, not all disks are operational -trying to recover array
Feb 2 13:11:23 lflsrvr kernel: raidl: raid set mdl active with 1 out of 2 mirrors
Feb 2 13:11:23 lflsrvr kernel: md: updating mdl RAID superblock on device
Feb 2 13:11:23 lflsrvr kernel: md: hda3 events: 00000034]<6>(write) hda3's sb offset: 119314688
Feb 2 13:11:23 lflsrvr kernel: md: recovery thread got woken up ...
Feb 2 13:11:23 lflsrvr kernel: mdl: no spare disk to reconstruct array! -continuing in degraded mode
Feb 2 13:11:23 lflsrvr kernel: md: recovery thread finished ...
Feb 2 13:11:23 lflsrvr kernel: md: ... autorun DONE.
Feb 2 13:11:23 lflsrvr kernel: kjournald starting. Commit interval 5 seconds
Feb 2 13:11:23 lflsrvr kernel: ExT3-fs: mounted filesystem with ordered data mode.

I imagine that this means that hdb needs to be replaced. Since the server is a couple of years old, I don't seem to be able to find another 120 GB disk. I have a 160 GB disk I am planning to use.

I would be grateful for suggestions as to how to accomplish the changeover....

Offline raem

  • *
  • 3,972
Re: Raid disk failure - cannot get same size disk
« Reply #1 on: February 04, 2008, 07:59:47 AM »
tlicht

Quote
....I don't seem to be able to find another 120 GB disk. I have a 160 GB disk I am planning to use.

The 160Gb can be added to the existing (working) 120GB, you would just partition it to the smaller size and sacrifice 40Gb.
See my other answers in your related posts.
...

Offline tlicht

  • **
  • 56
  • Imagination is more important than knowledge.
Re: Raid disk failure - cannot get same size disk
« Reply #2 on: February 04, 2008, 07:35:50 PM »
Thanx Ray,

It turned out that I could readd and resync the old disk, so now I have a spare 160 Gb IDE...  :smile:
Being very basic in linux it took some time to figure out how to manage it, an a lot of reading on the net.