Quote:
Originally Posted by signetone
linux-n2vd:~ # sudo /sbin/fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x2bab9524
Device Boot Start End Blocks Id System
/dev/sda1 1 1306 10490413+ 27 Unknown
/dev/sda2 1307 9237 63697725 7 HPFS/NTFS
/dev/sda3 * 9237 19457 82099747+ f W95 Ext'd (LBA)
/dev/sda5 9237 9499 2104080 82 Linux swap / Solaris
/dev/sda6 9499 12109 20972826 83 Linux
/dev/sda7 12110 19457 59022778+ 83 Linux
linux-n2vd:~ #
|
That's one of the cases where the manufacturer puts a utility partition first up on the drive (sad1) and then the bootloader goes sometimes into sda1 and sometimes into sda2. So it might be one of two possibilities. But before I go on, what does the file menu.lst contain after you made the new bootloader as per my first post? To open the bootloader's menu file and look at it, run this command:
Quote:
in KDE it's: kdesu kwrite /boot/grub/menu.lst
in Gnome it's: gnomesu gedit /boot/grub/menu.lst
|