This is a cryptographically signed message in MIME format.
--------------ms010609020705080206050407
Content-Type: text/plain; charset=KOI8-R; format=flowed
Content-Transfer-Encoding: quoted-printable
Michael Sperber wrote:
>
> Oliver Fromme<olli@lurza.secnetix.de> writes:
>
>> Michael Sperber<sperber@deinprogramm.de> wrote:
>> > I just upgraded my desktop system from 7.3 to 8.1, and the main h=
ard
>> > drive, which was /dev/ad6 before is now /dev/ad10. Consequently,=
the
>> > initial boot failed when trying to mount the root file system fro=
m ad6.
>> >
>> > The desktop system is now fixed, but I also have a rented server =
with
>> > only a serial console, and I worry that the upgrade is going to l=
eave me
>> > with a dead machine. Is there any way to predict how the drive n=
umber
>> > changes? (Why does it change at all?) If so, what's the proper =
way to
>> > tell the system the initial root device *before* rebooting?
>>
>> Remove "options ATA_STATIC_ID" from your kernel config
>> before building the new kernel and rebooting. Then your
>> first disk will be ad0, no matter what controller and
>> channel it is connected to. Be sure to update your
>> /etc/fstab file.
>
> Ah, excellent - that's what I was looking for. Thanks!
>
beware of drago^Wchanging of adX numbers each time you add/remove drive=20
;) It's better to label filesystems, imho ;)
--=20
SY, Marat
--------------ms010609020705080206050407--