If I use 'chainloader +1' it brings me to a grub command line
Same here.. but look at this line:
- Code: Select all
chroot /target /bin/bash grub-install --root-directory=/target --recheck --no-floppy --force
- Code: Select all
man grub-install
#snip
--boot-directory=DIR
install GRUB images under the directory DIR/grub instead of the
/boot/grub directory
Assuming "boot-directory" means "root-directory" (this is sid) it will do just that!
And I saw it happen, when I run the installer's grub code chunk manually. The grub files went to /target/grub! The installer's cleanup deletes that with rm -rf (watch out, that one can bite)
After running the code (as chroot) without --root-directory=/target it now chainloads to the normal menu and boots.
can you give me the quick tutorial on what kind of logging you suggest? (a one-liner, maybe?)
- Code: Select all
if [ "$DEBUG" = "yes" ]; then set -x; fi
maybe set $DEBUG (or not) in the conf file. Turn it off during the rsync else maybe a monster log
I still suspect VastOne's problem is grub* =>2.00 .. all this is another matter.