Comment 25 for bug 1064195

> But I don't think this is related to the patch or udisks2.
> I see the same behavior with "mdir". After inserting a new disk, "mdir" fails with:
> Can't open /dev/fd0: No such device or address
> Cannot initialize 'A:'
> Running it a second time works. Also after running mdir once, "udisksctl mount" works and vice versa. So this rather seems to be a kernel issue I think.

Same behaviour on kernel 3.14.
Floppy mounts from the first attempt on a kernel 3.2.