Re: mkraid could not lock sda2

From: Michael Webber (sssouthpaw_at_hotmail.com)
Date: 03/23/04

  • Next message: Kent West: "Re: mouse freezing in X Windows?"
    To: debian-user@lists.debian.org
    Date: Tue, 23 Mar 2004 11:12:43 -0800
    
    
    UPDATE on bottom


    On Monday 22 March 2004 22:12, Michael Webber wrote:
    > hi,   I have to scsi disks that are the same size and have the same
    > parititon sizes.  when I go   mkraid /dev/md0
    >
    > handeling MD device /dev/md0
    >
    > analyzin super-block
    >
    > disk0: /dev/sda1, 979933kb, raid superblock at 979840kB
    >
    > disk1: /dev/sdb1, 979933kb, raid superblock at 979840kB
    >
    > md: could not lock sda1.
    >
    > md: error, md_import_device() retured -16
    >
    > mkraid: aborted.
    >
    Is this a copy and paste from the actual output?  If not, posting the actual 
    output may help.
    > -----------------------------------------------------------------------
    >
    > my  raidtab file looks like this 
    >
    > raiddev /dev/md0
    >         raid-level              1
    >         nr-raid-disks           2
    >         nr-spare-disks          0
    >         chunk-size              4
    >         persistent-superblock   1
    >                 device          /dev/sda1
    >                 raid-disk       0
    >             ;     device          /dev/sdb1
    >            &nb ;    raid-disk       1
    >
    >
    > raiddev /dev/md1
    >         raid-level              1
    >         nr-raid-disks           2
    >         nr-spare-disks          0
    >         chunk-size              4
    >         persistent-superblock   1
    >                 device          /dev/sda2
    >                 raid-disk       0
    >             ;     device          /dev/sdb2
    >                 raid-disk       1
    >
    > thanks
    There's nothing wrong with your raidtab, unless those semi-colons are 
    actually part of the file and not garbled HTML.
    
    Are the partitions mentioned under the device section of the raidtab in use 
    when you try to make the raid array?  What is their partition type?  What 
    drive did you boot from to issue the mkraid command?  What is the current 
    contents of your /etc/fstab?
    
    What is the contents of /proc/mdstat?
    
    Justin Guerin
    _______________________________________________________
    sda1 is a swap partition  and im 100% sure that isnt being used   (I have 2 gigs of ram hehe)
    sda2 is being used   thats what I boot from ... but  .. what else can I do ?    the error  is on sda1 ..
    /etc/fstab     = below ..
    # /etc/fstab: static file system information.
    #
    # <file system> <mount point>   <type>  <options>               <dump>  <pass>
    /dev/sda2       /               ext3    errors=remount-ro       0       1
    /dev/sda1       none            swap    sw  & amp; nbsp;                   0       0
    proc            /proc           proc    defaults                0       0
    /dev/fd0        /floppy         auto    user,noauto             0       0
    /dev/cdrom      /cdrom          iso9660 ro,user,noauto          0       0
     
    ___________________________
     _______________
    mdstat 
     
    Personalities : [raid1]
    unused devices: <none>
     
    ______________________________
    I booted from sda and thats where i running mkraid from. Do I need to run it on a floppy or something?
    on boot I got this ..
     
    md: Autodetecting RAID arrays.
    md: autorun ...
    md: ... autorun DONE.
    kjournald starting.  Commit interval 5 seconds
    EXT3-fs: mounted filesystem with ordered data mode.
    VFS: Mounted root (ext3 filesystem) readonly.
    Freeing unused kernel memory: 232k freed
    Adding 979924k swap on /dev/sda1.  Priority:-1 extents:1
    EXT3 FS on sda2, internal journal
    drivers/usb/core/usb.c: registered new driver usbfs
    drivers/usb/core/usb.c: registered new driver hub
    drivers/usb/core/usb.c: registered new driver usbkbd
    drivers/usb/input/usbkbd.c: :USB HID Boot Protocol keyboard driver
    md: raidstart(pid 87) u sed deprecated START_ARRAY ioctl. This will not be support$
    md: could not lock sda1.
    md: could not import sda1!
    md: autostart unknown-block(0,2049) failed!
    md: raidstart(pid 87) used deprecated START_ARRAY ioctl. This will not be support$
    md: invalid raid superblock magic on sdb1
    md: sdb1 has invalid sb, not importing!
    md: could not import sdb1!
    md: autostart unknown-block(0,2065) failed!
    md: raidstart(pid 103) used deprecated START_ARRAY ioctl. This will not be suppor$
    md: could not lock sda2.
    md: could not import sda2!
    md: autostart unknown-block(0,2050) failed!
    md: invalid raid superblock magic on sdb2
    md: sdb2 has invalid sb, not importing!
    md: could not import sdb2!
    md: autostart unknown-block(0,2066) failed!
     
    Thanks.
     
    UPDATE :    ok I did swapoff -a     (turns the swap off and it let me mirror the swap partition)
    :0)  
    but  now   i try to do  the 
     main partition    sba2    and it says device is busy ..
    I went into   ini1  (I think thats one user mode)   and it still did it...
    heeelllpppppp


    Find a broadband plan that fits. Great local deals on high-speed Internet access. -- To UNSUBSCRIBE, email to debian-user-request@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Kent West: "Re: mouse freezing in X Windows?"

    Relevant Pages

    • Re: mkraid could not lock sda1
      ... > my raidtab file looks like this ... > raiddev /dev/md0 ... There's nothing wrong with your raidtab, unless those semi-colons are actually part of the file and not garbled HTML. ... What drive did you boot from to issue the mkraid command? ...
      (Debian-User)
    • Re: mkraid could not lock sda1
      ... > my raidtab file looks like this ... There's nothing wrong with your raidtab, ... drive did you boot from to issue the mkraid command? ...
      (Debian-User)