> step 16 said that it had detected a list of OS's on my computer. but the > list showed only one entry, 'Debian GNU/Linux (testing/unstable), which > could refer to my existing hda3 'testing' OS or my newly installed hda4 > 'testing' OS. the entry in the list shows no device info, so i cannot > tell whether it refers to hda3 or hda4.
It certainly refers to the old install, ie hda3. What's puzzling is the lack of detection of the Windows install. > my analysis: i think that the initial problem is that the OS list is not > correct. the install script does not detect all of the OS's on hda. in > my case, there should be 3 OSs: > > hda1 // windows Which Windows flavour? > hda2 // linux swap > hda3 // existing working debian 'testing' (still working well, i am > using it now as i type) > hda4 // newly installed 'testing' which i am trying to install > > since the OS list is not correct, all of the script logic that follows > does not have the correct input to configure grub and the grub boot menu > correctly. > > for more information, i also mounted hda on /mnt/tmp to have a look. > again, the app software was installed, but hda4/boot is empty, except > for the grub subdirectory and files. there is no kernel image stuff in > hda4/boot (i am comparing it to /hda3/boot, which has vmlinuz, config, > initrd, system.map, and all that stuff for booting the kernel.) This is really strange, indeed. Anyone with a better idea?
signature.asc
Description: Digital signature
