[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#511180: partman? failure to see ext3 fs on partitioned raid 1 array

Package: partman-base


Installing daily build (2008-01-07) of debian-testing-amd64-netinst.iso

When I get to the partition step, I can see my RAID arrays, but I do not see
my filesystem.  I have the following setup:

/dev/hd[ab] = 300GB
/dev/sd[ab] = 400GB

/dev/md/d0 -> /dev/sd[ab]5 /dev/hd[ab]1 = 600GB RAID6 ext3
/dev/md/d1 -> /dev/sd[ab]1 = 100GB RAID1 ext3

All HD/SD partitions type "fd" (Linux raid autodetect).
All MD devs with 1 partition each, type "83" (Linux) with ext3 fs.

Originally partitioned HD/SD and MD devices with cfdisk.  Used "maximize" (NC,
non-compatible with DOS) and "NO BOOT" options for both HD/SD and MD devices.

The disk detect routines see my disks, see the partitions, automatically start
the arrays, no problem.

When going to the partition stage, it sees the individual HD/SD partitions as
raid-related, and also shows the two MD partitions #_d0 and #_d1.  Also shown
is one partition on each MD device.

What is not shown is the existing ext3 fs.

fdisk -l shows the partition and the type as 83.  Both 600GB RAID6 and 100GB
RAID1 MD partitions mount fine.  ext3 filesystems have been checked with
"e2fsck -vf" and show no errors.  Cleanly unmounted.  Cleanly stopped "mdadm
-S" arrays, etc.

No option to not touch existing partition.  :(  No option to simply mount it. 
I tried tricking things by manually editing /etc/fstab to mount /dev/md/d1p1
as ext3 on /target, mounting manually, and continuing install.  Data was
copied fine until kernel config failed when trying to build an initrd.  Maybe
another problem, maybe same cause, unsure.  Maybe can't programmatically find
filesystem on my partitioned MD/RAID1 device, so can't determine what was
needed for the initrd.  Maybe lacking BOOT flags crashed it?  I planned to
handle GRUB2 install after all data and basic config files copied to RAID1
partition's ext3 fs.  Died at kernel initrd config, then nothing to configure
for boot?

If really needed, I can bring down each half of each array, re-create, copy
data, then re-build the other half, but that's a lot of time, and likely to
kill the discs anyways.

Any other alternatives welcome.  Any pointers where to look welcome.  Any more
info needed, I'll get it.  I can edit shell scripts, do file system or
partition tweaks, whatever is needed.  Let me know.

Thanks for your efforts.


Reply to: