Re: ZFS root on MB Intel S3420GP
On 17.04.11 21:54, Jeremy Chadwick wrote: I don't recommend enabling ahci.ko after the OS has already been installed on an adX disk, simply because I believe the combination of GEOM+CAM+ahci may show different geometry details than GEOM+ata would. With the disclaimer that I haven't studied all code to confirm this, but adX and adaX (with ahci.ko) have always played the same for me - geometry wise. I believe the translation is always 1:1. At least on modern SATA drives -- olderdrives from the transitional epoch of different CHS, LBA etc experiments might behave differently. Migration from gmirror to zfs(root) is trivial. Having only two gmirror-ed disks, you could replace that with ZFS mirror. Having 4-way gmirror can let you do a 4-disk ZFS migration (raidz1 or raidz2). I tend to do all of my new systems with ZFS on root. Probably because I no longer have to do systems that run with few MB of RAM :) - the I would use UFS alwats. One nice feature of ZFS I have discovered is with USB flash media. You are not typically supposed to write much to that media, but using UFS on USB sticks is awful. On contrary, when used with ZFS, the USB sticks behave much differently, because ZFS will group writes and not do silly things like issue lots of 512 byte writes. So, you may have complete development system on an USB stick, or a pair of these. The only real trouble with USB stisks is that some motherboards behave unpredictable as to boot order, but this is improving. My recent install procedure never used the FreeBSD release media. Instead, I have created myself USB stick distribution media (can work with CD/DVD as well, or over diskless boot), using a procedure like this: - on an up to date FreeBSD system, do make buildworld; make buildkernel - insert the USB stick, create filesystem. UFS or ZFS, doesn't matter - make installworld, make installkernel, make distribution to the mounted USB stick - fix fstab and loader.conf on the USB stick (optional) - copy over src and ports tree ro the USB stick - do in place rebuild/reinstall of the world, kernel and any packages you may need (end optional) - put the USB stick in my pocket Next time, I need to install a server on site, take the USB stick out of my pocket, plug it in one of the USB ports, boot the server, run small script (similar to that in the root-on-zfs guides), create ZFS on root and am done with it. I would use either pair of USB sticks for that, a separate set of (two) disk drives, or 'all' of the system's drives for this install, depending on the systems intended usage and hardware configuration. Typically on a multi-bay system I would do the root on a separate set of disks/USB flash in order to simplify documentation and operator training. If the system needs to be installed remotely, I would typically use rKVM (most rackmount-intended motherboards have this functionality), attaching either the prepared USB stick or it's image are virtual media and booting over that the new system. Many of these things can be done differently of course, it will depend on circumstances, but I hope the general idea is useful. Jeremy, one of the reasons I switched many systems to pure ZFS was related to the memory allocation troubles between USF and ZFS we observed for quite long time. Having pure ZFS system eliminates these issues completely. I do have still few mixed systems - only laziness and lack of (down)time prevented me from switching these to pure-ZFS too. My rationale is that if something breaks, it is likely it will break with or without ZFS on root. In either case, I would have to load FreeBSD from other media. So it does not matter from where you boot the system. One final note, on ZFS pool naming. I would traditionally name my root-on-zfs pool 'system'. However, this makes it difficult and error prone to create new zpools. Therefore, I have zpool of 'boot' for my install USB sticks and also have addopted the practice of naming the root pool after it's system's name. For example 'hostABCroot' or 'hostABCsystem'. This has never been an issue with UFS, until filesystem labels appeared and still not that many people use these. With ZFS, you cannot escape. Daniel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
Daniel Kalchev wrote: The only real trouble with USB stisks is that some motherboards behave unpredictable as to boot order, but this is improving. Why would you care about that? When running mirrored setups with ZFS on root, I'm using GPT scheme and every drive has boot partition, swap partition mirrored by gmirror and ZFS partition: = 34 625142381 ada0 GPT (298G) 34990- free - (495K) 1024128 1 freebsd-boot (64K) 1152 16777216 2 freebsd-swap (8.0G) 16778368 608364047 3 freebsd-zfs (290G) Didn't check swap-on-ZFS progress lately and when I did check it, it ended in panics. Unless by boot order you mean that it randomly tries to boot from something different than USB stick, then I suppose this could pose a problem or two :) My recent install procedure never used the FreeBSD release media. Instead, I have created myself USB stick distribution media (can work with CD/DVD as well, or over diskless boot), using a procedure like this: mfsbsd by Martin Matuška does the job well, and its simple and efficient, net-boot friendly. Jeremy, one of the reasons I switched many systems to pure ZFS was related to the memory allocation troubles between USF and ZFS we observed for quite long time. Having pure ZFS system eliminates these issues completely. I do have still few mixed systems - only laziness and lack of (down)time prevented me from switching these to pure-ZFS too. My rationale is that if something breaks, it is likely it will break with or without ZFS on root. In either case, I would have to load FreeBSD from other media. So it does not matter from where you boot the system. I switched to ZFS on root pretty much when it was for brave and/or stupid. Since about 8.1 I haven't ran into single problem caused by this and with added benefits, it's no-brainer for new setups today. While one would argue that it isn't always needed, I would argue that data integrity is always needed everywhere ;) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
On Sun, 17 Apr 2011 11:54:02 -0700 Jeremy Chadwick free...@jdc.parodius.com wrote: I don't recommend enabling ahci.ko after the OS has already been installed on an adX disk, simply because I believe the combination of GEOM+CAM+ahci may show different geometry details than GEOM+ata would. Does anything still care about CHS? In ATA-8 the fields have been marked as being obsolete. -- Bruce ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
One nice feature of ZFS I have discovered is with USB flash media. You are not typically supposed to write much to that media, but using UFS on USB sticks is awful. On contrary, when used with ZFS, the USB sticks behave much differently, because ZFS will group writes and not do silly things like issue lots of 512 byte writes. So, you may have complete development system on an USB stick, or a pair of these. The only real trouble with USB stisks is that some motherboards behave unpredictable as to boot order, but this is improving. I would second this - I have a USB 'rescue' stick with ZFS on root thats works very nicely. I also compress most of the ZFS filesystem on there (aside from the bits needed to boot) as that also improves performance due to making less reads and writes on the flash drive. It's a very nice tool to have in ones jacket pocket :-) -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
There is a nice guide in the WIKI regarding how to install your system with ZFS on root. http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ2 In any case don't configure the raid in your controller and let ZFS take care of this. Regards, 2011/4/17 Lystopad Olexandr l...@laa.zp.ua Hi! I have this hardware: smbios.system.maker=Intel Corporation smbios.system.product=S3420GP with 4G ram and 4x WD 500G drives. I try both raids in the bios, in both cases i try raid 10. I.e. I have 1Tb ar0 device. After reading http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 I try to install FreeBSD on this box, but I change ad0..ad1.. to my ar0 device. I try to have zfs on intel raid10. All commands run successfully, but after reboot I have: gptzfsboot no zfs pools located: can't boot What mistake I made? What best solution with my hardware exist? -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- George Kontostanos aisecure.net http://www.aisecure.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
On Sun, Apr 17, 2011 at 04:32:32PM +0400, Lystopad Olexandr wrote: I have this hardware: smbios.system.maker=Intel Corporation smbios.system.product=S3420GP with 4G ram and 4x WD 500G drives. I try both raids in the bios, in both cases i try raid 10. I.e. I have 1Tb ar0 device. I strongly urge you to remove use of Intel RST[1]. It's been confirmed many times over[2] that FreeBSD's support for it is broken in many regards. You are putting your data at extreme/great risk using it. Something as simple as a single-disk failure could result in the *entire* loss of your array. You will need to read the PRs listed at Wikipedia slowly, and in full to understand the nature of the problem. Do not skim them. I cannot stress the importance of this enough. This is not a joke nor is it overblown. I recommend you rely on ZFS entirely, and run your SATA controller in AHCI mode instead. My personal recommendation would be to use UFS for your root filesystem (or even gmirror) and use ZFS for the rest. With regards to AHCI mode: Most of us strongly advocate use of ahci.ko (not ataahci.ko; they differ), which does SATA-CAM translation. You also gain NCQ capability using this. Be aware your disks will appear as adaX (not a typo), and you will use camcontrol (rather than atacontrol) to maintain them. Utilities like smartmontools do work with this. Many of us (users and developers) have been using ahci.ko reliably for 1-2 years now. After reading http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 I try to install FreeBSD on this box, but I change ad0..ad1.. to my ar0 device. I try to have zfs on intel raid10. All commands run successfully, but after reboot I have: gptzfsboot no zfs pools located: can't boot What mistake I made? What best solution with my hardware exist? I imagine what you're trying to accomplish won't work given that the disk geometry and other mechanics are completely lost given use of Intel RST, and *especially* with regards to the boot sequence. Furthermore, the bootstraps you're using imply use of GPT; did you configure your setup using GPT? I'm guessing not. [1]: Known as Intel Rapid Storage Technology, Intel MatrixRAID, Intel HostRAID, Intel Embedded Server RAID Technology, Intel Matrix Storage RAID Technology, and many other terms. Intel keeps changing the term/labelling of this BIOS-level RAID, almost certainly for marketing purposes. [2]: http://en.wikipedia.org/wiki/Intel_Rapid_Storage_Technology Note that FreeBSD PRs are provided in the article. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
Hello, George Kontostanos! On Sun, Apr 17, 2011 at 04:54:34PM +0300 gkontos.m...@gmail.com wrote about Re: ZFS root on MB Intel S3420GP: There is a nice guide in the WIKI regarding how to install your system with ZFS on root. http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ2 In any case don't configure the raid in your controller and let ZFS take care of this. Thanks for answer! Is it possible to hot change disks with zfs raid on my motherboard? Regards, 2011/4/17 Lystopad Olexandr l...@laa.zp.ua Hi! I have this hardware: smbios.system.maker=Intel Corporation smbios.system.product=S3420GP with 4G ram and 4x WD 500G drives. I try both raids in the bios, in both cases i try raid 10. I.e. I have 1Tb ar0 device. After reading http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 I try to install FreeBSD on this box, but I change ad0..ad1.. to my ar0 device. I try to have zfs on intel raid10. All commands run successfully, but after reboot I have: gptzfsboot no zfs pools located: can't boot What mistake I made? What best solution with my hardware exist? -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- George Kontostanos aisecure.net http://www.aisecure.net -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
Hello, Jeremy Chadwick! On Sun, Apr 17, 2011 at 07:21:35AM -0700 free...@jdc.parodius.com wrote about Re: ZFS root on MB Intel S3420GP: On Sun, Apr 17, 2011 at 04:32:32PM +0400, Lystopad Olexandr wrote: I have this hardware: smbios.system.maker=Intel Corporation smbios.system.product=S3420GP with 4G ram and 4x WD 500G drives. I try both raids in the bios, in both cases i try raid 10. I.e. I have 1Tb ar0 device. I strongly urge you to remove use of Intel RST[1]. It's been confirmed many times over[2] that FreeBSD's support for it is broken in many regards. You are putting your data at extreme/great risk using it. Something as simple as a single-disk failure could result in the *entire* loss of your array. You will need to read the PRs listed at Wikipedia slowly, and in full to understand the nature of the problem. Do not skim them. I cannot stress the importance of this enough. This is not a joke nor is it overblown. I recommend you rely on ZFS entirely, and run your SATA controller in AHCI mode instead. My personal recommendation would be to use UFS for your root filesystem (or even gmirror) and use ZFS for the rest. Jeremy, thank you very much! I remove intel raids and move to ahci already. I install freebsd 8.2-amd64 on that box and about to make gmirror with 4 disks. :-) Is it possible to remote migrate to zfs? I have access to this server remotely, and do not have local access. This server with 4 disks, and I can do anything with 3 of disks. Now there installed 8.2-amd64 on ad4. With regards to AHCI mode: Most of us strongly advocate use of ahci.ko (not ataahci.ko; they differ), which does SATA-CAM translation. You also gain NCQ capability using this. Be aware your disks will appear as adaX (not a typo), and you will use camcontrol (rather than atacontrol) to maintain them. Utilities like smartmontools do work with this. Many of us (users and developers) have been using ahci.ko reliably for 1-2 years now. Simply add ahci_load=YES in loader.conf? Or something else? After reading http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 I try to install FreeBSD on this box, but I change ad0..ad1.. to my ar0 device. I try to have zfs on intel raid10. All commands run successfully, but after reboot I have: gptzfsboot no zfs pools located: can't boot What mistake I made? What best solution with my hardware exist? I imagine what you're trying to accomplish won't work given that the disk geometry and other mechanics are completely lost given use of Intel RST, and *especially* with regards to the boot sequence. Furthermore, the bootstraps you're using imply use of GPT; did you configure your setup using GPT? I'm guessing not. I make all steps in url in first my mail. Am I wrong? [1]: Known as Intel Rapid Storage Technology, Intel MatrixRAID, Intel HostRAID, Intel Embedded Server RAID Technology, Intel Matrix Storage RAID Technology, and many other terms. Intel keeps changing the term/labelling of this BIOS-level RAID, almost certainly for marketing purposes. :-((( I dont know... [2]: http://en.wikipedia.org/wiki/Intel_Rapid_Storage_Technology Note that FreeBSD PRs are provided in the article. -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
On Sun, Apr 17, 2011 at 08:31:35PM +0400, Lystopad Olexandr wrote: On Sun, Apr 17, 2011 at 07:21:35AM -0700 free...@jdc.parodius.com wrote about Re: ZFS root on MB Intel S3420GP: On Sun, Apr 17, 2011 at 04:32:32PM +0400, Lystopad Olexandr wrote: I have this hardware: smbios.system.maker=Intel Corporation smbios.system.product=S3420GP with 4G ram and 4x WD 500G drives. I try both raids in the bios, in both cases i try raid 10. I.e. I have 1Tb ar0 device. I strongly urge you to remove use of Intel RST[1]. It's been confirmed many times over[2] that FreeBSD's support for it is broken in many regards. You are putting your data at extreme/great risk using it. Something as simple as a single-disk failure could result in the *entire* loss of your array. You will need to read the PRs listed at Wikipedia slowly, and in full to understand the nature of the problem. Do not skim them. I cannot stress the importance of this enough. This is not a joke nor is it overblown. I recommend you rely on ZFS entirely, and run your SATA controller in AHCI mode instead. My personal recommendation would be to use UFS for your root filesystem (or even gmirror) and use ZFS for the rest. Jeremy, thank you very much! I remove intel raids and move to ahci already. I install freebsd 8.2-amd64 on that box and about to make gmirror with 4 disks. :-) Is it possible to remote migrate to zfs? I have access to this server remotely, and do not have local access. This server with 4 disks, and I can do anything with 3 of disks. Now there installed 8.2-amd64 on ad4. An honest and simple answer: I don't know. I don't use ZFS for my root filesystems on any server I manage, only as a secondary filesystem that gets used for things like /home. I do remote installations of FreeBSD on occasion (PXE boot + all access via serial console), but I don't do ZFS-on-root. With regards to AHCI mode: Most of us strongly advocate use of ahci.ko (not ataahci.ko; they differ), which does SATA-CAM translation. You also gain NCQ capability using this. Be aware your disks will appear as adaX (not a typo), and you will use camcontrol (rather than atacontrol) to maintain them. Utilities like smartmontools do work with this. Many of us (users and developers) have been using ahci.ko reliably for 1-2 years now. Simply add ahci_load=YES in loader.conf? Or something else? Correct. I tend to do the following from the very beginning of a new FreeBSD box installation, however: - Boot FreeBSD installation medium (PXE, CD, USB, whatever) - At beastie menu, escape to loader prompt and do load ahci then boot - Install FreeBSD like usual, creating slices/partitions on adaX disks like normal, etc... - When the system reboots, at the beastie prompt, make sure to escape to loader and do load ahci then boot again. - Once the system is finally up, edit /boot/loader.conf to add ahci_load=yes. I wish one could easily (read: across serial console/remote/PXE) add stuff to /boot/loader.conf *prior* to the completion of the FreeBSD installation. One can edit /etc/ttys from within sysinstall, why not /boot/loader.conf? The emergency terminal isn't accessible if you're doing things via serial console, so dropping to that to do some magic won't work. After reading http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 I try to install FreeBSD on this box, but I change ad0..ad1.. to my ar0 device. I try to have zfs on intel raid10. All commands run successfully, but after reboot I have: gptzfsboot no zfs pools located: can't boot What mistake I made? What best solution with my hardware exist? I imagine what you're trying to accomplish won't work given that the disk geometry and other mechanics are completely lost given use of Intel RST, and *especially* with regards to the boot sequence. Furthermore, the bootstraps you're using imply use of GPT; did you configure your setup using GPT? I'm guessing not. I make all steps in url in first my mail. Am I wrong? The default FreeBSD installer/labeller/partitioner doesn't use GPT. I do not use GPT myself either. If you need GPT, lots of others here can help you with that part. All I know is that you should not confuse the term GPT with gpart. :-) -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
Hello, Jeremy Chadwick! With regards to AHCI mode: Most of us strongly advocate use of ahci.ko (not ataahci.ko; they differ), which does SATA-CAM translation. You also gain NCQ capability using this. Be aware your disks will appear as adaX (not a typo), and you will use camcontrol (rather than atacontrol) to maintain them. Utilities like smartmontools do work with this. Many of us (users and developers) have been using ahci.ko reliably for 1-2 years now. Simply add ahci_load=YES in loader.conf? Or something else? Correct. I tend to do the following from the very beginning of a new FreeBSD box installation, however: - Boot FreeBSD installation medium (PXE, CD, USB, whatever) - At beastie menu, escape to loader prompt and do load ahci then boot - Install FreeBSD like usual, creating slices/partitions on adaX disks like normal, etc... - When the system reboots, at the beastie prompt, make sure to escape to loader and do load ahci then boot again. - Once the system is finally up, edit /boot/loader.conf to add ahci_load=yes. What about ahci_load=YES after freebsd install? Is it too late? Thank you for your quick answers! -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
On Sun, Apr 17, 2011 at 08:14:40PM +0400, Lystopad Olexandr wrote: On Sun, Apr 17, 2011 at 04:54:34PM +0300 gkontos.m...@gmail.com wrote about Re: ZFS root on MB Intel S3420GP: There is a nice guide in the WIKI regarding how to install your system with ZFS on root. http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ2 In any case don't configure the raid in your controller and let ZFS take care of this. Thanks for answer! Is it possible to hot change disks with zfs raid on my motherboard? This has little to do with ZFS and more to do with SATA. You will need a hot-swap backplane for this to be possible. Decent server chassis usually provide this. We use Supermicro systems with hot-swap backplanes and they work fantastic with FreeBSD + ahci.ko. If you do not have a hot-swap backplane, there is a very good chance strange things will happen when you yank power or the signal cable. I've personally tried it on a test system without a hot-swap bay. When I pulled the SATA power connector from the hard disk, I saw a blue spark near the power connector and the entire system lost power. I've blogged about hot-swapping SATA disks on FreeBSD with ZFS in use and with ahci.ko, with full kernel output and all necessary details: http://koitsu.wordpress.com/2010/07/22/freebsd-and-zfs-hot-swapping-sata-disks-with-ahci/ Please note the blog post demonstrated how I went about upgrading disks without needing to power the system off. Readers have commented how I could have done it all by using the spare bay I had, but I explicitly chose *not* to use that bay for the benefit of the readers who might not have a spare bay. Furthermore, the zpool offline steps probably aren't needed (ZFS should note the disk as UNAVAIL immediately and the array should become degraded), same with zpool online. I should really refine those procedures, or re-do the post for present-day 8.2-RELEASE. When doing administrative/maintenance tasks, I tend to do as much possible to ensure the kernel/system knows what I'm about to do. :-) If you want me to perform an actual disk failure (literally yanking a disk out of a bay while the disk is in use + part of a ZFS pool), I can do that without any worry and provide the results here. Just ask. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
On Sun, Apr 17, 2011 at 10:45:38PM +0400, Lystopad Olexandr wrote: Hello, Jeremy Chadwick! With regards to AHCI mode: Most of us strongly advocate use of ahci.ko (not ataahci.ko; they differ), which does SATA-CAM translation. You also gain NCQ capability using this. Be aware your disks will appear as adaX (not a typo), and you will use camcontrol (rather than atacontrol) to maintain them. Utilities like smartmontools do work with this. Many of us (users and developers) have been using ahci.ko reliably for 1-2 years now. Simply add ahci_load=YES in loader.conf? Or something else? Correct. I tend to do the following from the very beginning of a new FreeBSD box installation, however: - Boot FreeBSD installation medium (PXE, CD, USB, whatever) - At beastie menu, escape to loader prompt and do load ahci then boot - Install FreeBSD like usual, creating slices/partitions on adaX disks like normal, etc... - When the system reboots, at the beastie prompt, make sure to escape to loader and do load ahci then boot again. - Once the system is finally up, edit /boot/loader.conf to add ahci_load=yes. What about ahci_load=YES after freebsd install? Is it too late? I don't recommend enabling ahci.ko after the OS has already been installed on an adX disk, simply because I believe the combination of GEOM+CAM+ahci may show different geometry details than GEOM+ata would. Note: I said I believe, not I can confirm/validate. I could be completely wrong. Rather than find out ( :-) ) I tend to try and do things consistently from the very beginning. So you can try it if you want, be my guest, report back. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
Hello, Jeremy Chadwick!
What about ahci_load=YES after freebsd install? Is it too late?
I don't recommend enabling ahci.ko after the OS has already been
installed on an adX disk, simply because I believe the combination of
GEOM+CAM+ahci may show different geometry details than GEOM+ata would.
Note: I said I believe, not I can confirm/validate. I could be
completely wrong. Rather than find out ( :-) ) I tend to try and do
things consistently from the very beginning.
So you can try it if you want, be my guest, report back.
Jeremy, I ask remote boy to reinstall freebsd ot that box with load
ahci in loader prompt and successfully get adaX deveices! Thanks.
I'll try to make zfs on ada{6,8,10} devices remotely with raidz1.
thanks!
--
Lystopad Olexandr
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
Hello, Jeremy Chadwick! What about ahci_load=YES after freebsd install? Is it too late? I don't recommend enabling ahci.ko after the OS has already been installed on an adX disk, simply because I believe the combination of GEOM+CAM+ahci may show different geometry details than GEOM+ata would. Note: I said I believe, not I can confirm/validate. I could be completely wrong. Rather than find out ( :-) ) I tend to try and do things consistently from the very beginning. So you can try it if you want, be my guest, report back. Wow! Remote boy install freebsd onto another hdd, but boot server from old hdd with gmirror! In the loader prompt he write load ahci and server boots ok!!! :-) I see adaX devices! Thanks! -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
2011/4/17 Jeremy Chadwick free...@jdc.parodius.com:
On Sun, Apr 17, 2011 at 10:45:38PM +0400, Lystopad Olexandr wrote:
What about ahci_load=YES after freebsd install? Is it too late?
I don't recommend enabling ahci.ko after the OS has already been
installed on an adX disk, simply because I believe the combination of
GEOM+CAM+ahci may show different geometry details than GEOM+ata would.
Note: I said I believe, not I can confirm/validate. I could be
completely wrong. Rather than find out ( :-) ) I tend to try and do
things consistently from the very beginning.
So you can try it if you want, be my guest, report back.
I did it on a 8.1-RELEASE install: I installed the system as explained
in the wiki (http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot) and after
some months of use, I added ahci_load=YES to /boot/loader.conf.
Device names changed from ad{4,8} to ada{0,1} and everything still
worked fine, which kind of surprised me because I didn't do any
labelling to my disks (I remember having done that earlier in 8.0
times, and zfs pool reported devices were unavailable, as was the
pool, at that time).
Regards,
Romain
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
Le 17 avr. 2011 à 20:54, Jeremy Chadwick free...@jdc.parodius.com a écrit : Note: I said I believe, not I can confirm/validate. I could be completely wrong. Rather than find out ( :-) ) I tend to try and do things consistently from the very beginning. I did it a while ago, it worked. As ZFS put it's metadata at the end, the pool reconfigured itself with ada.___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
Hello, Jeremy Chadwick! On Sun, Apr 17, 2011 at 11:49:12AM -0700 free...@jdc.parodius.com wrote about Re: ZFS root on MB Intel S3420GP: On Sun, Apr 17, 2011 at 08:14:40PM +0400, Lystopad Olexandr wrote: On Sun, Apr 17, 2011 at 04:54:34PM +0300 gkontos.m...@gmail.com wrote about Re: ZFS root on MB Intel S3420GP: There is a nice guide in the WIKI regarding how to install your system with ZFS on root. http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ2 In any case don't configure the raid in your controller and let ZFS take care of this. Thanks for answer! Is it possible to hot change disks with zfs raid on my motherboard? This has little to do with ZFS and more to do with SATA. You will need a hot-swap backplane for this to be possible. Decent server chassis usually provide this. We use Supermicro systems with hot-swap backplanes and they work fantastic with FreeBSD + ahci.ko. If you do not have a hot-swap backplane, there is a very good chance strange things will happen when you yank power or the signal cable. I've personally tried it on a test system without a hot-swap bay. When I pulled the SATA power connector from the hard disk, I saw a blue spark near the power connector and the entire system lost power. I've blogged about hot-swapping SATA disks on FreeBSD with ZFS in use and with ahci.ko, with full kernel output and all necessary details: http://koitsu.wordpress.com/2010/07/22/freebsd-and-zfs-hot-swapping-sata-disks-with-ahci/ Please note the blog post demonstrated how I went about upgrading disks without needing to power the system off. Readers have commented how I could have done it all by using the spare bay I had, but I explicitly chose *not* to use that bay for the benefit of the readers who might not have a spare bay. Furthermore, the zpool offline steps probably aren't needed (ZFS should note the disk as UNAVAIL immediately and the array should become degraded), same with zpool online. I should really refine those procedures, or re-do the post for present-day 8.2-RELEASE. When doing administrative/maintenance tasks, I tend to do as much possible to ensure the kernel/system knows what I'm about to do. :-) If you want me to perform an actual disk failure (literally yanking a disk out of a bay while the disk is in use + part of a ZFS pool), I can do that without any worry and provide the results here. Just ask. Needed one reboot and change boot sequnce. Remote boy helps me. I successfully migrate remotely from gmirror (ada0) to gpt+zfs(raidz1): [root@ ~]# df -h Filesystem SizeUsed Avail Capacity Mounted on zroot905G569M904G 0%/ devfs1.0K1.0K 0B 100%/dev zroot/tmp904G 35K904G 0%/tmp zroot/usr906G2.0G904G 0%/usr zroot/usr/local 904G142M904G 0%/usr/local zroot/usr/local/pgsql904G 33K904G 0%/usr/local/pgsql zroot/usr/ports 904G 31K904G 0%/usr/ports zroot/usr/ports/distfiles904G 28K904G 0%/usr/ports/distfiles zroot/usr/src905G242M904G 0%/usr/src zroot/var904G111M904G 0%/var # zpool status pool: zroot state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scrub: resilver completed after 0h0m with 0 errors on Sun Apr 17 20:56:30 2011 config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 raidz1 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 5 12K resilvered gpt/disk2 ONLINE 0 0 0 gpt/disk3 ONLINE 0 0 0 errors: No known data errors [root@ ~]# -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
Hello, Jeremy Chadwick! On Sun, Apr 17, 2011 at 11:49:12AM -0700 free...@jdc.parodius.com wrote about Re: ZFS root on MB Intel S3420GP: On Sun, Apr 17, 2011 at 08:14:40PM +0400, Lystopad Olexandr wrote: On Sun, Apr 17, 2011 at 04:54:34PM +0300 gkontos.m...@gmail.com wrote about Re: ZFS root on MB Intel S3420GP: There is a nice guide in the WIKI regarding how to install your system with ZFS on root. http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ2 In any case don't configure the raid in your controller and let ZFS take care of this. Thanks for answer! Is it possible to hot change disks with zfs raid on my motherboard? This has little to do with ZFS and more to do with SATA. You will need a hot-swap backplane for this to be possible. Decent server chassis usually provide this. We use Supermicro systems with hot-swap backplanes and they work fantastic with FreeBSD + ahci.ko. Opps, forgot to add in my prev mail about hot swap: Apr 17 20:50:32 kernel: (ada1:ahcich1:0:0:0): lost device Apr 17 20:50:32 kernel: (ada1:ahcich1:0:0:0): Synchronize cache failed Apr 17 20:50:32 kernel: (ada1:ahcich1:0:0:0): removing device entry Apr 17 20:50:49 kernel: ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 Apr 17 20:50:49 kernel: ada1: WDC WD5003ABYX-01WERA0 01.01S01 ATA-8 SATA 2.x device Apr 17 20:50:49 kernel: ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) Apr 17 20:50:49 kernel: ada1: Command Queueing enabled Apr 17 20:50:49 kernel: ada1: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) worked fine. Thanks you, guys! -- Lystopad Olexandr ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS root on MB Intel S3420GP
On Sun, Apr 17, 2011 at 3:54 PM, George Kontostanos gkontos.m...@gmail.com wrote: There is a nice guide in the WIKI regarding how to install your system with ZFS on root. http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ2 My recipe on the last few installs have been the [1]UFSBoot guide, but instead I put /boot on a USB stick. After installation I insert a second USB stick and follow the [2]handbook to configure a gmirror over 2 of them. [1] http://wiki.freebsd.org/RootOnZFS/UFSBoot [2] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html I make sure to: newfs -L usbboot -b 65536 /dev/daXs1a and use the ufs label in /etc/fstab: tank/ zfs rw 0 0 /dev/ufs/usbboot/bootdirufs rw 0 0 This works very well so far and I can use 100% of my disk drives for ZFS without wasting so much as a slice. I'm not sure if there's any particular gotcha with this in the long run... the usbs are pretty much read-only until I do another make installkernel. Now I've also converted to using ahci.ko after Jeremys tip. I run releng_8_2 and http://people.freebsd.org/~mm/patches/zfs/v28/releng-8.2-zfsv28-20110317.patch.xz on all (4) machines so far. -- Mikael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
