Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: raid1, crypt, now can't mount....

  1. #1

    Exclamation raid1, crypt, now can't mount....

    I've been beating my head against this for the second day now, and think I'm going in circles now, so could use some external guidance please.
    This is in a laptop with two hard drives running opensuse 11.1.
    I setup raid1 (mirror) between the two drives.
    md0 mounts root / using sda8 and sdb8
    md1 mounts /home user sda9 and sdb9

    /home is also encrypted (LUKS password at boot time).
    And I (think) I added a second layer of encryption (but not sure at this point) encrypted the specific director /home/user.

    This system has been purring along fine with this setup for months. All of a sudden on a boot up yesterday afternoon (it was working earlier on bootup that morning), I couldn't access /home anymore. It didn't ask for the LUKS password, and showed errors on the bootup indicating that the md1 was not a device, and so crypt couldn't load.
    md0 loads fine (root).

    When the system boots or runs /etc/init.d/boot.crypt-early it fails because md1 fails (or the interdependency between them).

    Here is some output, maybe folks can help point me in the right direction, I've tried dozens of sites and forums approaches from previous others postings, but not quite getting there.

    Here some info:

    v9:/ # cat /etc/mdadm.conf
    DEVICE partitions
    ARRAY /dev/md0 level=raid1 UUID=cc67b93f:c23c38d7:6a446079:1726b629
    ARRAY /dev/md1 level=raid1 UUID=adb90daa:7e594eba:f6dc04c6:73a5d54a


    cat /etc/crypttab
    cr_md1 /dev/md1 none none

    mdadm -E /dev/sda9
    /dev/sda9:
    Magic : a92b4efc
    Version : 1.0
    Feature Map : 0x1
    Array UUID : adb90daa:7e594eba:f6dc04c6:73a5d54a
    Name : 1
    Creation Time : Fri Dec 5 20:22:43 2008
    Raid Level : raid1
    Raid Devices : 2

    Avail Dev Size : 104920304 (50.03 GiB 53.72 GB)
    Array Size : 104920304 (50.03 GiB 53.72 GB)
    Super Offset : 104920432 sectors
    State : active
    Device UUID : 7d0b8cee:55afb0b5:2f6d4ca3:c820e941

    Internal Bitmap : -101 sectors from superblock
    Update Time : Tue Apr 7 10:30:12 2009
    Checksum : 4dad99ba - correct
    Events : 0


    Array Slot : 2 (0, 1)
    Array State : uu



    mdadm -E /dev/sdb9
    /dev/sdb9:
    Magic : a92b4efc
    Version : 1.0
    Feature Map : 0x1
    Array UUID : adb90daa:7e594eba:f6dc04c6:73a5d54a
    Name : 1
    Creation Time : Fri Dec 5 20:22:43 2008
    Raid Level : raid1
    Raid Devices : 2

    Avail Dev Size : 104920304 (50.03 GiB 53.72 GB)
    Array Size : 104920304 (50.03 GiB 53.72 GB)
    Super Offset : 104920432 sectors
    State : active
    Device UUID : 776ec64a:5a5f3aef:37170c0e:0969cccb

    Internal Bitmap : -101 sectors from superblock
    Update Time : Tue Apr 7 10:30:12 2009
    Checksum : d8149f11 - correct
    Events : 17


    Array Slot : 1 (0, 1)
    Array State : uU



    cat /proc/mdstat
    Personalities : [raid1] [raid0] [raid6] [raid5] [raid4]
    md0 : active raid1 sdb8[0] sda8[1]
    31463196 blocks super 1.0 [2/2] [UU]
    bitmap: 3/241 pages [12KB], 64KB chunk

    unused devices: <none>

    dv9:/ # /etc/init.d/boot.crypto-early start
    Activating crypto devices using /etc/crypttab ...
    Command failed: Not a block device
    /dev/md1... failed

    dv9:/ # /etc/init.d/boot.md start
    Starting MD Raid mdadm: failed to RUN_ARRAY /dev/md/1: Input/output error
    failed

    dv9:/ # mdadm -S /dev/md1
    mdadm: stopped /dev/md1
    dv9:/ # mdadm -A /dev/md1
    mdadm: failed to RUN_ARRAY /dev/md/1: Input/output error


    /var/log/messages:
    Apr 8 12:13:53 dv9 kernel: md: md1 stopped.
    Apr 8 12:13:53 dv9 kernel: md: bind<sda9>
    Apr 8 12:13:53 dv9 kernel: md: bind<sdb9>
    Apr 8 12:13:53 dv9 kernel: md: kicking non-fresh sda9 from array!
    Apr 8 12:13:53 dv9 kernel: md: unbind<sda9>
    Apr 8 12:13:53 dv9 kernel: md: export_rdev(sda9)
    Apr 8 12:13:53 dv9 kernel: md: md1: raid array is not clean -- starting background reconstruction
    Apr 8 12:13:53 dv9 kernel: raid1: raid set md1 active with 1 out of 2 mirrors
    Apr 8 12:13:53 dv9 kernel: md1: bitmap file is out of date, doing full recovery
    Apr 8 12:13:53 dv9 kernel: md1: bitmap initialisation failed: -5
    Apr 8 12:13:53 dv9 kernel: md1: failed to create bitmap (-5)



    Thanks for any suggestions.





    What else can I provide? Does anything jump out at anyone as to what's wrong?

    I've run the BIOS's HD test and checked smart and no errors on either drive there.

  2. #2

    Default Re: raid1, crypt, now can't mount....

    Oh, and additional information:

    mdadm --version
    mdadm - v3.0-devel2 - 5th November 2008


    uname -a
    Linux dv9 2.6.27.19-3.2-default #1 SMP 2009-02-25 15:40:44 +0100 x86_64 x86_64 x86_64 GNU/Linux

    rpm -qa | grep crypt
    cryptsetup-1.0.5_SVNr46-57.12
    cryptconfig-32bit-0.3-63.26
    libxcrypt-3.0.1-25.29
    libxcrypt-32bit-3.0.1-25.20
    libcryptsetup0-1.0.5_SVNr46-57.12
    python-crypto-2.0.1-28.81
    libgcrypt11-32bit-1.4.1-4.1
    libgcrypt-devel-1.4.1-4.1
    libgcrypt11-1.4.1-4.1
    cryptconfig-0.3-63.28

  3. #3

    Default Re: raid1, crypt, now can't mount....

    When attempting to just load with one drive in the array, does not work either...

    dv9:/ # mdadm -S /dev/md1
    mdadm: stopped /dev/md1
    dv9:/ # mdadm --assemble --run /dev/md1 /dev/sdb9
    mdadm: failed to RUN_ARRAY /dev/md/1: Input/output error


    /var/log/messages:
    Apr 8 14:37:53 dv9 kernel: md: md1 stopped.
    Apr 8 14:37:53 dv9 kernel: md: bind<sdb9>
    Apr 8 14:37:53 dv9 kernel: md: md1: raid array is not clean -- starting background reconstruction
    Apr 8 14:37:53 dv9 kernel: raid1: raid set md1 active with 1 out of 2 mirrors
    Apr 8 14:37:53 dv9 kernel: md1: bitmap file is out of date, doing full recovery
    Apr 8 14:37:54 dv9 kernel: md1: bitmap initialisation failed: -5
    Apr 8 14:37:54 dv9 kernel: md1: failed to create bitmap (-5)

  4. #4

    Default Re: raid1, crypt, now can't mount....

    dv9:/ # mdadm -D /dev/md1
    /dev/md1:
    Version : 1.00
    Creation Time : Fri Dec 5 20:22:43 2008
    Raid Level : raid1
    Used Dev Size : 52460152 (50.03 GiB 53.72 GB)
    Raid Devices : 2
    Total Devices : 1
    Persistence : Superblock is persistent

    Update Time : Tue Apr 7 10:30:12 2009
    State : active, degraded, Not Started
    Active Devices : 1
    Working Devices : 1
    Failed Devices : 0
    Spare Devices : 0

    Name : 1
    UUID : adb90daa:7e594eba:f6dc04c6:73a5d54a
    Events : 17

    Number Major Minor RaidDevice State
    0 0 0 0 removed
    1 8 25 1 active sync /dev/sdb9

  5. #5

    Default Re: raid1, crypt, now can't mount....

    dv9:/ # cat /proc/mdstat
    Personalities : [raid1] [raid0] [raid6] [raid5] [raid4]
    md1 : inactive sdb9[1]
    52460152 blocks super 1.0

    md0 : active raid1 sdb8[0] sda8[1]
    31463196 blocks super 1.0 [2/2] [UU]
    bitmap: 5/241 pages [20KB], 64KB chunk

    unused devices: <none>

  6. #6

    Default Re: raid1, crypt, now can't mount....

    dv9:/ # mdadm /dev/md1 --fail /dev/sda9 --remove /dev/sda9
    mdadm: set device faulty failed for /dev/sda9: No such device
    dv9:/ # mdadm /dev/md1 --re-add /dev/sda9
    mdadm: add new device failed for /dev/sda9 as 2: Invalid argument

  7. #7

    Default Re: raid1, crypt, now can't mount....

    dv9 kernel: md1: ADD_NEW_DISK not supported
    dv9 kernel: md1: ADD_NEW_DISK not supported

  8. #8

    Default Re: raid1, crypt, now can't mount....

    v9:/ # mdadm --examine-bitmap /dev/sdb9
    Filename : /dev/sdb9
    Magic : 6d746962
    Version : 4
    UUID : adb90daa:7e594eba:f6dc04c6:73a5d54a
    Events : 17
    Events Cleared : 16
    State : Out of date
    Chunksize : 128 KB
    Daemon : 5s flush period
    Write Mode : Normal
    Sync Size : 52460152 (50.03 GiB 53.72 GB)
    Bitmap : 409845 bits (chunks), 391168 dirty (95.4%)

  9. #9

    Default Re: raid1, crypt, now can't mount....

    Notice how sda9 looks compared to previosly posted sdb9....

    dv9:/ # mdadm --examine-bitmap /dev/sda9
    Filename : /dev/sda9
    Magic : 6d746962
    Version : 4
    UUID : adb90daa:7e594eba:f6dc04c6:73a5d54a
    Events : 17
    Events Cleared : 16
    State : Out of date
    Chunksize : 128 KB
    Daemon : 5s flush period
    Write Mode : Normal
    Sync Size : 52460152 (50.03 GiB 53.72 GB)
    Bitmap : 409845 bits (chunks), 409845 dirty (100.0%)

  10. #10

    Default Re: raid1, crypt, now can't mount....

    dv9:/ # fdisk -l /dev/sda

    Disk /dev/sda: 120.0 GB, 120034123776 bytes
    255 heads, 63 sectors/track, 14593 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x282d282d

    Device Boot Start End Blocks Id System
    /dev/sda1 1 64 514048+ 6 FAT16
    /dev/sda2 * 65 14592 116696160 f W95 Ext'd (LBA)
    /dev/sda5 65 3888 30716248+ b W95 FAT32
    /dev/sda6 3889 3952 514048+ 83 Linux
    /dev/sda7 3953 4144 1542208+ 82 Linux swap / Solaris
    /dev/sda8 4145 8061 31463271 fd Linux raid autodetect
    /dev/sda9 8062 14592 52460226 fd Linux raid autodetect
    dv9:/ # fdisk -l /dev/sdb

    Disk /dev/sdb: 120.0 GB, 120034123776 bytes
    255 heads, 63 sectors/track, 14593 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x000ec89e

    Device Boot Start End Blocks Id System
    /dev/sdb1 1 64 514048+ 7 HPFS/NTFS
    /dev/sdb2 65 14592 116696160 f W95 Ext'd (LBA)
    /dev/sdb5 65 3888 30716248+ 7 HPFS/NTFS
    /dev/sdb6 3889 3952 514048+ 83 Linux
    /dev/sdb7 3953 4144 1542208+ 82 Linux swap / Solaris
    /dev/sdb8 4145 8061 31463271 fd Linux raid autodetect
    /dev/sdb9 8062 14592 52460226 fd Linux raid autodetect

Page 1 of 2 12 LastLast

Posting Permissions

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