Re: Re: Re: Re: mdadm serious does wrong partition changes
On Tue, 2017-12-05 at 11:35 +0100, Hermann Lauer wrote:
> On Tue, Dec 05, 2017 at 03:55:16AM +0100, Frans van Berckel wrote:
> > So md1 = sda1 (and sdb1) = boot, a less then 1GB with ext2 (or
> > ext3).
> > 1) Creating a md1 on sda1 (and sdb1) with a 1.2 layout will make
> > sda2 and sda4 no longer accessible. And that's what Debian
> > installer does.
> Yep. I break out before that point to a shell and use mdadm commands
> to create 0.9 or 1.0 md raid1 versions.
Okay let us fire up a other Sun v440 server. Insert CD. Done as above.
# mdadm --create /dev/md1 --metadata=0.90 --level=1 --raid-devices=2
# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sda2
> > 2) Creating a md1 on sda1 (and sdb1) with a 0.90 layout works. It
> > will leaf sda2 and sda4 as it is.
> > But mdadm creates a md1p1 (and md1p3) partition on sda1 (and
> > sdb1) 'itselfs'. If you ignore p1 and creating a ext3 file system
> > on md1, it's gonna yell there's a partition table on it, do you
> > wanna overwrite it? It's the same counts for creating a ext3 on
> > md1p1. So there goes something wrong.
> No, there is only the unavoidable ambiguity. Having setup the md0 and
> md1 I go back in the manual partitioning and made the md1 an ext2
> /boot partition.
> On md0 I had other machines with ext3 (and even 4, if I remember
> correct). And yes, just tell the installer "overwrite it".
All done as above, with ext4 on /.
> At the end of the installation silo install should ask for the
> devices - the give "/dev/sda" and "/dev/sdb" as location to install -
> at least at wheezy times that worked.
Silo does not ask for a device, it just installs. Rebooting goes into a
disk errors and searching for the dhcp network device.
Rebooting with command: boot
Bad magic number in disk label
Can't open disk label package
Boot device: net File and args:
/pci@1c,600000/network@2: 1000 Mbps full duplex link up
Requesting Internet Address for 0:3:ba:6f:bc:f9
Frans van Berckel