Re: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
On 4 May 2011 04:13, Jason Hellenthal jh...@dataix.net wrote: Edwin, /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 As a side note. These are also now useless can be sent to /dev/null for extra padding ;) Shouldn't cause no harm being there but just for reference. -- Regards, (jhell) Jason Hellenthal Just a sanity check here people, but if the machine was built with freebsd 6.x i would guess it machine is a few years old. If so i doubt the hardware would support ahci, and therefore wouldn't have the ada type devices, it would have the old ad style ata ones and therefore noe fstab twiddling should be necessary. Forgive me if im missing something here. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
On Wed, May 4, 2011 at 8:16 AM, krad kra...@gmail.com wrote: On 4 May 2011 04:13, Jason Hellenthal jh...@dataix.net wrote: Edwin, /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 As a side note. These are also now useless can be sent to /dev/null for extra padding ;) Shouldn't cause no harm being there but just for reference. Just a sanity check here people, but if the machine was built with freebsd 6.x i would guess it machine is a few years old. If so i doubt the hardware would support ahci, and therefore wouldn't have the ada type devices, it would have the old ad style ata ones and therefore noe fstab twiddling should be necessary. Forgive me if im missing something here. If you enable options ATA_CAM in the kernel, which uses the old ata(4) driver via some cam(4) shims, then you also get the adaX device nodes. There's currently 4 ways to access PATA/SATA disks: - old-style ata(4) using adX device nodes - old-style ata(4) using ataahci(4) for ACHI-like access to PATA/SATA disks, I believe using adX - old-style ata(4) via ATA_CAM using adaX device nodes - new-style ahci(4)/siis(4)/another(4) using adaX device nodes I forget the name of the other AHCI-style driver. The first two options uses atacontrol to manage the disks. The last two options use camcontrol to manage the disks. I believe the plan in 9.0 is to have everything accessed via ATA_CAM/ahci(4) so all PATA/SATA drives show up the same, as adaX, with everything being managed via camcontrol, finally unifying all PATA/SATA/SCSI/SAS disk access via cam(4). -- Freddie Cash fjwc...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
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. optionsATA_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/ad4s1bnoneswapsw 0 0 /dev/ad4s1a/ ufs rw 1 1 /dev/ad4s2g/backup ufs rw 2 2 /dev/ad4s1g/home ufs rw 2 2 /dev/ad4s2f/releaseufs rw 2 2 /dev/ad4s2d/tmpufs rw 2 2 /dev/ad4s1e/usrufs rw 2 2 /dev/ad4s1h/usr/local ufs rw 2 2 /dev/ad4s1f/varufs rw 2 2 /dev/ad4s2e/var/tmpufs 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 /newufs rw 1 1 /dev/ad0s1g /new/home ufs rw 2 2 /dev/ad0s1d/new/tmpufs rw 2 2 /dev/ad0s1e/new/usrufs rw 2 2 /dev/ad0s1h /new/usr/local ufs rw 2 2 /dev/ad0s1f/new/varufs 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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
On Tue, May 3, 2011 at 6:59 AM, John Baldwin j...@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. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
On Tue, 3 May 2011, Edwin L. Culp W. wrote: 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? The device names change from ad to ada. Slice and partition identifiers don't change. Device numbering is dynamic with ahci. Using labels is an easy way to not have to worry about a device's name or number. Moving A FreeBSD System To AHCI http://www.wonkity.com/~wblock/docs/html/ahci.html FreeBSD Labeled Filesystems http://www.wonkity.com/~wblock/docs/html/labels.html___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
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 j...@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. optionsATA_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/ad4s1bnoneswapsw 0 0 /dev/ad4s1a/ ufs rw 1 1 /dev/ad4s2g/backup ufs rw 2 2 /dev/ad4s1g/home ufs rw 2 2 /dev/ad4s2f/releaseufs rw 2 2 /dev/ad4s2d/tmpufs rw 2 2 /dev/ad4s1e/usrufs rw 2 2 /dev/ad4s1h/usr/local ufs rw 2 2 /dev/ad4s1f/varufs rw 2 2 /dev/ad4s2e/var/tmpufs 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 /newufs rw 1 1 /dev/ad0s1g /new/home ufs rw 2 2 /dev/ad0s1d/new/tmpufs rw 2 2 /dev/ad0s1e/new/usrufs rw 2 2 /dev/ad0s1h /new/usr/local ufs rw 2 2 /dev/ad0s1f/new/varufs 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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
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. If I have understood ada correct, the first disk (lowest current number) is ada0, the next ada1, and so on. If you have ad0 and ad4, they will be ad0=ada0, and ad4=ada1 . It doesn't affect anything _except_ the disk names, so ad4s1f = ada1s1f and so on. You'll have to change most of your fstab, basically s/ad0/ada0/g and s/ad4/ada1/g . That said, my one ad to ada transition was on a ZFS-only system, which took the fstab editing out of it. I might be horribly wrong in some or all of the above. -- Daniel Nebdal ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
On Tue, May 3, 2011 at 8:54 AM, Daniel Nebdal dneb...@gmail.com wrote: 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. If I have understood ada correct, the first disk (lowest current number) is ada0, the next ada1, and so on. If you have ad0 and ad4, they will be ad0=ada0, and ad4=ada1 . It doesn't affect anything _except_ the disk names, so ad4s1f = ada1s1f and so on. You'll have to change most of your fstab, basically s/ad0/ada0/g and s/ad4/ada1/g . That said, my one ad to ada transition was on a ZFS-only system, which took the fstab editing out of it. I might be horribly wrong in some or all of the above. Thanks, Daniel. Your explanation makes sense to me and to eleminate problems with ad0, it is an old disk, that I will bring up later and just change ad4 to ada0 and ad4s1g to ada0s1g, etc. and reboot it again early tomorrow morning about 5 am CDT and will post a working fstab, if I manage to get it to work. Thanks again, ed -- Daniel Nebdal ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
On Tue, May 3, 2011 at 9:02 AM, John Baldwin j...@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 j...@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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
Hi, On Tue, May 3, 2011 at 7:16 AM, Edwin L. Culp W. edwinlc...@gmail.com wrote: ... thanks a lot to have posted the same message, twice, under different subject... - Arnaud ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: I am very confused and would appreciate some help on device renameing or on renumbering on current fstab.
Edwin, /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/acd1 /cdrom1 cd9660 ro,noauto 0 0 As a side note. These are also now useless can be sent to /dev/null for extra padding ;) Shouldn't cause no harm being there but just for reference. -- Regards, (jhell) Jason Hellenthal pgpB0GwwepyZI.pgp Description: PGP signature
