On Mon, 24 Oct 2005 10:25:07 -0600 Sibastien Taylor <[EMAIL PROTECTED]> wrote:
> I do have one question about the following lines though: > > dkcsum: wd0 matches BIOS drive 0x80 > wd1: no disk label > dkcsum: wd1 matches BIOS drive 0x81 > dkcsum: wd1 matches BIOS drive 0x82 IGNORED > wd2: no disk label > dkcsum: wd2 matches BIOS drive 0x81 IGNORED > dkcsum: wd2 matches BIOS drive 0x82 > root on wd0a I was those as well when I added 4 new drives to my system. I my case the drives were brand new and had no data on them, after I fdisk'ed & disklabel'ed them the warning was gone. So I guess it's related to some kind of checksum in the MBR or the partition table or something. I figure if you dd the the first few sectors from one raw hdd device to another you might get this as well, not sure though. > They do seem to work right now, but should this be a cause for > concern? Might wd1 come up as wd2 and vice versa under some > conditions? Not if you don't touch anything. Changing kernel parameters with either config or on the boot> prompt might result in that. Moving the drives to different channels or adding/removing drives can cause them to move as well. If you really don't want that you can hardcode wd* drives to pciide* locations. // nick
