Announcement

Collapse
No announcement yet.

Can't mount RAID after upgrade

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Can't mount RAID after upgrade

    Hi,

    I just upgraded my box to 14.04 and on bootup I got a message, that my RAID devices can't be mounted automatically so I chose to skip it and work through it after boot time. Now booted up, A mount -a gives me:
    Code:
    $ sudo mount -a
    [sudo] password for reg: 
    mount: wrong fs type, bad option, bad superblock on /dev/md0,
           missing codepage or helper program, or other error
           In some cases useful info is found in syslog - try
           dmesg | tail  or so
    
    mount: wrong fs type, bad option, bad superblock on /dev/md1,
           missing codepage or helper program, or other error
           In some cases useful info is found in syslog - try
           dmesg | tail  or so
    
    $
    while my mdadm.conf looks like:
    Code:
    $ cat /etc/mdadm/mdadm.conf
    # mdadm.conf
    #
    # Please refer to mdadm.conf(5) for information about this file.
    #
    
    # by default (built-in), scan all partitions (/proc/partitions) and all
    # containers for MD superblocks. alternatively, specify devices to scan, using
    # wildcards if desired.
    #DEVICE partitions containers
    
    # auto-create devices with Debian standard permissions
    CREATE owner=root group=disk mode=0660 auto=yes
    
    # automatically tag new arrays as belonging to the local system
    HOMEHOST <system>
    
    # instruct the monitoring daemon where to send mail alerts
    MAILADDR root
    
    # next line added by reg 09/01/2009
    ARRAY /dev/md0 devices=/dev/sdb6,/dev/sdc6
    ARRAY /dev/md1 devices=/dev/sdb7,/dev/sdc7
    #ARRAY /dev/md2 devices=/dev/sdb8,/dev/sdc8
    
    # definitions of existing MD arrays
    
    # This file was auto-generated on Tue, 08 May 2012 18:26:22 -0700
    # by mkconf $Id$
    $
    just quickly started gparted to check if all my dirves show up and fair enough, my partitions 6 & 7 show up just fine on drives sdb and sdc.
    Also, seems like mdadm is running just fine:
    Code:
    $ ps ax | grep mdadm
     1945 ?        Ss     0:00 /sbin/mdadm --monitor --pid-file /run/mdadm/monitor.pid --daemonise --scan --syslog
     7869 pts/8    S+     0:00 grep --color=auto mdadm
    $
    what could be my problem here, I don't quite follow. Any help would be appreciated!

    Thank you!
    Ron
    roN

    http://www.inetgate.biz

    #2
    What does your syslog or dmesg say? What the output of mdadm --detail --scan

    Please Read Me

    Comment


      #3
      Hi oshunluvr ,

      Thank you for your reply!
      Code:
      $ dmesg | tail
      [ 1437.716819] EXT4-fs (md0): bad geometry: block count 61034935 exceeds size of device (61034912 blocks)
      [ 1437.717197] EXT4-fs (md1): mounting ext3 file system using the ext4 subsystem
      [ 1437.717422] EXT4-fs (md1): bad geometry: block count 59585077 exceeds size of device (59585056 blocks)
      [ 3030.508560] init: nvidia-persistenced main process (21110) terminated with status 1
      [ 3757.003367] current rate 16719823 is different from the runtime rate 48000
      [ 3757.006356] current rate 10357448 is different from the runtime rate 48000
      [ 3850.605129] EXT4-fs (md0): mounting ext3 file system using the ext4 subsystem
      [ 3850.605299] EXT4-fs (md0): bad geometry: block count 61034935 exceeds size of device (61034912 blocks)
      [ 3850.605585] EXT4-fs (md1): mounting ext3 file system using the ext4 subsystem
      [ 3850.605782] EXT4-fs (md1): bad geometry: block count 59585077 exceeds size of device (59585056 blocks)
      reg@regDesktopHome:~/semios$
      and syslog says nothing but
      Code:
      $ sudo mdadm --detail --scan
      mdadm: cannot open /dev/md/127_0: No such file or directory
      ARRAY /dev/md1 metadata=0.90 UUID=0abe503f:401d8d09:cd707cc0:bc3f8165
      ARRAY /dev/md0 metadata=0.90 UUID=91e560f1:4e51d8eb:cd707cc0:bc3f8165
      reg@regDesktopHome:~/semios$
      roN

      http://www.inetgate.biz

      Comment

      Working...
      X