ad1 renumbered to ad0

Pierre Abbat phma at
Wed Feb 9 17:06:40 PST 2011

I just rebooted (after running into the "alt-ctrl-F1 hangs with beeper on" bug 
again), went into the BIOS setup, and enabled audio and SATA (because my 
friend is talking about getting a big SATA disk). On reaching cryptdisks, it 
said "device ad1s1e is not a luks device". I checked /dev/ad* and found that 
it's now ad0. Some months ago, when I upgraded the kernel on the laptop, ad0 
changed to ad1. What's going on?

La sal en el mar es más que en la sangre.
Le sel dans la mer est plus que dans le sang.

More information about the Users mailing list