+ Post New Thread
Results 1 to 3 of 3
*nix Thread, Server wont boot after raid failure in Technical; I have a Fujitsu RX220 running with SATA disks and Software Raid 1. The second drive in the machine has ...
  1. #1

    Geoff's Avatar
    Join Date
    Jun 2005
    Location
    Fylde, Lancs, UK.
    Posts
    11,804
    Thank Post
    110
    Thanked 583 Times in 504 Posts
    Blog Entries
    1
    Rep Power
    224

    Server wont boot after raid failure

    I have a Fujitsu RX220 running with SATA disks and Software Raid 1. The second drive in the machine has failed (sdb). I have replaced it however the machine will not boot up correctly and allow me to rebuild the raid the usual way.

    I get the following errors on the initramfs shell screen:

    Code:
    Gave up waiting for root device
    
    ALERT! Device /dev/md1 was not found! Dropping to shell!
    I have tried running the mdadm command to assemble the array from the shell:

    Code:
    mdadm --assemble /dev/md1 /dev/sda1 /dev/sdb1
    Gives the error:

    Code:
    mdadm: cannot open device /dev/sda1: Device or resource busy
    mdadm: /dev/sda1 has no superblock - assembly aborted
    However
    Code:
    mdadm --misc --scan /dev/sda
    works as expected.

  2. #2

    Geoff's Avatar
    Join Date
    Jun 2005
    Location
    Fylde, Lancs, UK.
    Posts
    11,804
    Thank Post
    110
    Thanked 583 Times in 504 Posts
    Blog Entries
    1
    Rep Power
    224
    Just to keep people up to date. I've been bitten by this bug.

    https://bugs.launchpad.net/ubuntu/+s...er/+bug/358654

  3. #3

    Geoff's Avatar
    Join Date
    Jun 2005
    Location
    Fylde, Lancs, UK.
    Posts
    11,804
    Thank Post
    110
    Thanked 583 Times in 504 Posts
    Blog Entries
    1
    Rep Power
    224
    I have fixed this problem now.

    I booted the machine using an Ubuntu Server install CD with the 'rescue a broke system option'. This automatically detected and mounted the raid arrays as best it could (running off /dev/sda only).

    I then used the 'run root shell in /dev/md1' option to get me into the installed system.

    I then ran
    Code:
    aptitude update && dpkg --configure -a
    to fix the initramfs issue.

    I then did

    Code:
    sfdisk -d /dev/sda | sfdisk /dev/sdb
    mdadm --manage /dev/md0 --fail /dev/sdb1
    mdadm --manage /dev/md0 --remove /dev/sdb1
    mdadm --manage /dev/md0 --add /dev/sdb1
    mdadm --manage /dev/md1 --fail /dev/sdb3
    mdadm --manage /dev/md1 --remove /dev/sdb3
    mdadm --manage /dev/md1 --add /dev/sdb3
    which fixes the raid1 arrays.

    Code:
    root@goliath:~# cat /proc/mdstat
    Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
    md1 : active raid1 sda3[0] sdb3[1]
          485452096 blocks [2/2] [UU]
    
    md0 : active raid1 sda1[0] sdb1[1]
          979840 blocks [2/2] [UU]
    
    unused devices: <none>
    alll better.

  4. Thanks to Geoff from:

    dhicks (21st August 2009)

SHARE:
+ Post New Thread

Similar Threads

  1. pc wont boot up
    By yusuf7 in forum Windows Vista
    Replies: 15
    Last Post: 22nd July 2009, 08:16 PM
  2. Windows boot failure
    By lionsl2005 in forum Windows
    Replies: 10
    Last Post: 17th December 2008, 02:51 PM
  3. iMac G3 wont boot
    By sidewinder in forum Mac
    Replies: 9
    Last Post: 21st November 2006, 08:58 AM
  4. iBook G4 wont boot
    By sidewinder in forum Mac
    Replies: 11
    Last Post: 16th November 2006, 09:50 AM
  5. IDE HDD boot sector failure
    By e_g_r in forum Hardware
    Replies: 1
    Last Post: 23rd November 2005, 10:03 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •