Re: mkraid could not lock sda2
From: Justin Guerin (jguerin_at_cso.atmel.com)
Date: 03/23/04
- Previous message: Eduardo Sampaio: "Re: persistant apt-get error (UNSUBSCRIBE)"
- In reply to: Michael Webber: "Re: mkraid could not lock sda2"
- Next in thread: Michael Webber: "Re: mkraid could not lock sda2"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 23 Mar 2004 13:33:26 -0700 To: debian-user@lists.debian.org
On Tuesday 23 March 2004 12:12, Michael Webber wrote:
> UPDATE on bottom
>
[snip]
> _______________________________________________________
> 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
>
>
Your fstab shows that sda1 is being used, as swap. Remove that line from
your fstab when you boot, and also use a program such as fdisk to change
the partition type from Linux swap to Linux Raid Autodetect. If you're
going to try to boot from your raid array, mark the partition as bootable.
> ___________________________
> _______________
> 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 ..
>
It doesn't matter what physical disk you boot from, but you have to be sure
that you aren't using the partitions you want to use in your raid set for
anything else when you boot.
> 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
> 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
>
I thought your swap partition was sda1. I'm assuming you mean sda2 instead
of sba2 above, right? If so, that device is still busy, because it's your
root partition (at least, according to your fstab).
Concentrate on /dev/md0 for now. Make sure you aren't using /dev/sda1
and /dev/sdb1 for anything when you boot. Don't mount them, or anything.
Then, you should be able to make them into a raid device.
Post your results, and we'll go from there.
Justin Guerin
- Previous message: Eduardo Sampaio: "Re: persistant apt-get error (UNSUBSCRIBE)"
- In reply to: Michael Webber: "Re: mkraid could not lock sda2"
- Next in thread: Michael Webber: "Re: mkraid could not lock sda2"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
