I have one image of a drive taken with 'dd'. It was split into segments
for transportation on a FAT32 volume. I'd like to be able to mount this
disk.
Here's what I did:
- Use loop.o to give each segment a /dev/loopN entry.
- Make a raidtab that utilizes these loop entries.
- raid0run --configfile my.raidtab /dev/md0
It doesn't work. :(
Can anyone help me troubleshoot this?
Here's what I can find from the command line:
mangonel:~# raid0run --configfile my.raidtab /dev/md0
handling MD device /dev/md0
analyzing super-block
/dev/md0: Invalid argument
mangonel:~# cat /proc/mdstat
Personalities : [linear]
read_ahead not set
md0 : inactive [dev 07:07][7] [dev 07:06][6] [dev 07:05][5] [dev 07:04][4]
[dev 07:03][3] [dev 07:02][2] [dev 07:01][1] [dev 07:00][0]
7341800 blocks
unused devices: <none>
Here's what's in my 'dmesg'.
md: bind<[dev 07:00],1>
md: nonpersistent superblock ...
md0: WARNING: [dev 07:01] appears to be on the same physical disk as [dev
07:00]. True
protection against single-disk failure might be compromised.
md: bind<[dev 07:01],2>
md: nonpersistent superblock ...
md0: WARNING: [dev 07:02] appears to be on the same physical disk as [dev
07:01]. True
protection against single-disk failure might be compromised.
md: bind<[dev 07:02],3>
md: nonpersistent superblock ...
md0: WARNING: [dev 07:03] appears to be on the same physical disk as [dev
07:02]. True
protection against single-disk failure might be compromised.
md: bind<[dev 07:03],4>
md: nonpersistent superblock ...
md0: WARNING: [dev 07:04] appears to be on the same physical disk as [dev
07:03]. True
protection against single-disk failure might be compromised.
md: bind<[dev 07:04],5>
md: nonpersistent superblock ...
md0: WARNING: [dev 07:05] appears to be on the same physical disk as [dev
07:04]. True
protection against single-disk failure might be compromised.
md: bind<[dev 07:05],6>
md: nonpersistent superblock ...
md0: WARNING: [dev 07:06] appears to be on the same physical disk as [dev
07:05]. True
protection against single-disk failure might be compromised.
md: bind<[dev 07:06],7>
md: nonpersistent superblock ...
md0: WARNING: [dev 07:07] appears to be on the same physical disk as [dev
07:06]. True
protection against single-disk failure might be compromised.
md: bind<[dev 07:07],8>
md: nonpersistent superblock ...
md: [dev 07:07]'s event counter: 00000000
md: [dev 07:06]'s event counter: 00000000
md: [dev 07:05]'s event counter: 00000000
md: [dev 07:04]'s event counter: 00000000
md: [dev 07:03]'s event counter: 00000000
md: [dev 07:02]'s event counter: 00000000
md: [dev 07:01]'s event counter: 00000000
md: [dev 07:00]'s event counter: 00000000
md0: max total readahead window set to 124k
md0: 1 data-disks, max readahead per data-disk: 124k
md: pers->run() failed ...
md: md0 still in use.
Here's my raidtab:
raiddev /dev/md0
raid-level linear
nr-raid-disks 8
chunk-size 4
persistent-superblock 0
device /dev/loop0
raid-disk 0
device /dev/loop1
raid-disk 1
device /dev/loop2
raid-disk 2
device /dev/loop3
raid-disk 3
device /dev/loop4
raid-disk 4
device /dev/loop5
raid-disk 5
device /dev/loop6
raid-disk 6
device /dev/loop7
raid-disk 7
Thanks!
-Jeff Meininger
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
