Totally confused with the /usrsrc/UPDATING for 20110424
CAM-based ATA stack
Edwin L. Culp W.
edwinlculp at gmail.com
Tue May 3 18:55:57 UTC 2011
On Tue, May 3, 2011 at 12:56 PM, Arnaud Lacombe <lacombar at gmail.com> wrote:
> Hi,
>
> On Mon, May 2, 2011 at 8:28 PM, eculp <eculp at encontacto.net> wrote:
>> With this confusion I need someone to give me an idea on renumbering.
>>
>> 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
>>
> I've got the following in my stripped down GENERIC:
>
> # ATA controllers
> device ahci # AHCI-compatible SATA controllers
> device ata # Legacy ATA/SATA controllers
> options ATA_CAM # Handle legacy controllers with CAM
>
> # ATA/SCSI peripherals
> device scbus # SCSI bus (required for ATA/SCSI)
> device da # Direct Access (disks)
> device pass # Passthrough device (direct ATA/SCSI access)
>
> I'm able to boot from CF on a couple of different machine. It would
> seem that without:
>
> device ata # Legacy ATA/SATA controllers
>
> the disk is not detected. With, the disk shows up as:
>
> ada0 at ata3 bus 0 scbus1 target 0 lun 0
> ada0: < 20070709> ATA-0 device
> ada0: 16.700MB/s transfers (WDMA2, PIO 512bytes)
> ada0: 967MB (1981728 512 byte sectors: 16H 63S/T 1966C)
> ada0: Previously was known as ad0
>
> and I did not need any /etc/fstab modification.
>
> my .2 credits,
> - Arnaud
Thanks Arnaud, Again I apologize of having posted this problem twice
but as I mentioned on the previous thread the machine in question is
dns and my screwing with it to get it up and runing having a bad
fstab. I wrote this email before checking and I thought it was lost.
Tomorrow morning I'll get to the bottom of my misunderstanding and
hopefully be able to help make this a bit more clear for others who
haven't taken the jump yet.
ed
>
>> 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 necessary is:
>>
>> /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/ada01h /new/usr/local ufs rw 2 2
>> /dev/ada01f /new/var ufs rw 2 2
>>
>> I am totally confused on how these should now be.
>>
>> Any help appreciated.
>>
>> ed
>> _______________________________________________
>> freebsd-current at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>>
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>
More information about the freebsd-current
mailing list