% ls /dev/ad*
. If the disk is DD, then you should see devices such as e.g. ad0a. Otherwise you should see e.g. ad0s1a.=> 0 39070080 ad0 [color="Red"]BSD[/color] (18G)
0 4194304 1 freebsd-ufs (2.0G)
4194304 1048576 2 freebsd-swap (512M)
5242880 2097152 4 freebsd-ufs (1.0G)
7340032 524288 5 freebsd-ufs (256M)
7864320 31205752 6 freebsd-ufs (14G)
39070072 8 - free - (4.0k)
Yep, that's the one.Fozzy said:The main drive I am concerned about is /dev/ad12, ls lists: /dev/ad12 /dev/ad12c /dev/ad12d. So since there is no s1 at the end of it, it is dangerously dedicated?
kpa said:There is an MBR with a proper slice table and with an active slice on a dangerously dedicated disk. It's the first 512 bytes of the /boot/boot loader that gets written on the first 16 sectors instead of /boot/mbr. The slice table is a bogus one however containing only one slice that covers the rest of the disk.
How GEOM can tell apart a dangerously dedicated disk from a regular MBR partitioned one I haven't figured out yet...
root@beastie:/root # gpart show md0
=> 0 262144 md0 BSD (128M)
0 262144 - free - (128M)
root@beastie:/root # fdisk md0
******* Working on device /dev/md0 *******
...
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 256977 (125 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1;
end: cyl 15/ head 254/ sector 63
The data for partition 2 is:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
root@beastie:/root # od -N 512 /dev/md0
0000000 000000 000000 000000 000000 000000 000000 000000 000000
*
0001000
Keep in mind that "dangerously dedicated" disks aren't supported anymore since 8.0. It'll still work but I'm not sure the tools allow you to create them anymore.
:/etc # less fstab
# Device Mountpoint FStype Options Dump Pass#
/dev/ada0a / ufs rw 1 1
/dev/ada0b none swap sw 0 0
proc /proc procfs rw 0 0