Bernard Li wrote:
We use this schema all the time, don't think this is an issue...
that is what I expected.
When SystemImager bails, can you check to see whether /a/boot was
mounted? It would help if you can grab the installation transcript to
figure out what exactly has gone wrong...
$ df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/root 2092 2092 0 100% /old_root
tmpfs 452788 33576 419212 7% /
/dev/fd0 1424 9 1415 1% /floppy
/dev/hda1 34435876 3626388 29060240 11% /a/boot
/dev/hda4 34435876 3626388 29060240 11% /a
this is what is actually displayed, but it is wonky. note:
$ df /a/boot
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda1 34435876 3626388 29060240 11% /a/boot
and...
$ df /a
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda1 34435876 3626388 29060240 11% /a/boot
df seems to be confused.
You could potentially try commenting out the umount command in the
master script, and see if it goes any further...
I will try that.
On thing that just occured to me. I've upgraded this installation
several times (original was 2-something). I'm now at 3.6.3.
Is it possible that some of my standard flavor scripts or other
components didn't get upgraded?
thanks again,
p
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
