I finally saw that in the very first steps of the install procedure, the type of partition ID of assigned install disk is set to A6 overwriting from the original value (in my case for NTFS this is 0x86 I assume) preventing to boot what was the original system on that disk. Changing to the original value the disk ID repaired this.
However this is only side effect since my original problem is in getting openbsd working. OpenbBSD crashes at the first boot. Could one help with how to get the crash infos out of the console (ps trace) ; is the only way to copy on paper then write in an email or is there a way to copy this one way or another ? 2009/7/9 jean-francois <[email protected]> > I remember that I used to start install procedure on each disk answering > yes to 'all disk should be used for this install', then I just checked > the size of the disk in the disklabel, in order to identify the one I > was look for and then quit & reboot without more modifications (p at > disklabel then q and halt). > > After this the two disks sdb/sdc that were hosting win and linux did not > boot anymore. > > Could you tell me if doing so has modified in any way the partitions or > mbr ? > > Thank you > > Le jeudi 09 juillet 2009 ` 10:45 -0600, Theo de Raadt a icrit : > > > Therefore I don'nt understand why installing openbsd on sd0 has changed > > > anything on the MBR of other disks ? > > > > The installer does not touch the other disks.
