There is still one redundant line, though I don't think it does any harm:
d-i partman-auto/choose_recipe select xenserver
I believed this was necessary to force a reference to the
partman-auto/expert_recipe, that's the reason I purposely left it in there,
oops.
There are also several syntax errors in your recipe:
- a period is missing after mountpoint{ /boot }
- you have several sizes with a weird period in them: "2.5000", "1.8000",
"1.5000"; I cannot imagine that that is supported
Please check things more carefully before coming back to the list. Maybe
start with a more simple (the standard?) recipe and slowly expand that.
Before attaching the file I'd actually ran the install script with d-i
partman-auto/choose_recipe select All files in one partition (recommended
for new users) enabled rather than trying anything complicated. That didn't
work so I tryed the expert receipe. It is both fortunate and unfortunate
that I chose to do it this way around. The missing full stop clearly occured
when I removed all the line continuation statements, the 1.5000 etc. was
actually generated by www.instalinux.com so I don't know if they are valid
or not but I'd agree with you, probably not. I'll remove them.
You can also debug this yourself (at least if you have some shell script
experience). Try adding a 'set -x' in /lib/partman/init.d/99initial_auto
and check the syslog for what happens.
Of course, this means that you will have to leave other questions not
preseeded or run at a lower priority.
I was up to 3am this morning trying to debug this problem but can't see
anything wrong (or at least reported). partman sees the disk, sees the
partitions but just doesn't accept what is in the preseed file. There are a
couple of error messages reported during the discovery process regarding not
being able to load up modules but given that I can see the disk etc I've
assumed that these are red herrings although I could be wrong. I'm currently
in the process of looking at building a custom kernel but looking at the
default config everything is enabled as modules that my ITX c3-2 board
requires so should work. The only thing that I can think of trying is trying
a later revision of the kernel.
In a last vain attempt to get things working I tried etch last night and
some of the preseed configs provided on the debian-installer wiki. Every one
stopped at the same place. Clearly this has to be machine specific as I'm
sure the people who have published these examples know of no problems and it
works for them.
I'm new to debian so it's a steep learning curve. I could install it by hand
but that's not what I want to achieve short term (I want a fully automatic
build mechanism). Could you give me some pointers as to where to look, what
to do, or any other suggestions.
Your help is appreciated.
-Andrew
