Re: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.

From: Edwin L. Culp W. <edwinlculp_at_gmail.com>
Date: Tue, 3 May 2011 13:35:51 -0500
On Tue, May 3, 2011 at 9:02 AM, John Baldwin <jhb_at_freebsd.org> wrote:
> On Tuesday, May 03, 2011 8:51:02 am Edwin L. Culp W. wrote:
>> On Tue, May 3, 2011 at 6:59 AM, John Baldwin <jhb_at_freebsd.org> wrote:
>> > On Tuesday, May 03, 2011 7:16:34 am Edwin L. Culp W. wrote:
>> >> I have two disks on this old machine that I have keep current sin
>> >> FreeBSD 6 IIRC as preparation for all the new goodies but this really
>> >> bit me in the morning with a generic kernel and had a heck of a time
>> >> getting it up.
>> >>
>> >> I have a new kernel with the new options.
>> >>             options        ATA_CAM
>> >>             device         ahci
>> >>             device         mvs
>> >>             device         siis
>> >>
>> >> This  morning was such a shock that I am tempted to go back to the old
>> >> kernel config that I understand still works but gonna try to bite the
>> >> bullit.
>> >>
>> >> My fstab that I assume is still needed, is as before, although I had
>> >> changed ad4xx to ada4xx (etc) that I found was incorrect the HARD way
>> >> after trying to reboot;
>> >>
>> >>  /dev/ad4s1b            none            swap    sw              0       0
>> >>  /dev/ad4s1a            /               ufs     rw              1       1
>> >>  /dev/ad4s2g            /backup         ufs     rw              2       2
>> >>  /dev/ad4s1g            /home           ufs     rw              2       2
>> >>  /dev/ad4s2f            /release                ufs     rw
>> >>  2       2
>> >>  /dev/ad4s2d            /tmp            ufs     rw              2       2
>> >>  /dev/ad4s1e            /usr            ufs     rw              2       2
>> >>  /dev/ad4s1h            /usr/local              ufs     rw
>> >>  2       2
>> >>  /dev/ad4s1f            /var            ufs     rw              2       2
>> >>  /dev/ad4s2e            /var/tmp                ufs     rw
>> >>  2       2
>> >>  /dev/acd0              /cdrom          cd9660  ro,noauto       0       0
>> >>  /dev/acd1              /cdrom1         cd9660  ro,noauto       0       0
>> >>  /dev/cd0               /cdrom          cd9660  ro,noauto       0       0
>> >>  /dev/cd1               /cdrom          cd9660  ro,noauto       0       0
>> >> #
>> >> /dev/ad0s1a           /new            ufs     rw              1       1
>> >> /dev/ad0s1g          /new/home       ufs     rw              2       2
>> >> /dev/ad0s1d                /new/tmp        ufs     rw              2       2
>> >> /dev/ad0s1e                /new/usr        ufs     rw              2       2
>> >> /dev/ad0s1h          /new/usr/local  ufs     rw              2       2
>> >> /dev/ad0s1f                /new/var        ufs     rw              2       2
>> >>
>> >> I am totally confused on how these should now be.
>> >>
>> >> Any and all help appreciated.
>> >
>> > It will be ada0 rather than ad4.  With adaX the weird ATA_STATIC_ID stuff is
>> > gone and ATA disks are now numbered starting from 0 just like SCSI disks use
>> > da0, da1, ... etc.
>> >
>> > --
>> > John Baldwin
>> >
>>
>> Thanks, John.  I was afraid that was the answer. Now, II'm really
>> confused.  I'm guessing that the partitions will notl need to be shown
>> in fstab (ada0s1a).   What little mind I have left is a blank,
>> /dev/ad4s1g will be automatically be detected.  Is that correct?
>>
>> What will I do with my second disk /dev/ad0s1a that is already zero?
>>
>> I apologize but I have really confused myself.  I've filled my glass
>> with too much water and I'm drowning.
>>
>> Thanks for everyone's patience.
>>
>> ed
>>
>> P.S.  If I am not the only idiot, maybe a couple of lines as an
>> example could go into UPDATING.
>
> Oh, I missed that you had an ad0.  Most likely ad0 will become ada0, and
> ad4 will become ada1.  All the partitions will still exist, so ad0s1a
> will become ada0s1a and ad4s1a will become ada1s1a.
>
> There is a chance that ad0 will become ada1 and ad4 will become ada1
> instead.  That depends on how your PCI devices are laid out on the
> PCI bus.  I can't answer that without seeing a dmesg though.
>
> Do you have mav's latest changes?  They should provide aliases for the
> old names along with printfs to let you know what the new names are for
> each old disk I think.
>
> --
> John Baldwin
>

Thanks, John.  I apologize for being so thick on this but since I
screwed it up the first time, but It  took a few extra minutes to get
it up and make me a bit nervous.  Need it for dns and a few other
things,
.
I cvsup current, build and install a new world and kernel every
morning so I assume that I should have mav's latest changes. I'll try
it again in the morning with the new build, correct kernel config and
fstab entry..  I'll report the results on this thread then.

Thanks for you help.

ed
Received on Tue May 03 2011 - 16:35:52 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:13 UTC