Bug#286276: kernel-image-2.6.8-9-amd64-k8: Unable to mount md devices

[Marc Singer <elf@buici.com>]

On Mon, Dec 20, 2004 at 02:52:50AM +0100, Goswin von Brederlow wrote:
> Marc Singer <elf@buici.com> writes:
> 
> > On running mdadm --assemble /dev/md0
> >
> >   mdadm[4247]: segfault at 000000000000002c rip 000000000804b19e rsp 00000000ffffdb80 error 4
> >   mdadm[4253]: segfault at 000000000000002c rip 000000000804b19e rsp 00000000ffffdb80 error 4
> 
> That doesn't mean much. Unaligned access gets reported as such as
> well for example.
> 
> Could you paste a gdb stack backtrace preverably after rebuilding
> mdadm with debug info?

I've had a look at the mdadm side of this problem.  It looks like it
is crashing because there is no configuration file.  From mdadm.c

          break;
  case ASSEMBLE:
          if (devs_found == 1 && ident.uuid_set == 0 &&
              ident.super_minor == UnSet && !scan ) {
                  /* Only a device has been given, so get details from config file */
                  mddev_ident_t array_ident = conf_get_ident(configfile, devlist->devname);
                  mdfd = open_mddev(devlist->devname, array_ident->autof);

The conf_get_ident() is returning 0 which is then dereferenced by the
open_mddev() call and segfault'ing.  configfile is NULL because none
was given.  AFAICT, configfile never defaults.  And even if it did,
there is no config file on my machine.

I haven't yet looked into the code within the initrd to see what it
does.  It is possible that the only way that my setup can work is if
the md driver is compiled in.

Still, I wonder about the ioctl errors that I see with fdisk.