MLH wrote: ... > Now all of the drives I built to boot UEFI a couple of years ago > now can boot, though my UEFI raid drives get pushed to the front > somehow and I haven't determined how to specify the SSD. I have to > boot -a and select the correct dk. None of the "NAME=" stuff seems > to work and even specifying the boot dev listed (and specified to > be the boot drive) works. I can only specify which one (other than > RAID0) using the boot -a method.
So I have the following drives: [ 1.630860] ld0: GPT GUID: 6daca67a-2453-4331-8cf9-0c7c5ec8817f [ 1.630860] dk0 at ld0: "c6830be4-7f3e-4631-b6b7-75ae6428db71", 262144 blocks at 2048, type: msdos [ 1.630860] dk1 at ld0: "d0ff5477-8cd0-42eb-ae72-b3bdf7644e8d", 3839840256 blocks at 264192, type: ffs [ 1.641214] dk2 at ld0: "534f14ac-5a35-4a05-9262-6a435d4e75ae", 66924687 blocks at 3840104448, type: swap [ 1.641214] IPsec: Initialized Security Association Processing. [ 1.730860] ahcisata0 port 2: device present, speed: 6.0Gb/s [ 1.730860] ahcisata0 port 3: device present, speed: 6.0Gb/s [ 1.740860] ahcisata0 port 1: device present, speed: 6.0Gb/s [ 2.110858] uhub4 at uhub1 port 7: vendor 214b (0x214b) USB2.0 HUB (0x7000), class 9/0, rev 2.00/1.00, addr 1 [ 2.120858] uhub4: single transaction translator [ 2.140858] uhub4: 4 ports with 4 removable, self powered [ 2.150858] uhidev0 at uhub3 port 3 configuration 1 interface 0 [ 2.160858] uhidev0: Logitech (0x046d) USB Keyboard (0xc31c), rev 1.10/64.02, addr 1, iclass 3/1 [ 2.170858] ukbd0 at uhidev0 [ 2.190858] wskbd0 at ukbd0: console keyboard [ 2.200858] uhidev1 at uhub3 port 3 configuration 1 interface 1 [ 2.210858] uhidev1: Logitech (0x046d) USB Keyboard (0xc31c), rev 1.10/64.02, addr 1, iclass 3/0 [ 2.230858] uhidev1: 5 report ids [ 2.240858] uhid0 at uhidev1 reportid 1: input=1, output=0, feature=0 [ 2.250858] uhid1 at uhidev1 reportid 2: input=1, output=0, feature=0 [ 2.260857] uhid2 at uhidev1 reportid 3: input=3, output=0, feature=0 [ 2.270857] uhid3 at uhidev1 reportid 5: input=0, output=0, feature=5 [ 2.780855] uhidev2 at uhub3 port 4 configuration 1 interface 0 [ 2.790855] uhidev2: Logitech (0x046d) USB-PS/2 Optical Mouse (0xc00e), rev 2.00/11.10, addr 2, iclass 3/1 [ 2.810855] ums0 at uhidev2: 3 buttons and Z dir [ 2.820855] wsmouse0 at ums0 mux 0 [ 2.830855] wd0 at atabus1 drive 0 [ 2.840855] wd0: <ST4000DM004-2CV104> [ 2.850855] wd0: drive supports 16-sector PIO transfers, LBA48 addressing [ 2.850855] wd0: 3726 GB, 7752021 cyl, 16 head, 63 sec, 512 bytes/sect x 7814037168 sectors (4096 bytes/physsect; first aligned sector: 8) [ 2.900855] wd0: GPT GUID: b3d4301a-cbfe-414e-ac61-16571d17d548 [ 2.900855] dk3 at wd0: "boot1", 100000 blocks at 34, type: ffs [ 2.910855] dk4 at wd0: "swap1", 10000000 blocks at 100034, type: swap [ 2.920855] dk5 at wd0: "raidw1", 7803937101 blocks at 10100034, type: raidframe [ 2.930854] wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133), WRITE DMA FUA, NCQ (32 tags) [ 2.940855] wd0(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA), NCQ (31 tags) [ 2.940855] wd1 at atabus2 drive 0 [ 2.940855] wd1: <ST4000DM004-2CV104> [ 2.940855] wd1: drive supports 16-sector PIO transfers, LBA48 addressing [ 2.940855] wd1: 3726 GB, 7752021 cyl, 16 head, 63 sec, 512 bytes/sect x 7814037168 sectors (4096 bytes/physsect; first aligned sector: 8) [ 2.960855] uhub5 at uhub4 port 3: vendor 214b (0x214b) USB2.0 HUB (0x7000), class 9/0, rev 2.00/1.00, addr 2 [ 2.960855] uhub5: single transaction translator [ 2.980854] uhub5: 4 ports with 4 removable, self powered [ 2.980854] wd1: GPT GUID: f10e8bb0-de35-4b54-b365-6571da54d265 [ 2.980854] dk6 at wd1: "boot0", 100000 blocks at 34, type: ffs [ 2.991421] dk7 at wd1: "swap0", 10000000 blocks at 100034, type: swap [ 2.991421] dk8 at wd1: "raidw0", 7803937101 blocks at 10100034, type: raidframe [ 2.991421] wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133), WRITE DMA FUA, NCQ (32 tags) [ 2.991421] wd1(ahcisata0:2:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA), NCQ (31 tags) [ 2.991421] wd2 at atabus3 drive 0 [ 2.991421] wd2: <Hitachi HUS724040ALE641> [ 3.001566] wd2: drive supports 16-sector PIO transfers, LBA48 addressing [ 3.001566] wd2: 3726 GB, 7752021 cyl, 16 head, 63 sec, 512 bytes/sect x 7814037168 sectors (4096 bytes/physsect; first aligned sector: 8) [ 3.030854] wd2: GPT GUID: dcac6a4f-5d57-4398-8f8f-3e16635a817d [ 3.030854] dk9 at wd2: "boot_h1", 2097152 blocks at 64, type: ffs [ 3.030854] dk10 at wd2: "swap_h1", 8388608 blocks at 2097216, type: swap [ 3.030854] dk11 at wd2: "rooth1", 7803550936 blocks at 10485824, type: ffs fstab: NAME=d0ff5477-8cd0-42eb-ae72-b3bdf7644e8d / ffs rw,log 1 1 NAME=rooth1 /opt ffs rw,log 1 2 NAME=ffs@raid0 /raid0 ffs rw,log 1 2 On boot, only "raid0" can be specified by name and I have to manually select to boot from dk1 or dk9 after choosing "boot -a" to boot from the other two which are non-raid drives. How can I specify in boot.cfg to boot from the dk1 drive? Specifying by "boot dk1" (and variations) or "boot NAME=d0ff5477-8cd0-42eb-ae72-b3bdf7644e8d" doesn't work. Thx