Hi, [...] > Executing: mdadm --examine --scan --verbose -c partitions > INTERNAL ERROR in setup-storage: > mdadm ARRAY line not yet seen > Please report this error to the Debian Bug Tracking System. >
Thanks for reporting :-) - indeed this output is not very helpful. Future (experimental) versions will therefore be more verbose in this case and include the output that you manually generated below. > > This is the output from the mdadm (package version 3.1.4-1+8efb9d1) > command given manually: > > # mdadm --examine --scan --verbose -c partitions > ARRAY metadata=ddf UUID=185c798d:6447583a:4e46c882:9f780cee > devices=/dev/sda > ARRAY container=185c798d:6447583a:4e46c882:9f780cee member=0 > UUID=8fb3d057:eae09224:02771795:415cc091 > [...] According to mdadm documentation this disk, although not quite your intention, earlier on apparently was part of some software RAID configuration (with metadata format ddf, but the container seems to be empty). I have currently no plans of supporting such a format in setup-storage; simply ignoring it, however, seems to be wrong as well. Therefore setup-storage will keep complaining, although with a more verbose error message. You should manually zero the RAID superblocks (using mdadm --zero-superblock /dev/sda) and then re-run the install. Hope this helps, Michael PS.: Bug will be closed once a new version with the improved error message gets uploaded.
pgpyTvOsiJPyY.pgp
Description: PGP signature
