On Fri Apr 10, 2009 at 02:26:26PM -0700, Timothy D. Lenz wrote:
> Strange:
> -----------------
> sudo mdadm -D /dev/md0
> /dev/md0:
> Version : 00.90
> Creation Time : Fri Mar 27 16:49:37 2009
> Raid Level : raid1
> Array Size : 24418688 (23.29 GiB 25.00 GB)
> Used Dev Size : 24418688 (23.29 GiB 25.00 GB)
> Raid Devices : 2
> Total Devices : 2
> Preferred Minor : 0
> Persistence : Superblock is persistent
>
> Update Time : Fri Apr 10 12:58:59 2009
> State : clean
> Active Devices : 2
> Working Devices : 2
> Failed Devices : 0
> Spare Devices : 0
>
> UUID : 27ce9bd9:4ce6ceb2:670e265f:82e0c670 (local to host LLLx64-32)
> Events : 0.38
>
> Number Major Minor RaidDevice State
> 0 8 1 0 active sync /dev/sda1
> 1 8 17 1 active sync /dev/sdb1
> -----------------
>
> Seems ok, but then:
> -----------------
> sudo mdadm -E /dev/md0
> mdadm: No md superblock detected on /dev/md0.
>
Not really - as I said, "mdadm -E" on the partition, so:
mdadm -E /dev/sda1
or
mdadm -E /dev/sdb1
But these'll give the same results as you've already got - it is using a
version 0.9 superblock, so ought to get auto-assembled by the kernel.
If it doesn't, you'll get an error about being unable to find/mount the
block device. From your original email, it looks like this stage is
working okay anyway. The "Unable to open initial console" error you got
comes after the root FS has been mounted, and would suggest a problem
with the device nodes. I'd guess that there's some static device nodes
which are needed before udev is mounted - because you did the copy with
a mounted udev, you've missed these.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@xxxxxxxxxxxxxxx> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
Attachment:
pgp0WQL7qeCkM.pgp
Description: PGP signature
