On Jun 27, 2006 11:23 +1000, Neil Brown wrote:
You could try hunting for ext3 superblocks on the device. There might
be an easier way but
od -x /dev/hdb | grep '^.60 ef53 '
Compile the findsuper tool from e2fsprogs - it was made for this. Also
possible to use
On Tue, 27 Jun 2006, Neil Brown wrote:
On Monday June 26, [EMAIL PROTECTED] wrote:
This is what I get now, after creating with fdisk /dev/hdb1 and
/dev/hdc1 as linux raid autodetect partitions
So I'm totally confused now.
You said it was 'linear', but the boot log showed 'raid0'.
As Christian said, specific error message help a lot.
Assume the two devices are hdc and hde,
fdisk -l /dev/hdc
fdisk -l /dev/hde
mdadm -E /dev/hdc
mdadm -E /dev/hde
and my best guess
mdadm --build /dev/md0 --level linear --raid-disks 2 /dev/hdc /dev/hde
fsck -n /dev/md0
(and
I managed to get the hard disk of the retired system and this is
its raid-related boot log:
md: Autodetecting RAID arrays.
[events: 004d]
[events: 004d]
md: autorun ...
md: considering hdb1 ...
md: adding hdb1 ...
md: adding hdc1 ...
md: created md0
md: bindhdc1,1
md: bindhdb1,2
This is what I get now, after creating with fdisk /dev/hdb1 and
/dev/hdc1 as linux raid autodetect partitions
mdadm -E /dev/hdb1
/dev/hdb1:
Magic : a92b4efc
Version : 00.90.00
UUID : a7e90d4b:f347bd0e:07ebf941:e718f695
Creation Time : Wed Mar 16 18:14:25 2005
On Monday June 26, [EMAIL PROTECTED] wrote:
This is what I get now, after creating with fdisk /dev/hdb1 and
/dev/hdc1 as linux raid autodetect partitions
So I'm totally confused now.
You said it was 'linear', but the boot log showed 'raid0'.
The drives didn't have a partition table
On Monday June 26, [EMAIL PROTECTED] wrote:
This is what I get now, after creating with fdisk /dev/hdb1 and
/dev/hdc1 as linux raid autodetect partitions
So I'm totally confused now.
You said it was 'linear', but the boot log showed 'raid0'.
The drives didn't have a partition table
