Hi, Clive, can you forward this onto Ian please.
Information on subscribing to the list is at http://dorset.lug.org.uk/wiki/doku.php?id=mailing_list (Background for everyone else, Ian has two "drives", a normal one with Windows and a RAID pair. Ubuntu installed happily into pre-made logical partitions on the RAID drive, but Windows' normal boot.ini is still reached on booting, with no Ubuntu in sight. Ideas welcome.) Ian, one way to see if GRUB modified the MBR of the RAID pair is look at the first 512 bytes, the MBR, and see if GRUB's strings, like "GRUB" occur. So after running from a live CD try $ sudo dd if=/dev/sda bs=512 count=1 | (sleep 1; strings -t x) 1+0 records in 1+0 records out 512 bytes (512 B) copied, 4.4526e-05 s, 11.5 MB/s a5 ZRr= 11e `|f 127 \|f1 188 GRUB 18e Geom 193 Hard Disk 19d Read 1a2 Error $ Depending on the distro it may be it uses su(1) instead of sudo(1), i.e. su -c 'dd if=/dev/sda bs=512 count=1' | (sleep 1; strings -t x) Change the `sda' to whatever drive you want to examine. Be *very* careful about entering it correctly, the `if=' specifies the input file, mistype it and you could write to the MBR. http://en.wikipedia.org/wiki/Master_boot_record Having the BIOS attempt to boot from the RAID pair is another easy test. You were asking about modifying boot.ini to boot Linux. A bit of Googling suggests this is possible but I think the norm amongst dual-booters is to let GRUB kick off Windows instead. Cheers, Ralph. -- Next meeting: Bournemouth, Tuesday 2011-06-07 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
