The output of 'fdisk -l' would indicate that the device names are correct, but I am attaching the output of 'dmesg' anyway.
The relevant stuff is probably here:
Code:
$ sudo dmesg | grep sd[abc]
[ 34.167023] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
[ 34.167028] sd 0:0:0:0: [sda] Write Protect is off
[ 34.167030] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 34.167038] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 34.167076] sda: sda1 sda2
[ 34.193693] sd 0:0:0:0: [sda] Attached SCSI disk
[ 35.012733] sd 1:0:0:0: [sdb] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
[ 35.012738] sd 1:0:0:0: [sdb] Write Protect is off
[ 35.012740] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 35.012748] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 35.012778] sdb:<6>usb 2-6: configuration #1 chosen from 1 choice
[ 35.040306] sdb1
[ 35.040338] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 36.070214] sd 2:0:0:0: [sdc] 1465149168 512-byte hardware sectors: (750 GB/698 GiB)
[ 36.070219] sd 2:0:0:0: [sdc] Write Protect is off
[ 36.070221] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 36.070229] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 36.070259] sdc: sdc1 sdc2 < sdc5 sdc6 > sdc3
[ 36.115180] sd 2:0:0:0: [sdc] Attached SCSI disk
[ 39.540724] kjournald2 starting: pid 922, dev sdc5:8, commit interval 5 seconds
[ 39.553978] EXT4-fs: mounted filesystem sdc5 with ordered data mode
[ 44.592423] EXT4 FS on sdc5, internal journal on sdc5:8
[ 45.265730] kjournald2 starting: pid 2277, dev sdc1:8, commit interval 5 seconds
[ 45.266803] EXT4 FS on sdc1, internal journal on sdc1:8
[ 45.266868] EXT4-fs: mounted filesystem sdc1 with ordered data mode
[ 45.272555] kjournald2 starting: pid 2278, dev sdc6:8, commit interval 5 seconds
[ 45.272939] EXT4 FS on sdc6, internal journal on sdc6:8
[ 45.281889] EXT4-fs: mounted filesystem sdc6 with ordered data mode
As to the menu.lst, grub2 doesn't have one. It has been replaced by /boot/grub/grub.cfg (attached in first post). That file is automatically generated from scripts in /etc/grub.d/ and is updated whenever 'update-grub' is exectuted. (you can also prefedine fixed entries that it will include).
the relevant bit of the grub.cfg is:
Code:
51 ### BEGIN /etc/grub.d/30_os-prober ###
52 menuentry "Windows Vista (loader) (on /dev/sda1)" {
53 set root=(hd0,1)
54 chainloader +1
55 }
(the line numbers are because I copied it out of vim).
Actually, looking at that now, I wonder if it shuoldn't be (hd0,0) instead... I will reboot and the post another update about that.
Oh, apparently the output of dmesg is too large a file to attach as a text file. Oh well.
EDIT: So I tried changing it to root=(hd0,0) but it said "no such partition". So, that wasn't the problem. Or at least not the solution. It could be related to the problem. "Invalid signature" seems to suggest that it is finding something, it just doens't like it for some reason.
Bookmarks